Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes." [1]
The United States Federal Government is an example of an organization that practices EA, in this case with its Capital Planning and Investment Control processes. [2] Companies such as Independence Blue Cross, Intel, Volkswagen AG, [3] and InterContinental Hotels Group also use EA to improve their business architectures as well as to improve business performance and productivity. Additionally, the Federal Enterprise Architecture's reference guide aids federal agencies in the development of their architectures. [4]
As a discipline, EA "proactively and holistically lead[s] enterprise responses to disruptive forces by identifying and analyzing the execution of change" towards organizational goals. EA gives business and IT leaders recommendations for policy adjustments and provides best strategies to support and enable business development and change within the information systems the business depends on. EA provides a guide for decision making towards these objectives. [5] The National Computing Centre's EA best practice guidance states that an EA typically "takes the form of a comprehensive set of cohesive models that describe the structure and functions of an enterprise. The individual models in an EA are arranged in a logical manner that provides an ever-increasing level of detail about the enterprise." [6]
Important players within EA include enterprise architects and solutions architects. Enterprise architects are at the top level of the architect hierarchy, meaning they have more responsibilities than solutions architects. While solutions architects focus on their own relevant solutions, enterprise architects focus on solutions for and the impact on the whole organization. Enterprise architects oversee many solution architects and business functions. As practitioners of EA, enterprise architects support an organization's strategic vision by acting to align people, process, and technology decisions with actionable goals and objectives that result in quantifiable improvements toward achieving that vision. The practice of EA "analyzes areas of common activity within or between organizations, where information and other resources are exchanged to guide future states from an integrated viewpoint of strategy, business, and technology." [7]
The term enterprise can be defined as an organizational unit, organization, or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers. [8] In that sense, the term enterprise covers various types of organizations, regardless of their size, ownership model, operational model, or geographical distribution. It includes those organizations' complete sociotechnical system, [9] including people, information, processes, and technologies. Enterprise as a sociotechnical system defines the scope of EA.
The term architecture refers to fundamental concepts or properties of a system in its environment; and embodied in its elements, relationships, and in the principles of its design and evolution. [10] A methodology for developing and using architecture to guide the transformation of a business from a baseline state to a target state, sometimes through several transition states, is usually known as an enterprise architecture framework. A framework provides a structured collection of processes, techniques, artifact descriptions, reference models, and guidance for the production and use of an enterprise-specific architecture description.[ citation needed ]
Paramount to changing the EA is the identification of a sponsor. Their mission, vision, strategy, and the governance framework define all roles, responsibilities, and relationships involved in the anticipated transformation. Changes considered by enterprise architects typically include innovations in the structure or processes of an organization; innovations in the use of information systems or technologies; the integration and/or standardization of business processes; and improvement of the quality and timeliness of business information.[ citation needed ]
According to the standard ISO/IEC/IEEE 42010, [10] the product used to describe the architecture of a system is called an architectural description. In practice, an architectural description contains a variety of lists, tables, and diagrams. These are models known as views . In the case of EA, these models describe the logical business functions or capabilities, business processes, human roles and actors, the physical organization structure, data flows and data stores, business applications and platform applications, hardware, and communications infrastructure. [11]
The first use of the term "enterprise architecture" is often incorrectly attributed to John Zachman's 1987 A framework for information systems architecture. [12] The first publication to use it was instead a National Institute of Standards (NIST) Special Publication [13] on the challenges of information system integration.[ citation needed ] The NIST article describes EA as consisting of several levels. Business unit architecture is the top level and might be a total corporate entity or a sub-unit. It establishes for the whole organization necessary frameworks for "satisfying both internal information needs" as well as the needs of external entities, which include cooperating organizations, customers, and federal agencies. The lower levels of the EA that provide information to higher levels are more attentive to detail on behalf of their superiors. In addition to this structure, business unit architecture establishes standards, policies, and procedures that either enhance or stymie the organization's mission. [13]
The main difference between these two definitions is that Zachman's concept was the creation of individual information systems optimized for business, while NIST's described the management of all information systems within a business unit. The definitions in both publications, however, agreed that due to the "increasing size and complexity of the [i]mplementations of [i]nformation systems... logical construct[s] (or architecture) for defining and controlling the interfaces and... [i]ntegration of all the components of a system" is necessary. Zachman in particular urged for a "strategic planning methodology." [12]
Within the field of enterprise architecture, there are three overarching schools: Enterprise IT Design, Enterprise Integrating, and Enterprise Ecosystem Adaption. Which school one subscribes to will impact how they see the EA's purpose and scope, as well as the means of achieving it, the skills needed to conduct it, and the locus of responsibility for conducting it. [14]
Under Enterprise IT Design, the main purpose of EA is to guide the process of planning and designing an enterprise's IT/IS capabilities to meet the desired organizational objectives, often by greater alignment between IT/IS and business concerns. Architecture proposals and decisions are limited to the IT/IS aspects of the enterprise and other aspects service only as inputs. The Enterprise Integrating school believes that the purpose of EA is to create a greater coherency between the various concerns of an enterprise (HR, IT, Operations, etc.), including the link between strategy formulation and execution. Architecture proposals and decisions here encompass all aspects of the enterprise. The Enterprise Ecosystem Adaption school states that the purpose of EA is to foster and maintain the learning capabilities of enterprises so they may be sustainable. Consequently, a great deal of emphasis is put on improving the capabilities of the enterprise to improve itself, to innovate, and to coevolve with its environment. Typically, proposals and decisions encompass both the enterprise and its environment.
The benefits of EA are achieved through its direct and indirect contributions to organizational goals. [15] Notable benefits include support in the areas related to design and re-design of the organizational structures during mergers, acquisitions, or general organizational change; [16] [17] [18] [19] enforcement of discipline and business process standardization, and enablement of process consolidation, reuse, and integration; [20] [21] support for investment decision-making and work prioritization; [17] [22] [18] enhancement of collaboration and communication between project stakeholders and contribution to efficient project scoping and to defining more complete and consistent project deliverabless; [19] [20] and an increase in the timeliness of requirements elicitation and the accuracy of requirement definitions through publishing of the EA documentation. [23]
Other benefits include contribution to optimal system designs and efficient resource allocation during system development and testing; [17] [18] enforcement of discipline and standardization of IT planning activities and contribution to a reduction in time for technology-related decision making; [18] [21] reduction of the system's implementation and operational costs, and minimization of replicate infrastructure services across business units; [21] [24] reduction in IT complexity, consolidation of data and applications, and improvement of interoperability of the systems; [20] [21] [24] more open and responsive IT as reflected through increased accessibility of data for regulatory compliance, and increased transparency of infrastructure changes; [21] [25] and a reduction of business risks from system failures and security breaches. EA also helps reduce risks of project delivery. [21] [26] Establishing EA as an accepted, recognized, functionally integrated and fully involved concept at operational and tactical levels is one of the biggest challenges facing Enterprise Architects today and one of the main reasons why many EA initiatives fail. [27]
A key concern about EA has been the difficulty in arriving at metrics of success because of the broad-brush and often opaque nature of EA projects. [28] Additionally, there have been a number of reports, including those written by Ivar Jacobson, [29] Gartner, [30] Erasmus University Rotterdam and IDS Scheer, [31] Dion Hinchcliffe, [32] and Stanley Gaver, [33] that argue that the frequent failure of EA initiatives makes the concept not worth the effort and that the methodology will fade out quickly.
According to the Federation of Enterprise Architecture Professional Organizations (FEAPO), EA interacts with a wide array of other disciplines commonly found in business settings such as performance engineering and management, process engineering and management, IT and enterprise portfolio management, governance and compliance, IT strategic planning, risk analysis, information management, metadata management, organization development, design thinking, systems thinking, and user experience design. [1] [34] [35] [36] The EA of an organization is too complex and extensive to document in its entirety, so knowledge management techniques provide a way to explore and analyze these hidden, tacit, or implicit areas. In return, EA provides a way of documenting the components of an organization and their interaction in a systemic and holistic way that complements knowledge management. [37]
In various venues, [38] EA has been discussed as having a relationship with Service Oriented Architecture (SOA), a particular style of application integration. Research points to EA promoting the use of SOA as an enterprise-wide integration pattern. [39] [40] The broad reach of EA has resulted in this business role being included in the information technology governance processes of many organizations. Analyst firm Real Story Group suggested that EA and the emerging concept of the digital workplace are "two sides to the same coin." [41] The Cutter Consortium described EA as an information and knowledge-based discipline. [42]
Media related to Enterprise architecture at Wikimedia Commons
Quotations related to Enterprise architecture at Wikiquote
The dictionary definition of enterprise architecture at Wiktionary
The Zachman Framework is an enterprise ontology and is a fundamental structure for enterprise architecture which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications. The first are primitive interrogatives: What, How, When, Who, Where, and Why. The second is derived from the philosophical concept of reification, the transformation of an abstract idea into an instantiation. The Zachman Framework reification transformations are: identification, definition, representation, specification, configuration and instantiation.
The Open Group Architecture Framework (TOGAF) is the most used framework for enterprise architecture as of 2020 that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. TOGAF is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.
A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.
Unicom System Architect is an enterprise architecture tool that is used by the business and technology departments of corporations and government agencies to model their business operations and the systems, applications, and databases that support them. System Architect is used to build architectures using various frameworks including TOGAF, ArchiMate, DoDAF, MODAF, NAF and standard method notations such as sysML, UML, BPMN, and relational data modeling. System Architect is developed by UNICOM Systems, a division of UNICOM Global, a United States-based company.
Data architecture consist of models, policies, rules, and standards that govern which data is collected and how it is stored, arranged, integrated, and put to use in data systems and in organizations. Data is usually one of several architecture domains that form the pillars of an enterprise architecture or solution architecture.
An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models – typically matrices and diagrams – for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.
Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.
John A. Zachman is an American business and IT consultant, early pioneer of enterprise architecture, chief executive officer of Zachman International, and originator of the Zachman Framework.
Information Framework (IFW) is an enterprise architecture framework, populated with a comprehensive set of banking-specific business models. It was developed as an alternative to the Zachman Framework by Roger Evernden.
Business–IT alignment is a process in which a business organization uses information technology (IT) to achieve business objectives, such as improved financial performance or marketplace competitiveness. Some definitions focus more on outcomes that means ; for example,
Alignment is the capacity to demonstrate a positive relationship between information technologies and the accepted financial measures of performance.
In information systems, applications architecture or application architecture is one of several architecture domains that form the pillars of an enterprise architecture (EA).
Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.
A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of the whole system from the perspective of a related set of concerns.
Treasury Enterprise Architecture Framework (TEAF) was an enterprise architecture framework for treasury, based on the Zachman Framework. It was developed by the US Department of the Treasury and published in July 2000. May 2012 this framework has been subsumed by evolving Federal Enterprise Architecture Policy as documented in "The Common Approach to Federal Enterprise Architecture".
FDIC Enterprise Architecture Framework was the enterprise architecture framework of the United States Federal Deposit Insurance Corporation (FDIC). A lot of the current article is about the enterprise architecture framework developed around 2005, and currently anno 2011 out-of-date.
Enterprise architecture planning (EAP) in enterprise architecture is the planning process of defining architectures for the use of information in support of the business and the plan for implementing those architectures.
NIST Enterprise Architecture Model is a late-1980s reference model for enterprise architecture. It defines an enterprise architecture by the interrelationship between an enterprise's business, information, and technology environments.
Sparx Systems Enterprise Architect is a visual modeling and design tool based on the OMG UML. The platform supports: the design and construction of software systems; modeling business processes; and modeling industry based domains. It is used by businesses and organizations to not only model the architecture of their systems, but to process the implementation of these models across the full application development life-cycle.
Roger Evernden is a British enterprise architect, musician, composer, and writer. He is a consultant at the Cutter Consortium, known for his contributions to Enterprise Architecture and as author of the Information FrameWork, an enterprise architecture framework presented in 1996 as a more generic alternative to the Zachman Framework. He has given talks on enterprise architecture.
The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.
| Authority control databases: National |
|---|
