Agile Change Impact Analysis of Safety Critical Software

  • Tor Stålhane
  • Geir Kjetil Hanssen
  • Thor Myklebust
  • Børge Haugset
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8696)


Change Impact Analysis (CIA) is an important task for all who develops and maintains safety critical software. Many of the safety standards that are used in the development and use of systems with a certified safety integrity level (SIL) requires changes of such systems to be initiated by a CIA. The resulting CIA report will identify planned changes that may threaten the existing safety level. The challenge with CIA is that there are no practical guidelines on how to conduct and report such an analysis. This has led to a practice where most changes lead to extensive up-front analysis that may be costly and delay the change process itself. In this paper we propose a new strategy for CIA based on the principles of agile software development and the SafeScrum approach to establish a more efficient in-process impact analysis. We discuss several benefits of this approach, like resource savings, shorter time to initiate the change process, better prioritization and management of the change process, and others.


Safety critical systems agile software development SafeScrum change impact analysis IEC61508 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    IEC, 61508:2010 Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems (E/E/PE, or E/E/PES)Google Scholar
  2. 2.
    EN 5012X series. Railway applicationsGoogle Scholar
  3. 3.
    Lehman, M.M., Ramil, J.F.: Software evolution - Background, theory, practice. Information Processing Letters 88, 11 (2003)CrossRefGoogle Scholar
  4. 4.
    Lehman, M.M., Ramil, J.F.: An Approach to a Theory of Software Evolution. Presented at the IWPSE, Vienna, Austria (2001)Google Scholar
  5. 5.
    Myklebust, T., Stålhane, T., Hanssen, G.K., Haugset, B.: Change Impact Analysis as required by safety standards, what to do? Presented at the Probabilistic Safety Assessment & Management Conference (PSAM12), Honolulu, USA (2014)Google Scholar
  6. 6.
    Agile Manifesto (2009),
  7. 7.
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall, New Jersey (2001)Google Scholar
  8. 8.
    Takeuchi, H., Nonaka, I.: The New New Product Development Game. Harward Buisiness Review (1986)Google Scholar
  9. 9.
    Dingsoyr, T., Nerur, S., Balijepally, V., Moe, N.B.: A decade of agile methodologies: Towards explaining agile software development. Journal on Systems and Software 85, 1213–1221 (2012)CrossRefGoogle Scholar
  10. 10.
    Stålhane, T., Myklebust, T., Hanssen, G.K.: The application of Scrum IEC 61508 certifiable software. Presented at the ESREL, Helsinki, Finland (2012)Google Scholar
  11. 11.
    Myklebust, T., Stålhane, T., Hanssen, G.K., Haugset, B.: Change Impact Analysis as required by safety standards, what to do? Presented at the Probabilistic Safety Assessment & Management Conference, Hawaii, USA (2014)Google Scholar
  12. 12.
    de la Vara, J.L., Panesar-Walawege, R.K.: SafetyMet: A Metamodel for Safety Standards. In: Moreira, A., Schätz, B., Gray, J., Vallecillo, A., Clarke, P. (eds.) MODELS 2013. LNCS, vol. 8107, pp. 69–86. Springer, Heidelberg (2013)CrossRefGoogle Scholar
  13. 13.
    Li, B., Sun, X., Leung, H., Zhang, S.: A survey of code-based change impact analysis techniques. Software Testing, Verification and Reliability 23, 613–646 (2012)CrossRefGoogle Scholar
  14. 14.
    Lehnert, S.: A Review of Software Change Impact Analysis. Ilmenau University of Technology, Department of Software Systems / Process Informatics, Germany (2011)Google Scholar
  15. 15.
    Acharya, M., Robinson, B.: Practical change impact analysis based on static program slicing for industrial software systems. Presented at the 33rd International Conference on Software Engineering (ICSE 2011), Honolulu, USA (2011)Google Scholar
  16. 16.
    Kilpinen, M.S., Clarkson, P.J., Eckert, C.M.: Change Impact Analysis at the Interface of System and Embedded Software Design. Presented at the International Design Conference, Dubrovnik (2006)Google Scholar
  17. 17.
    Lindvall, M., Sandahl, K.: How Well do Experienced Software Developers Predict Software Change? Journal on Systems and Software 43, 19–27 (1998)CrossRefGoogle Scholar
  18. 18.
    Deming, W.E.: Out of the Crisis. The MIT Press, Cambridge (2000)Google Scholar
  19. 19.
    Vuori, M.: Agile Development of Safety-Critical Software.pdf. Tampere University (2011)Google Scholar
  20. 20.
    Armitage, J.: Are agile methods good for design? Interactions 11, 14–23 (2004)CrossRefGoogle Scholar
  21. 21.
    IEC, 60812: Analysis techniques for system reliability - Procedure for failure mode and effects analysis (FMEA), 2nd edn. (2006)Google Scholar
  22. 22.
    Poppendieck, M., Poppendieck, T.: Lean Software Development: An Agile Toolkit for Software Development Managers. Addison Wesley, New Jersey (2003)Google Scholar
  23. 23.
    Baskerville, R., Ramesh, B., Levine, L., Pries-Heje, J., Slaughter, S.: Is “Internet-speed” software development different? IEEE Software 20, 70–77 (2003)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Tor Stålhane
    • 1
  • Geir Kjetil Hanssen
    • 2
  • Thor Myklebust
    • 2
  • Børge Haugset
    • 2
  1. 1.Norwegian University of Science & TechnologyTrondheimNorway
  2. 2.SINTEF ICTTrondheimNorway

Personalised recommendations