Dependency based Technique for Identifying the Ripple Effect of Requirements Evolution

Requirements evolve continuously and inevitably. In order to effectively manage requirements change, an understa- nding from a quantitative perspective is needed in determining the extent of the propagation of the requirements as they evolve. In this paper, we first look back at the impact analysis in the software life cycle and give an overview of requ irements dependencies. We present a generic algorithm for ide ntifying requirements dependencies and the definitions that are adopted for this study.Using matrix theory on the requirements dependencies, we present the formulas of the ripple effects of requirements evolution and their properties. A typical example in structured analysis of M.Jackson is described to sh ow the effectiveness of the method presented here.

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

[2]  Bashar Nuseibeh,et al.  The process of inconsistency management: a framework for understanding , 1999, Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99.

[3]  Frank Tip,et al.  Change impact analysis for object-oriented programs , 2001, PASTE '01.

[4]  Åsa G. Dahlstedt,et al.  Requirements Interdependencies-Moulding the State of Research into a Research Agenda , 2003 .

[5]  Bashar Nuseibeh,et al.  Using Abduction to Evolve Inconsistent Requirements Specification , 1999, Australas. J. Inf. Syst..

[6]  Mei Xiao-yong.  Analysis of Defect Requirements and Management Model , 2009 .

[7]  Shawn A. Bohner,et al.  Impact analysis-Towards a framework for comparison , 1993, 1993 Conference on Software Maintenance.

[8]  Björn Regnell,et al.  An industrial survey of requirements interdependencies in software product release planning , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[9]  Malcolm Munro,et al.  The impact analysis task in software maintenance: a model and a case study , 1994, Proceedings 1994 International Conference on Software Maintenance.

[10]  Bashar Nuseibeh,et al.  Managing inconsistent specifications: reasoning, analysis, and action , 1998, TSEM.

[11]  M. R. Strens,et al.  Change analysis: a step towards meeting the challenge of changing requirements , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[12]  Qaiser S. Durrani,et al.  A study to investigate the impact of requirements instability on software defects , 2004, SOEN.

[13]  Glenford J. Myers,et al.  Structured Design , 1974, IBM Syst. J..

[14]  Bashar Nuseibeh,et al.  Analysing inconsistent specifications , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[15]  Jameleddine Hassine,et al.  Change impact analysis for requirement evolution using use case maps , 2005, Eighth International Workshop on Principles of Software Evolution (IWPSE'05).

[16]  Dov M. Gabbay,et al.  Inconsistency Handling in Multperspective Specifications , 1994, IEEE Trans. Software Eng..

[17]  Dov M. Gabbay,et al.  Inconsistency Handling in Multi-Perspective Specifications , 1993, ESEC.

[18]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

[19]  Steve M. Easterbrook,et al.  Using ViewPoints for inconsistency management , 1996, Softw. Eng. J..

[20]  Frederick M. Haney.  Module connection analysis: a tool for scheduling software debugging activities , 1972, AFIPS '72 (Fall, part I).

[21]  Stephen S. Yau,et al.  Ripple effect analysis of software maintenance , 1978, COMPSAC.

[22]  Massimo Felici,et al.  Taxonomy of Evolution and Dependability , 2003 .

[23]  Yu-Qing Yan,et al.  Quantitative Analysis for Requirements Evolution's Ripple-Effect , 2009, 2009 International Asia Conference on Informatics in Control, Automation and Robotics.