Auflistung nach:
Auflistung EMISA nach Autor:in "Aier, Stephan"
1 - 5 von 5
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragBeyond Enterprise Architecture Modeling – What are the Essentials to Support Enterprise Transformations?(Enterprise Modelling and Information Systems Architectures (EMISA 2013), 2013) Labusch, Nils; Aier, Stephan; Winter, RobertIn recent years, many different modeling techniques and languages were developed in order to allow for an efficient and appropriate enterprise architecture management (EAM). Recently, EAM is no longer only seen as a means to ensure business/IT alignment but further as a means to support fundamental changes of the organization, often called enterprise transformation (ET). In a joint project with a group of practitioners we aim at developing a framework that provides guidance on how EAM can support such ETs and thus leverage the benefit of modeling. Our design results after more than one year of research reveal different types of EAM, areas of action in ETs and ET activities that can be supported by EAM. The findings show that modeling techniques or languages should focus on constructs like transitions, benefits or risks in order to increase their value for ET support.
- KonferenzbeitragCan boundary objects mitigate communication defects in enterprise transformation? Findings from expert interviews(Enterprise Modelling and Information Systems Architectures (EMISA 2013), 2013) Abraham, Ralf; Niemietz, Hella; Kinderen, Sybren de; Aier, StephanInappropriate communication is a major threat to enterprise transformations. While enterprise architecture (EA) models may be helpful to support communication, these models are often tailored to the needs of specialists like enterprise architects. Based on empirical data from 12 expert interviews, we analyze how EA models can become boundary objects that span knowledge boundaries and alleviate communication defects among heterogeneous stakeholder groups in enterprise transformations. We contribute a framework that maps six communication defects to three knowledge boundaries and to 12 boundary object properties as a foundation for future EA model design. Our findings also indicate that EA models alone are not sufficient for overcoming communication defects, but that facilitators like architects are needed in addition.
- KonferenzbeitragA Federated Approach to Enterprise Architecture Model Maintenance(Enterprise modelling and information systems architectures – concepts and applications, 2007) Fischer, Ronny; Aier, Stephan; Winter, RobertThis report introduces an approach how Enterprise Architecture (EA) design can be deployed in a large financial organisation for strategic transformation. Our EA design embraces all main components of the business organisations, its information systems and the way they work to achieve business objectives. In order to tackle such EA design and its deployment, governance, design and measurement principles are required to keep EA consistent and avoid misunderstandings among stakeholders. Since EA focuses on a holistic view of the organisation, full EA deployment is risky due to cost and organisational impact. Therefore we use an iterative approach within EA deployment that will be considered as an assessment process evaluating the whole IT-landscape of a certain CIO area. There are metrics used which allow the identification of transformation objects and these will be reworked in different structures by using architectural principles and then integrated into EA. Finally the existing EA will be evaluated (together with transformation object) by EA design principles and either the transformation will be rejected or design principles will be adopted. In order to make this model operative it is embedded in an architecture organizational structure which is independent from the organizational structure of the enterprise.
- KonferenzbeitragA survival analysis of application life spans based on enterprise architecture models(Enterprise modelling and information systems architectures, 2009) Aier, Stephan; Buckl, Sabine; Franke, Ulrik; Gleichauf, Bettina; Johnson, Pontus; Närman, Per; Schweda, Christian M.; Ullberg, JohanModern enterprises face the challenge to survive in an ever changing environment. One commonly accepted means to address this challenge and further enhance survivability is enterprise architecture (EA) management, which provides a holistic model-based approach to business/IT alignment. Thereby, the decisions taken in the context of EA management are based on accurate documentation of IT systems and business processes. The maintenance of such documentation causes high investments for enterprises, especially in the absence of information on the change rates of different systems and processes. In this paper we propose a method for gathering and analyzing such information. The method is used to analyze the life spans of the application portfolio of three companies from different industry sectors. Based on the results of the three case studies implications and limitations of the method are discussed.
- KonferenzbeitragTowards a more integrated EA planning: linking transformation planning with evolutionary change(Enterprise modelling and information systems architectures (EMISA 2011), 2011) Aier, Stephan; Buckl, Sabine; Gleichauf, Bettina; Matthes, Florian; Schweda, Christian M.; Winter, RobertEnterprises are subject to continuous change driven by top-down planned transformation projects as well as by bottom-up initiatives realizing what is called the evolution of the enterprise. Enterprise architecture (EA) planning presents itself as a means for facilitating and controlling this change. Nevertheless, the methods and models of EA planning developed in recent years either have a strong focus on planned (proactive) transformations or on guided (reactive) evolution. In this paper, we outline an EA planning method that accounts for both types of enterprise change by illustrating the interplay of EA planning, requirements, release, and synchronization management. Specifically we focus on the coordination of design activities modeled as intermeshed closed-loop control systems and on an integrated information model describing EA transformation planning.