Assessing Issues of Change Impact Analysis Process for a Software Projects

Software Change Impact Analysis (SCIA) has defined as a process of identifying the consequences of the software changes requests. Almost no major corporations are free from the challenge of developing and implementing successful strategies for managing change. Different studies have been conducted in this subject for the last two decades, several approaches have been proposed. But most of these studies have less support to the current process of a software change management. The complexities of software change development nowadays cause the process of managing software change to be difficulty. There is major organizations that are free from the challenges of initiating, developing and implementing effective software changes management. As a result, software practitioners recognize that strategic change is not temporary issues but it's continued process. Only few project managers got the ability to manage th change efficiently. Therefore, this paper investigates issues of change impact analysis process and identifies and compares current practice issues of a software change impact analysis, by evaluating their strengths and weaknesses. It also reviews existing tools and models of change impact analysis and how it supports to the current software change managements. Hence, it proposes existing processe issues and suggests the need of an effective process of software change management.

[1]  Ian J. Davis,et al.  DRACA: decision support for root cause analysis and change impact analysis for CMDBs , 2009, CASCON.

[2]  Luigi Lavazza,et al.  Enhancing requirements and change management through process modelling and measurement , 2000, Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219).

[3]  David D. Walden,et al.  Systems engineering handbook : a guide for system life cycle processes and activities , 2015 .

[4]  Samuel Ajila,et al.  Software maintenance: An approach to impact analysis of objects change , 1995, Softw. Pract. Exp..

[5]  Bashar Nuseibeh,et al.  ViewPoints: meaningful relationships are difficult! , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[6]  Mark Dowson,et al.  Concepts For Process Definition And Support , 1990, 'Support for the Software Process'.,Proceedings of the 6th International Software Process Workshop.

[7]  O. Debande,et al.  Information and Communication Technologies: A Tool Empowering and Developing the Horizon of the Learner. , 2004 .

[8]  S. Rao Vallabhaneni.  Auditing the Maintenance of Software , 1986 .

[9]  Matthias Weber,et al.  Requirements for requirements management tools , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[10]  Sara Jones,et al.  Change analysis and management: a process model and its application within a commercial setting , 1998, Proceedings. 1998 IEEE Workshop on Application-Specific Software Engineering and Technology. ASSET-98 (Cat. No.98EX183).

[11]  Keith Brian Gallagher,et al.  Using Program Slicing in Software Maintenance , 1991, IEEE Trans. Software Eng..

[12]  Jianjun Zhao,et al.  Celadon: a change impact analysis tool for aspect-oriented programs , 2008, ICSE Companion '08.

[13]  BenbasatIzak,et al.  Development of an Instrument to Measure the Perceptions of Adopting an Information Technology Innovation , 1991 .

[14]  Jacques Lonchamp,et al.  A structured conceptual and terminological framework for software process engineering , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

[15]  Rafael Prikladnicki,et al.  A Reference Model for Global Software Development: Findings from a Case Study , 2006, 2006 IEEE International Conference on Global Software Engineering (ICGSE'06).

[16]  Izak Benbasat,et al.  Development of an Instrument to Measure the Perceptions of Adopting an Information Technology Innovation , 1991, Inf. Syst. Res..

[17]  Allison W. Pearson,et al.  Work-Family Conflict: A Model of Linkages between Work and Family Domain Variables and Turnover Intentions , 2003 .

[18]  Watts S. Humphrey,et al.  Software process development and enactment: concepts and definitions , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

[19]  Xavier Ferré,et al.  Software Process Modelling , 2001, ISAS-SCI.

[20]  Ivan Kurtev,et al.  Change Impact Analysis based on Formalization of Trace Relations for Requirements , 2008 .

[21]  N. Ikram,et al.  Making Decision in Requirement Change Management , 2005, 2005 International Conference on Information and Communication Technologies.

[22]  Lloyd G. Williams.  A behavioral approach to software process modelling , 1988, ISPW '88.

[23]  Minna Mäkäräinen,et al.  Software change management process in the development of embedded software , 2000 .

[24]  Pei-Chi Chen,et al.  A holistic approach to managing software change impact , 2009, J. Syst. Softw..

[25]  Dalton Serey Guerrero,et al.  On the Precision and Accuracy of Impact Analysis Techniques , 2008, Seventh IEEE/ACIS International Conference on Computer and Information Science (icis 2008).

[26]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

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

[28]  Gerald Kotonya,et al.  An Integrated Framework for Requirement Change Impact Analysis , 1999 .

[29]  Shawn A. Bohner,et al.  Impact analysis in the software change process: a year 2000 perspective , 1996, 1996 Proceedings of International Conference on Software Maintenance.

[30]  Neil C. Olsen.  The software rush hour (software engineering) , 1993, IEEE Software.

[31]  Claes Wohlin,et al.  Aggregating viewpoints for strategic software process improvement-a method and a case study , 2002, IEE Proc. Softw..

[32]  James J. Appleton,et al.  Measuring cognitive and psychological engagement: Validation of the Student Engagement Instrument , 2006 .

[33]  Tony Cant,et al.  Tools for Requirements Management: A Comparison of Telelogic DOORS and the HiVe , 2006 .

[34]  Václav Rajlich,et al.  Incremental change in object-oriented programming , 2004, IEEE Software.

[35]  N. Ikram,et al.  Requirement Change Management Process Models: Activities, Artifacts and Roles , 2006, 2006 IEEE International Multitopic Conference.