Requirements for requirements engineering techniques

The first argument presented is that if we have a clear understanding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be sufficient. The second argument is that a key objective of the RE process is to specify a system which will ultimately be successful. Three common types of failure are examined: process failure, expectation failure and interaction failure. The third argument is that if the causes of each type of failure can be described then we will be able to identify what techniques are needed to help us avoid failure. The five common causes are described: the requirements engineering process itself, human communication within requirements, knowledge development, documentation of requirements and management. A discussion of each cause is followed by a list of the RE techniques needed. The paper concludes with a 'wish list' of seventy requirements for RE techniques, and a brief discussion of the strengths and weaknesses of the RE community in meeting those requirements.

[1]  Finn Kensing,et al.  PD: structure in the toolbox , 1993, CACM.

[2]  Bronwen Taylor,et al.  The HUFIT planning analysis and specification toolset , 1990, INTERACT.

[3]  Linda A. Macaulay Human-computer interaction for software designers , 1995, Tutorial guides in computing and information systems.

[4]  Paul J. Layzell,et al.  Assisting the Analyst - The aims and objectives of the Analyst Assist project , 1986 .

[5]  Thomas J. Smith READS: a requirements engineering tool , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[6]  James A. Waters,et al.  Group Facilitation Skills for Managers , 1988 .

[7]  Khaled El Emam,et al.  Measuring the success of requirements engineering processes , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[8]  Edward Yourdon,et al.  Object-oriented analysis , 2012 .

[9]  Eswaran Subrahmanian,et al.  Participation and Design: An Extended View , 1992 .

[10]  I. Brandt,et al.  A Comparative Study of Information Systems Design Methodologies , 1983, CRIS.

[11]  Frances Bell,et al.  A framework for method integration , 1994 .

[12]  Kalle Lyytinen,et al.  Information systems failures—a survey and classification of the empirical literature , 1988 .

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

[14]  Judy H. August Joint application design: the group session approach to system design , 1991 .

[15]  Geoff P. Mullery,et al.  CORE : A Method for Controlled Requirement Expression , 1979, ICSE.

[16]  Kiyoshi Agusa,et al.  CARD: a software requirements definition environment , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[17]  Ken Eason,et al.  Information technology and organisational change , 1988 .

[18]  Charles Richter,et al.  A review of the state of the practice in requirements modeling , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[19]  J. J. V. R. Wintraecken,et al.  The NIAM Information Analysis Method , 1990, Springer Netherlands.

[20]  Information Systems Failures , 1993 .

[21]  George Rzevski On the Comparison of Design Methodologies , 1983, CRIS.

[22]  L P Sullivan,et al.  QUALITY FUNCTION DEPLOYMENT , 1996 .