A Concrete Method for Developing and Applying Product Line Architectures

  • Michalis Anastasopoulos
  • Colin Atkinson
  • Dirk Muthig
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2591)


Software development organizations are often deterred from introducing product line architectures by the lack of simple, ready-to-use methods for developing and applying them. The well-known, published product-line-engineering methods tend to focus on the early stages of the software life cycle and address product line issues at a high-level of abstraction. Connecting product-line concepts with established implementation technologies is thus largely left to the user.

This paper introduces a method, known as the KobrA method, which addresses this problem by enabling product line concerns to be coupled with regular (nonproduct line) architectural artifacts, and thus introduced incrementally. By explaining how the method can be understood as a concrete instantiation of the well-established PuLSE-DSSA product-line architecture approach, the paper clarifies the product line features of the KobrA method and illustrates how they can be used in tandem with established, general-purpose product line methods.


Unify Modeling Language Class Diagram Software Product Line Context Realization Model Drive Architecture 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Weiss, D. M. and Lai, C. T. R., Software Product Line Engineering: A family Based Software Engineering Process, Addison-Wesley, 1999.Google Scholar
  2. [2]
    K. Kang, S. Cohen, J. Hess, W. Nowak and S. Peterson, Feature-oriented Domain Analysis (FODA), Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, November 1990Google Scholar
  3. [3]
    Bayer, J., Flege, O., Knauber, P., Laqua, R., Muthig, D., Schmid. K., Widen, T, and Debaud, J.-M., PuLSE: A Methodology to develop Software Product Lines, Proceedings of the Symposium on Software Reuse(SSR’99), May 1999Google Scholar
  4. [4]
    Bosch, J. Design and Use of Software Architectures. Addison-Wesley, 2000.Google Scholar
  5. [5]
    C. Atkinson, J. Bayer, C. Bunse, E. Kamsties, O. Laitenberger, R. Laqua, D. Muthig, B. Paech, J. Wüst, J. Zettel. Component-Based Product-Line Engineering with UML. Addison-Wesley, 2001Google Scholar
  6. [6]
    M. Anastasopoulos, J. Bayer, O. Flege, and C. Gacek. A Process for Product Line Architecture Creation and Evaluation: PuLSE-DSSA V2.0, Technical Report, Fraunhofer IESE, 2000Google Scholar
  7. [7] Szyperski, C., Component Software: Beyond Object-Oriented Programming, Addison-Wesley 1999.Google Scholar
  8. [8]
    Executive Overview: Model Driven Architecture, Object Management Group, 2001
  9. [9]
    Unified Modeling Language Specification, Version 1.4, Object Management Group, 2000.Google Scholar
  10. [10]
    F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad and M. Stal, Pattern-Oriented Software Architecture-A System of Patterns, John Wiley & Sons, July 1996.Google Scholar
  11. [11]
    M. Shaw, and D. Garlan, Software Architecture: Perspective on an Emerging Discipline, Prentice-Hall, 1996Google Scholar
  12. [12]
    John Carroll, Making Use, Scenario-Based Design of Human-Computer Interactions, Cambridge: MIT Press, 2000Google Scholar
  13. [13]
    Len Bass, Mark Klein, Felix Bachmann, “Quality Attribute Design Primitives and the Attribute Driven Design Method.” 4th Conference on Product Family Engineering. Bilbao, Spain, October 2001.Google Scholar
  14. [14]
    Rick Kazman, Mark Klein, Paul Clements, ATAM: Method for Architecture Evaluation, Technical Report, CMU/SEI-2000-TR-004, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA,August 2000Google Scholar
  15. [16]
    Felix Bachmann, Len Bass, Gary Chastek, Patrick Donohoe, Fabio Peruzzi, The Architecture Based Design Method, Technical Report CMU/SEI-2000-TR-001, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, January 2000Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2003

Authors and Affiliations

  • Michalis Anastasopoulos
    • 1
  • Colin Atkinson
    • 1
  • Dirk Muthig
    • 1
  1. 1.Fraunhofer Institute Experimental Software Engineering (IESE)KaiserslauternGermany

Personalised recommendations