Practitioners' Perspectives on Change Impact Analysis for Safety-Critical Software - A Preliminary Analysis

Safety standards prescribe change impact analysis (CIA) during evolution of safety-critical software systems. Although CIA is a fundamental activity, there is a lack of empirical studies about how it is performed in practice. We present a case study on CIA in the context of an evolving automation system, based on 14 interviews in Sweden and India. Our analysis suggests that engineers on average spend 50–100 h on CIA per year, but the effort varies considerably with the phases of projects. Also, the respondents presented different connotations to CIA and perceived the importance of CIA differently. We report the most pressing CIA challenges, and several ideas on how to support future CIA. However, we show that measuring the effect of such improvement solutions is non-trivial, as CIA is intertwined with other development activities. While this paper only reports preliminary results, our work contributes empirical insights into practical CIA.

[1]  Per Runeson,et al.  A replicated study on duplicate detection: using apache lucene to search among Android defects , 2014, ESEM '14.

[2]  Markus Borg,et al.  Enabling traceability reuse for impact analyses: A feasibility study in a safety context , 2013, 2013 7th International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE).

[3]  Hareton K. N. Leung,et al.  A survey of code‐based change impact analysis techniques , 2013, Softw. Test. Verification Reliab..

[4]  Séverine Sentilles,et al.  Towards Software Assets Origin Selection Supported by a Knowledge Repository , 2016, 2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH).

[5]  Tony Gorschek,et al.  Challenges and practices in aligning requirements with verification and validation: a case study of six companies , 2013, Empirical Software Engineering.

[6]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[7]  Anselm L. Strauss,et al.  Basics of qualitative research : techniques and procedures for developing grounded theory , 1998 .

[8]  Steffen Lehnert,et al.  A review of software change impact analysis , 2011 .

[9]  Gilbert Regan,et al.  Investigation of Traceability within a Medical Device Organization , 2013, SPICE.

[10]  Artour Klevin.  People, process and tools: A Study of Impact Analysis in a Change Process , 2012 .

[11]  Markus Borg,et al.  An Industrial Survey of Safety Evidence Change Impact Analysis Practice , 2016, IEEE Transactions on Software Engineering.

[12]  N. Hoffart.  Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory , 2000 .

[13]  Mehrdad Sabetzadeh,et al.  Evidence management for compliance of critical systems with safety standards: A survey on the state of practice , 2015, Inf. Softw. Technol..

[14]  Robert S. Arnold,et al.  Software Change Impact Analysis , 1996 .

[15]  Lefteris Angelis,et al.  An Empirical Study on Views of Importance of Change Impact Analysis Issues , 2008, IEEE Transactions on Software Engineering.

[16]  Steffen Lehnert,et al.  A taxonomy for software change impact analysis , 2011, IWPSE-EVOL '11.

[17]  Per Runeson,et al.  Changes, Evolution, and Bugs - Recommendation Systems for Issue Management , 2014, Recommendation Systems in Software Engineering.

[18]  M. Host,et al.  Comprar Case Study Research In Software Engineering: Guidelines And Examples | P. Runeson | 9781118104354 | john wiley sons , 2012 .