Revisiting Goal-Oriented Requirements Engineering with a Regulation View

Goal-Oriented Requirements Engineering (GORE) is considered to be one of the main achievements that the Requirements Engineering field has produced since its inception. Several GORE methods were designed in the last twenty years in both research and industry. In analyzing individual and organizational behavior, goals appear as a natural element. There are other organizational models that may better explain human behavior, albeit at the expense of more complex models. We present one such alternative model that explains individual and organizational survival through continuous regulation. We give our point of view of the changes needed in GORE methods in order to support this alternative view through the use of maintenance goals and beliefs. We illustrate our discussion with the real example of a family practitioner association that needed a new information system.

[1]  Patrick Heymans,et al.  Visual syntax does matter: improving the cognitive effectiveness of the i* visual notation , 2010, Requirements Engineering.

[2]  Stafford Beer,et al.  The Viable System Model : its provenance , development , methodology and pathology * Stafford Beer = President of the World Organization for Systems and Cybernetics , 2000 .

[3]  Neil A. M. Maiden,et al.  Bridging the requirements gap: policies, goals and domains , 1993, Proceedings of 1993 IEEE 7th International Workshop on Software Specification and Design.

[4]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[5]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[6]  Peter Checkland,et al.  Soft Systems Methodology: a 30-year retrospective , 1999 .

[7]  Annie I. Antón,et al.  The use of goals to surface requirements for evolving systems , 1998, Proceedings of the 20th International Conference on Software Engineering.

[8]  K. Weick.  The social psychology of organizing , 1969 .

[9]  Alain Wegmann,et al.  Defining early IT system requirements with regulation principles: the Lightswitch approach , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[10]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[11]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[12]  Gerald M. Weinberg,et al.  Exploring Requirements: Quality Before Design , 1989 .

[13]  Peter Checkland.  Webs of significance: the work of Geoffrey Vickers , 2005 .

[14]  Geoffrey Vickers.  Policymaking, communication, and social learning , 1987 .

[15]  Pericles Loucopoulos,et al.  Goal Modeling in Requirements Engineering: Analysis and Critique of Current Methods , 2005, Information Modeling Methods and Methodologies.

[16]  John Mylopoulos,et al.  UML for Agent-Oriented Software Development: The Tropos Proposal , 2001, UML.

[17]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[18]  Alain Wegmann,et al.  Where do goals come from: the underlying principles of goal-oriented requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[19]  Pamela Zave.  Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..

[20]  John Mylopoulos,et al.  Goal-Oriented Requirements Engineering, Part II , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[21]  Pericles Loucopoulos,et al.  Enterprise Modelling and the Teleological Approach to Requirements Engineering , 1995, Int. J. Cooperative Inf. Syst..

[22]  Colette Rolland,et al.  Modeling Goals and Reasoning with Them , 2005 .

[23]  Evangelia Kavakli,et al.  Goal-Oriented Requirements Engineering: A Unifying Framework , 2002, Requirements Engineering.

[24]  W. N. Robinson,et al.  Integrating multiple specifications using domain goals , 1989, IWSSD '89.

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

[26]  G. Weinberg.  An Introduction to General Systems Thinking , 1975 .

[27]  Stephen Fickas,et al.  Goal-directed concept acquisition in requirements elicitation , 1991, Proceedings of the Sixth International Workshop on Software Specification and Design.

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

[29]  Gerald M. Weinberg,et al.  General principles of systems design , 1988 .

[30]  Alain Wegmann,et al.  Service Systems and Value Modeling from an Appreciative System Perspective , 2011, IESS.

[31]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[32]  K. Boulding,et al.  Value Systems and Social Process. , 1971 .

[33]  Sue Holwell,et al.  Information, Systems and Information Systems: Making Sense of the Field , 1998 .

[34]  Nils J. Nilsson,et al.  Problem-solving methods in artificial intelligence , 1971, McGraw-Hill computer science series.

[35]  Alain Wegmann,et al.  Creativity and the Age-Old Resistance to Change Problem in RE , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[36]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[37]  Larry L. Constantine,et al.  Essential modeling: use cases for user interfaces , 1995, INTR.