Construction and Validation of Prediction Models for Number of Changes to Requirements

In this paper we present a correlational study in which we assess the ability of five size measures to predict the number of changes to requirements for a medium size software project. The study is ...

[1]  Kevin J. Madders,et al.  EUROPEAN SPACE AGENCY , 1983 .

[2]  George E. Stark,et al.  An examination of the effects of requirements changes on software maintenance releases , 1999 .

[3]  Lionel C. Briand,et al.  Exploring the relationships between design measures and software quality in object-oriented systems , 2000, J. Syst. Softw..

[4]  Gary A. Ham.  Four Roads to Use Case Discovery There Is a Use ( and a Case ) for Each One , .

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

[6]  J. T. Lochner.  The Journal of Defense Software Engineering , 1999 .

[7]  N. Draper,et al.  Applied Regression Analysis. , 1967 .

[8]  Stephen G. MacDonell.  Metrics for database systems: an empirical study , 1997, Proceedings Fourth International Software Metrics Symposium.

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

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

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

[12]  L. H. Rosenberg,et al.  Developing a Successful Metrics Programme , 1996 .

[13]  Jürgen Börstler,et al.  An industrial case study on requirements volatility measures , 2005, 12th Asia-Pacific Software Engineering Conference (APSEC'05).

[14]  Norman F. Schneidewind,et al.  A Methodology for Validating Software Product Metrics , 2000 .

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

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

[17]  Andrea De Lucia,et al.  Assessing effort estimation models for corrective maintenance through empirical studies , 2005, Inf. Softw. Technol..

[18]  J. M. Singer,et al.  IEEE Recommended Practice for Software Requirements SpeciÞcations , 1993 .

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

[20]  John H. Baumert,et al.  Software Measures and the Capability Maturity Model , 1992 .

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

[22]  Bente Anda.  Comparing Effort Estimates Based on Use Case Points with Expert Estimates , 2002 .

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

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

[25]  Linda H. Rosenberg,et al.  A Software Quality Model and Metrics for Identifying Project Risks and Assessing Software Quality , 1996 .

[26]  Mario Piattini,et al.  Building UML class diagram maintainability prediction models based on early metrics , 2003, Proceedings. 5th International Workshop on Enterprise Networking and Computing in Healthcare Industry (IEEE Cat. No.03EX717).

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

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

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

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

[31]  Magne Jørgensen,et al.  Experience With the Accuracy of Software Maintenance Task Effort Prediction Models , 1995, IEEE Trans. Software Eng..

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

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

[34]  Susan Lilly,et al.  Use case pitfalls: top 10 problems from real projects using use cases , 1999, Proceedings of Technology of Object-Oriented Languages and Systems - TOOLS 30 (Cat. No.PR00278).

[35]  Lionel C. Briand,et al.  Empirical Studies of Quality Models in Object-Oriented Systems , 2002, Adv. Comput..

[36]  Jürgen Börstler,et al.  Preliminary Results of two Academic Case Studies on Cost Estimation of Changes to Requirements , 2004 .

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

[38]  Mary Beth Chrissis,et al.  CMMI: Guidelines for Process Integration and Product Improvement , 2003 .

[39]  Phillip G. Armour.  Beware of counting LOC , 2004, CACM.

[40]  Geri Schneider,et al.  Applying Use Cases: A Practical Guide , 1998 .

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

[42]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[43]  Dr. Yun-Tung Lau.  Service-Oriented Architecture and the C 4 ISR Framework , .

[44]  Ivar Jacobson,et al.  Use cases – Yesterday, today, and tomorrow , 2004, Software & Systems Modeling.

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

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

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