Conference Paper

A Contingency Approach to Enterprise Architecture Method Engineering

DOI: 10.1007/978-3-642-01247-1_39 Conference: 3rd Workshop on Trends in Enterprise Architecture Research (TEAR 2008) at the 6th International Conference on Service Oriented Computing (ICSOC 2008), At Sydney, Volume: LNCS 5472
Source: DBLP

ABSTRACT

Enterprise Architecture (EA) and methods for the design and em- ployment of EA significantly contribute to the transparency, consistency and eventually to the flexibility of an organization. However, there is hardly any "one-size-fits-all" EA method that is equally effective for a broad range of transformation projects or in a large number of different contexts. Based on an empirical analysis, this paper identifies three relevant EA contingency factors as well as three dominating EA application scenarios as a basis for a situational EA method engineering taking these into account.

Download full-text

Full-text

Available from: Stephan Aier, Aug 26, 2014
    • "Enterprise Modelling aims to capture the essentials of a business, its IT and its evolution, and to support analysis of this information using a coherent whole of principles, methods, and models in the design and realisation of an enterprise's organizational structure, business processes, information systems and infrastructure [13]. Examples of analysis possible using EA include: strategic planning , process optimisation, alignment between business functions and IT systems and business change for describing the current state of a business (as-is) and a desired state of a business (to-be) [14] [15] [16] [17] [18] [3]. As noted in section 1, of particular interest to the MDO is the historically thorny but important issue of business and IT alignment. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Modern organizations are faced with the need to rapidly respond to frequent changes arising from external business pressures. There has been little attempt to apply model driven principles to addressing these issues. We present a vision of a Model Driven Organisation (MDO) that is based on the use of modelling languages to provide usable abstractions for understanding business contexts and goals, through to specifying IT systems, and ultimately to adapting deployed systems. The paper motivates the problem, proposes the MDO and analyses its requirements for large numbers of tightly integrated domain specific languages.
    No preview · Conference Paper · Jul 2013
  • Source
    • "An EA repository can support different methodologies and modeling approaches (Schekkerman, 2006, p.202). EA governance: Recent studies have emphasized the importance of formalizing EAM procedures in corporate governance (Boh & Yellin, 2006; Schmidt & Buxmann, 2010; Riege & Aier, 2009; Iyer & Gottlieb, 2004; Winter & Schelp, 2008). A centralized governance structure is required to ensure concordance of different architectural layers and to oversee EAM quality (Boh & Yellin, 2006; Radeke, 2011). "
    [Show abstract] [Hide abstract]
    ABSTRACT: Despite the increasing popularity of enterprise architecture management (EAM) in practice, many EAM initiatives either do not fully meet the expected targets or fail. EAM frameworks have been suggested as guidelines to EAM implementation, but our experience indicates that very few companies follow the steps prescribed by such frameworks. Motivated by the diverse approaches that we have observed in practice, our research strives for a broader understanding of how companies adopt EAM in their organizations. We address two questions: (1) Which approaches do companies take in adopting EAM? (2) What factors influence EAM adoption? To answer these questions, we developed an analysis framework to conceptualize EAM adoption and its contextual factors. Based on a set of eight case studies, we explore situational EAM designs and derive four EAM archetypes, which illustrate very diverse EAM adoption approaches in different situations. Our research helps broaden knowledge of EAM adoption by considering multi-dimensional and context-dependent EAM designs. It thereby relativizes the importance of frameworks and modeling, which we find over-emphasized in existing EA research. Our findings also offer starting points for prescriptive EAM research, supporting the successful introduction of EAM in organizations by taking contingencies into account.
    Full-text · Conference Paper · Jan 2012
  • Source
    • "A key objective of EA is being able to provide a holistic understanding of all aspects of a business, connecting the business drivers and the surrounding business environment, through the business processes, organizational units, roles and responsibilities, to the underlying IT systems that the business relies on. In addition to presenting a coherent explanation of the what, why and how of a business, EA aims to support specific types of business analysis including [11], [12], [13], [14], [15]: alignment between business functions and IT systems; business change describing the current state of a business (as-is) and a desired state of a business (tobe ); maintenance the de-installation and disposal, upgrading, procurement and integration of systems including the prioritization of maintenance needs; quality by managing and determining the quality attributes for aspects of the business such as security, performance to ensure a certain level of quality to meet the needs of the business; acquisition and mergers describing the alignment of businesses and the effect on both when they merge; compliance in terms of a regulatory framework, e.g. Sarbanes-Oxley; strategic planning including corporate strategy planning, business process optimization, business continuity planning, IT management. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Enterprise Architecture (EA) Modelling aims to analyze an organization in terms of its components, IT systems and business processes. Current modelling approaches are based on Service Oriented Architecture (SOA) whereby components publish interfaces of operations that are used via message passing. It has been argued that SOA leads to tight coupling between components and does not handle complex component interactions, with resulting maintenance difficulties. Event Driven Architecture (EDA) is an alternative strategy, based on listening for events, that is designed to address SOA shortcomings. However, there are no EA modelling technologies based on EDA. This paper reviews EA, SOA and EDA, identifies EDA characteristic features and proposes modelling and simulation technologies that are introduced through a simple case study.
    Full-text · Conference Paper · Dec 2011
Show more