http://dl.gi.de/handle/20.500.12116/30819 Tue, 21 Jul 2026 13:29:47 GMT 2026-07-21T13:29:47Z http://dl.gi.de:80/bitstream/id/0c15ff33-fe7c-47c5-95ce-a34f829cbd5b/ http://dl.gi.de/handle/20.500.12116/30819 http://dl.gi.de/handle/20.500.12116/30834 UML metamodel extensions for specifying functional requirements of mechatronic components in vehicles Petersen, Jörg; Bertram, Torsten; Lapp, Andreas; Knorr, Kathrin; Torre Flores, Pio; Schirmer, Jürgen; Kraft, Dieter; Hermsen, Wolfgang Hofmann, Peter P.; Schürr, Andy Increasing demands concerning safety, economic impact, fuel consumption and comfort result in a growing utilisation of mechatronic components and networking of up to now widely independent systems in vehicles. The development of networked electronic control units (ECU) as the most frequent mechatronic applications contains three core aspects: the development of the (control) functions itself, and their realisation in hardware and software as embedded systems. A co-ordinated, systematic and concurrent function, hardware and software development process including co-engineering and simulation environments requires a detailed specification in early development phases and a formalised description to improve the clearness of these specifications, decrease contradictions and increase information density. The Unified Modeling Language (UML) offers such a formalised description facility. A UML metamodel will be presented used for a mapping of automotive domain specific functional models onto UML models including constraints formalised by Object Constraint Language (OCL) expressions. The model also comprises the specification of functional interfaces together with a hierarchical decomposition of the system. The UML automotive domain models are basis for the system design and architecture and support aspects like re-use, exchangeability, scalability and distributed development. Particular importance is attached to the implementation of the UML model in a commercial tool together with a prototype checker of OCL expressions realised in Java. Mon, 01 Jan 2001 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/30834 2001-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/30832 Development of a car seat: A case study using AUTOFOCUS, DOORS, and the Validas Validator Braun, Peter; Slotosch, Oscar Hofmann, Peter P.; Schürr, Andy In 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. Mon, 01 Jan 2001 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/30832 2001-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/30833 Model-based design of ECU software – A component-based approach Freund, Ulrich; Burst, Alexander Hofmann, Peter P.; Schürr, Andy This paper shows how architecture description languages can be tailored to the design of embedded automotive control software. Furthermore, graphical modeling means are put in an object oriented programming context using classes, attributes and methods. After a survey of typical automotive requirements, an example from a vehicle’s body electronics software shows the component based architecture. Introducing the concepts of component and connector refinement provide means to close the gap between system theoretical modeling and resource constraint embedded programming practice, leading to an object-oriented behavior description on the one hand and to a common middleware on the other. Mon, 01 Jan 2001 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/30833 2001-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/30835 A model-based approach for automotive software development Braun, Peter; Rappl, Martin Hofmann, Peter P.; Schürr, Andy Integrated 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. Mon, 01 Jan 2001 00:00:00 GMT http://dl.gi.de/handle/20.500.12116/30835 2001-01-01T00:00:00Z