Requirements engineering: In search of the dependent variables

When software development teams modify their requirements engineering process as an independent variable, they often examine the implications of these process changes by assessing the quality of the products of the requirements engineering process, e.g., a software requirements specification (SRS). Using the quality of the SRS as the dependent variable is flawed. As an alternative, this paper presents a framework of dependent variables that serves as a full range for requirements engineering quality assessment. In this framework, the quality of the SRS itself is just the first level. Other higher, and more significant levels, include whether the project was successful and whether the resulting product was successful. And still higher levels include whether or not the company was successful and whether there was a positive or negative impact on society as a whole.

[1]  Ben Kovitz.  Ambiguity and what to do about it [requirements engineering] , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[2]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[3]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[4]  Dennis R. Goldenson,et al.  A systematic survey of CMM experience and results , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[5]  W. Lam,et al.  A case-;study of requirements reuse through product families , 1998, Ann. Softw. Eng..

[6]  E. GaffneyJ.,et al.  Software Function, Source Lines of Code, and Development Effort Prediction , 1983 .

[7]  Capers Jones,et al.  Applied software measurement (2nd ed.): assuring productivity and quality , 1996 .

[8]  Khaled El Emam,et al.  Spice: The Theory and Practice of Software Process Improvement and Capability Determination , 1997 .

[9]  John D'Ambra,et al.  Practical software process improvement - the IMPACT project , 2001, Proceedings 2001 Australian Software Engineering Conference.

[10]  Kosei Tanahashi,et al.  Quantitative evaluation of mura in liquid crystal displays , 2004 .

[11]  Alan M. Davis,et al.  Good requirements practices are neither necessary nor sufficient , 2005, Requirements Engineering.

[12]  Marvin V. Zelkowitz,et al.  Lessons learned from 25 years of process improvement: the rise and fall of the NASA software engineering laboratory , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.

[13]  Karl Cox,et al.  Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams , 2006, J. Syst. Softw..

[14]  Alan M. Davis,et al.  A Strategy for Comparing Alternative Software Development Life Cycle Models , 1988, IEEE Trans. Software Eng..

[15]  Linda Gorchels.  The Product Manager's Handbook: The Complete Product Management Resource , 2000 .

[16]  Geoffrey Randall.  Principles of Marketing , 1993 .

[17]  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.

[18]  Karlheinz Kautz,et al.  Applying and adjusting a software process improvement model in practice: the use of the IDEAL model in a small software enterprise , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[19]  Erik Simmons,et al.  Requirements Triage: What Can We Learn from a "Medical" Approach? , 2004, IEEE Softw..

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

[21]  Klaus Schmid.  A comprehensive product line scoping approach and its validation , 2002, ICSE '02.

[22]  Daniela E. Damian,et al.  An industrial case study of the impact of requirements engineering on downstream development , 2003, 2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings..

[23]  Nigel Hill,et al.  How to Measure Customer Satisfaction , 1999 .

[24]  Moshe Ben-Horim,et al.  Essentials of corporate finance , 1987 .

[25]  W. Lam,et al.  Requirements change: a dissection of management issues , 1999, Proceedings 25th EUROMICRO Conference. Informatics: Theory and Practice for the New Millennium.

[26]  T. J. Redling.  A methodology for developing new product line requirements through gap analysis , 2003, Digital Avionics Systems Conference, 2003. DASC '03. The 22nd.

[27]  Henry Mintzberg,et al.  Strategy safari : a guided tour through the wilds of strategic management , 1998 .

[28]  T. Sasaki,et al.  Coevolution of patent strategy and product strategy , 2001, PICMET '01. Portland International Conference on Management of Engineering and Technology. Proceedings Vol.1: Book of Summaries (IEEE Cat. No.01CH37199).

[29]  Roel Wieringa,et al.  Guest Editors' Introduction: RE'03-Practical Requirements Engineering Solutions , 2004, IEEE Softw..

[30]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[31]  Nathan Rosenberg,et al.  Inside the Black Box: Technology and Economics , 1984 .

[32]  Khaled El Emam,et al.  Elements of Software Process Assessment & Improvement , 1999 .

[33]  Victor R. Basili,et al.  Evaluation of a software requirements document by analysis of change data , 1981, ICSE '81.

[34]  Steven R. Rakitin,et al.  Software verification and validation for practitioners and managers , 2001 .

[35]  D. Teece.  Managing Intellectual Capital: Organizational, Strategic, and Policy Dimensions , 2000 .

[36]  Simona Ronchi Della Rocca,et al.  λ Δ -Models , 2004 .

[37]  Klaus Pohl,et al.  Product Management , 2005, Software Product Line Engineering.

[38]  Tim Menzies,et al.  Converging on the optimal attainment of requirements , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[39]  Björn Regnell,et al.  Challenges in Market-Driven Requirements Engineering - an Industrial Interview Study , 2002 .

[40]  Manuel Pérez Cota,et al.  Experiences in the Application of Software Process Improvement in SMES , 2004, Software Quality Journal.

[41]  Forrest Shull,et al.  How perspective-based reading can improve requirements inspections , 2000, Computer.

[42]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[43]  Adam A. Porter,et al.  Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment , 1995, IEEE Trans. Software Eng..

[44]  Didar Zowghi,et al.  The Three Cs of Requirements : Consistency , Completeness , and Correctness , 2002 .

[45]  Ben Kovitz.  Ambiguity and What to Do about It , 2002 .

[46]  K. Forsberg,et al.  System Engineering Overview , 2000 .

[47]  Martin Höst,et al.  An analytical model for requirements selection quality evaluation in product software development , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[48]  Joseph A. Goguen,et al.  Requirements engineering: social and technical issues , 1994 .

[49]  Pamela Zave,et al.  Executable requirements for embedded systems , 1981, ICSE '81.

[50]  Alan M. Davis,et al.  Just Enough Requirements Management: Where Software Development Meets Marketing , 2005 .

[51]  Karl Cox,et al.  Modeling Business Strategy in E-Business Systems Requirements Engineering , 2004, ER.

[52]  Alan M. Davis,et al.  Identifying and measuring quality in a software requirements specification , 1993, [1993] Proceedings First International Software Metrics Symposium.

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

[54]  Claes Wohlin,et al.  Requirements prioritisation: an experiment on exhaustive pair-wise comparisons versus planning game partitioning , 2004, ICSE 2004.

[55]  Jose A. Calvo-Manzano Villalón,et al.  Experiences in the Application of Software Process Improvement in SMES , 2002 .

[56]  Mohamed Zairi,et al.  Best Practice: Process Innovation Management , 1999 .

[57]  Richard Turner,et al.  CMMI Distilled: A Practical Introduction to Integrated Process Improvement , 2001 .

[58]  Alan M. Davis,et al.  The Art of Requirements Triage , 2003, Computer.

[59]  Björn Regnell,et al.  Post-release analysis of requirements selection quality - an industrial case study , 2003 .

[60]  Capers Jones,et al.  Applied software measurement: assuring productivity and quality , 1991 .

[61]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[62]  Mehdi T. Harandi,et al.  Workshop on software specification and design , 1988, SOEN.

[63]  George Stalk,et al.  Perspectives on strategy : from the Boston Consulting Group , 1998 .

[64]  Hoh Peter In,et al.  A requirements negotiation model based on multi-criteria analysis , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[65]  Khaled El Emam,et al.  Causal analysis of the requirements change process for a large system , 1997, 1997 Proceedings International Conference on Software Maintenance.

[66]  Victor R. Basili,et al.  Quantitative Evaluation of Software Methodology , 1985 .

[67]  Pär Carlshamre,et al.  Release Planning in Market-Driven Software Product Development: Provoking an Understanding , 2002, Requirements Engineering.