No abstract

Formal verification of software systems is a challenge that is particularly important in the area of safety-critical automotive systems. Here, approaches like direct code verification are far too complicated, unless the verification is restricted to small textbook examples. Furthermore, the verification of application logic is of limited use in industrial context, unless the underlying operating system and the hardware are verified, too. This paper introduces a generic model stack, allowing the verification of all system layers as well as the concrete application models being used in the upper layers. The presented models and proofs close the gap between the correctness proof for the lower layers of car electronics developed at the Saarland University and the verification procedure for distributed applications developed at the Technische Universität München.

Automotive software is one of the most challenging fields of software engineering: it must meet real time requirements, is safety critical and distributed over multiple processors. With the increasing complexity of automotive software, as for example in the case of drive-by-wire, automated driving and driver assitents, software correctness becomes more and more a crucial issue. In order that these innovations can become reality, it is necessary to be able to guarantee software correctness.The presented work aims at verification of automotive software. For this purpose it introduces a verification approach, including a framework of verified modules which assists the verification of the actual application. Feasibility of this approach was validated on a case study that also showed how verification can be integrated into the development process.

Despite the large amount of models for different aspects of factory automation systems, many of these models target at individual and in most cases static aspects of the system, such as the geometry or its electric parts. There is a lack of suitable description methods, which integrate these individual models to a behavior model including spatial aspects and the handling of material. Furthermore, it is important that this model keeps the link to the more detailed individual models and is sufficiently formal in order to allow an automated analysis. This paper provides a solution to this problem by introducing a model which addresses both spatial structure and behavior and is based on a thorough mathematical theory. Complementary, we report on a tool realization of the modelling theory and explain how the model supports the development of mechatronic systems.

Abstract:This paper discusses a model-based approach to test software requirements in agile development processes. The use of models as central development artifact needs to be added to the portfolio of software engineering techniques, to further increase efficiency and flexibility of the development beginning already early in the requirements definition phase. Testing requirements is one of the most important techniques to give feedback and to increase the quality of the result. Therefore testing of artifacts should be introduced as early as possible, even in the requirements definition phase.

Automotive software is one of the most challenging fields of software engineering: it must meet real time requirements, is safety critical and distributed over multiple processors. With the increasing complexity of automotive software, as for example in the case of drive-by-wire, automated driving and driver assitents, software correctness becomes more and more a crucial issue. In order that these innovations can become reality, it is necessary to be able to guarantee software correctness.The presented work aims at verification of automotive software. For this purpose it introduces a verification approach, including a framework of verified modules which assists the verification of the actual application. Feasibility of this approach was validated on a case study that also showed how verification can be integrated into the development process.

Kurzfassung Moderne mechatronische Produktionssysteme sind durch ein Zusammenspiel der Disziplinen Mechanik, Elektrotechnik und Software gekennzeichnet. Vor allem in der Entwicklungsphase stellt die Integration der unterschiedlichen Fachbereiche eine Herausforderung für die Maschinenhersteller dar. Sequenziell aufgebaute Entwicklungsprozesse führen zu langen Entwicklungszeiten. Zusätzlich erschweren die mangelnde Dokumentation und Kommunikation die interdisziplinäre Zusammenarbeit zwischen den Fachabteilungen. Im Rahmen des Forschungsvorhabens AutoVIBN wurde diese Problemstellung aufgegriffen und eine Beschreibungstechnik entwickelt, die eine disziplinenunabhängige, funktionale Modellierung einer Anlage erlaubt. Ergänzende Softwarewerkzeuge unterstützen die Erstellung und frühzeitige Simulation dieser Modelle sowie die Nutzung der gesammelten Informationen für die Anlagenentwicklung.

No abstract