Hier finden Sie wissenschaftliche Publikationen aus den Fraunhofer-Instituten.

Process family engineering in the automotive domain

Software architecture development and case study
: Bayer, J.; Forster, T.; Giese, C.; Lehner, T.; Schaude, M.; Schnieders, A.; Sommer, P.; Weiland, J.

Fulltext urn:nbn:de:0011-n-493253 (2.5 MByte PDF)
MD5 Fingerprint: 1d55ab82235501e113175033a8da2ba3
Created on: 21.11.2006

Kaiserslautern, 2006, VII, 68 pp.
IESE-Report, 131.06/E
Reportnr.: 131.06/E
Report, Electronic Publication
Fraunhofer IESE ()
PESOA; product line engineering; meta model; Unified Modeling Language (UML); variant-rich process; feature modeling; automotive industry; process family

In the automotive industry, embedded control processes determine the most important characteristics of the developed embedded systems. The variety of product variants driven by embedded systems calls for appropriate concepts for handling the variability in embedded control processes.
In PESOA, we developed process family engineering, an approach to software product line engineering that takes into account the importance of control processes in the development of embedded control systems. In this approach control processes, as used for specifying control systems in the automotive domain, are the central artifact in a process family infrastructure. Thus, they are used to determine the scope of the process family, to differentiate the process family members, and to specify a member of the process family, and to drive code generators for the efficient assembly of product family members.
This technical report discusses the application of these concepts within the automotive domain. It presents a concrete software architecture that implements these process family engineering concepts, which are also known as the "PESOA process". This software architecture provides the foundation for the "Windshield Wiper" case study, the second main subject of this report. This case study consists in the appliance of the software architecture to a concrete example, the "Windshield Wiper". It comprises all phases of the PESOA process, from domain scoping up to concrete product instances, tested on an appropriate hardware platform.
The report finishes with a discussion of the advantages and disadvantages, i.e. the boundaries of the PESOA approach within the automotive domain.

Introduction S.1-77
1 Introduction S.1-2
2 Scoping and Domain Analysis in the Automotive Domain S.3-6
- 2.1 Concepts and Software Architecture S.3
- 2.2 Windshield Wiper Example S.4-6
Table of Contents S.7
3 Domain Design in the Automotive Domain S.7-27
- 3.1 Concepts S.7-9
- 3.2 Software Architecture of the Rational Software Modeler and Decision Modeler Tool coupling S.10-16
- 3.2.1 The Integration Solution S.10-12
- 3.2.2 Requirements S.13-14
- 3.2.3 Architecture S.15-16
- 3.3 Windshield Wiper Example S.17-27
4 Domain Implementation in the Automotive Domain S.28-35
- 4.1 Concepts and Software Architecture S.28
- 4.2 Windshield Wiper Example S.28-35
5 Application Analysis in the Automotive Domain S.36-37
- 5.1 Concepts and Software Architecture S.36
- 5.2 Windshield Wiper Example S.36-37
6 Application Design in the Automotive Domain S.38-56
- 6.1 Concepts S.38-39
- 6.2 Software Architecture S.40-45
- 6.3 Windshield Wiper Example S.46-56
7 Application Implementation in the Automotive Domain57 S.57-62
- 7.1 Concepts and Software Architecture S.57
- 7.2 Windshield Wiper Example S.58-62
8 Conclusions S.63-65
- Abbreviations S.65
References S.66