Goal-Oriented Model Driven Enterprise Architecture Validation Approach
Volume 3 - Issue 4, April 2019 Edition
[Download Full Paper]
Author(s)
Joe Essien
Keywords
Goal-Oriented, Enterprise Architecture, Framework, Business Processes, Motivation, Validation, Modeling.
Abstract
Enterprise Architecture (EA) has been defined as the organization of a system embodied in its components, relationships to each other, environment, the principle guiding its design and evolution (IEEE, 2000). Thus an important characteristic of EA is to provide a holistic view of the enterprise visualizing the relevant aspects of the business for specific stakeholders. However, one of the many concerns of this interest has been how to deal with the complex challenges of implementing the models with the ability to validate its integrated components to ensure conformity with individual stakeholder’s motivation. To achieve this, methodologies that describe components in relation to their behavioral attributes, impact on other elements in the domain and their dependencies have been postulated. Albeit, studies show that these taxonomies do not adequately address validation requirements (Lankhorst, 2013). This article analyzes the EA concepts of ArchiMate, focusing on the business and application layers with the objective to extend motivation with tests specifications using the model-driven approach thus offer descriptive semantics for validation. The paper contributes to a better understanding on how EA models can be validated thus improve alignment with the business vision and strategy. Student Internship Program case study is used to exemplify this hypothesis.
References
[1]. Bahill, A. T., Botta, R., & Daniels, J.,2006. The Zachman framework populated with baseball models. Journal of EA, 2(4), 50-68.
[2]. Chen, D., Doumeingts, G., Vernadat, F., 2008. Architectures for enterprise integration and in-teroperability: Past, present and future. Computer and Industrial Engineering, 59:647659.
[3]. Clark, T., Barn, B. S., Oussena, S., 2011. Leap: a precise lightweight framework for enterprise ar-chitecture. In Proceedings of the 4th India Soft-ware Engineering Conference (pp. 85-94). ACM.
[4]. Coleman, P., Papp, R., 2006. Strategic Alignment: Analysis of Perspectives. Proceedings of the 2006 Southern Association for Information Systems Conference.
[5]. Davenport, T., 1993. Process Innovation: Reengi-neering work through IT. HBS School Press, Bos-ton.
[6]. Essien, J., Oussena, S., 2013. Enterprise Architec-ture Models for Description of Integrated Compo-nents for Validation - A Case Study of Student In-ternship Programme. In the 15th International Conference on Enterprise Information System 2013.
[7]. Fischer, C., winter, R, Aier, S., 2010. What Is an Enterprise Architecture Principle? Towards a Consolidated Definition, Computer and Infor-mation Science 2010, SCI 317, pp. 193–205. springerlink.com Springer-Verlag Berlin Heidel-berg.
[8]. GARTNER, 2013. Available at http://www.gartner.com. Accessed April, 2013
[9]. IEEE Computer Society. IEEE Recommended Practice for Architectural Description of Software Intensive Systems. IEEE Standard 1471-2000.
[10]. Johannesson, P., Soderstrom, E., 2008. Infor-mation Systems Engineering: From Data Analysis to Process Networks. Hershey, PA: IGI Publishing.. p.58-61.
[11]. Krogstie, J., 2008. Using EEML for Combined Goal and Process Oriented Modeling: A Case Study. Proceedings of EMMSAD 2008.
[12]. Krogstie, J., Sindre, G., & Jorgensen, H. D. 2006. Process models representing knowledge for action: A revised quality framework. European Journal of Information Systems 15 91-102.
[13]. Lankhorst, M., 2013. Enterprise Architecture at Work: Modelling, Communication and Analysis. Springer, Berlin, Heidelberg, New York.
[14]. Mabey, B., 2008. Imperative vs. Declarative Sce-narios in user stories; Available at: http://benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories.html; Ac-cessed 19 May 2013.
[15]. McGovern, J., 2004. A practical guide to enter-prise architecture. Prentice Hall Professional.
[16]. Noran, O., 2003. An Analysis of the Zachman Framework for Enterprise Architecture from the GERAM perspective, Annual Reviews in Control, 27, 163-183
[17]. North, D., 2006. Introducing BDD. Available at: http://dannorth.net/introducing-bdd/. Accessed on: March 2013.
[18]. OMG, http://www.omg.org/. Assessed 2013.
[19]. Polgreen, J., 2012. Using TOGAF to Develop and Implement Enterprise Architecture in Government - U.S. Federal Agencies as Example.
[20]. Quartel, D., Engelsman, W., Jonkers, H. 2009. A Goal-Oriented Requirements Modelling Language for Enterprise Architecture. Proceedings of the 13th IEEE International Enterprise Distributed Object Computing Conference, EDOC 2009, New Zealand.
[21]. Salmans, B., Kappelman, L. A.,2010. The State of EA: Progress, Not Perfection. The SIM guide to enterprise architecture, 165-187.
[22]. Sammuelsson, E.,2003, UML Testing Profile RFP, Telelogic, Rational, SofTEAM, FOKUS, Ericsson,
[23]. Sessions, R., 2007. A Comparison of the Top Four Enterprise-Architecture Methodologies, Ob-jectWatch, Inc.
[24]. TOGAF, The Open Group. ArchiMate Version 2. http://www.opengroup.org/archimate, Oct, 2012.
[25]. SIP, 2012, University of West London,Available at: http://samsa.uwl.ac.uk/mdse/. Accessed 07/01/2103
[26]. Urbaczewski, L., & Mrdalj, S. 2006. A comparison of enterprise architecture frameworks. Issues in Information Systems, 7(2), 18-23.
[27]. Venkatraman, N., Henderson, J., 2010. Strategic Alignment: Leveraging IT for Transforming Or-ganisations, IBM Systems Journal, Vol 32 No 1.
[28]. Weston, J., Defee, J., 2004. Performance Based Enterprise Architecture Planning – A white Paper, 2004, http://www.caci.com/.
[29]. Zachman, J. 2008. John Zachman’s Concise Defi-nition of The Zachman Framework. Zachman In-ternational. 2008. Available at: http://www.zachman.com/about-the-zachman-framework, Accessed April, 2013.
