Experience of introducing reference architectures in the development of automotive electronic systems

ABSTRACT

The requirements on increasing functionality, quality, and, customisation, while reducing cost has lead to the introduction of an architecture centred development process for electronic systems at Volvo Cars. This process enables better control of system integration and achieving non-functional requirements, such as reusability, understandability, etc. The result of the process is a reference architecture that includes strategies for implementing the balanced requirements, architectural views that provide means for reasoning about all the concerns of all stakeholders, and a top-level design of the architecturally significant parts. The reference architecture guides the design of several projects, and thus, cost is optimised accordingly. The main contribution of this paper is that we present experiences from introducing the architecture centred process. The main conclusions are that disseminating and maintaining the reference architecture actually require more resources than developing it. Furthermore, experience shows it is difficult to create an architecture that enables a lot of different variants that is also strategically useable in the long term.

REFERENCES

• 1: AUTOSAR, URL: <u>http://www.autosar.org</u>
• 2: Len Bass , Paul Clements , Rick Kazman, Software architecture in practice, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1998
• 3: Frederick P. Brooks, Jr., The mythical man-month (anniversary ed.), Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 4: Brownsword, L. and Clements, P., "A Case Study in Successful Product Line Development", Technical Report, CMU/SEI-96-TR-016, 1996.
• 5: Casparsson, L., Rajnák, A., Tindell, K. and Malmberg, P., "Volcano a revolution in on-board communications", Volvo Technology Report, 1, 1998.
• 6: Heinecke, H. et al., "AUTomotive Open System ARchitecture - An Industry-Wide Initiative to Manage the Complexity of Emerging Automotive E/E Architectures", Proc. Convergence, SAE-2004-21-0042, 2004.
• 7: "IEEE Recommended Practice for Architectural Description of Software-Intensive Systems". IEEE Std. 1471-2000.
• 8: Philippe Kruchten, The 4+1 View Model of Architecture, IEEE Software, v.12 n.6, p.42-50, November 1995 [doi>10.1109/52.469759]
• 9: Melin, K., "Volvo S80: Electrical system of the future" Volvo Technology Report, 1, 1998.
• 10: Reichart, G. and Haneberg, M., "Key Drivers for a Future System Architecture in Vehicles", Proc. Convergence, SAE-2004-21-0025, 2004.
• 11: Rhodin, M., Ljungberg, L., and Eklund., U., "A Method for Model Based Automotive Software Development", Proc. Work in Progress and Industrial Experience Sessions, pp. 15--18, 12th Euromicro Conference on Real-Time Systems, Stockholm, 2002.

INDEX TERMS

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

General Terms:
Design, Documentation, Economics, Management, Measurement, Performance, Reliability

Keywords:
automotive electronics and software, non-functional requirements, product line architecture, reference architecture