and structured is the Zachman Framework. It was originally developed as an Information Systems architecture. The main idea is to provide the possibility of a consistent description of system’s individual aspects in coordination with all the rest. The Zachman model is used to describe the enterprise as a whole, so the proposed model can be generally used as a means for describing architectures of any complex production system. The main characteristics of this model are:
• Integrity of the enterprise;
• discussing complex issues using a relatively small number of non-technical concepts;
• applicability for solving problems, i.e. the ability to work with abstractions and entities, highlighting and isolating individual system parameters without losing the perception of the enterprise as a whole;
• Simplicity of description.
The advantages of the Zachman model over others are:
• It is easy to understand for both technical and non-technical experts;
• It has more detailed descriptions of architecture components;
• It can be applied to planning and better decision making;
• It has the most visible representation of the company’s components.
• It describes complex architecture using a small number of non-technical terms;
• It has independent tools for specific description;
• It can be used as a tool for describing architectures of any complex production system.
Enterprise Architecture – Zachman Framework Matrix
Enterprise Architecture using “FEAF”
FEAF is a framework developed by the US government, as an approach for the development of information technology for Public agencies to use a single architecture. The FEAF is based on five reference models:
• Performance reference model;
• Business reference model;
• Service component reference model;
• Technical reference model.
• Data reference model.
One of the useful properties of the FEA framework is the principle of a segment approach, allowing accelerating the implementation of the Enterprise Architecture. The process of developing an enterprise architecture using the FEA methodology includes the following steps:
• Architecture analysis;
• Architectural definition;
• Investment and financing strategy;
• Program management and project implementation plan
Enterprise Architecture using “GARTNER”
Gartner Methodology can be described as a set of recommendations for creating an enterprise architecture. The 2002 Gartner model is designed in four related, interdependent, and increasingly complex levels:
• Business Relationship Grid;
• Business processes and business process styles;
• Templates;
• Technological building blocks (bricks).
Essentially the Gartner methodology is neither a methodology, such as a structured Zachman model, nor a process like TOGAF or FEA. Gartner is a set of practical recommendations. This methodology is a collection of tips for building enterprise architecture from one of the world’s most famous consulting IT companies. This framework is a three-dimensional cube consisting of following levels:
• Horizontal layers;
• Vertical domains;
• Vertical elements of technical architecture.
Enterprise Architecture using “TOGAF”
The main area for TOGAF application is the software infrastructure of the information system. It best suits for describing the integration components used to support a wide range of critical enterprise applications for business. The model can be described as:
• Business architecture overview;
• Description of the current system with the level of detail required;
• Identification and description of elementary architectural blocks to be used in the new architecture;
• Development of a draft technical report;
• Submitting the draft report for review.
TOGAF is positioned not as a reference model, but a “tool for developing information system architectures”. The primary function is to speed up and facilitate the process of developing the architecture of a particular organization, providing the possibility of future development. Let us consider building of the Enterprise Architecture based on the TOGAF methodology in more details, which in my opinion has several advantages:
• TOGAF approach allows you to build the entire architectural process – from the launch of the practice to the results.
• TOGAF is the de facto standard and has a certification program.
• TOGAF is absolutely free and has lots of open resources to download and use.
• TOGAF contains a complete set of tools for creating and developing architectural practices in an organization. There is a step-by-step process for developing a description of the Enterprise Architecture and a complete range of tools, templates, etc.
• TOGAF is compatible with other frameworks, for example, “Zahman Framework”. As an architectural process, the TOGAF model supplements the Zachman model classified as an architectural taxonomy. Zachman demonstrates how to classify the artifacts. The TOGAF model describes their creation.
Enterprise Architecture using “TOGAF”
Even though the TOGAF methodology and Zakhman infrastructure are merged into the “enterprise infrastructures” category, their principles, structures and competencies are different. TOGAF is a functional and dynamic infrastructure including guidelines for process use patterns. While the Zachman framework is a static architecture structure, it is the most effective one for applying the analysis and meta-analysis of infrastructure frameworks. Despite the significant differences in these frameworks, they can be used together.
TOGAF Basic principles
Creating a specific enterprise architecture is considered as a transition from a general architecture to a specialized one. The architecture development methodology in TOGAF model is the process
