Towards Value-Oriented Enterprise Engineering – Relativity in Service System Networks
- 1 Citations
- 761 Downloads
Abstract
Defining the purpose of a system is non-trivial as, by definition, it arises from the relation with its environment. In this paper, we analyze relevant state of the art in the areas of General Systems Theory, Enterprise Engineering, Value Modeling, Enterprise Architecture and Business Modeling. Their main shortcoming essentially resides in lack of flexibly dealing with relativity of enterprise frontier definition. To address this issue, our research is focused on modeling different perspectives of enterprises as systems, namely construction, function and contribution. The approach presented in this paper involves 1) distinguishing the three mentioned perspectives and 2) articulating the concepts of each perspective so that an end-to-end, integrated, model is provided. To this end, we propose a conceptual framework that supports recursive contribution definition, by design. Specifying the value in a contribution perspective allows improved specification of the rationale behind value network establishment and system/subsystem bonding. We can now specify how each component of a system S contributes (provides value) not only to the purpose of S but to other purposes present in the value chains S participates in.
Keywords
Enterprise Engineering Value Contribution PurposePreview
Unable to display preview. Download preview PDF.
References
- 1.Kaplan, R.S., Norton, D.P.: Strategy Maps: Converting Intangible Assets Into Tangible Outcomes. Harvard Business School Press, Boston (2004)Google Scholar
- 2.Henderson, J.C., Venkatraman, N.: Strategic alignment: leveraging information technology for transforming organizations, vol. 32(1), pp. 4–16 (1993)Google Scholar
- 3.Laudon, K.C., Laudon, J.P.: Management Information Systems: Managing the Digital Firm. Prentice Hall (2011)Google Scholar
- 4.Dietz, J.L.G.: Enterprise Ontology: Theory and Methodology. Springer (2006)Google Scholar
- 5.Dietz, J.L.G.: Architecture - Building strategy into design. Netherlands Architecture Forum, Academic Service - SDU, The Hague, The Netherlands (2008)Google Scholar
- 6.Skyttner, L.: General Systems Theory: Problems, Perspectives, Practice, 2nd edn. World Scientific Publishing Co. Pte. Ltd., Singapore (2005)Google Scholar
- 7.Maglio, P.P., Vargo, S.L., Caswell, N., Spohrer, J.: The service system is the basic abstraction of the service science. Information Systems and eBusiness Management (2009)Google Scholar
- 8.Gordijn, J.: Value-based requirements Engineering: Exploring innovatie e-commerce ideas. Vrije Universiteit Amsterdam, Amsterdam (2002)Google Scholar
- 9.Cameron, B., Leaver, S., Worthington, B.: Value-Based Communication Boosts Business’ Perception of IT. Forrester Research (2009)Google Scholar
- 10.Ettema, R., Dietz, J.L.G.: ArchiMate and DEMO – Mates to Date? In: Albani, A., Barjis, J., Dietz, J.L.G. (eds.) CIAO!/EOMAS 2009. LNBIP, vol. 34, pp. 172–186. Springer, Heidelberg (2009)Google Scholar
- 11.The Open Group, Archimate 2.0 Specification. Van Haren Publishing (2012) Google Scholar
- 12.Osterwalder, A., Pigneur, Y.: Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers. Self-Published (2009)Google Scholar
- 13.Rosenberg, A., von Rosing, M., Chase, G., Omar, R., Taylor, J.: Applying Real-World BPM in an SAP Environment. SAP Press (2011)Google Scholar
- 14.Gordijn, J., Osterwalder, A., Pigneur, Y.: Comparing two Business Model Ontologies for Designing eBusiness Models and Value Constellations. In: 18th Bled eConference - eIntegration in Action, Bled, Slovenia (2005)Google Scholar
- 15.Oliver, R.W.: Real-Time Strategy: What Is Strategy, Anyway? Journal of Business Strategy 22(6), 7–10 (2001)CrossRefGoogle Scholar
- 16.Bleistein, S.J., Aurum, A., Cox, K., Ray, P.K.: Strategy-Oriented Alignment in Requirements Engineering: Linking Business Strategy to Requirements of e-Business Systems using the SOARE Approach. Journal of Research and Practice in Information Technology 36(4), 259–276 (2004)Google Scholar
- 17.International Institute of Business Analysis, The Guide to the Business Analysis Body of Knowledge Version 2.0 (2009)Google Scholar
- 18.Quartel, D., Engelsman, W., Jonkers, H., van Sinderen, M.: A goal-oriented requirements modelling language for enterprise architecture. In: IEEE International Enterprise Distributed Object Computing Conference, Auckland, New Zealand (2009)Google Scholar
- 19.Weigand, H., Heuvel, W.-J.V.D.: A Conceptual Architecture for Pragmatic Web Services. In: First International Conference on the Pragmatic Web, Stuttgart, Germany (2006)Google Scholar
- 20.Pombinho, J., Tribolet, J.: Modeling the Value of a System’s Production – Matching DEMO and e3Value. In: 6th International Workshop on Value Modeling and Business Ontology, Vienna, Austria (2012)Google Scholar
- 21.Pombinho, J., Aveiro, D., Tribolet, J.: Towards Objective Business Modeling in Enterprise Engineering – Defining Function, Value and Purpose. In: Albani, A., Aveiro, D., Barjis, J. (eds.) EEWC 2012. LNBIP, vol. 110, pp. 93–107. Springer, Heidelberg (2012)CrossRefGoogle Scholar
- 22.Weigand, H., Johannesson, P., Andersson, B., Bergholtz, M., Edirisuriya, A., Ilayperuma, T.: On the Notion of Value Object. In: Martinez, F.H., Pohl, K. (eds.) CAiSE 2006. LNCS, vol. 4001, pp. 321–335. Springer, Heidelberg (2006)CrossRefGoogle Scholar
- 23.Porter, M.E.: Competitive Advantage: Creating and Sustaining Superior Performance. Free Press (1998)Google Scholar
- 24.Boehm, B.: Value-Based Software Engineering. SIGSOFT Software Engineering Notes 28(2), 4 (2003)CrossRefGoogle Scholar
- 25.Streitfeld, D.: Amazon Signing Up Authors, Writing Publishers Out of Deal. New York Times, A1 (2011)Google Scholar