Requirements engineering: a review and research agenda

This paper reviews the area of requirements engineering. It outlines the key concerns to which attention should be devoted by both practitioners, who wish to "reengineer" their development processes, and academics, seeking intellectual challenges. It presents an assessment of the state-of-the-art and draws conclusions in the form of a research agenda.<<ETX>>

[1]  Barry W. Boehm,et al.  Software requirements as negotiated win conditions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[2]  Richard H. Thayer,et al.  System and Software Requirements Engineering , 1994 .

[3]  Peter Johnson,et al.  Human computer interaction: Psychology, task analysis, and software engineering , 1992 .

[4]  Philip M. Johnson.  An instrumented approach to improving software quality through formal technical review , 1994, Proceedings of 16th International Conference on Software Engineering.

[5]  Norman E. Fenton,et al.  Software Metrics: A Rigorous Approach , 1991 .

[6]  Neil A. M. Maiden,et al.  Exploiting reusable specifications through analogy , 1992, CACM.

[7]  William N. Robinson,et al.  Negotiation behavior during requirement specification , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[8]  Charles Richter,et al.  Developing initial OOA models , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

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

[10]  Stephen Fickas,et al.  Knowledge Representation and Reasoning in the Design of Composite Systems , 1992, IEEE Trans. Software Eng..

[11]  Martin S. Feather,et al.  Language support for the specification and development of composite systems , 1987, TOPL.

[12]  Jeff Conklin.  Design rationale and maintainability , 1989, [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume II: Software Track.

[13]  Meir M. Lehman,et al.  Approach to a disciplined development process - the ISTAR integrated project support environment , 1986, SOEN.

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

[15]  Barry W. Boehm,et al.  Understanding and Controlling Software Costs , 1988, IEEE Trans. Software Eng..

[16]  Anthony Finkelstein,et al.  Review of design methodology , 1983 .

[17]  Linda A. Macaulay.  Requirements capture as a cooperative activity , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[18]  Adam A. Porter,et al.  An experiment to assess different defect detection methods for software requirements inspections , 1994, Proceedings of 16th International Conference on Software Engineering.

[19]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[20]  R. C. Waters,et al.  The requirements apprentice: an initial scenario , 1989, IWSSD '89.

[21]  Watts S. Humphrey,et al.  Characterizing the software process: a maturity framework , 1988, IEEE Software.

[22]  Michael Jackson,et al.  Domain descriptions , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

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

[24]  Jintae Lee,et al.  What's in Design Rationale? , 1991, Hum. Comput. Interact..

[25]  Watts S. Humphrey,et al.  The State Of Software Engineering Practice: A Preliminary Report , 1989, 11th International Conference on Software Engineering.

[26]  John Mylopoulos,et al.  On formal requirements modeling languages: RML revisited , 1994, Proceedings of 16th International Conference on Software Engineering.

[27]  Alan M. Davis,et al.  Software requirements - analysis and specification , 1990 .

[28]  B. I. Blum,et al.  Characterizing the software process , 1994 .

[29]  Joseph A. Goguen,et al.  Techniques for requirements elicitation , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[30]  James E. Rumbaugh,et al.  Object-Oriented Modelling and Design , 1991 .

[31]  David Garlan.  The Role Of Formalized Domain-specific Software Frameworks , 1989, [1989] Proceedings of the 5th International Software Process Workshop.

[32]  S. Joy Mountford,et al.  The Art of Human-Computer Interface Design , 1990 .

[33]  Laurence Brooks,et al.  Addressing organisational context in requirements analysis , 1994 .

[34]  Simon M. Kaplan,et al.  Supporting collaborative software development with ConversationBuilder , 1992, SDE.

[35]  Patrick G. Brown,et al.  QFD: Echoing the voice of the customer , 1991, AT&T Technical Journal.

[36]  John E. Dobson,et al.  ORDIT: a new methodology to assist in the process of eliciting and modelling organizational requirements , 1993, COCS '93.

[37]  Luqi.  Computer-aided prototyping for a command-and-control system using CAPS , 1992, IEEE Software.

[38]  Richard H. Thayer,et al.  Standards, Guidelines, and Examples on System and Software Requirements Engineering , 1994 .

[39]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[40]  Bill Curtis,et al.  Five Paradigms in the Psychology of Programming , 1988 .

[41]  Martin S. Feather,et al.  Utilizing Scenarios in the Software Development Process , 1993, Information System Development Process.

[42]  Ian Sommerville,et al.  Viewpoints for requirements definition , 1992, Softw. Eng. J..

[43]  Kee Yong Lim,et al.  Integrating human factors with structured analysis and design methods: An enhanced conception of the extended Jackson system development method , 1990, INTERACT.

[44]  Colin Potts,et al.  Inquiry-Based Scenario Analysis of System Requirements , 1994 .

[45]  Michael G. Christel,et al.  AMORE: The Advanced Multimedia Organizer for Requirements Elicitation , 1993 .

[46]  Stephen Fickas,et al.  Being Suspicious: Critiquing Problem Specifications , 1988, AAAI.