An industrial case study on requirements volatility measures

Requirements volatility is an important risk factor for software projects. Software measures can help in quantifying and predicting this risk. In this paper, we present an industrial case study that investigated measures of volatility for a medium size software project. The goal of the study was twofold: 1) to empirically validate a set of measures associated with the volatility of use case models (UCM); 2) to investigate the correlation between subjective and objective volatility. Measurement data was collected in retrospect for all use case models of the software project. In addition, we determined subjective volatility by interviewing stakeholders of the project. Our data analysis showed a high correlation between our measures of size of UCM and total number of changes, indicating that the measures of size of UCMs are good indicators of requirements volatility. No correlations was found between subjective and objective volatility. These results suggest that project managers at this company should measure their projects because of the risk to take wrong decisions based on their own and the developer's perceptions.

[1]  Mark C. Paulk,et al.  Capability Maturity Model for Software , 2001 .

[2]  Craig Larman,et al.  Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process , 2001 .

[3]  Eli P. Cox,et al.  The Optimal Number of Response Alternatives for a Scale: A Review , 1980 .

[4]  Barbara Ann Kitchenham,et al.  Evaluating software engineering methods and tools: part 9: quantitative case study methodology , 1998, SOEN.

[5]  Yashwant K. Malaiya,et al.  Requirements volatility and defect density , 1999, Proceedings 10th International Symposium on Software Reliability Engineering (Cat. No.PR00443).

[6]  KitchenhamBarbara Ann,et al.  Evaluating software engineering methods and tools , 1998 .

[7]  W. Lam,et al.  Managing change in software development using a process improvement approach , 1998, Proceedings. 24th EUROMICRO Conference (Cat. No.98EX204).

[8]  Donald F. Shafer,et al.  Quality Software Project Management , 2001 .

[9]  OmanPaul,et al.  An examination of the effects of requirements changes on software maintenance releases , 1999 .

[10]  Annabella Loconsole,et al.  Measuring the requirements management key process area , 2001 .

[11]  Anthony Finkelstein,et al.  Requirements stability assessment using scenarios , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[12]  Horst Zuse,et al.  A Framework of Software Measurement , 1998 .

[13]  Dietmar Pfahl,et al.  Using simulation to analyse the impact of software requirement volatility on project performance , 2000, Inf. Softw. Technol..

[14]  Mark C. Paulk,et al.  The Capability Maturity Model , 1991 .

[15]  Albert Sydney Hornby,et al.  Oxford advanced learner\'s dictionary of current English / A S Hornby with A P Cowie, A C Gimson , 1975 .

[16]  Norman F. Schneidewind,et al.  Methodology For Validating Software Metrics , 1992, IEEE Trans. Software Eng..

[17]  Claes Wohlin,et al.  Experimentation in Software Engineering , 2000, The Kluwer International Series in Software Engineering.

[18]  Shari Lawrence Pfleeger,et al.  Towards a Framework for Software Measurement Validation , 1995, IEEE Trans. Software Eng..

[19]  Didar Zowghi,et al.  Analysis of requirements volatility during software development life cycle , 2004, 2004 Australian Software Engineering Conference. Proceedings..

[20]  Jacob Cohen.  A Coefficient of Agreement for Nominal Scales , 1960 .

[21]  Anthony Finkelstein,et al.  Environmental scenarios and requirements stability , 2002, IWPSE '02.

[22]  Khaled El Emam,et al.  Benchmarking Kappa: Interrater Agreement in Software Process Assessments , 1999, Empirical Software Engineering.

[23]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[24]  Victor R. Basili,et al.  The TAME Project: Towards Improvement-Oriented Software Environments , 1988, IEEE Trans. Software Eng..

[25]  Egon Berghout,et al.  The Goal/Question/Metric method: a practical guide for quality improvement of software development , 1999 .

[26]  Ian K. Bray,et al.  An Introduction to Requirements Engineering , 2002 .

[27]  Dar-Biau Liu,et al.  Metrics for requirements engineering , 1995, J. Syst. Softw..

[28]  Sallie M. Henry,et al.  Quantitative assessment of the software maintenance process and requirements volatility , 1993, CSC '93.

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

[30]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[31]  Jürgen Börstler,et al.  Theoretical Validation and Case Study of Requirements Management Measures , 2007 .

[32]  Craig Larman,et al.  Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition) , 1997 .

[33]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[34]  George E. Stark,et al.  An examination of the effects of requirements changes on software maintenance releases , 1999, J. Softw. Maintenance Res. Pract..

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

[36]  S.D.P. Harker,et al.  The change and evolution of requirements as a challenge to the practice of software engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[37]  Linda H. Rosenberg,et al.  Doing Requirements Right the First Time , 1998 .

[38]  Vincenzo Gervasi,et al.  Process Metrics for Requirements Analysis , 2000, EWSPT.

[39]  Brian Henderson-Sellers,et al.  Sizing Use Cases: How to Create a Standard Metrical Approach , 2002, OOIS.

[40]  Sandro Morasca,et al.  On the application of measurement theory in software engineering , 2004, Empirical Software Engineering.

[41]  Annabella Loconsole.  Measuring the Requirements Management Key Process Area : Application of the Goal Question Metric to the Requirements Management Key Process Area of the Capability Maturity Model , 2001 .

[42]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[43]  刘江雪,et al.  LIN volume 11 issue 2 Cover and Back matter , 1975, Journal of Linguistics.

[44]  Joseph Raynus.  Software Process Improvement With CMM , 1998 .

[45]  Ralph Young,et al.  The requirements engineering handbook , 2003 .

[46]  Didar Zowghi,et al.  A study of the impact of requirements volatility on software project performance , 2002, Ninth Asia-Pacific Software Engineering Conference, 2002..