Requirements for Relquirements Engineering Techniques

The first argument presented in this paper is that if we have a clear understding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be suficient. The second argumenl is that a key objective of the RE process is to specify LI system which will ultimately be successful. Three common types of failure are eximined, process failure, expectation failure and interaction failure. The third argumerur is that if the causes of each type of failure can be described thm we will be able to identify what techniques are netrded tal help us avo& failure. The five comvnon causes ure described: the requirements engineering process ii’self; human communication within requirements, knowledge development, documentation of requirenxmts cad management. A discussion of each cause is follow<ed a list of the RE techniques needed The paper concludes with a ‘wish list’ of seventy requirements for RE )techniques, cad a brief discussion of the strengths and weuknessies of the RE community in meeting those requirements.

[1]  Ed Downs,et al.  Structured systems analysis and design method: application and context , 1988 .

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

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

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

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

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

[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]  James A. Waters,et al.  Group Facilitation Skills for Managers , 1988 .

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

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

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

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

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

[14]  D ChatzoglouProdromos,et al.  Requirements capture and analysis , 1996 .

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

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

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

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

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

[20]  Kenneth Knight Participation in Systems Development , 1989 .

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

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