Gap Analysis in Enterprise Architecture using Semantic Web Technologies
... However, they have not recognized and defined a Gap of Changes as a pattern, repeatedly used used by different business roles for planning and implementation activities. (Diefenthaler and Bauer, 2013) have recognised a Gap of Changes and proposed a solution for "gap analysis using semantic web technologies on a highlevel current and target state of an enterprise architecture". The authors identify only the replacement relations between elements of two architectures, whereas also other relations exist between the elements of As-Is and To-Be architectures. ...
... However, they have not recognized and defined a Gap of Changes as a pattern, repeatedly used used by different business roles for planning and implementation activities. (Diefenthaler and Bauer, 2013) have recognised a Gap of Changes and proposed a solution for "gap analysis using semantic web technologies on a highlevel current and target state of an enterprise architecture". The authors identify only the replacement relations between elements of two architectures, whereas also other relations exist between the elements of As-Is and To-Be architectures. ...
Change analysis of enterprise architectures is usually done by observing differences between two enterprise architectures, As-Is and To-Be. If the As-Is and To-Be have a lot of differences, it is problematic to manually create a correct view on changes. This paper proposes a revision of a definition of the Gap of Changes and defines it as a language independent analytic pattern suitable for using in tools. The paper describes a tool built on the basis of this definition. The change analysis without the tool and with the tool output has been tested in a workshop. The added value of the tool was acknowledged by the workshop participants.
Enterprise architecture (EA) models are tools of analysis, communication, and support towards enterprise transformation. These models need a suitable maintenance process to support comprehensive knowledge of the enterprise’s structure and dynamics. This study aims to identify and discuss the existing approaches to EA model maintenance published in the scientific literature. A systematic literature review was employed as the research method. A keyword-based search in six databases identified a total of 4495 papers in which 31 primary studies were included. A total of nine categories of EA model maintenance approaches were identified from both information systems and enterprise engineering fields of research. The increasing amount of research in EA model maintenance suggests that the topic still presents opportunities for research contributions. This study also proposes future lines of research according to the results identified in the theoretical corpus.
Enterprises have to react to changes with an increasing speed in order to stay competitive. Many approaches support the modeling of enterprise architectures but lack an evolution of enterprise architectures through demonstrating a transformation path from one architecture state to another. Enterprises know their strategic goals and are able to model them, but are not supported towards achieving these goals in terms of developing their architecture. We want to improve the current manual creation of the transformation paths in enterprise architecture planning by providing possible and sound sequences of actions as part of a roadmap from the current to a desired target architecture.
Therefore, we present a solution that supports the enterprise architect with proposals for a transformation path from the current to the target state considering dependencies to be taken into account during the enterprise transformation.
Enterprise architecture (EA) management supports transformation path planning to facilitate the change from the current to the target architecture. We create parts of these transformation paths automatically using the information from current and target business support maps. Restrictions on the business support maps, i.e. areas which shall remain stable and which shall be transformed, are modeled by an enterprise architect to allow for a goal oriented transformation path generation. The transformation paths serve as project proposals for the project portfolio management. Necessary changes to the EA are prioritized and estimated. Our solution uses a graph transformation based approach to allow for an interactive creation of possible transformation paths. The transformation paths are the state transitions of a graph transition system, which we create from an EA model. We weigh the effort of each transformation according cost, time and risk.
Enterprises and their architecture (EA) are changing continuously, what leads to changes in enterprise information systems (IS) and its architecture. Ineffective IS change management has a particularly adverse effect on EA because of wrong architectural decisions. These decisions can lead to several problems such as poor IS performance, wrong interfaces, bad data quality, doubled data input and sub-optimal IS support to business processes. It is assumed than an enterprise IS strategy is an important source of information guiding the EA architecting and implementation of the changes. In this paper, a case study on definition of the IS strategy for a Latvian telecommunication company is presented. The goal of the case study is to identify typical practical challenges arising in EA architecting and to examine the role of the enterprise IS strategy. The results of this study will be used in further research on development of the approach for the strategic IS change control.
ResearchGate has not been able to resolve any references for this publication.