The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
Software architecture in practice
Software architecture in practice
The 4+1 View Model of Architecture
IEEE Software
Product Line Based Reuse Methodology for Developing Generic ECU
ICESS '07 Proceedings of the 3rd international conference on Embedded Software and Systems
Using systematic mapping to explore software architecture knowledge
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Empirically-grounded reference architectures: a proposal
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
An aspect-oriented reference architecture for Software Engineering Environments
Journal of Systems and Software
Exploring the use of reference architectures in the development of product line artifacts
Proceedings of the 15th International Software Product Line Conference, Volume 2
Architectural description of embedded systems: a systematic review
Proceedings of the 3rd international ACM SIGSOFT symposium on Architecting Critical Systems
A reference architecture template for software-intensive embedded systems
Proceedings of the WICSA/ECSA 2012 Companion Volume
Architecting automotive product lines: Industrial practice
Science of Computer Programming
A reference architecture for cooperative driving
Journal of Systems Architecture: the EUROMICRO Journal
| Hi-index | 0.00 |
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.