Dr. O. Aly
Computer Science

Abstract

The purpose of this project is to discuss Zachman Enterprise Architecture which is also known as the Zachman Framework.  Zachman introduced the concept of architecture in 1987 and compared the framework to the construction architecture which requires components, builders, time frame and so forth.  The framework is not a methodological but a logical framework. It is a two-dimensional framework.  The framework is not a security-based framework.  However, it allows analysis of enterprise to be presented to different groups in the enterprise in ways that relate to the responsibilities of the groups.  A few architectures expanded since the inception of Zachman’s Framework. This project discussed a few of them such as TOGAF, DoDAF, MODAF, SABSA, and CobiT. In brief, the concept of architecture did not exist until the Zachman’s initiative. The architecture concept was limited to building and construction in the Industrial Age. However, in the Information Age, Zachman was inspired to develop an information system architecture and framework for Enterprise.  The application of the architecture concept to the enterprise information system was an innovative idea from Zachman that deserves recognition.

Keywords: Zachman Framework; Zachman Enterprise Architecture.

Introduction

This project discusses the enterprise framework which is developed by Zachman. As indicated in (Zachman, 1987), information system architecture was not significant thirty years ago from the time Zachman started to develop the framework in 1987.  Zachman was inspired to develop such a framework and architecture for the enterprise information system.  This project begins with Zachman Enterprise Architecture, followed by additional frameworks and architectures that appeared and expanded since the inception of Zachman Framework.

Zachman Enterprise Architecture or Zachman’s Framework

In 1987, John A. Zachman published a unique approach to the elements of the information system.  Zachman is often mentioned in the literature as the primary contributor to enterprise architecture.  Zachman (1987) presented a comparison between project design and the implementation using the classical engineering and building constructions, roads, and bridges (Zachman, 1987).  The construction begins with requirements and then the structure to implement these requirements is designed.  Before starting the implementation of a project that is based on stakeholders’ requirement, the design to implement such a project must be developed (Zachman, 1987).   Zachman provided a comparison using a generic set of architectural representations produced during the process of constructing a building, including concepts, work breakdown structure, engineering design, manufacturing engineering, and assembly and fabrication drawings.

The framework for enterprise architecture or as it is called Zachman Framework is a logical structure for classifying and organizing the descriptive representations of the enterprise which are significant to the management and the development of the systems of the enterprise including manual and automated systems (Zachman, 1997).   The generic classification structure of the design artifacts involves questions of what, how, where, who, when and why with various players planner, owner, design, builder, implementer, and operator. The artifacts involve scope, concepts, logic, physics, technology, and product.  It also includes material, process, geometry, instructions, timing, and objectives.  Figure 1 shows the generic classification structure of Zachman’s Design Artifacts. Figure 2 shows the populated framework. 

Figure 1.  Generic Classification Structure of Design Artifacts (Zachman, 1997).

Figure 2.  The Populated Zachman’s Framework for Enterprise Architecture (Zachman, 1997).

            Zachman’s Framework is a generic classification scheme for design artifacts, which is detailed representations of a complex object. The utility of such a scheme is to enable focused concentration on selected aspects of an object without losing a sense of the contextual or holistic perspective (Zachman, 1997).  The framework is logical with five perspectives Owner, Designer, Builder, bounded by Scope or Strategist and Detail or Implementer in addition to the instantiation.  Six abstractions of What for things, How for the process, Where for location, Who for responsibility, When for timing, and Why for motivation.  The framework is comprehensive as it addresses the enterprise as a whole. The framework does not require technical professionals.  The framework serves as a planning tool to make better choices by positioning issues in the context of the enterprise and view various alternatives.  It also serves as a problem-solving tool to enable enterprise work with abstractions to simplify, isolate simple and single variables without losing the sense of the complexity of the enterprise as a whole.  Zachman’s framework is described as a neutral as it is defined independently of tools or methodologies and therefore any tool or any methodology can be mapped against it.  It is also described as a raw material for enterprise engineering (Zachman, 1997).

            Zachman’s Framework is the basis for architecture (Zachman, 2008).  During the industrial age, the industrial products were increasing in complexity and products that are changing.  However, in the age of information system, the enterprise is increasing in complexity and is changing continuously.  Zachman suggested that enterprise architecture is the determinant factor of survival in the Information Age (Zachman, 2008).  Thus, the Framework for Enterprise Architecture which is also called the Zachman Framework has profound significance in placing definitions around Enterprise Architecture, the survival issue of the century.  It is not a methodology but rather an ontology and a theory of the existence of a structured set of essential components of an object for which explicit expressions is required and probably mandatory for creating, operating and changing the object (Zachman, 2008).

            Zachman’s Framework is also described as a two-dimensional classification system based on six communication questions of What, Where, When, Why, Who and How as discussed above, which intersect with different views of Planner, Owner, Designer, Builder, Subcontractor, and Actual System (Abernathy & McMillan, 2016).  The system allows the analysis of an organization to be presented to different groups in the organization in ways that relate to the groups’ responsibilities. The enterprise architecture framework is not security oriented. However, it helps organizations relay information for personnel in a language and format that is most useful to them.  Since the inception of Zachman’s enterprise architecture, a few architectures were developed.  The next section will address some of these architectures.

Architectures Expansion

            Since the inception of Zachman’s Enterprise Architecture, a few architectures have been expanded along with the technology growth.  Organizations should choose the enterprise architecture framework that represents the organization in the most useful manner, based on the needs of the stakeholders.  This section discusses some of these architectures that expanded since Zachman’s Framework.

The Open Group Architecture Framework (TOGAF) is another enterprise architecture framework that aids organization design, plan, implement and govern enterprise information architecture (Abernathy & McMillan, 2016). TOGAF is based on four inter-related domains: technology, applications, data, and business.

            The Department of Defense Architecture Framework (DoDAF) is another architecture framework that organizes a set of products under eight views starting with “All viewpoint” (AV) for required, capability viewpoint (CV), data and information viewpoint (DIV), operation viewpoint (OV), project viewpoint (PV), services viewpoint (SvcV), standards viewpoint (STDV), and system viewpoint (SV).  This framework is used to ensure that new Department of Defense (DoD) techn9ologies integrate correctly with the current infrastructures (Abernathy & McMillan, 2016).

            The British Ministry of Defence Architecture Framework (MODAF) is another architecture framework that divides information into seven viewpoints starting with strategic viewpoint (StV), operational viewpoint (OV), service-oriented viewpoint (SOV), systems viewpoints (SV), acquisition viewpoint (AcV), technical viewpoint (TV), and all viewpoint (AV) (Abernathy & McMillan, 2016).

Sherwood Applied Business Security Architecture (SABSA) is an enterprise security architecture framework which is similar to Zachman’s Framework (Abernathy & McMillan, 2016).  It uses six communication questions of What, Where, When, Why, Who and How which intersect with six players of Operational, Component, Physical, Logical, Conceptual and Contextual. It is described to be a risk-driven architecture (Abernathy & McMillan, 2016).  Table 1 shows the SABSA Framework Matrix. 

Table 1.  SABSA Framework Matrix (Abernathy & McMillan, 2016).

Control Objectives for Information and Related Technology (CobiT) is a security control development framework that documents five principles.  The first principle is about meeting stakeholder needs while covering the enterprise end-to-end is the second principle.  The application of a single integrated framework is the third principle, following by enabling a holistic approach and separating governance from management principle. These five principles drive control objectives categorized into seven enablers starting with principles, policies, and framework, followed by processes, organizational structures. Culture, ethics, and behavior is the fourth enabler, followed by the information. Services, infrastructure, and application is another enabler, followed by the last enabler of people, skills and competencies.

Conclusion

            This project discussed Zachman Enterprise Architecture which is also known as the Zachman Framework.  Zachman introduced the concept of architecture in 1987 and compared the framework to the construction architecture which requires components, builders, time frame and so forth.  The framework is not a methodological but a logical framework. It is a two-dimensional framework.  The framework is not a security-based framework.  However, it allows analysis of enterprise to be presented to different groups in the enterprise in ways that relate to the responsibilities of the groups.  A few architectures expanded since the inception of Zachman’s Framework. This project discussed a few of them such as TOGAF, DoDAF, MODAF, SABSA, and CobiT. In brief, the concept of architecture did not exist until the Zachman’s initiative. The architecture concept was limited to the construction in the Industrial Age. However, in the Information Age, Zachman was inspired to develop an information system architecture and framework for Enterprise.  The application of architecture concept to the enterprise information system was an innovative idea from Zachman that deserves recognition.

References

Abernathy, R., & McMillan, T. (2016). CISSP Cert Guide: Pearson IT Certification.

Zachman, J. A. (1987). A framework for information systems architecture. IBM Systems Journal

Retrieved from https://www.zachman.com/images/ZI_PIcs/ibmsj2603e.pdf, 26(3), 276.

Zachman, J. A. (1997). The Framework for Enterprise Architecture: Background, Description, and Utility by John A. Zachman. Retrieved from https://www.zachman.com/resources/ea-articles-reference/327-the-framework-for-enterprise-architecture-background-description-and-utility-by-john-a-zachman. 

Zachman, J. A. (2008). The Concise Definition of The Zachman Framework by John A. Zachman. Retrieved from https://www.zachman.com/about-the-zachman-framework.