Towards modelling and reasoning support for early-phase requirements engineering

Requirements are usually understood as stating what a system is supposed to do, as apposed to how it should do it. However, understanding the organizational context and rationales (the "Whys") that lead up to systems requirements can be just as important for the ongoing success of the system. Requirements modelling techniques can be used to help deal with the knowledge and reasoning needed in this earlier phase of requirements engineering. However most existing requirements techniques are intended more for the later phase of requirements engineering, which focuses on completeness, consistency, and automated verification of requirements. In contrast, the early phase aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives. This paper argues, therefore, that a different kind of modelling and reasoning support is needed for the early phase. An outline of the i* framework is given as an example of a step in this direction. Meeting scheduling is used as a domain example.

[1]  Jonathan Grudin,et al.  Why CSCW Applications Fail: Problems in the Design and Evaluation of Organization of Organizational Interfaces. , 1988 .

[2]  Victor R. Basili,et al.  Characterizing and Assessing a Large-Scale Software Maintenance Organization , 1994, 1995 17th International Conference on Software Engineering.

[3]  Janis A. Bubenko,et al.  Extending the Scope of Information Modelling , 1993, International Workshop on the Deductive Approach to Information Systems and Databases.

[4]  Matthias Jarke,et al.  DAIDA: an environment for evolving information systems , 1992, TOIS.

[5]  M. Hammer,et al.  REENGINEERING THE CORPORATION: A MANIFESTO FOR BUSINESS REVOLUTION , 1995 .

[6]  Janis A. Bubenko,et al.  Challenges in requirements engineering , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[7]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[8]  Eric S. K. Yu,et al.  Modeling organizations for information systems requirements engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[9]  John Mylopoulos,et al.  On formal requirements modeling languages: RML revisited , 1994, Proceedings of 16th International Conference on Software Engineering.

[10]  Thomas P. Moran,et al.  Questions, Options, and Criteria: Elements of Design Space Analysis , 1991, Hum. Comput. Interact..

[11]  Herbert A. Simon,et al.  The Sciences of the Artificial , 1970 .

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

[13]  John Mylopoulos,et al.  Capturing more world knowledge in the requirements specification , 1982, ICSE '82.

[14]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[15]  Janis A. Bubenko,et al.  Information Modeling in the Context of System Development , 1980, IFIP Congress.

[16]  Eric S. K. Yu,et al.  Using non-functional requirements to systematically support change , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[17]  Jintae Lee,et al.  A decision rationale management system: capturing, reusing, and managing the reasons for decisions , 2015 .

[18]  Philippe Massonet,et al.  Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[19]  John Mylopoulos,et al.  From E-R to "A-R" - Modelling Strategic Actor Relationships for Business Process Reengineering , 1994, Int. J. Cooperative Inf. Syst..

[20]  F. Caeldries.  Reengineering the Corporation: A Manifesto for Business Revolution , 1994 .

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

[22]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[23]  B. W. Manley,et al.  Reengineering the Corporation. A Manifesto for Business Evolution , 1993 .

[24]  John E. Dobson,et al.  ORDIT: a new methodology to assist in the process of eliciting and modelling organizational requirements , 1993, COCS '93.

[25]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[26]  John Mylopoulos,et al.  From Organization Models to System Requirements: A 'Cooperating Agents' Approach , 1995, CoopIS.

[27]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

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

[29]  Peter Wilson.  Information Modeling , 1987, IEEE Computer Graphics and Applications.

[30]  M. Hammer,et al.  Reengineering the Corporation , 1993 .

[31]  Martin S. Feather,et al.  Language support for the specification and development of composite systems , 1987, TOPL.

[32]  Barry Boehm,et al.  Aids for Identifying Conflicts Among Quality Requirements , 1996 .

[33]  E. Dubois,et al.  A knowledge representation language for requirements engineering , 1986, Proceedings of the IEEE.

[34]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[35]  John Mylopoulos,et al.  AI Models for Business Process Reengineering , 1996, IEEE Expert.

[36]  P MoranThomas,et al.  Questions, options, and criteria , 1991 .

[37]  P. J. Russell,et al.  Open systems architecture for CIM , 1988 .

[38]  M. S. Dubois.  A logic of action for supporting goal-oriented elaborations of requirements , 1989, IWSSD '89.

[39]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[40]  John Mylopoulos,et al.  Understanding "why" in software process modelling, analysis, and design , 1994, Proceedings of 16th International Conference on Software Engineering.

[41]  Stephen Fickas,et al.  Knowledge Representation and Reasoning in the Design of Composite Systems , 1992, IEEE Trans. Software Eng..