Software product lines: practices and patterns
Software product lines: practices and patterns
Building Reliable Component-Based Software Systems
Building Reliable Component-Based Software Systems
A survey on software architecture analysis methods
IEEE Transactions on Software Engineering
Establishing a Software Product Line in an Immature Domain
SPLC 2 Proceedings of the Second International Conference on Software Product Lines
Software Architecture in Practice
Software Architecture in Practice
Software technology in an automotive company: major challenges
Proceedings of the 25th International Conference on Software Engineering
An Integrated Architecture for Future Car Generations
ISORC '05 Proceedings of the Eighth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing
A taxonomy of variability realization techniques: Research Articles
Software—Practice & Experience
SEAS '05 Proceedings of the second international workshop on Software engineering for automotive systems
Generalizing a Model of Software Architecture Design from Five Industrial Approaches
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Challenges in automotive software engineering
Proceedings of the 28th international conference on Software engineering
Software Engineering for Automotive Systems: A Roadmap
FOSE '07 2007 Future of Software Engineering
Why does it take that long? Establishing Product Lines in the Automotive Domain
SPLC '07 Proceedings of the 11th International Software Product Line Conference
The Process of Software Architecting
The Process of Software Architecting
The Concept of Reference Architectures
Systems Engineering
SE '08 Proceedings of the IASTED International Conference on Software Engineering
Software architecture awareness in long-term software product evolution
Journal of Systems and Software
Lean Architecture: for Agile Software Development
Lean Architecture: for Agile Software Development
Hi-index | 0.00 |
This paper presents an in-depth view of how architects work with maintaining product line architectures at two internationally well-known automotive companies. The case study shows several interesting results. The process of managing architectural changes as well as the information the architects maintain and update is surprisingly similar between the two companies, despite that one has a strong line organisation and the other a strong project organisation. The architecting process found does not differ from what can be seen in other business domains. What does differ is that the architects studied see themselves interacting much more with other stakeholders than architects in general. The actual architectures are based on similar technology, e.g. CAN, but the network topology, S/W deployment and interfaces are totally different. The results indicate how the company's different core values influence the architects when defining and maintaining the architectures over time. One company maintains four similar architectures in parallel, each at a different stage in their respective life-cycle, while the other has a single architecture for all products since 2002. The organisational belonging of the architects in the former company has been turbulent in contrast to the latter and there is some speculation if this is correlated.