Value-Oriented Solution Development Process: Uncovering the Rationale behind Organization Components
Although significant progresses have been made in recent years regarding the goals of Enterprise Engineering, we find that the rationale behind every component of an organization is still not systematically and clearly specified. Indeed, state of the art approaches to enterprise development processes do not explicitly incorporate an essential dimension of analysis: value. This state of affairs does not warrant a leading role in enterprise alignment.
We propose to address this issue by specifying a value-aware system development process and a system development organization. To this end, we began by applying DEMO to model the system development organization. Furthermore, the original Generic System Development Process (GSDP) was modelled, and improvement points identified. Our main contribution is a revision of the GSDP, combined with research on value modelling and enterprise architecture that explicitly includes the teleological part of the system development process.
The explicitation of the development process focusing on the value dimension, contributes to providing traceability and clarifying the rationale of each organizational artefact. We believe that modelling this rationale systematically will improve reactive and proactive change management through increased self-awareness, improved scenario specification, objective evaluation and well-grounded system development decisions.
KeywordsDEMO GSDP Value Modelling e3Value Solution Development
Unable to display preview. Download preview PDF.
- 1.Laudon, K.C., Laudon, J.P.: Management Information Systems: Managing the Digital Firm. Prentice Hall (2011)Google Scholar
- 2.Kaplan, R.S., Norton, D.P.: Strategy Maps: Converting Intangible Assets Into Tangible Outcomes. Harvard Business School Press, Boston (2004)Google Scholar
- 3.Henderson, J.C., Venkatraman, N.: Strategic alignment: leveraging information technology for transforming organizations 32(1), 4–16 (1993)Google Scholar
- 6.Dietz, J.L.G.: Enterprise Ontology: Theory and Methodology. Springer (2006)Google Scholar
- 7.Dietz, J.L.G.: Architecture - Building strategy into design. Netherlands Architecture Forum, Academic Service - SDU, The Hague, The Netherlands (2008)Google Scholar
- 9.Aveiro, D., Silva, A.R., Tribolet, J.: Extending the Design and Engineering Methodology for Organizations with the Generation Operationalization and Discontinuation Organization. In: Winter, R., Zhao, J.L., Aier, S. (eds.) DESRIST 2010. LNCS, vol. 6105, pp. 226–241. Springer, Heidelberg (2010)CrossRefGoogle Scholar
- 10.Cameron, B., Leaver, S., Worthington, B.: Value-Based Communication Boosts Business’ Perception of IT. Forrester Research (2009)Google Scholar
- 11.Gordijn, J.: Value-based requirements Engineering: Exploring innovatie e-commerce ideas. Vrije Universiteit Amsterdam, Amsterdam (2002)Google Scholar
- 12.Aveiro, D.: G.O.D. (Generation, Operationalization & Discontinuation) and Control (sub)organizations: A DEMO-based approach for continuous real-time management of organizational change caused by exceptions. UTL, Lisboa (2010)Google Scholar
- 13.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
- 14.Pombinho, J., Aveiro, D., Tribolet, J.: Business Service Definition in Enterprise Engineering - A Value-oriented Approach. In: 4th Workshop on Service Oriented Enterprise Architecture for Enterprise Engineering, Beijing, China (2012)Google Scholar