|
|||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
ABSTRACT
With the possibility to configure new cars completely individual almost no premium-class vehicle with the same configuration exists twice. As a consequence the cars differ not only in design but also have different functional features as well, which usually are provided by the interplay between a huge number of software and hardware components. Consequently the compatibility of all of these subsystems becomes a more and more pressing topic within the automotive industry.The main contribution of this paper is to provide a precise definition of the term compatibility and to show how to furnish proof of compatibility of concerning software functions in a model based development process. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
General Terms:
Collaborative Colleagues:
|
|||||||||||||||||||||||||||||||||||