Software Requirements

This tutorial describes the activities and work products that contribute to the specification and validation of the software requirements of a system. Although requirements practices are closely related to specific software development life cycle models, the general activities described in this paper are common to most process models. The activities of elicitation, analysis, specification, validation, and requirements management are discussed and recommended practices in each of those areas are highlighted. Characteristics of a quality requirements specification are also described. .

[1]  Barry W. Boehm,et al.  Verifying and Validating Software Requirements and Design Specifications , 1989, IEEE Software.

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

[3]  Gerald M. Weinberg,et al.  Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products , 1990 .

[4]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[5]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[6]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[7]  Neil A. M. Maiden,et al.  ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..

[8]  Capers Jones,et al.  Patterns of software system failure and success , 1996 .

[9]  A. Finkelstein,et al.  A comedy of errors: the London Ambulance Service case study , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[10]  Ian Sommerville,et al.  Viewpoints: principles, problems and a practical approach to requirements engineering , 1997, Ann. Softw. Eng..

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

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

[13]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[14]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[15]  Bashar Nuseibeh,et al.  Weaving Together Requirements and Architectures , 2001, Computer.

[16]  Barry W. Boehm,et al.  Using WinWin Quality Requirements Management Tools: A Case Study , 2001, Ann. Softw. Eng..

[17]  Ralph R. Young.  Effective Requirements Practices , 2001 .

[18]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[19]  Eila Niemelä,et al.  A Survey on Software Architecture Analysis Methods , 2002, IEEE Trans. Software Eng..

[20]  Alistair Sutcliffe,et al.  User-Centred Requirements Engineering , 2002 .

[21]  Barry W. Boehm.  Value-based software engineering: reinventing , 2003, SOEN.

[22]  Donald Firesmith,et al.  Modern Requirements Specification , 2003, J. Object Technol..

[23]  Jane Cleland-Huang,et al.  Software by Numbers - Low-Risk, High-Return Development , 2003 .

[24]  Alan M. Davis,et al.  Elicitation technique selection: how do experts do it? , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[25]  Ian F. Alexander,et al.  Understanding project sociology by modeling stakeholders , 2004, IEEE Software.

[26]  Jane Cleland-Huang,et al.  A heterogeneous solution for improving the return on investment of requirements traceability , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..