Advertisement

What We Can Learn about Business Modeling from Homeostasis

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

Abstract

Business modeling methods most often model an organization’s value provision to its customers followed by the necessary activities and structure to deliver this value. These activities and structure are seen as infinitely malleable; they can be specified and engineered at will. This is hardly in line with what even laymen can observe of organizations, that they are not easy to change and that their behavior often is not directly centered on providing value to customers. Homeostasis is an almost century old model that was developed in the field of physiology to explain how living beings survive by maintaining the constancy of their internal states. Homeostasis helps to explain both the inability of organizations to provide maximum value to their customers and their reluctance to change. From this point of view, resistance to change is not something to fight or to ignore but an essential force behind organizational behavior that can either enable or defeat new business models.

Keywords

Business Models Business Modeling Survival Systems Identity Homeostasis Entropy Negentropy 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Cannon, W.B.: Organization for Physiological Homeostasis. Physiological Reviews IX(3), 399–431 (1929)Google Scholar
  2. 2.
    Cannon, W.B.: The Wisdom of the Body. Norton & Company, New York (1939)Google Scholar
  3. 3.
    Chan, Y.E., Reich, B.H.: IT alignment: What have we learned? Information Technology 22, 297–315 (2007)CrossRefGoogle Scholar
  4. 4.
    Cooper, S.J.: From Claude Bernard to Walter Cannon. Emergence of the concept of homeostasis. Appetite 51, 419–427 (2008)CrossRefGoogle Scholar
  5. 5.
    Dietz, J.L.G.: The Deep Structure of Business Processes. Communications of the ACM 49(5) (2006)Google Scholar
  6. 6.
    Fritscher, B., Pigneur, Y.: Business IT Alignment from Business Model to Enterprise Architecture. In: Salinesi, C., Pastor, O. (eds.) CAiSE Workshops 2011. LNBIP, vol. 83, pp. 4–15. Springer, Heidelberg (2011)CrossRefGoogle Scholar
  7. 7.
    Gordijn, J., Akkermans, J.M.: Value-based requirements engineering: exploring innovative e-commerce ideas. Requirement Engineering 8(2), 114–134 (2003)CrossRefGoogle Scholar
  8. 8.
    Gordijn, J., Yu, E., van der Raadt, B.: e-Service Design Using i* and e3value Modeling. IEEE Software 23(3) (2006)Google Scholar
  9. 9.
    ISO/IEC 10746-1, 2, 3, 4 |. ITU-T Recommendation X.901, X.902, X.903, X.904. Open Distributed Processing - Reference Model (1995-1998)Google Scholar
  10. 10.
    Kilov, H.: Business Specifications: The Key to Successful Software Engineering. Prentice Hall PTR (1999)Google Scholar
  11. 11.
    Mintzberg, H., Ahlstrand, B., Lampel, J.: Strategy Safary – The complete guide through the wilds of strategic management. Prentice Hall (1998)Google Scholar
  12. 12.
    Lankhorst, M.M., Proper, H.A., Jonkers, H.: The Architecture of the ArchiMate Language. In: Halpin, T., Krogstie, J., Nurcan, S., Proper, E., Schmidt, R., Soffer, P., Ukor, R. (eds.) BPMDS 2009 and EMMSAD 2009. LNBIP, vol. 29, pp. 367–380. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  13. 13.
    Osterwalder, A., Pigneur, Y.: Business Model Generation (2010)Google Scholar
  14. 14.
    Regev, G., Wegmann, A.: Defining Early IT System Requirements with Regulation Principles: the Lightswitch Approach. In: 12th IEEE International Requirements Engineering Conference, RE 2004. IEEE (2004)Google Scholar
  15. 15.
    Regev, G., Wegmann, A.: Where do Goals Come From: the Underlying Principles of Goal-Oriented Requirements Engineering. In: RE 2005 13th IEEE International Requirements Engineering Conference. IEEE (2005)Google Scholar
  16. 16.
    Regev, G., Alexander, I.F., Wegmann, A.: Modelling the regulative role of business processes with use and misuse cases. Business Process Management 11(6) (2005)Google Scholar
  17. 17.
    Regev, G., Hayard, O., Gause, D.C., Wegmann, A.: Toward a Service Management Quality Model. In: Glinz, M., Heymans, P. (eds.) REFSQ 2009. LNCS, vol. 5512, pp. 16–21. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  18. 18.
    Regev, G., Hayard, O., Wegmann, A.: Service Systems and Value Modeling from an Appreciative System Perspective. In: Snene, M., Ralyté, J., Morin, J.-H. (eds.) IESS 2011. LNBIP, vol. 82, pp. 146–157. Springer, Heidelberg (2011)CrossRefGoogle Scholar
  19. 19.
    Regev, G., Wegmann, A.: Regulation, The Invisible Part of the Goal Oriented Requirements Engineering Iceberg. In: 1st International Symposium on Business Modeling and Software Design, BMSD 2011. SciTePress (2011)Google Scholar
  20. 20.
    Shishkov, B.: Foreword. In: 1st International Symposium on Business Modeling and Software Design, BMSD 2011. SciTePress (2011)Google Scholar
  21. 21.
    Sowa, J.F., Zachman, J.A.: Extending and formalizing the framework for information systems architecture. IBM Systems Journal 31(3) (1992)Google Scholar
  22. 22.
    Spohrer, J., Riecken, D.: Special issue: services science. Communications of the ACM 49(7) (2006)Google Scholar
  23. 23.
    Vickers, G.: Policymaking, Communication, and Social Learning. In: Adams, G.B., Forester, J., Catron, B.L. (eds.) Transaction Books, New Brunswick NJ (1987)Google Scholar
  24. 24.
    Weinberg, G.M., Weinberg, D.: General Principles of Systems Design. Dorset House (1988)Google Scholar
  25. 25.
    Winograd, T., Flores, F.: Understanding Computers and Cognition: A New Foundation for Design. Ablex, Norwood (1986)Google Scholar
  26. 26.
    Zachman, J.A.: A framework for information systems architecture. IBM Systems Journal 26(3) (1987)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Gil Regev
    • 1
    • 2
  • Olivier Hayard
    • 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