Auflistung nach Autor:in "Schneider, Alexander W."
1 - 2 von 2
Treffer pro Seite
Sortieroptionen
- ZeitschriftenartikelFostering Collaborative and Integrated Enterprise Architecture Modelling(Enterprise Modelling and Information Systems Architectures - An International Journal: Vol. 8, Nr. 1, 2013) Matthes, Florian; Neubert, Christian; Schneider, Alexander W.Enterprise Architecture Management (EAM) is a challenging task in modern enterprises. Tools supporting EA management activities are based on extensive models either created by enterprise architects or built-in. However, these models cannot be adapted according to specific data acquisition needs by persons having the architectural knowledge on the instance level. In this article, we describe how Hybrid Wikis empower these information carriers and enterprise architects to collaboratively and incrementally develop and manage a model in a bottom-up fashion by using wiki pages enriched with types and attributes. We visualise these emergent models by using UML-like class diagrams. Our approach is evaluated in a case study in a global operating bank participating in our Wiki4EAM community, a community of German enterprise architects applying Hybrid Wikis in different EA management contexts.
- KonferenzbeitragRoadmaps for enterprise architecture evolution(Software Engineering 2010 – Workshopband (inkl. Doktorandensymposium), 2010) Ernst, Alexander M.; Schneider, Alexander W.Managing the enterprise architecture (EA) is a major challenge of every larger modern enterprise. Aligning business and IT in order to optimize their interaction is the main goal of EA management. The first step of an EA management approach typically is to analyze and document the as-is-situation. Subsequently, the second step has to be the management of the EA evolution in order to achieve the desired target EA. Although IT projects guide this evolution by implementing the transformations from a current to an envisioned architecture, they are considered sparsely by EA approaches. Therefore, this article presents a methodology pattern (M-Pattern) describing a process including all necessary tasks and associated roles, which help to cope with the challenge of EA evolution management.