Software architecture in practice
Software architecture in practice
Experience with performing architecture tradeoff analysis
Proceedings of the 21st international conference on Software engineering
Active design reviews: principles and practices
ICSE '85 Proceedings of the 8th international conference on Software engineering
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
Experiences in assessing product family software architecture for evolution
Proceedings of the 24th International Conference on Software Engineering
A holistic architecture assessment method for software product lines
Information and Software Technology
Experiences from scenario-based architecture evaluations with ATAM
ECSA'10 Proceedings of the 4th European conference on Software architecture
Product-line architecture: new issues for evaluation
SPLC'05 Proceedings of the 9th international conference on Software Product Lines
| Hi-index | 0.00 |
Product lines are an important system development paradigm in the automotive industry to amortize costs beyond a single product. The paradigm is well established in the mechanical and electrical engineering practise in automotive companies like Bosch. As software is covering more and more functionality in cars, software product lines are getting more attention. The architecture of a software-intensive system is a key asser in developing a software product line.The Architecture Trade-off Analysis Method (ATAM) developed by the SEI assesses the quality of software architecture early in the development process. ATAM is therefore a useful review technique to guarantee important quality attributes of every single product created with the product line architecture later on. This article reports about the experience Bosch made in using ATAM in two cases.Benefits in using ATAM are not only the review results itself but a better documented and better understood architecture. We experienced the most important benefit of ATAM is the rising stakeholder's awareness of architectural decisions, tradeoffs, and risks. It illuminates the software architecture better than any written documentation.Bosch employees are trained in the evaluation roles in order to trasition ATAM to Bosch.The reports conclude with some suggestions fo improving the ATAM itself and the training of ATAM roles.