November 2018
·
25 Reads
·
1 Citation
This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.
November 2018
·
25 Reads
·
1 Citation
June 2015
·
32 Reads
Lecture Notes in Business Information Processing
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.
January 2015
·
4 Reads
October 2014
·
31 Reads
·
3 Citations
HMD Praxis der Wirtschaftsinformatik
Wir präsentieren eine Lösung für das Business-IT-Alignment in Unternehmen, um eine solide Informationsbasis für fundierte und sichere Entscheidungen aufzubauen. Die Grundlage dazu findet sich in einer semantischen Unternehmensarchitektur, einem ganzheitlichen, formalen Modell der zentralen Artefakte eines Unternehmens und ihrer Beziehungen. Semantic Enterprise Architecture Management setzt semantische Technologien ein, um Unternehmensarchitekturen formal zu modellieren, vorhandene Datenquellen direkt darin zu integrieren und auf dieser Basis komplexe Analysen oder auch die automatisierte Planung von Veränderungen in IT-Landschaften zu unterstützen. Der Einsatz semantischer Technologien reduziert den Aufwand für den Aufbau einer Unternehmensarchitektur und gewährleistet gleichzeitig die Aktualität und Konsistenz der bereitgestellten Informationen. Die Formalisierung der Unternehmensarchitektur macht die dort vorliegenden Informationen auch für neuartige intelligente Werkzeuge nutzbar.
July 2014
·
38 Reads
·
2 Citations
Lecture Notes in Business Information Processing
Planning changes in an enterprise and its supporting IT can be supported by enterprise architecture (EA) models. The planned changes result in gaps which can be derived by a gap analysis. But, knowing the gaps is not enough. Also important is to know in which sequence gaps are to be closed for transformation path planning. In this paper we show how gaps are identified and reused for detailing a model of the target architecture. Based on this refinement further gaps become visible. Furthermore, we describe how it is possible to create with a transformation model and an action repository transformation paths towards a desired and detailed target architecture. Afterwards, we give a use case example and propose a technical realization of the solution.
January 2014
·
10 Reads
·
3 Citations
November 2013
·
19 Reads
·
5 Citations
Lecture Notes in Business Information Processing
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.
January 2013
·
92 Reads
·
28 Citations
Enterprise architecture management (EAM) provides information about an enterprise and its information systems landscape for thorough analysis. Semantic technologies allow for integrating data sets from various relevant information sources within enterprises in a so-called EA repository, which serves as a comprehensive formal information base for EAM. We call this approach Semantic Enterprise Architecture Management, SEAM for short. We show how SEAM uses semantic technologies to bridge the heterogeneity between various data sets relevant for EAM, such as The Open Group Architecture Framework (TOGAF) models, Business Process Modeling Notation (BPMN) business process models and Service-oriented Architecture (SOA) models. Query answering and reasoning enable detailed analysis and consistency checks on the SEAM repository in order to discover complex dependencies and implicit knowledge.
January 2013
·
13 Reads
·
2 Citations
January 2013
·
242 Reads
·
1 Citation
... 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. ...
January 2013
... Organizations typically adopt EA frameworks [33] that guide their EA initiatives. However, regarding architecture planning, EA frameworks stay vague on how to actually conduct it [1]. ...
January 2013
... The purpose of the gap analysis in the EA context is the determination of differences, respectively gaps, between two different architectural models [The18,DB14]. Thereby both models are described using the same schema and elements in the two models can be identified using names or IDs. Its goal is to identify newly added elements and elements that no longer exist. ...
January 2014
... The IS change management and governance, according to the best practices, are defined in several standards. Enterprise architecture (EA) provides the basis for strategic level evaluation of the changes in IS [10], [11]. EA frameworks such as TOGAF provide general guidelines for EA change management. ...
November 2013
Lecture Notes in Business Information Processing
... EA Management is a discipline for managing architectural development across an organization, coordinating people to achieve and maintain IS, and improving business efficiency and effectiveness [11]. This includes constructing architectural models within large enterprises and complex information system landscapes containing many data sources with relevant information for a complete EA description, which may consist of business process models, software documentation, and service documentation, among others [12]. ...
January 2013
... To support the enterprise architect in finding the successor relationships, we analyze the similarity of the elements in the current and target architecture. The automatic derivation of successor relationships for applications based on business support maps and suggestions for successor services is described by Diefenthaler and Bauer [26]. However, this approach is limited to architectures, where applications are localized in the cells of a business support map. ...
Reference:
Planning Support for Enterprise Changes
January 2013
... To enhance the applicability in different EAs the model is stored utilizing a generic meta model that represents the architecture as a stereotyped graph. The A2E and the utilized analyses are results of previous work [4,8]. For analysis execution A2E converts the analysis definitions into executable constructs. ...
July 2014
Lecture Notes in Business Information Processing
... The applied snowballing methodology resulted in a final set of 20 papers (Diefenthaler, 2016;Farwick et al., 2016;Fittkau et al., 2015;Hacks et al., 2016;Holm et al., 2014;Johnson et al.,2016;Kirschner and Roth, 2014;Möhring and Schmidt, 2015;Ortmann et al., 2014;Rosina, 2015;Roth, 2014;Roth and Matthes, 2014;Schmidt et al., 2014a;Schmidt et al., 2014b;Välja et al., 2016;Välja et al., 2015;Vanauer et al., 2015;Zimmermann et al., 2016;Zimmermann et al., 2017;Zimmermann et al., 2015). In this section, the content of these papers and the results of the classification are discussed. ...
October 2014
HMD Praxis der Wirtschaftsinformatik