A Risk Model of Requirements Change Impact Analysis

Software systems are critical assets to organisations as they support important business processes and workflow. To maintain the value of these assets, the requirements of software systems must evolve whenever there are changes in business needs. A key problem to organisations is implementing requirements change to the existing software systems. Such initiatives need proper analyses so that their effects could be determined before resources are spent. Impact analysis is therefore an important step in requirements change management. As a project, any change implementation involves risks. It is thus necessary for impact analysis to consider risk factors for implementing requirements change. However to date, the risk factors concerning requirement change are not much explored. This paper aims to identify the risk factors for implementing requirements change. The risk factors were identified through two qualitative approaches, namely a review of related work and a focus group study. The former involved fifty published articles and the latter concerned five domain experts. The collected risk factors from both studies were analysed by using content analysis. The risk factors form a risk model for analysing impacts of implementing requirements change. The model helps practitioners to assess the viability of requirements change requests.

[1]  Klaus Krippendorff,et al.  Content Analysis: An Introduction to Its Methodology , 1980 .

[2]  Nadeem Ehsan,et al.  A methodology to manage the changing requirements of a software project , 2010, 2010 International Conference on Computer Information Systems and Industrial Management Applications (CISIM).

[3]  Jeffrey C. Carver,et al.  Change Risk Assessment: Understanding Risks Involved in Changing Software Requirements , 2006, Software Engineering Research and Practice.

[4]  Norman F. Schneidewind.  Predicting Risk as a Function of Risk Factors , 2005, SEW.

[5]  Doo-Hwan Bae,et al.  An approach to analyzing the software process change impact using process slicing and simulation , 2011, J. Syst. Softw..

[6]  Say Wei Foo,et al.  Software risk assessment model , 2000, Proceedings of the 2000 IEEE International Conference on Management of Innovation and Technology. ICMIT 2000. 'Management in the 21st Century' (Cat. No.00EX457).

[7]  Claudio Bartolini,et al.  A decision support tool to optimize scheduling of IT changes , 2007, 2007 10th IFIP/IEEE International Symposium on Integrated Network Management.

[8]  James W. Fawcett,et al.  New change impact factor estimation in software development , 2012 .

[9]  KeilMark,et al.  Identifying Software Project Risks , 2001 .

[10]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[11]  Susan P. Williams,et al.  Requirements Volatility and Its Impact on Change Effort: Evidence-based Research in Software Development Projects Return to Published Papers , 2006 .

[12]  Lisandro Zambenedetti Granville,et al.  Improving IT Change Management Processes with Automated Risk Assessment , 2009, DSOM.

[13]  Bee Bee Chua.  Rework Requirement Changes in Software Maintenance , 2010, 2010 Fifth International Conference on Software Engineering Advances.

[14]  Sun-Jen Huang,et al.  An empirical analysis of risk components and performance on software projects , 2007, J. Syst. Softw..

[15]  Mohamed E. Fayad.  Software Maintenance , 2005, IEEE Softw..

[16]  H. O. Ali,et al.  Identifying challenges of change impact analysis for software projects , 2012, 2012 International Conference on Innovation Management and Technology Research.

[17]  Nadeem Ehsan,et al.  An investigation of changing requirements with respect to development phases of a software project , 2010, 2010 International Conference on Computer Information Systems and Industrial Management Applications (CISIM).

[18]  Zhu Jiayi,et al.  The Requirements Change Analysis for Different Level Users , 2008, 2008 International Symposium on Intelligent Information Technology Application Workshops.

[19]  Penny Grubb,et al.  Software maintenance , 1996 .

[20]  Haruhiko Kaiya,et al.  Exploring How to Support Software Revision in Software Non-intensive Projects Using Existing Techniques , 2011, 2011 IEEE 35th Annual Computer Software and Applications Conference Workshops.

[21]  Susan P. Williams,et al.  Requirements volatility & its impact on change effort: Evidence based research n software development projects , 2006 .

[22]  George Stark.  An Examination of the Effects of Requirements Changes on Software Releases , 1998 .

[23]  Laura Lehtola,et al.  The Focus Group Method as an Empirical Tool in Software Engineering , 2008, Guide to Advanced Empirical Software Engineering.

[24]  Robert Lagerström,et al.  Identifying factors affecting software development cost and productivity , 2011, Software Quality Journal.

[25]  Norman F. Schneidewind,et al.  Investigation of the risk to software reliability and maintainability of requirements changes , 2001, Proceedings IEEE International Conference on Software Maintenance. ICSM 2001.

[26]  Johan F. Hoorn,et al.  Requirements change: Fears dictate the must haves; desires the won't haves , 2007, J. Syst. Softw..

[27]  Leonard J. Bass,et al.  Factors Influencing Industrial Practices of Software Architecture Evaluation: An Empirical Investigation , 2007, QoSA.

[28]  Beatrice Alenljung,et al.  Portraying the practice of decision-making in requirements engineering: a case of large scale bespoke development , 2008, Requirements Engineering.

[29]  Bee Bee Chua,et al.  Examining Requirements Change Rework Effort: A Study , 2010, ArXiv.

[30]  Urjaswala Vora,et al.  Change Impact Analysis and Software Evolution Specification for Continually Evolving Systems , 2010, 2010 Fifth International Conference on Software Engineering Advances.

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

[32]  Janice Singer,et al.  Studying Software Engineers: Data Collection Techniques for Software Field Studies , 2005, Empirical Software Engineering.

[33]  Mark Keil,et al.  Software project risks and their effect on outcomes , 2004, CACM.

[34]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[35]  Susan P. Williams,et al.  Using card sorting technique to classify requirements change , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..