P005 - OMER 2001- Object-oriented Modeling of Embedded Real-Time Systems, GI-Workshops OMER-1 & OMER-2
Auflistung P005 - OMER 2001- Object-oriented Modeling of Embedded Real-Time Systems, GI-Workshops OMER-1 & OMER-2 nach Autor:in "Braun, Peter"
1 - 2 von 2
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragDevelopment of a car seat: A case study using AUTOFOCUS, DOORS, and the Validas Validator(OMER - Object-oriented Modeling of Embedded Real-Time Systems, GI-Workshops OMER-1 & OMER-2, 2001) Braun, Peter; Slotosch, OscarIn this paper we describe the modeling process and the resulting model of a typical car seat. The requirements of this seat are documented in [Chr00] which are the input of our process. We used the tools AUTOFOCUS [AF-02], DOORS [Tel02], and Validas Validator [Val02]. Starting with requirements analysis we develop first model fragments. Afterwards the graphical, component oriented approach of AUTOFOCUS is used to model the system. Requirements management and tracing techniques ensure that all requirements are implemented. The model-based core of the development process helps very much for the requirements tracing. The model fragments of the earlier phases can be updated so that tracing information is consistent. Compared to traditional requirements tracing techniques less manual interaction is needed. Beside this the test management is also done based upon the requirements. For relevant requirements test cases are specified. This is done using the AUTOFOCUS notation of Extended Event Traces (EETs) a variant of Message Sequence Charts (MSCs). Afterwards the generated code of the model is tested based upon those test cases. Further validation techniques like simulation, consistency, and determinism checks of the Validas Validator have led to the detection of inconsistencies in the model and in the specification.
- KonferenzbeitragA model-based approach for automotive software development(OMER - Object-oriented Modeling of Embedded Real-Time Systems, GI-Workshops OMER-1 & OMER-2, 2001) Braun, Peter; Rappl, MartinIntegrated model-based specification techniques facilitate the definition of seamless development processes for electronic control units (ECUs) including support for domain specific issues such as management of signals, the integration of isolated logical functions or the deployment of functions to distributed networks of ECUs. A fundamental prerequisite of such approaches is the existence of an adequate modeling notation tailored to the specific needs of the application domain together with a precise definition of its syntax and its semantics. However, although these constituents are necessary, they are not sufficient for guaranteeing an efficient development process of ECU networks. In addition, methodical support which guides the application of the modeling notation must be an integral part of a model-based approach. Therefore we propose the introduction of a so-called 'system model' which comprises all of these constituents. A major part of this system model constitutes the Automotive Modeling Language (AML), an architecture centric modeling language. The system model further comprises specifically tailored modeling notations derived from the Unified Modeling Language (UML) or the engineering tool ASCET-SD or general applicable structuring mechanisms like abstraction levels which support the definition of an AML relevant well-structured development process.