REGULATION, THE INVISIBLE PART OF THE GOAL ORIENTED REQUIREMENTS ENGINEERING ICEBERG

Gil Regev

Abstract

Goal-Oriented Requirements Engineering (GORE) is considered to be one of the main achievements that the requirements of the Requirements Engineering field has produced since its inception. Several GORE methods were designed in the last twenty years in both research and industry. Curiously, GORE methods seem to have emerged out of nowhere in the early 1990s, the concept of Goal appearing as a natural element in explaining human and organizational behaviour. We have found no theoretical or philosophical work that explicitly link GORE to an underlying organizational model. In this paper, we show that most GORE methods are implicitly based on the goal-seeking, decision making organizational model. We argue that there are other organizational models that may better explain human behaviour, 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 to support this alternative view through the use of maintenance goals and beliefs.

References

  1. Anton, A. I., 1996. Goal-based requirements analysis. In ICRE'96 Second International Conference on Requirements Engineering, IEEE.
  2. Anton, A. I., Potts, C., 1998. The use of goals to surface requirements for evolving systems. In ICSE 98 International Conference on Software Engineering, IEEE.
  3. Ashby, W. R., 1956. An Introduction to Cybernetics, Chapman Hall. London.
  4. Checkland, P., Scholes, J., 1990. Soft System Methodology in action, Wiley. Chichester, UK.
  5. Checkland P, Holwell, S., 1998. Information, systems and information systems - making sense of the field. Wiley. Chichester, UK.
  6. Chong, S., Liu, K., 2002. A Semiotic Approach to Improve the Design Quality of Agent-Based Information Systems. In Liu, K., Clarke, R.J., Anderson, P.B., and Stamper, R.K. Coordination and Communication Using Signs: Studies in Organizational Semiotics, Kluwer.
  7. Cockburn, A., 2001. Writing Effective Use Cases, Addison-Wesley. Reading, MA.
  8. Constantine, L., 1995. Essential modeling: Use cases for user interfaces. In ACM Interactions, 2(2), 34-46.
  9. Dardenne, A., Fickas, S., van Lamsweerde, A., 1991. Goal-directed concept acquisition in requirements elicitation. In IWSSD 7891, Sixth International Workshop on Software Specification and Design, ACM.
  10. Dardenne, A., van Lamsweerde A., Fickas, S., 1993. Goal Directed Requirements Acquisition. Science of Computer Programming, 20(1-2), 3-50.
  11. Dubois, E., 1989. A Logic of Action for Supporting Goaloriented Elaborations of Requirements. In IWSSD 7889, Fifth International Workshop on Software Specification and Design, ACM.
  12. Gause, D.C., Weinberg, G. M., 1989. Exploring Requirements: Quality BEFORE Design, Dorset House, N.Y.
  13. ITU-T, Telecommunication Standardization Sector of ITU, 2008. User requirements notation (URN) - Language definition (Z.151).
  14. Kavakli, E., 2002. Goal-Oriented Requirements Engineering: A Unifying Framework. Requirements Engineering, 6(4), 237-251.
  15. Kavakli, E., Loucopoulos, P., 2005. Goal Modeling in Requirements Engineering: Analysis and Critique of Current Methods. Information Modeling Methods and Methodologies, 102-124.
  16. Loucopoulos, P., Kavakli, E., 1995. Enterprise Modelling and the Teleological Approach to Requirements Engineering. Intelligent and Cooperative Information Systems, 4(1), 45-79.
  17. Moody, D., Heymans, P., Matulevicius, R., 2010. Visual syntax does matter: improving the cognitive effectiveness of the i* visual notation. Requirements Engineering, 15(2), 141-175.
  18. Mylopoulos, J., Kolp, M., Castro, J., 2001. UML for Agent-Oriented Software Development: The Tropos Proposal. In UML 2001, Fourth International Conference on the Unified Modeling Language, Springer.
  19. Mylopoulos J., 2006. Goal-Oriented Requirements Engineering: Part II. Keynote Talk, RE'06, 14th IEEE Requirements Engineering Conference, Minneapolis, MS, September 2006. http://www.ifi.uzh.ch/req/events/RE06/ConferencePro gram/RE06_slides_Mylopoulos.pdf, accessed May 2011.
  20. Nilsson, N. J., 1971. Problem Solving Methods in Artificial Intelligence, McGraw-Hill.
  21. Nuseibeh, B., Easterbrook, S., 2000. Requirements engineering: a roadmap. In ICSE 7800, International Conference on The Future of Software Engineering, ACM.
  22. RE04, 2004. Requirements Engineering International Conference 2004, http://www.re04.org/, accessed May 2011.
  23. Regev, G., Wegmann, A., 2004. Defining early it system requirements with regulation principles: the lightswitch approach. In RE'04, 12th IEEE International Requirements Engineering Conference, IEEE.
  24. Regev, G., Wegmann, A., 2005. Where do Goals Come From: the Underlying Principles of Goal-Oriented Requirements Engineering. In RE'05 13th IEEE International Requirements Engineering Conference, IEEE.
  25. Regev, G., Hayard, O., Gause, D. C., Wegmann, A. 2009. Toward a Service Management Quality Model. In REFSQ'09, 15th International Working Conference on Requirements Engineering: Foundation for Software Quality Springer.
  26. Regev, G., Hayard, O., Wegmann, A., 2011. Service Systems and Value Modeling from an Appreciative System Perspective. In IESS1.1, Second International Conference on Exploring Services Sciences, Springer.
  27. Robinson, W. N., 1989. Integrating multiple specifications using domain goals. In In IWSSD 7889, Fifth International Workshop on Software Specification and Design, ACM.
  28. Rolland, C., Souveyet, C., Ben Achour, C., 1998. Guiding goal modeling using scenarios. IEEE Trans. Software Eng., 24, 1055-1071.
  29. Sutcliffe, A. G., Maiden, N. A. M., 1993. Bridging the Requirements Gap: Policies, Goals and Domains. In IWSSD 7893 7th International Workshop on Software Specification and Design, IEEE.
  30. Shishkov, B., Xie, Z., Liu, K., Dietz, J. L. G., 2002. Using Norm Analysis to Derive Use Cases from Business Processes, In OS 2002, 5th Workshop On Organizational Semiotics.
  31. van Lamsweerde, A., 2001. Goal-Oriented Requirements Engineering: A Guided Tour, in RE'01, 5th IEEE International Symposium on Requirements Engineering, IEEE.
  32. Vickers, Sir G., 1968. Value Systems and Social Process, Tavistock, London.
  33. Vickers, Sir G., 1987. Policymaking, Communication, and Social Learning, eds, Adams, G. B., Forester, J., Catron, B. L.,Transaction Books. New Brunswick NJ.
  34. Weinberg, G. M., 1975. An Introduction to General Systems Thinking, Wiley, New York.
  35. Weinberg, G. M., Weinberg, D., 1988. General Principles of Systems Design, Dorset House.
  36. Yu, E. S. K., 1997. Towards modelling and reasoning support for early-phase requirements engineering. In RE'97, Third IEEE International Symposium on Requirements Engineering, IEEE.
  37. Zave, P. and Jackson, M., 1997. Four Dark Corners of Requirements Engineering, ACM Transactions on Software Engineering and Methodology, 6(1), 1-30.
Download


Paper Citation


in Harvard Style

Regev G. and Wegmann A. (2011). REGULATION, THE INVISIBLE PART OF THE GOAL ORIENTED REQUIREMENTS ENGINEERING ICEBERG . In Proceedings of the First International Symposium on Business Modeling and Software Design - Volume 1: BMSD, ISBN 978-989-8425-68-3, pages 42-50. DOI: 10.5220/0004458400420050


in Bibtex Style

@conference{bmsd11,
author={Gil Regev and Alain Wegmann},
title={REGULATION, THE INVISIBLE PART OF THE GOAL ORIENTED REQUIREMENTS ENGINEERING ICEBERG},
booktitle={Proceedings of the First International Symposium on Business Modeling and Software Design - Volume 1: BMSD,},
year={2011},
pages={42-50},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0004458400420050},
isbn={978-989-8425-68-3},
}


in EndNote Style

TY - CONF
JO - Proceedings of the First International Symposium on Business Modeling and Software Design - Volume 1: BMSD,
TI - REGULATION, THE INVISIBLE PART OF THE GOAL ORIENTED REQUIREMENTS ENGINEERING ICEBERG
SN - 978-989-8425-68-3
AU - Regev G.
AU - Wegmann A.
PY - 2011
SP - 42
EP - 50
DO - 10.5220/0004458400420050