Revisiting Goal-Oriented Requirements Engineering with a Regulation View

  • Gil Regev
  • Alain Wegmann
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 109)


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.


Goals Requirements Regulation Survival Appreciative System Norms Beliefs 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Anton, A.I.: Goal-based requirements analysis. In: Proc. ICRE 1996 Second International Conference on Requirements Engineering. IEEE (1996)Google Scholar
  2. 2.
    Anton, A.I., Potts, C.: The use of goals to surface requirements for evolving systems. In: International Conference on Software Engineering, ICSE 1998. IEEE (1998)Google Scholar
  3. 3.
    Beer, S.: The viable system model: its provenance, development, methodology and pathology. Journal of the Operational Research Society 35(1), 7–25 (1984)Google Scholar
  4. 4.
    Checkland, P.: Soft System Methodology: a 30-year retrospective. Wiley, Chichester (1999)Google Scholar
  5. 5.
    Checkland, P., Holwell, S.: Information, systems and information systems - making sense of the field. Wiley, Chichester (1998)Google Scholar
  6. 6.
    Checkland, P.: Webs of significance: the work of Geoffrey Vickers. Systems Research and Behavioral Science 22(4) (2005)Google Scholar
  7. 7.
    Cockburn, A.: Writing Effective Use Cases. Addison-Wesley, Reading (2001)Google Scholar
  8. 8.
    Constantine, L.: Essential modeling: Use cases for user interfaces. ACM Interactions 2(2), 34–46 (1995)CrossRefGoogle Scholar
  9. 9.
    Dardenne, A., Fickas, S., van Lamsweerde, A.: Goal-directed concept acquisition in requirements elicitation. In: Sixth International Workshop on Software Specification and Design, IWSSD 1991. ACM (1991)Google Scholar
  10. 10.
    Dardenne, A., van Lamsweerde, A., Fickas, S.: Goal Directed Requirements Acquisition. Science of Computer Programming 20(1-2), 3–50 (1993)CrossRefGoogle Scholar
  11. 11.
    Dubois, E.: A Logic of Action for Supporting Goal-oriented Elaborations of Requirements. In: Fifth International Workshop on Software Specification and Design, IWSSD 1989. ACM (1989)Google Scholar
  12. 12.
    Gause, D.C., Weinberg, G.M.: Exploring Requirements: Quality BEFORE Design. Dorset House, N.Y. (1989)Google Scholar
  13. 13.
    ITU-T, Telecommunication Standardization Sector of ITU: User requirements notation (URN) – Language definition (Z.151) (2008) Google Scholar
  14. 14.
    Kavakli, E.: Goal-Oriented Requirements Engineering: A Unifying Framework. Requirements Engineering 6(4), 237–251 (2002)CrossRefGoogle Scholar
  15. 15.
    Kavakli, E., Loucopoulos, P.: Goal Modeling in Requirements Engineering: Analysis and Critique of Current Methods. Information Modeling Methods and Methodologies, 102–124 (2005)Google Scholar
  16. 16.
    Loucopoulos, P., Kavakli, E.: Enterprise Modelling and the Teleological Approach to Requirements Engineering. Intelligent and Cooperative Information Systems 4(1), 45–79 (1995)CrossRefGoogle Scholar
  17. 17.
    Moody, D., Heymans, P., Matulevičius, R.: Visual syntax does matter: improving the cognitive effectiveness of the i* visual notation. Requirements Engineering 15(2), 141–175 (2010)CrossRefGoogle Scholar
  18. 18.
    Mylopoulos, J., Kolp, M., Castro, J.: UML for Agent-Oriented Software Development: The Tropos Proposal. In: Gogolla, M., Kobryn, C. (eds.) UML 2001. LNCS, vol. 2185, pp. 422–441. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  19. 19.
    Mylopoulos, J.: Goal-Oriented Requirements Engineering: Part II. Keynote Talk. In: 14th IEEE Requirements Engineering Conference, RE 2006, Minneapolis, MS (September 2006), (accessed May 2011)
  20. 20.
    Nilsson, N.J.: Problem Solving Methods in Artificial Intelligence. McGraw-Hill (1971)Google Scholar
  21. 21.
    Nuseibeh, B., Easterbrook, S.: Requirements engineering: a roadmap. In: International Conference on The Future of Software Engineering, ICSE 2000. ACM (2000)Google Scholar
  22. 22.
    RE04, 2004. Requirements Engineering International Conference (2004), (accessed May 2011)
  23. 23.
    Regev, G., Wegmann, A.: Defining Early IT System Requirements with Regulation Principles: the Lightswitch Approach. In: Proc. 12th IEEE International Requirements Engineering Conference (RE 2005), Kyoto, Japan (2004)Google Scholar
  24. 24.
    Regev, G., Wegmann, A.: Where do Goals Come From: the Underlying Principles of Goal-Oriented Requirements Engineering. In: Proc. 13th IEEE International Requirements Engineering Conference (RE 2005), Paris (2005)Google Scholar
  25. 25.
    Regev, G., Gause, D.C., Wegmann, A.: Creativity and the Age-Old Resistance to Change Problem in RE. In: Proc. 14th IEEE International Requirements Engineering Conference (RE 2006), Minneapolis, MN (2006)Google Scholar
  26. 26.
    Regev, G., Hayard, O., Wegmann, A.: Service Systems and Value Modeling from an Appreciative System Perspective. In: IESS1.1, Second International Conference on Exploring Services Sciences. Springer, Heidelberg (2011)Google Scholar
  27. 27.
    Robinson, W.N.: Integrating multiple specifications using domain goals. In: Fifth International Workshop on Software Specification and Design, IWSSD 1989. ACM (1989)Google Scholar
  28. 28.
    Rolland, C., Souveyet, C., Ben Achour, C.: Guiding goal modeling using scenarios. IEEE Trans. Software Eng. 24, 1055–1071 (1998)CrossRefGoogle Scholar
  29. 29.
    Rolland, C., Salinesi, C.: Modeling Goals and Reasoning with Them. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements (EMSR). Springer (2005)Google Scholar
  30. 30.
    Sutcliffe, A.G., Maiden, N.A.M.: Bridging the Requirements Gap: Policies, Goals and Domains. In: 7th International Workshop on Software Specification and Design, IWSSD 1993. IEEE (1993)Google Scholar
  31. 31.
    van Lamsweerde, A.: Goal-Oriented Requirements Engineering: A Guided Tour. In: 5th IEEE International Symposium on Requirements Engineering, RE 2001. IEEE (2001)Google Scholar
  32. 32.
    Vickers, S.G.: Value Systems and Social Process. Tavistock, London (1968)Google Scholar
  33. 33.
    Vickers, S.G.: Policymaking, Communication, and Social Learning. In: Adams, G.B., Forester, J., Catron, B.L. (eds.), Transaction Books, New Brunswick, NJ (1987)Google Scholar
  34. 34.
    Weick, K.E.: The Social Psychology of Organizing, 2nd edn. McGraw-Hill (1979)Google Scholar
  35. 35.
    Weinberg, G.M.: An Introduction to General Systems Thinking. Wiley & Sons, New York (1975)Google Scholar
  36. 36.
    Weinberg, G.M., Weinberg, D.: General Principles of Systems Design. Dorset House, New York (1988)Google Scholar
  37. 37.
    Yu, E.S.K.: Towards modelling and reasoning support for early-phase requirements engineering. In: Third IEEE International Symposium on Requirements Engineering, RE 1997. IEEE (1997)Google Scholar
  38. 38.
    Zave, P., Jackson, M.: Four Dark Corners of Requirements Engineering. ACM Transactions on Software Engineering and Methodology 6(1), 1–30 (1997)CrossRefGoogle Scholar
  39. 39.
    Zave, P.: Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys 29(4) (1997)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Gil Regev
    • 1
    • 2
  • Alain Wegmann
    • 1
  1. 1.School of Computer and Communication SciencesEcole Polytechnique Fédérale de Lausanne (EPFL)LausanneSwitzerland
  2. 2.ItecorVevey 1Switzerland

Personalised recommendations