The Three Dimensions of Requirements Engineering

Requirements engineering (RE) is perceived as an area of growing importance. Due to the increasing effort spent for research in this area many contributions to solve different problems within RE exist. The purpose of this paper is to identify the main goals to be reached during the requirements engineering process in order to develop a framework for RE. This framework consists of the three dimensions: • the specification dimension • the representation dimension • the agreement dimension Looking at the RE research using this framework, the different approaches can be classified and therefore their interrelationships become much clearer. Additionally the framework offers a first step towards a common understanding of RE.

[1]  Sol Jaffe Greenspan,et al.  Requirements modeling: a knowledge representation approach to software requirements definition , 1984 .

[2]  D. Gentner.  Structure‐Mapping: A Theoretical Framework for Analogy* , 1983 .

[3]  Clarence A. Ellis,et al.  Groupware: some issues and experiences , 1991, CACM.

[4]  Colette Rolland,et al.  A Natural Language Approach for Requirements Engineering , 1992, CAiSE.

[5]  Marilyn W. Bush,et al.  Improving software quality: the use of formal inspections at the Jet Propulsion Laboratory , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[6]  Anthony Hall,et al.  Seven myths of formal methods , 1990, IEEE Software.

[7]  Neil A. M. Maiden,et al.  Software Reusability: Delivering productivity gains or short cuts , 1990, INTERACT.

[8]  Piero Torrigiani,et al.  ASPIS: a knowledge-based CASE environment , 1988, IEEE Software.

[9]  Gill Smith,et al.  Object-oriented analysis , 1988, WADAS '88.

[10]  Barry W. Boehm,et al.  Verifying and Validating Software Requirements and Design Specifications , 1989, IEEE Software.

[11]  Michael V. Mannino,et al.  Inferring Database Requirements from Examples in Forms , 1988, ER.

[12]  Peter P. Chen.  The Entity-Relationship Model: Towards a unified view of Data , 1976 .

[13]  John Mylopoulos,et al.  Knowledge Representation as the Basis for Requirements Specifications , 1985, Computer.

[14]  Matthias Jarke,et al.  Information Systems Quality and Quality Informations Systems , 1992, The Impact of Computer Supported Technologies in Information Systems Development.

[15]  Martin S. Feather,et al.  Coping with Requirements Freedom , 1991 .

[16]  Matthias Jarke,et al.  Specification Management with CADo , 1992 .

[17]  Robert Balzer,et al.  Tolerating Inconsistency , 1991, [1989] Proceedings of the 5th International Software Process Workshop.

[18]  Gerald M. Weinberg,et al.  Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products , 1990 .

[19]  Edward Yourdon,et al.  Modern structured analysis , 1989 .

[20]  Victor Weinberg,et al.  Structured Analysis , 1978 .

[21]  Julio Cesar Sampaio do Prado Leite,et al.  Requirements Validation Through Viewpoint Resolution , 1991, IEEE Trans. Software Eng..

[22]  James Bigelow,et al.  Hypertext and CASE , 1988, IEEE Software.

[23]  Mack W. Alford,et al.  Software Requirements Engineering Methodology (SREM) at the age of two , 1978, COMPSAC.

[24]  Matthias Jarke,et al.  A software process data model for knowledge engineering in information systems , 1990, Inf. Syst..

[25]  David R. Harris,et al.  KBRA: A new paradigm for requirements engineering , 1988, IEEE Expert.

[26]  Neil A. M. Maiden,et al.  Analogy as a paradigm for specification reuse , 1991, Softw. Eng. J..

[27]  Dines Bjørner,et al.  VDM '87 VDM — A Formal Method at Work , 1987, Lecture Notes in Computer Science.

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

[29]  Michael L. Brodie,et al.  On Conceptual Modelling , 1984, Topics in Information Systems.

[30]  Matthias Jarke,et al.  Telos: representing knowledge about information systems , 1990, TOIS.

[31]  Richard C. Waters,et al.  The Requirements Apprentice: Automated Assistance for Requirements Acquisition , 1991, IEEE Trans. Software Eng..

[32]  Panos Constantopoulos,et al.  Similarity for Analogical Software Reuse: A Computational Model , 1994, ECAI.

[33]  David E. Monarchi,et al.  A research typology for object-oriented analysis and design , 1992, CACM.

[34]  J S Oakland.  Total quality management; proceedings , 1989 .

[35]  Neil A. M. Maiden,et al.  Analogical specification reuse during requirements analysis , 1992 .

[36]  Bashar Nuseibeh,et al.  Viewpoints: A Framework for Integrating Multiple Perspectives in System Development , 1992, Int. J. Softw. Eng. Knowl. Eng..

[37]  Edward Yourdon,et al.  Structured walkthroughs , 1978 .

[38]  Wolfgang Polak,et al.  Iteration in the software process , 1986, ISPW.

[39]  Manfred A. Jeusfeld,et al.  Anderungskontrolle in deduktiven Objektbanken , 1992 .

[40]  Walt Scacchi,et al.  On designing intelligent hypertext systems for information management in software engineering , 1987, Hypertext.

[41]  Walt Scacchi,et al.  A hypertext system to manage software life-cycle documents , 1990, IEEE Software.

[42]  Walt Scacchi,et al.  Managing Software Engineering Projects: A Social Analysis , 1984, IEEE Transactions on Software Engineering.

[43]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[44]  Pierangela Samarati,et al.  F-ORM METHOD: a F-ORM Methodology for Reusing Specifications , 1991 .

[45]  Raymond McCall,et al.  JANUS: integrating hypertext with a knowledge-based design environment , 1989, Hypertext.

[46]  Kanth Miriyala,et al.  Automatic Derivation of Formal Software Specifications From Informal Descriptions , 1991, IEEE Trans. Software Eng..

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

[48]  Colette Rolland,et al.  Using Artificial Inteligence Techniques to Formalize the Information System Design Process , 1990, DEXA.

[49]  Martin S. Feather,et al.  Representation and Presentation of Requirements Knowledge , 1992, IEEE Trans. Software Eng..

[50]  Paul Johannesson,et al.  A method for transforming relational schemas into conceptual schemas , 1989, Proceedings of 1994 IEEE 10th International Conference on Data Engineering.

[51]  Colin Potts.  A generic model for representing design methods , 1989, ICSE '89.

[52]  Martin S. Feather,et al.  Building an evolution transformation library , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[53]  W. Edwards Deming,et al.  Out of the Crisis , 1982 .

[54]  Kuldeep Kumar,et al.  Informal and Formal Requirements Specification Languages: Bridging the Gap , 1991, IEEE Trans. Software Eng..

[55]  Terry Winograd,et al.  Understanding computers and cognition - a new foundation for design , 1987 .

[56]  Janis A. Bubenko,et al.  Theories underlying requirements engineering: an overview of NATURE at Genesis , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[57]  Janis A. Bubenko,et al.  Requirements Engineering: An Integrated View of Representation, Process, and Domain , 1993, ESEC.

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

[59]  Geoffrey Bock,et al.  Groupware - software for computer-supported cooperative work , 1992 .

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

[61]  Robert Balzer,et al.  Informality in Program Specifications , 1899, IEEE Transactions on Software Engineering.

[62]  J. Michael Spivey,et al.  An introduction to Z and formal specifications , 1989, Softw. Eng. J..

[63]  T. Biggerstaff,et al.  Reusability Framework, Assessment, and Directions , 1987, IEEE Software.

[64]  Bertrand Meyer,et al.  On Formalism in Specifications , 1985, IEEE Software.

[65]  Matthias Jarke,et al.  A decision based configuration process environment , 1991, Softw. Eng. J..

[66]  Stephen M. McMenamin,et al.  Essential systems analysis , 1984 .

[67]  Pamela Zave,et al.  An Insider's Evaluation of PAISLey , 1991, IEEE Trans. Software Eng..

[68]  Matthias Jarke,et al.  Quality Information Systems: Repository Support for Evolving Process Models , 1992 .

[69]  David R. Barstow.  Domain-Specific Automatic Programming , 1985, IEEE Transactions on Software Engineering.

[70]  I. G. BONNER CLAPPISON.  Editor , 1960, The Electric Power Engineering Handbook - Five Volume Set.

[71]  Jeannette M. Wing.  A specifier's introduction to formal methods , 1990, Computer.

[72]  Mehdi T. Harandi,et al.  Knowledge-based software design using design schemas , 1987, ICSE '87.

[73]  Pericles Loucopoulos,et al.  Knowledge-based approach to requirements engineering using method and domain knowledge , 1988, Knowl. Based Syst..

[74]  Matthias Jarke,et al.  Dependency Directed Reasoning and Learning in Systems Maintenance Support , 1987, IEEE Trans. Software Eng..

[75]  Alan M. Davis,et al.  A comparison of techniques for the specification of external system behavior , 1988, CACM.

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

[77]  R. Guindon,et al.  Control of cognitive processes during software design: what tools are needed? , 1988, CHI '88.

[78]  H. Stähelin.  Guidelines , 1994, Communicating Science.

[79]  Julio Cesar Sampaio do Prado Leite,et al.  Viewpoint analysis: a case study , 1989, IWSSD '89.

[80]  Jacques Hagelstein,et al.  Declarative approach to information systems requirements , 1988, Knowl. Based Syst..