Impact of Application Lifecycle Management — A Case Study

  • J. Kääriäinen
  • A. Välimäki


Lifecycle management provides a generic frame of reference for systems and methods that are needed for managing all product related data during the product’s lifecycle. This paper reports experiences from a case study performed in the automation industry. The goal was to study the concept of Application Lifecycle Management (ALM) and gather and analyse first experiences when a company is moving towards distributed application lifecycle management. The results show that several benefits were gained when introducing an ALM solution in a case company. This research also produced a first version of an ALM framework that can be used to support practical ALM improvement efforts. In this case, the experiences show that lifecycle activity should manage artefacts produced in different stages in a project lifecycle and keep all activities in synchronised. The challenge resides in how to generate efficient company-specific implementations of ALM for complicated real-life situations.


Industrial case studies and demonstrators of interoperability Interoperability best practice and success stories Tools for interoperability 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Sääksvuori A, Immonen A, (2004) Product Lifecycle Management, Springer-Verlag BerlinGoogle Scholar
  2. [2]
    Doyle C, (2007) The importance of ALM for aerospace and defence (A&D), Embedded System Engineering (ESE magazine), Vol. 15, Issue 5, 28–29Google Scholar
  3. [3]
    Schwaber C, (2006) The Changing Face of Application Life-Cycle Management, Forrester Research Inc., White paper, August 18Google Scholar
  4. [4]
    Doyle C, Lloyd R, (2007) Application lifecycle management in embedded systems engineering, Embedded System Engineering (ESE magazine), Vol. 15, Issue 2, 24–25Google Scholar
  5. [5]
    Gotel O, Finkelstein A, (1994) An Analysis of the Requirements Traceability Problem, Proceedings of the First International Conference on Requirements Engineering, 94–101Google Scholar
  6. [6]
    Ramesh B, Dhar V, (1992) Supporting systems development by capturing deliberations during requirements engineering, IEEE Transactions on Software Engineering, Vol. 18, No. 6, 498–510CrossRefGoogle Scholar
  7. [7]
    Ramesh B, Jarke M, (2001) Toward Reference Models for Requirements Traceability. IEEE Transactions on Software Engineering, Vol. 27, No. 1, 58–93CrossRefGoogle Scholar
  8. [8]
    Weatherall B, (2007) Application Lifecycle Management-A Look Back, CM Journal, CM Crossroads — The configuration management community, January 2007, (available 18.10.2007)Google Scholar
  9. [9]
    Kolawa A, (2006) The Future of ALM and CM, CM Journal, CM Crossroads — The configuration management community, January 2006. (available 18.10.2007)Google Scholar
  10. [10]
    Estublier J, Leblang D, van der Hoek A, Conradi R, Clemm G, Tichy W, Wiborg-Weber D, (2005) Impact of software engineering research on the practice of software configuration management. ACM Transactions on Software Engineering and Methodology (TOSEM). ACM Press, New York, USA, Vol. 14, Issue 4, 383–430Google Scholar
  11. [11]
    Heinonen S, Kääriäinen J, Takalo J, (2007) Challenges in Collaboration: Tool Chain Enables Transparency Beyond Partner Borders, In proceedings of 3rd International Conference Interoperability for Enterprise Software and Applications 2007, Funchal, PortugalGoogle Scholar
  12. [12]
    Yang Z, Jiang M, (2007) Using Eclipse as a Tool-Integration Platform for Software Development, IEEE Software, Vol. 24, Issue 2, 87–89CrossRefGoogle Scholar
  13. [13]
    Shaw K, (2007) Application lifecycle management for the enterprise, Serena Software, White Paper, April 2007, (available 18.10.2007)Google Scholar
  14. [14]
    Eclipse web-pages, (available 18.10.2007)Google Scholar
  15. [15]
    Buckley F, (1996) Implementing configuration management: hardware, software, and firmware, IEEE Computer Society Press, Los AlamitosGoogle Scholar
  16. [16]
    Leon A, (2000) A Guide to software configuration management, Artech House, BostonzbMATHGoogle Scholar
  17. [17]
    Crnkovic I, Dahlqvist AP, Svensson D, (2001) Complex systems development requirements-PDM and SCM integration, Asia-Pacific Conference on Quality SoftwareGoogle Scholar
  18. [18]
    Välimäki A, Kääriäinen J, (2007) Product Managers’ Requirement Management Practices As Patterns in Distributed Development, 8th International PROFES (Product Focused Software and Process Improvement) conference, LatviaGoogle Scholar
  19. [19]
    Guckenheimer S, (2006) Software Engineering with Microsoft Visual Studio Team System, Addison-WesleyGoogle Scholar

Copyright information

© Springer-Verlag London Limited 2008

Authors and Affiliations

  • J. Kääriäinen
    • 1
  • A. Välimäki
    • 2
  1. 1.Technical Research Centre of FinlandVTTOuluFinland
  2. 2.Metso Automation IncTampereFinland

Personalised recommendations