CMU / SEI-92-TR-0 12 ESC-TR-92-012 Issues in Requirements Elicitation

There are many problems associated with requirements engineering, including problems in defining the system scope, problems in fostering understanding among the different communities affected by the development of a given system, and problems in dealing with the volatile nature of requirements. These problems may lead to poor requirements and the cancellation of system development, or else the development of a system that is later judged unsatisfactory or unacceptable, has high maintenance costs, or undergoes frequent changes. By improving requirements elicitation, the requirements engineering process can be improved, resulting in enhanced system requirements and potentially a much better system. Requirements engineering can be decomposed into the activities of requirements elicitation, specification, and validation. Most of the requirements techniques and tools today focus on specification, i.e., the representation of the requirements. This report concentrates instead on elicitation concerns, those problems with requirements engineering that are not adequately addressed by specification techniques. An elicitation methodology is proposed to handle these concerns. This new elicitation methodology strives to incorporate the advantages of existing elicitation techniques while comprehensively addressing the activities performed during requirements elicitation. These activities include fact-finding, requirements gathering, evaluation and rationalization, prioritization, and integration. Taken by themselves, existing elicitation techniques are lacking in one or more of these areas.

[1]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[2]  Yoji Akao,et al.  Quality Function Deployment : Integrating Customer Requirements into Product Design , 1990 .

[3]  E. Colbert,et al.  The object-oriented software development method: a practical approach to object-oriented development , 1989, TRI-Ada '89.

[4]  Jahangir Karimi,et al.  A Framework for Comparing Information Engineering Methods , 1988, MIS Q..

[5]  M. Stephens,et al.  The Analyst—a workstation for analysis and design , 1985, ICSE '85.

[6]  H. Holbrook,et al.  A scenario-based methodology for conducting requirements elicitation , 1990, SOEN.

[7]  F. D. Milsom Using CORE with SDL to specify requirements , 1989, ICSE 1989.

[8]  V. Goodrich,et al.  An experimental evaluation of task and methodology variables for requirements definition phase success , 1990, Twenty-Third Annual Hawaii International Conference on System Sciences.

[9]  K. C. Burgess Yakemovic,et al.  Report on a development project use of an issue-based information system , 1990, CSCW '90.

[10]  Julio Cesar Sampaio do Prado Leite A Survey on Requirements Analysis , 1987 .

[11]  John E. Dobson,et al.  The ORDIT approach to requirements identification , 1992, [1992] Proceedings. The Sixteenth Annual International Computer Software and Applications Conference.

[12]  Timo Jokela,et al.  Statecharts based requirements analysis: Deriving user oriented models , 1990 .

[13]  L. Zucconi Techniques and experiences capturing requirements for several real-time applications , 1989, SOEN.

[14]  J. Z. Lavi,et al.  Requirements analysis and specification of embedded systems using ESCAM-a case study , 1990, COMPEURO'90: Proceedings of the 1990 IEEE International Conference on Computer Systems and Software Engineering@m_Systems Engineering Aspects of Complex Computerized Systems.

[15]  Linda A. Macaulay,et al.  Historical Analysis: A Method for Evaluating Requirement Capture Methodologies , 1990, Interact. Comput..

[16]  Anthony Finkelstein,et al.  Re-use of formatted requirements specifications , 1988, Softw. Eng. J..

[17]  Stephen Fickas,et al.  Critiquing software specifications , 1988, IEEE Software.

[18]  D. Benyon,et al.  Towards a Tool Kit for the Systems Analyst , 1987, Comput. J..

[19]  Doris L. Carver,et al.  Evaluation method for user requirements documents , 1989 .

[20]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[21]  G. P. Mullery,et al.  CORE - a method for controlled requirement specification , 1979, ICSE 1979.

[22]  J. McDermid Requirements analysis: problems and the STARTS approach , 1989 .

[23]  Nick Roussopoulos,et al.  An integrated approach to requirements analysis , 1989 .

[24]  Pamela Zave,et al.  Salient features of an executable specification language and its environment , 1986, IEEE Transactions on Software Engineering.

[25]  John T. Nosek,et al.  User Validation of Information System Requirements: Some Empirical Results , 1988, IEEE Trans. Software Eng..

[26]  Jonathan Rosenhead,et al.  Soft Systems Methodology in Action , 1991 .

[27]  Robert G. Mays,et al.  PDM: A Requirements Methodology for Software System Enhancements , 1985, IBM Syst. J..

[28]  Anthony Finkelstein,et al.  Structured common sense: the elicitation and formalisation of system requirements , 1986 .

[29]  Jonah Z. Lavi,et al.  Embedded Computer Systems. Requirements Analysis & Specification - An Industrial Course , 1988, CSEE.

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

[31]  E. Jeffrey Conklin,et al.  A process-oriented approach to design rationale , 1991 .

[32]  Michael W. Nicholson,et al.  Rational Analysis for a Problematic World , 1990 .

[33]  Colin Potts,et al.  Tool support for requirements analysis , 1988, Softw. Eng. J..

[34]  Michael S. Deutsch Focusing real-time systems analysis on user operations , 1988, IEEE Software.

[35]  Linda A. Macaulay,et al.  USTM: A New Approach to Requirements Specification , 1990, Interact. Comput..

[36]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[37]  Pamela Zave,et al.  An Operational Approach to Requirements Specification for Embedded Systems , 1982, IEEE Transactions on Software Engineering.

[38]  Harry S. Delugach,et al.  A multiple viewed approach to software requirements , 1992 .

[39]  Pamela W. Jordan,et al.  Software storming: combining rapid prototyping and knowledge engineering , 1989, Computer.

[40]  John R. Cameron,et al.  An overview of JSD , 1986, IEEE Transactions on Software Engineering.

[41]  Pericles Loucopoulos,et al.  Knowledge-Based Support for Requirements Engineering , 1989, CASE.

[42]  M. A. Schubert Quality function deployment-'a comprehensive tool for planning and development' , 1989, Proceedings of the IEEE National Aerospace and Electronics Conference.

[43]  Sidney C. Bailin,et al.  An object-oriented requirements specifications method , 1989, CACM.

[44]  W. E. Rzepka A requirements engineering testbed: concept, status and first results , 1989, [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume II: Software Track.

[45]  Stephen J. Andriole Command and Control Information Systems Engineering: Progress and Prospects , 1990, Adv. Comput..

[46]  Andrew P. Sage,et al.  Software systems engineering , 1990 .

[47]  Jane Wood,et al.  Joint Application Design: How to Design Quality Systems in 40% Less Time , 1989 .

[48]  Vasant Dhar,et al.  Representation And Maintenance of process knowledge for large Scale Systems development , 1991, Proceedings., 6th Annual Knowledge-Based Software Engineering Conference.

[49]  Gary J. Chastek,et al.  Requirements Engineering and Analysis Workshop Proceedings , 1991 .