Skip to main content

Lund University Publications

LUND UNIVERSITY LIBRARIES

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

Eklund, Ulrik ; Askerdal, Örjan ; Granholm, Johan LU orcid ; Alminger, Anders and Axelsson, Jakob LU (2005) 2nd International Workshop on Software Engineering for Automotive Systems, SEAS 2005
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.... (More)

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.

(Less)
Please use this url to cite or link to this publication:
author
; ; ; and
publishing date
type
Chapter in Book/Report/Conference proceeding
publication status
published
subject
keywords
Automotive electronics and software, Non-functional requirements, Product line architecture, Reference architecture
host publication
SEAS 2005 - Proceedings of the 2nd International Workshop on Software Engineering for Automotive Systems
publisher
Association for Computing Machinery (ACM)
conference name
2nd International Workshop on Software Engineering for Automotive Systems, SEAS 2005
conference location
St. Louis, United States
conference dates
2005-05-21
external identifiers
  • scopus:84876098612
ISBN
1595931287
9781595931283
DOI
10.1145/1083190.1083195
language
English
LU publication?
no
id
43286609-56ae-4432-a732-16d571add236
date added to LUP
2019-06-21 11:22:05
date last changed
2023-08-30 12:11:28
@inproceedings{43286609-56ae-4432-a732-16d571add236,
  abstract     = {{<p>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.</p>}},
  author       = {{Eklund, Ulrik and Askerdal, Örjan and Granholm, Johan and Alminger, Anders and Axelsson, Jakob}},
  booktitle    = {{SEAS 2005 - Proceedings of the 2nd International Workshop on Software Engineering for Automotive Systems}},
  isbn         = {{1595931287}},
  keywords     = {{Automotive electronics and software; Non-functional requirements; Product line architecture; Reference architecture}},
  language     = {{eng}},
  month        = {{05}},
  publisher    = {{Association for Computing Machinery (ACM)}},
  title        = {{Experience of introducing reference architectures in the development of automotive electronic systems}},
  url          = {{http://dx.doi.org/10.1145/1083190.1083195}},
  doi          = {{10.1145/1083190.1083195}},
  year         = {{2005}},
}