Reuse of software in distributed embedded automotive systems

ABSTRACT

Until recently, in the automotive industry, reuse of software has entirely been a typical activity of suppliers. They try to reduce the increasing software development costs that stem from rising complexity and size of software in the modern automobile. Lately, also the automotive manufacturers began to develop specific software with competitive relevance. Now they have to deal with the problem of reuse, too. Nevertheless, there is a difference between the manufacturers' and the suppliers' point of view because the manufacturers have to integrate the networked hardware components to one automotive system. Therefore, the manufacturers have to deal with additional problems compared to the supplier. At the beginning of this paper, the specific problems of reuse of software in the automotive domain are shown from the perspective of automotive manufacturers. After that, a framework is proposed to deal with these problems. Moreover, the application of this framework is shown in a realistic application example.

REFERENCES

• 1: AUTOSAR. Automotive Open System Architecture. http://www.autosar.de, Apr. 2004.
• 2: Bundesministerium des Inneren. Entwicklungsstandard für IT-Systeme des Bundes. Vorgehensmodell. Kurzbeschreibung. Bonn, 1997.
• 3: CAN in Automation. Controller Area Network (CAN) - an overview. http://www.can-cia.de/can/, Mar. 2003.
• 4: Carnegie Mellon Software Engineering Institute. Software Product Lines. http:// www.sei.cmu.edu/plp/product_line_overview.html, Feb. 2003.
• 5: P. Clemens and L. Northop. Software Product Lines - Practices and Patterns. Addison-Wesley, Boston, 2002.
• 6: DSpace. TargetLink -- Automatic Production Code Generation for Target Implementation. http://www.dspace.deU/ww/en/pub/products/targetimp.htm, Apr. 2004.
• 7: EAST-EEA. Embedded Electronic Architecture. http://www.east-eea.net, Apr. 2004.
• 8: B. Hardung, M. Wernicke, A. Krüger, G. Wagner, and F. Wohlgemuth. Development Process for Networked Electronic Systems. VDI-Berichte 1789, VDI Congress Electronic Systems for Vehicles, Baden-Baden, pages 77--97, Sept. 2003.
• 9: Jochen Hartmann , Shihong Huang , Scott Tilley, Documenting software systems with views II: an integrated approach based on XML, Proceedings of the 19th annual international conference on Computer documentation, October 21-24, 2001, Sante Fe, New Mexico, USA [doi>10.1145/501516.501571]
• 10: H. Heinecke, A. Schedl, J. Berwanger, M. Peller, V. Nieten, R. Belschner, B. Hedenetz, P. Lohrmann, and C. Bracklo. FlexRay -- ein Kommunikationssystem für das Automobil der Zukunft. Elektronik Automotive, pages 36--45, Sept. 2002.
• 11: HIS -- Hersteller Initiative Software, Volkswagen AG. HIS / Vector CAN-Driver Specification V1.0. http://www.automotive-his.de, Aug. 2003.
• 12: Raimund Kirner , Roland Lang , Gerald Freiberger , Peter Puschner, Fully Automatic Worst-Case Execution Time Analysis for Matlab/Simulink Models, Proceedings of the 14th Euromicro Conference on Real-Time Systems, p.31, June 19-21, 2002
• 13: A. Krüger, G. Wagner, N. Ehmke, and S. Prokop. Economic Considerations and Business Models for Automotive Standard Software Components. VDI-Berichte 1789, VDI Congress Electronic Systems for Vehicles, Baden-Baden, pages 1057--1071, Sept. 2003.
• 14: LIN Consortium. LIN Specification Package Revision 2.0. http://www.lin-subbus.org, Sept. 2003.
• 15: MathWorks. MATLAB and Simulink for Technical Computing. http://www.mathworks.com, Apr. 2004.
• 16: Mercer Management Consulting and Hypovereinsbank. Studie, Automobiltechnologie 2010. München, Aug. 2001.
• 17: MOST Cooperation. MOST Specification Rev., 2.2. http://www.mostnet.de/downloads/Specifications/, Nov. 2002.
• 18: MSR. Development of Methods, Definition of Standards, Subsequent Implementation. http://www.msr-wg.de, Apr. 2004.
• 19: OSEK/VDX. Communication Version 3.0.1. http://www.osek-vdx.org/mirror/com301.pdf, 2003.
• 20: OSEK/VDX. Operating System Version 2.2.1. http://www.osek-vdx.org/mirror/os221.pdf, 2003.
• 21: C. Raith, F. Gesele, W. Dick, and M. Miegler. Audi Dynamic Steering as an Example of Distributed Joint Development. VDI-Berichte 1789, VDI Congress Electronic Systems for Vehicles, Baden-Baden, pages 185--205, Sept. 2003.
• 22: J. Schuller and M. Haneberg. Funktionale Analyse -- Eine Methode für den Entwurf hochvernetzter Systeme. Vortrag, VDI-Mechatronik-Konferenz, Fulda, May 2003.
• 23: F. Simonot-Lion. In Car Embedded Electronic Architectures: How to Ensure their Safety. 5th IFAC International Conference on Fieldbus Systems and their Applications - FeT'2003, Aveiro, Portugal, pages 1--8, July 2003.
• 24: Telelogic. Telelogic Doors Overview. http://www.telelogic.com/products/doorsers/doors/, Apr. 2004.
• 25: Steffen Thiel , Andreas Hein, Modeling and Using Product Line Variability in Automotive Systems, IEEE Software, v.19 n.4, p.66-72, July 2002 [doi>10.1109/MS.2002.1020289]
• 26: T. Thurner, J. Eisenmann, U. Freund, R. Geiger, M. Haneberg, U. Virnich, and S. Voget. The EAST-EEA project -- A Middleware Based Software Architecture for Networked Electronic Control Units in Vehicles. VDI-Berichte 1789, VDI Congress Electronic Systems for Vehicles, Baden-Baden, pages 545--563, Sept. 2003.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.13 Reusable Software
            Subjects: Reuse models

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Domain-specific architectures

Keywords:
architecture, automotive, product line, reuse, software