ACRE: selecting methods for requirements acquisition

A framework is presented that assists requirements engineers in choosing methods for requirements acquisition. Practitioners are often unaware of the range of methods available. Even when practitioners are aware, most do not foresee the need to use several methods to acquire complete and accurate requirements. One reason for this is the lack of guidelines for method selection. The ACRE framework sets out to overcome these limitations. Method selection is achieved using questions driven from a set of facets which define the strengths and weaknesses of each method. The framework provides guidelines for requirements engineering practitioners. It has undergone evaluation through its presentation to highly experienced requirements engineers. Some results from this evaluation have been incorporated into the presented version of ACRE.

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

[2]  Frederick Hayes-Roth,et al.  Building expert systems , 1983, Advanced book program.

[3]  Nigel Shadbolt,et al.  A comparison of sorting techniques in knowledge acquisition , 1992 .

[4]  Nigel Shadbolt,et al.  Laddering: technique and tool use in knowledge acquisition , 1994 .

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

[6]  D. Diaper,et al.  Knowledge Elicitation: Principles, Techniques and Applications , 1989 .

[7]  R.D. Acosta,et al.  A case study of applying rapid prototyping techniques in the Requirements Engineering Environment , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[8]  Michelene T. H. Chi,et al.  Expertise in Problem Solving. , 1981 .

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

[10]  A. Baddeley.  Your Memory: A User's Guide , 1982 .

[11]  John Mylopoulos,et al.  A requirements modeling language and its logic , 1986, Inf. Syst..

[12]  A. W. Wicker.  Attitudes Versus Actions: The Relationship of Verbal and Overt Behavioral Responses to Attitude Objects. , 1969 .

[13]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[14]  Stewart A. Higgins,et al.  Scenarios-an industrial case study and hypermedia enhancements , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[15]  Elizabeth C. Hirschman,et al.  Judgment under Uncertainty: Heuristics and Biases , 1974, Science.

[16]  Kazuhisa Kawai,et al.  Requirement analysis by the KJ editor , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[17]  A. Finkelstein,et al.  Software package requirements and procurement , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[18]  Andrew Clement,et al.  A retrospective look at PD projects , 1993, CACM.

[19]  Michael G. Christel,et al.  A multimedia approach to requirements capture and modeling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[20]  John Crinnion.  Evolutionary Systems Development: A Practical Guide to the Use of Prototyping within a Structured Systems Methodology , 1992 .

[21]  P. Luff,et al.  Tasks and social interaction: the relevance of naturalistic analyses of conduct for requirements engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[22]  G. Kelly.  The Psychology of Personal Constructs , 2020 .

[23]  E. Goffman.  The Presentation of Self in Everyday Life , 1959 .

[24]  Elizabeth S. Cordingley,et al.  Knowledge elicitation techniques for knowledge-based systems , 1989 .

[25]  Harold R. Booher,et al.  Manprint: An Approach to Systems Integration , 1990 .

[26]  Björn Regnell,et al.  Improving the use case driven approach to requirements engineering , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[27]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[28]  John R. Anderson,et al.  The Adaptive Character of Thought , 1990 .

[29]  Geoff Cutts,et al.  Structured systems analysis and design methodology , 1988 .

[30]  Daniel M. Berry,et al.  AbstFinder, a prototype abstraction finder for natural language text for use in requirements elicitation: design, methodology, and evaluation , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[31]  Richard Bentley,et al.  Sociologists can be surprisingly useful in interactive systems design , 1992 .

[32]  M.J. Bickerton,et al.  The classification of requirements engineering methods , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[33]  Efraim Turban,et al.  Decision support and expert systems , 1993 .

[34]  Ian M. Graham.  Object-oriented methods , 1991 .

[35]  Guus Schreiber.  Applying KADS to the office assignment domain , 1994, Int. J. Hum. Comput. Stud..

[36]  Richard Bentley,et al.  Integrating ethnography into the requirements engineering process , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[37]  H. Grice.  Logic and conversation , 1975 .

[38]  John G. Gammack.  Different Techniques and Different Aspects on Declarative Knowledge , 1987 .

[39]  E. Tulving,et al.  Effectiveness of retrieval cues in memory for words. , 1968, Journal of experimental psychology.