Enterprise architecture framework

NIST Enterprise Architecture Model initiated in 1989, one of the earliest frameworks for enterprise architecture.[1]

An enterprise architecture framework (EA 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.

Overview

Enterprise architecture regards the enterprise as a large and complex system or system of systems.[2] To manage the scale and complexity of this system, an architectural framework provides tools and approaches that help architects abstract from the level of detail that builders work at to bring enterprise design tasks into focus and produce valuable architecture description documentation.

The components of an architecture framework provide structured guidance that is divided into three main areas:[3]

History

Overview of Enterprise Architecture Frameworks evolution (1987–2003).[3][4] On the left: The Zachman Framework 1987, NIST Enterprise Architecture 1989, EAP 1992, TISAF 1997, FEAF 1999 and TEAF 2000. On the right: TAFIM influenced by POSIX, JTA, JTAA, TOGAF 1995, DoD TRM[5] and C4ISR 1996, and DoDAF 2003.

Since the 1970s people working in IS/IT have looked for ways to engage business people – to enable business roles and processes - and to influence investment in business information systems and technologies – with a view to the wide and long term benefit of the enterprise. Many of the aims, principles, concepts and methods now employed in EA frameworks were established in the 1980s, and can be found in IS and IT architecture frameworks published in that decade and the next.[6]

By 1980, IBM’s Business Systems Planning (BSP) was promoted as a method for analyzing and designing an organization’s information architecture, with the goals:

  1. understand the issues and opportunities with the current applications and technical architecture;
  2. develop a future state and migration path for the technology that supports the enterprise;
  3. provide business executives with a direction and decision making framework for IT capital expenditures;
  4. provide information system (IS) with a blueprint for development.

In 1982, when working for IBM and with BSP, John Zachman was perhaps the first to mention Enterprise Architecture in the public domain. Then and in later papers, Zachman used the word enterprise as a synonym for business. "Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures." [7]

In 1987, Zachman published a paper, A Framework for Information Systems Architecture.[8] The paper provided a classification scheme for artifacts that describe (at several levels of abstraction) the what, how, where, who, when and why of information systems. Given IBM already employed BSP, Zachman had no need to provide planning process. The paper did not mention enterprise architecture.

In 1989, the National Institute of Standards and Technology (NIST) published the NIST Enterprise Architecture Model. This was a five-layer reference model that illustrates the interrelationship of business, information system, and technology domains. It was promoted within the U.S. federal government. It was not an EA framework as we see it now, but it helped to establish the notion of dividing EA into architecture domains or layers.

In 1992, a paper by Zachman and Sowa [9] started thus "John Zachman introduced a framework for information systems architecture (ISA) that has been widely adopted by systems analysts and database designers." The term enterprise architecture did not appear. The paper was about using the ISA framework to describe, “...the overall information system and how it relates to the enterprise and its surrounding environment.” The word enterprise was used as a synonym for business.

In 1993, Stephen Spewak’s book Enterprise Architecture Planning (EAP) defined a process for defining architectures for the use of information in support of the business and the plan for implementing those architectures. The business mission is the primary driver. Then the data required to satisfy the mission. Then the applications built to store and provide that data. Finally the technology to implement the applications. Enterprise Architecture Planning is a data-centric approach to architecture planning. An aim is to improve data quality, access to data, adaptability to changing requirements, data interoperability and sharing, and cost containment.

In 1994, the Open Group selected TAFIM from the US DoD as a basis for development of The Open Group Architecture Framework (TOGAF), where architecture meant IT architecture. TOGAF started out taking a strategic and enterprise-wide, but technology-oriented, view. It emerged from the desire to rationalize a messy IT estate. Right up to version 7, TOGAF was still focused on defining and using a Technical Reference Model (or foundation architecture) to define the platform services required from the technologies that an entire enterprise uses to support business applications.[6]

In 1996, the US IT Management Reform Act, more commonly known as the Clinger-Cohen Act, repeatedly directed that a US federal government agency’s investment in IT must be mapped to identifiable business benefits. In addition, it made the agency CIO responsible for, “...developing, maintaining and facilitating the implementation of a sound and integrated IT architecture for the executive agency.”

By 1997, Zachman had renamed and refocused his ISA framework as an EA framework; it remained a classification scheme for descriptive artifacts, not a process for planning systems or changes to systems.

In 1998, The Federal CIO Council began developing the Federal Enterprise Architecture Framework (FEAF) in accordance with the priorities enunciated in Clinger-Cohen and issued it in 1999. FEAF was a process much like TOGAF’s ADM, in which “The architecture team generates a sequencing plan for the transition of systems, applications, and associated business practices predicated upon a detailed gap analysis [between baseline and target architectures].”

In 2001, the US Chief CIO council published A practical guide to Federal Enterprise Architecture, which starts, “An enterprise architecture (EA) establishes the Agency-wide roadmap to achieve an Agency’s mission through optimal performance of its core business processes within an efficient information technology (IT) environment." At that point, the processes in TOGAF, FEAF, EAP and BSP were clearly related.

In 2002/3, in its Enterprise Edition, TOGAF 8 shifted focus from the technology architecture layer to the higher business, data and application layers. It introduced structured analysis, after Information Engineering, which features, for example, mappings of organization units to business functions and data entities to business functions. Today, business functions are often called business capabilities. And many enterprise architects regard their business function/capability hierarchy/map as the fundamental Enterprise Architecture artifact. They relate data entities, use cases, applications and technologies to the functions/capabilities.

In 2006, the popular book Enterprise Architecture As Strategy [10] reported the results of work by MIT’s Center for Information System Research. This book emphasises the need for enterprise architects to focus on core business processes ("Companies excel because they've [decided] which processes they must execute well, and have implemented the IT systems to digitise those processes.") and to engage business managers with the benefits that strategic cross-organisational process integration and/or standardisation could provide.

A 2008 research project for the development of professional certificates in enterprise and solution architecture by the British Computer Society (BCS) showed that enterprise architecture has always been inseparable from information system architecture, which is natural, since business people need information to make decisions and carry out business processes.[6]

In 2011, the TOGAF 9.1. specification says: "Business planning at the strategy level provides the initial direction to enterprise architecture."[11] Normally, the business principles, business goals, and strategic drivers of the organization are defined elsewhere.[6] In other words, Enterprise Architecture is not a business strategy, planning or management methodology. Enterprise Architecture strives to align business information systems technology with given business strategy, goals and drivers. The TOGAF 9.1 specification clarified, that, "A complete enterprise architecture description should contain all four architecture domains (business, data, application, technology), but the realities of resource and time constraints often mean there is not enough time, funding, or resources to build a top-down, all-inclusive architecture description encompassing all four architecture domains, even if the enterprise scope is [...] less than the full extent of the overall enterprise."[12]

In 2013, TOGAF[13] is the most popular Architecture framework (judged by published certification numbers) that some assume it defines EA.[6] However, some still use the term Enterprise Architecture as a synonym for Business Architecture, rather than covering all four architecture domains - business, data, applications and technology.

EA framework topics

Artist impression.[14]

Architecture and building governance

People who remodel a home are aware that the architect produces detailed drawings that specify plumbing, electrical, and building construction information for the entire structure. The architect responsible for the design produces (or oversees others who produce) blueprints for each phase of the project—from structural changes to size and layout of rooms. Moreover, to successfully complete the project, the architect operates within a framework of building codes. City or county inspections ensure the work complies with building codes.

Enterprise architecture works in a similar manner.[14] An architecture description document can be thought of as the blueprint for the procurement and realization of a system. But an enterprise architecture includes more than just an abstract description of the system's structure and behavior. It includes also principles, policies and standards (akin to building codes) that ensure that systems are soundly constructed. Governance of the enterprise architecture and of its implementation requires organization and processes (akin to city and county inspectors and the processes for checking building improvement projects).

Architecture domain

Layers of the enterprise architecture.[15]

Since Stephen Spewak's Enterprise Architecture Planning (EAP) in 1993, and perhaps before then, it has been normal to divide enterprisesss architecture into four architecture domain.

Note that the applications architecture is about the choice of and relationships between applications in the enterprise's application portfolio, not about the internal architecture of a single application (which is often called application architecture).

Many EA frameworks combine data and application domains into a single (digitized) information system layer, sitting below the business (usually a human activity system) and above the technology (the platform IT infrastructure).

Layers of the enterprise architecture

Example of the federal enterprise architecture, which has defined five architectural layers.[16]

For many years, it has been common to regard the architecture domains as layers, with the idea that each layer contains components that execute processes and offer services to the layer above. This way of looking at the architecture domains was evident in TOGAF v1 (1996), which encapsulated the technology component layer behind the platform services defined in the "Technical Reference Model" - very much according to the philosophy of TAFIM and POSIX.

The view of architecture domains as layers can be presented thus:

Each layer delegates work to the layer below. In each layer, the components, the processes and the services can be defined at a coarse-grained level and decomposed into finer-grained components, processes and services. The graphic shows a variation on this theme.

Components of enterprise architecture framework

In addition to three major framework components discussed above.

  1. Description advice: some kind of Architecture Artifacts Map or Viewpoint Library
  2. Process advice: some kind of Architecture Development Method, with supporting guidance.
  3. Organization advice: including an EA Governance Model

An Ideal EA Framework should feature:

  1. Business Value Measurement Metrics
  2. EA Initiative Model
  3. EA Maturity Model
  4. Enterprise Communication Model

Most modern EA Frameworks (e.g. TOGAF, ASSIMPLER, EAF) include most of the above. Zachman has always focused on architecture description advice.

Enterprise architecture domains and subdomains

Enterprise architecture reference architecture with sub domains

The application and technology domains (not to be confused with business domains) are characterized by domain capabilities and domain services. The capabilities are supported by the services. The application services are also referred to in service-oriented architecture (SOA). The technical services are typically supported by software products.

The data view starts with the data classes which can be decomposed into data subjects which can be further decomposed into data entities. The basic data model type which is most commonly used is called merda (master entity relationship diagrams assessment, see entity-relationship model). The Class, subject and entity forms a hierarchical view of data. Enterprises may have millions of instances of data entities.

The Enterprise Architecture Reference Traditional Model offers clear distinction between the architecture domains (business, information/data, application/integration and technical/infrastructure). These domains can be further divided into Sub domain disciplines. An example of the EA domain and sub domains is in the image on the right.

Many enterprise architecture teams consist of Individuals with Skills aligned with the Enterprise Architecture Domains and sub-domain disciplines. Here are some examples: enterprise business architect, enterprise documentational architect, enterprise application architect, enterprise infrastructure architect, enterprise information architect, etc.

An example of the list of reference architecture patterns in the application and information architecture domains are available at Architectural pattern (computer science).

View model

Illustration of the 4+1 view model of architecture.

A view model is a framework that defines the set of views or approaches used in systems analysis, systems design, or the construction of an enterprise architecture.

Since the early 1990s there have been a number of efforts to define standard approaches for describing and analyzing system architectures. Many of the recent Enterprise Architecture frameworks have some kind of set of views defined, but these sets are not always called view models.

Standardization

Perhaps the best-known standard in the field of software architecture and system architecture started life as IEEE 1471, an IEEE Standard for describing the architecture of a software-intensive system approved in 2000.

In its latest version, the standard is published as ISO/IEC/IEEE 42010:2011. The standard defines an architecture framework as conventions, principles and practices for the description of architectures established within a specific domain of application and/or community of stakeholders, and proposes an architecture framework is specified by:

  1. the relevant stakeholders in the domain,
  2. the types of concerns arising in that domain,
  3. architecture viewpoints framing those concerns and
  4. correspondence rules integrating those viewpoints cited before.

Architecture frameworks conforming to the standard can include additional methods, tools, definitions, and practices beyond those specified.

Types of enterprise architecture framework

Just a few of the Enterprise Architecture frameworks utilized today, 2011[17]

Nowadays there are now countless EA frameworks, many more than in the following listing.

Consortia-developed frameworks

Defense industry frameworks

Government frameworks

Open-source frameworks

Enterprise architecture frameworks that are released as open source:

Proprietary frameworks

See also

Wikimedia Commons has media related to Enterprise architecture.

References

  1. ↑ The Chief Information Officers Council (1999). Federal Enterprise Architecture Framework Version 1.1. September 1999.
  2. ↑ The Open Group (2008) TOGAF Version 9. Van Haren Publishing, 1 nov. 2008.p. 73
  3. 1 2 Stephen Marley (2003). Architectural Framework. NASA /SCI. At Webarchive.org, retrieved 3-04-2015.
  4. ↑ Jaap Schekkerman (2004) How to Survive in the Jungle of Enterprise Architecture Frameworks. p.89 gives a similar scheme.
  5. ↑ US Department of Defense (2001) Department of Defense Technical Reference Model. Version 2.0. 9 April 2001. p. 11, mentioned that also the DoD TRM is influenced by POSIX.
  6. 1 2 3 4 5 Graham Berrisford (2008-13) "A brief history of EA: what is in it and what is not" on grahamberrisford.com, last update 16/07/2013. Accessed 16/07?2003
  7. ↑ John Zachman (1982) Business Systems Planning and Business Information Control Study: A comparison in IBM Systems Journal 21(1). p32.
  8. ↑ John A. Zachman (1987). A Framework for Information Systems Architecture. In: IBM Systems Journal, vol 26, no 3. IBM Publication G321-5298.
  9. ↑ Zachman and Sowa (1992) Extending and formalising the framework of information systems architecture IBM Systems Journal, Vol 31, No 3
  10. ↑ Jeanne W. Ross, Peter Weill, and David C. Robertson ( (2006) Enterprise Architecture As Strategy: Creating a Foundation for Business Execution. Harvard Business Review Press
  11. ↑ The Open Group (2011) TOGAF® 9.1 > Part II: Architecture Development Method (ADM) > Preliminary Phase. Accessed July 16, 2013
  12. ↑ The Open Group (2011) TOGAF® 9.1 > Part II: Architecture Development Method (ADM) > Introduction to the ADM. Accessed July 16, 2013
  13. ↑ TOGAF 9.1 White Paper An Introduction to TOGAF Version 9.1 http://www.opengroup.org/togaf/
  14. 1 2 Rob Thomas and Phil Cullen (2001). Building an Enterprise Architecture framework. In: US Customs Today April 2001.
  15. ↑ Niles E Hewlett (2006) , The USDA Enterprise Architecture Program. PMP CEA, Enterprise Architecture Team, USDA-OCIO. January 25, 2006.
  16. ↑ FEA Consolidated Reference Model Document. whitehouse.gov May 2005.
  17. ↑ Dennis E. Wisnosky (2011) Engineering Enterprise Architecture: Call to Action. in: Common Defense Quarterly. January 2011, p. 9
  18. ↑ L.M. Camarinha-Matos, H. Afsarmanesh, Collaborative Networks: Reference Modeling, Springer, 2008.
  19. ↑ L.M. Camarinha-Matos, H. Afsarmanesh, On reference models for collaborative networked organizations, International Journal Production Research, Vol 46, Nº 9, May 2008, pp 2453–2469.
  20. ↑ DNDAF
  21. ↑ "Introducing the European Space Agency Architectural Framework for Space-Based Systems of Systems Engineering - Springer". Link.springer.com. Retrieved 2013-06-16.
  22. ↑ Gianni, D., Lindman, N., Fuchs, J., & Suzic, R. (2012). Introducing the european space agency architectural framework for space-based systems of systems engineering. In Complex Systems Design & Management (pp. 335-346). Springer Berlin Heidelberg.
  23. ↑ US Department of the Treasury Chief Information Officer Council (2000). Treasury Enterprise Architecture Framework. Version 1, July 2000.
  24. ↑ MEGAF
  25. ↑ SABSA
  26. ↑ Avancier Methods (AM)
  27. ↑ Pragmatic EA
  28. ↑ Solution Architecting Mechanism (SAM)
  29. ↑ Tony Shan and Winnie Hua (2006). Solution Architecting Mechanism. Proceedings of the 10th IEEE International EDOC Enterprise Computing Conference (EDOC 2006), October 2006, p23-32.
This article is issued from Wikipedia - version of the Thursday, February 25, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.