Software Product Lines – An Agile Success Factor?

  • Andrea Leitner
  • Christian Kreiner
Part of the Communications in Computer and Information Science book series (CCIS, volume 172)


Introducing agility into the systems and software engineering process important, as customers demand more flexibility. For companies it is essential to react on changing requirements as well as on changing market demands.

A catalog of Agile Systems Engineering success factors also lists ”flexible product (line) architecture”. Being counterintuitive at first sight, the relation between these agile success factors and Software Product Lines (SPL) is discussed. Equally well, the concepts of SPL are mapped to a top-down Systems Engineering (SE) approach as possible SE implementation approach.

A closer look at these mappings reveals what we call an agile continuum. It represents a time line of binding times in an SPL from domain definition time to runtime. Binding of variability can occur at any of these times. It has been named a continuum, as there is no clear point in time, when the product line process is finished and the product life cycle starts. In this respect, the concepts of ”flexible product lines” (processes) and ”flexible products” form a continuous spectrum.


Success Factor Software Product Line Product Architecture Agile Method Binding Time 
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. [ABTP09]
    Babar, M.A., Tuomas, I., Pikkarainen, M.: An industrial case of exploiting product line architectures in agile software development. In: Proc. of the 13th Int. Software Product Line Conf., pp. 171–179 (2009)Google Scholar
  2. [Ado06]
    Adolph, S.: What Lessons Can the Agile Community Learn from A Maverick Fighter Pilot? In: AGILE Conference, pp. 94–99 (2006)Google Scholar
  3. [BFG+02]
    Bosch, J., Florijn, G., Greefhorst, D., Kuusela, J., Henk Obbink, J., Pohl, K.: Variability Issues in Software Product Lines. In: PFE 2001: Revised Papers from the 4th International Workshop on Software Product-Family Engineering, London, UK, pp. 13–21. Springer, Heidelberg (2002)Google Scholar
  4. [CMC05]
    Clements, P.C., McGregor, J.D., Cohen, S.G.: The Structured Intuitive Model for Product Line Economics (SIMPLE). Technical report, SEI at CMU (February 2005)Google Scholar
  5. [CN02]
    Clements, P., Northrop, L.M.: Software Product Lines: Practices and Patterns. Addison-Wesley, Reading (2002)Google Scholar
  6. [EGE10]
    Ehsani, M., Gao, Y., Emadi, A.: Modern Electric, Hybrid Electric, and Fuel Cell Vehicles: Fundamentals, Theory, and Design, 2nd edn. CRC Press, Boca Raton (2010)Google Scholar
  7. [GBS01]
    Van Gurp, J., Bosch, J., Svahnberg, M.: On the Notion of Variability in Software Product Lines. In: WICSA 2001: Proceedings of the Working IEEE/IFIP Conference on Software Architecture, page 45. IEEE Computer Society, Washington, DC, USA (2001)Google Scholar
  8. [Gil05]
    Gilb, T.: Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Butterworth-Heinemann, Newton (2005)Google Scholar
  9. [Hal]
    Product Line Hall of Fame, (05.07.2010)
  10. [HdW05]
    Haberfellner, R., de Weck, O.: Agile Systems Engineering Versus Agile System engineering. In: Proc. 15th Ann. Intl. Symposium of the Intl. Council on Systems Engineering, INCOSE (2005)Google Scholar
  11. [HF08]
    Hanssen, G.K., Fægri, T.E.: Process fusion: An industrial case study on agile software product line engineering. J. Syst. Softw. 81, 843–854 (2008)CrossRefGoogle Scholar
  12. [HKNM10]
    Hoda, R., Kruchten, P., Noble, J., Marshall, S.: Agility in context. In: ACM Int. Conf. on Object Oriented Programming Systems Languages and Applications, OOPSLA 2010, pp. 74–88. ACM, New York (2010)Google Scholar
  13. [INC04]
    Systems Engineering Handbook. Technical report, Technical Board International Council on Systems Engineering, INCOSE (2004)Google Scholar
  14. [Kru03]
    Krueger, C.W.: Towards a Taxonomy for Software Product Lines. In: van der Linden, F.J. (ed.) PFE 2003. LNCS, vol. 3014, pp. 323–331. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  15. [LK10]
    Leitner, A., Kreiner, C.: Managing ERP Configuration Variants: An Experience Report. In: Proc. of the 1st Workshop on Knowledge Oriented Product Line Engineering (2010)Google Scholar
  16. [Man10]
    Manifesto for Agile Software Development (2010),
  17. [Mau09]
  18. [McG08]
    McGregor, J.D.: Agile Software Product Lines, Deconstructed. Journal of Object Technology 7(8), 7–19 (2008)CrossRefGoogle Scholar
  19. [NdAM08]
    Nobrega, J.P., de Almeida, E.S., Meira, S.: InCoME: Integrated Cost Model for Product Line Engineering. In: Software Engineering and Advanced Applications, Euromicro Conf., pp. 27–34 (2008)Google Scholar
  20. [SKS+10]
    Stelzmann, E., Kreiner, C., Spork, G., Messnarz, R., Koenig, F.: Agility meets systems engineering: A catalogue of success factors from industry practice. In: Systems, Software and Services Process Improvement. CCIS, vol. 99, pp. 245–256. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  21. [SM89]
    Shigley, J.E., Mischke, C.R.: Mechanical Engineering Design, 5th edn. McGraw-Hill, New York (1989)Google Scholar
  22. [vdLSR07]
    van der Linden, F.J., Schmid, K., Rommes, E.: Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering. Springer, Berlin (2007)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Andrea Leitner
    • 1
  • Christian Kreiner
    • 1
  1. 1.Institute for Technical InformaticsGraz University of TechnologyGrazAustria

Personalised recommendations