Enterprise Architecture In Organizations Research Articles

The theoretical basis of enterprise architecture: A critical review and taxonomy of relevant theories

Enterprise architecture is a collection of artifacts describing various aspects of an organization from an integrated business and IT perspective. Practicing enterprise architecture in organizations implies using these artifacts to facilitate information systems planning and improve business and IT alignment. Despite its long history, the enterprise architecture discipline still remains largely atheoretical and lacks a solid theoretical basis. Based on our previous empirical studies of the practical usage of enterprise architecture artifacts in multiple organizations and broad literature analysis, this conceptual article identifies and discusses in detail 10 theories that can be considered key for understanding how an enterprise architecture practice works: actor-network theory, boundary objects theory, cognitive fit theory, communities of practice theory, decision-making theories, information processing theory, knowledge management theory, management fashion theory, media richness theory, and uncertainty principle. Taken together, these theories offer a comprehensive theoretical view of an enterprise architecture practice explaining the role of enterprise architecture artifacts, their usability, and participation of stakeholders and, therefore, may constitute a theoretical basis of the entire enterprise architecture discipline. Although this article does not elaborate on any of these theories, it brings these theories to light, establishes their critical importance for comprehending an enterprise architecture practice, and positions them as central to the enterprise architecture discourse. Each of these theories can be leveraged by enterprise architecture scholars in their future studies for analyzing enterprise architecture practices through respective theoretical lenses. This article intends to provide fresh theoretical insights on enterprise architecture, spark new waves of theoretical enterprise architecture research, and contribute to the development of a sound theoretical foundation for the enterprise architecture discipline.

Enterprise Architecture Planning Using TOGAF Version 9 (Case Study Of Badan Pengelolaan Pendapatan Daerah Kab.Sumedang)

Bappenda currently utilizes Information Systems as the main driver in its activities which include the process of registration, data collection, determination, acceptance, billing, and reporting, in supporting its activities Bappenda needs to have an Information System strategic planning that can identify computer-based application portfolios in carrying out business processes, by therefore we need a tool that can be used to provide a basic organizational structure for the company as a whole using Enterprise Architecture. The method used in architectural planning is The Open Group Architecture Framework (TOGAF), which can provide techniques on how to build, manage and implement enterprise architecture and information systems called the Architecture Development Method (ADM). Based on the results of the study, it can be concluded that the application of the TOGAF method in Bappenda can improve the performance of the system applied by a percentage of 57.29%. The suggestion for implementing TOGAF in Bappenda is to be able to develop gradually according to the existing stages in TOGAF and explain how to find an organization's enterprise architecture specifically based on business needs and processes

From enterprise architecture to business models and back

In this study, we argue that important IT change processes affecting an organization's enterprise architecture are also mirrored by a change in the organization's business model. An analysis of the business model may establish whether the architecture change has value for the business. Therefore, in order to facilitate such analyses, we propose an approach to relate enterprise models specified in ArchiMate to business models, modeled using Osterwalder's Business Model Canvas. Our approach is accompanied by a method that supports business model-driven migration from a baseline architecture to a target architecture and is demonstrated by means of a case study.

A Service Identification Method Based on Enterprise Ontology In Service Oriented Architecture

Service Identification is one of the important and first activities in SOA analysis and design phase. Factors that affect Service Identification include the wide range of business concepts and elements; so different service identification methods, concentrating on special conceptual definition of service, use special element and concept of business domain. Enterprise Ontology is one way to unique understanding of business concepts and provide an explicit and clear description of different elements, concepts and components of businesses. In this paper we try introduce a new Service Identification method using Enterprise Ontology as a codified and integrated semantic framework to recognize effective elements and factors in Service Identification context. By using Enterprise Ontology in service identification, In comparison with other service identification methods, different semantic aspect of service and a lot of effective business element and concept for service identification are considered. In our proposed method, we’ve applied some parts of an enterprise ontology that are used in military organization Enterprise Architecture.

Business Security Architecture: Weaving Information Security into Your Organization's Enterprise Architecture through SABSA®

ABSTRACT Information security is an imperative factor in organizational success, driven by the need to protect information assets. The continuous evolution of external and internal threats and the associated need to protect and secure information from exploitation of vulnerabilities has become a struggle for many organizations in both the public and private sectors. This struggle is the direct result of the narrow focus on operational security. Just as the lines between business and information technology have disappeared, so have the lines between business and information security. Some organizations simply “check the box” by performing the minimum actions required to pass or meet mandated compliance standards. Without practicing due diligence and by only meeting the minimum requirements, leads to the reactive response of exploited vulnerabilities in addition to the increase of after the fact incident investigations. Organizations need to take a proactive approach using established methodologies known to incorporate security into information technologies and systems. The Sherwood Applied Business Security Architecture (SABSA) is a solution oriented methodology for any business enterprise that seeks to enable its information infrastructure by applying security solutions within every layer of the organization. This article describes how SABSA can be integrated into organizations' existing architectures utilizing organizational business drivers.

Measurement of enterprise architecture readiness within organizations

PurposeThe purpose of this paper is to present a model for measuring enterprise architecture (EA) readiness in organizations.Design/methodology/approachThis paper reviews the literature of enterprise architecture, defines and extracts factors and indicators of enterprise architecture readiness with factor weighting and indicators. Thereafter the authors propose a model to measure organization EA readiness in practice.FindingsIn this paper nine factors and 34 indicators that affect enterprise architecture are defined and an enterprise architecture readiness model is constructed. The model of research is practical, because it specifies readiness of organization in enterprise architecture and helps to define current state of organization via factors and indicators, and from priorities of factors and indicators, alerts organization of an optimization strategy.Research limitations/implicationsIn order to increase the utility of the model for use in other organizations, further studies can help to refine the model.Originality/valueThe essence of extracting and choosing factors and indicators in this study is from enterprise architecture processes and key success and failure factors of enterprise architecture in organizations. In addition selected factors and indicators related to organization infrastructure not related only to enterprise architecture project planning and executing are examined through the use of a questionnaire. The model derived from this study can be utilized as a multi‐dimensional and practical model because of its complexity and examination of organizational infrastructures.

IT Outsourcing Impacts on Enterprise Architecture

Enterprises outsource IT for many reasons, such as reducing costs, shedding of overhead functions that divert management attention away from the core business, and obtaining services from industry leaders specializing in the associated competencies. IT sourcing profoundly impacts the client organization's enterprise architecture. In an outstanding scenario, IT services come from an external services provider. Moreover, the client and vendor interact through an interorganizational interface containing operational, technical, and business components. This interface involves two major modes of interaction: delivery of the IT services and the service-management framework. The interface describes all of the processes, procedures, and protocols that the client and provider use to interact. Because enterprise architectures are unique to organizations, designing this interface might involve customization. For a large, complex client enterprise, bringing the business, operational, and technical components of the interface into alignment is often a nontrivial challenge