Abstract
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 practice 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 asset 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 stakeholders’ 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 transition ATAM to Bosch.
The reports conclude with some suggestions for improving the ATAM itself and the training of ATAM roles.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Felix Bachmann, Len Bass, Gary Chastek, Patrick Donohoe, and Fabio Peruzzi. The architecture based design method. Technical Report CMU/SEI-2000-TR-001, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, January 2000.
M. Barbacci and W. Wood. Architecture tradeoff analyses of C4ISR products. Technical Report CMU/SEI-99-TR-014, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, January 1999.
Len Bass, Paul Clements, and Rick Kazman. Software Architecture in Practice. SEI Series in Software Engineering. Addison-Wesley, Reading, MA, 1998.
J. Bergey, M. Fisher, L. Jones, and Kazman R. Software architecture with ATAM in the DoD system acquisition context. Technical Note CMU/SEI-99-TN-012, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, September 1999.
Jan Bosch. Design & Use of Software Architectures: Adopting and evolving a product-line approach. Addison-Wesley, Reading, MA, 2000.
Paul Clements, Rick Kazman, and Mark Klein. Evaluating Software Architectures: Methods and Case Studies. SEI Series in Software Engineering. Addison-Wesley, Reading, MA, 2001. to appear in October.
Brian Gallagher. Using the architecture tradeoff analysis method to evaluate a reference architecture: A case study. Technical Report CMU/SEI-2000-TN-007, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2000.
R. Kazman, M. Barbacci, M. Klein, and S.J. Carriere. Experience with performing architecture tradeoff analysis. In Proceedings of the International Conference on Software Engineering (ICSE99), Los Angeles, CA, (May 16–22, 1999), pages 54–63. ACM, 1999.
Rick Kazman, Mark Klein, and Paul Clements. ATAM: Method for architecture evaluation. Technical Report CMU/SEI-2000-TR-004, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, August 2000.
Karl-Thomas Neumann, Hermann Kopetz, Pierre Malaterre, and Will Specks. Electronics architecture for the millennium. Automotive Engineering International, 109(7):110–114, July 2001.
David L. Parnas and David M. Weiss. Active design reviews: Principles and practices. In Proceedings of the 8th International Conference on Software Engineering, London, England, pages 132–136, Los Alamitos, CA, 1985. IEEE Computer Society Press.
SEI. ATAM reference guide (ARG). not published techreport, Software Engineering Institute (SEI), Carnegie Mellon University, Pittsburgh, PA, August 2000.
Steffen Thiel, Stefan Ferber, Thomas Fischer, Andreas Hein, and Michael Schlick. A case study in applying a product line approach for car periphery supervision systems. In In-Vehicle Software 2001, SAE 2001 World Congress, March 5–8, 2001, Cobo Center, Detroit, Michigan, volume SP-1587, pages 43–55, Warrendale, PA, 2001. Society of Automotive Engineers (SAE).
Steffen Thiel and Fabio Peruzzi. Starting a product line approach for an envisioned market: Research and experience in an industrial environment. In Patrick Donohoe, editor, Software Product Lines—Experience and Research Directions, pages 495–512. Kluwer Academic Publishers, Boston, 2000.
Jens Weber and Karlheinz Topp. Information technology — a challenge for automotive electronics. In Embedded Software Session (PC34), SAE 2001 World Congress, March 5-8, 2001, Cobo Center, Detroit, Michigan, number 2001-01-0029, Warrendale, PA, 2001. Society of Automotive Engineers (SAE).
Jianjun Zhao. Bibliography on software architecture analysis. Software Engineering Notes, 24(3):61–62, May 1999.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Ferber, S., Heidl, P., Lutz, P. (2002). Reviewing Product Line Architectures: Experience Report of ATAM in an Automotive Context. In: van der Linden, F. (eds) Software Product-Family Engineering. PFE 2001. Lecture Notes in Computer Science, vol 2290. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-47833-7_33
Download citation
DOI: https://doi.org/10.1007/3-540-47833-7_33
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-43659-1
Online ISBN: 978-3-540-47833-1
eBook Packages: Springer Book Archive