Abstract
ContextIn automotive, stage-gate processes have previously been the norm, with architecture created mainly during an early phase and then used to guide subsequent development phases. Current iterative and Agile development methods, where the implementation evolves continuously, changes the role of architecture. ObjectiveWe investigate how architecture evaluation can provide useful feedback during development of continuously evolving systems. MethodStarting from the Architecture Tradeoff Analysis Method (ATAM), we performed architecture evaluation, both in a national research project led by an automotive Original Equipment Manufacturer (OEM), and at the OEM, in the context of continuous development. This allows us to include the experience of several architects from different organizations over several years. Using data produced during the evaluations we perform a post-hoc analysis to derive initial findings. We then validate and refine these findings through a series of focus groups with architects and industry experts. FindingsWe propose principles of continuous evaluation and evolution of architecture, and based on these discuss a roadmap for future research. ConclusionIn iterative development settings, the needs are different from what typical architecture evaluation methods provide. Our principles show the importance of dedicated feedback-loops for continuous evolution of systems and their architecture.
Highlights
In traditional and stage-gated systems development, a software architecture is a high-level abstraction of the system that guides its implementation
Knodel and Naab (2016) provide an approach to architecture evaluation that goes beyond what Architecture Tradeoff Analysis Method (ATAM) covers, evaluating whether business drivers are agreed on, the quality of the architecture documentation, consistency between architecture and implementation, and the quality of the implementation
Two of the authors separately went through the data and wrote down their reflections. We unified these reflections to a set of principles, which served as interview guide for a series of focus group meetings
Summary
We investigate how architecture evaluation can provide useful feedback during development of continuously evolving systems. Method Starting from the Architecture Tradeoff Analysis Method (ATAM), we performed architecture evaluation, both in a national research project led by an automotive Original Equipment Manufacturer (OEM), and at the OEM, in the context of continuous development. This allows us to include the experience of several architects from different organizations over several years. Findings We propose principles of continuous evaluation and evolution of architecture, and based on these discuss a roadmap for future research
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
