2.2 What is Enterprise Architecture?
There are many definitions of Enterprise Architecture. Most focus on structure and organization. Two definitions are given below:
Enterprise Architecture is:
1. The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.
[Source: MIT Center for Information Systems Research]
2. A conceptual blueprint that defines the structure and operation of an organization. The intent of an Enterprise Architecture is to determine how an organization can most effectively achieve its current and future objectives.
[Source: SearchCIO.com]
2.3 Why do I Need Enterprise Architecture?
The purpose of Enterprise Architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy. Effective management and exploitation of information and Digital Transformation are key factors to business success, and an indispensable means to achieving competitive advantage. An Enterprise Architecture addresses these drivers by providing a strategic context for the evolution and reach of digital capability in response to the constantly changing needs of the business environment.
For example, the rapid development of social media, Internet of Things (IoT), virtualization, and cloud computing has radically extended the capacity of the enterprise to create new market opportunities.
The advantages that result from a good Enterprise Architecture can bring important business benefits, including:
• More effective and efficient business operations:
— Lower business operation costs
— More agile organization
— Business capabilities shared across the organization
— Lower change management costs
— More flexible workforce
— Improved business productivity
• More effective and efficient Digital Transformation and IT operations:
— Extending the effective reach of the enterprise through digital capability
— Bringing all components of the enterprise into a harmonized environment
— Lower software development, support, and maintenance costs
— Increased portability of applications
— Improved interoperability and easier system and network management
— Improved ability to address critical enterprise-wide issues, such as security
— Easier upgrade and exchange of system components
• Better return on existing investment, reduced risk for future investment:
— Reduced complexity in the business and IT
— Maximum return on investment in existing business and IT infrastructure
— The flexibility to make, buy, or out-source business and IT solutions
— Reduced risk overall in new investments and their costs of ownership
• Faster, simpler, and cheaper procurement:
— Simpler buying decisions, because the information governing procurement is readily available in a coherent plan
— Faster procurement process, maximizing procurement speed and flexibility without sacrificing architectural coherence
— The ability to procure heterogeneous, multi-vendor open systems
— The ability to secure more economic capabilities
Ultimately, the benefits of Enterprise Architecture derive from the better planning, earlier visibility, and more informed designs that result when it is introduced.
[Source: The Open Group White Paper: Why Does Enterprise Architecture Matter?]
2.4 What is the TOGAF Standard?
The TOGAF standard is an architecture framework providing the methods and tools for assisting in the production, acceptance, use, and maintenance of Enterprise Architectures. It is based on an iterative process model supported by best practices and a re-usable set of existing architectural assets.
The TOGAF standard is developed and maintained by The Open Group Architecture Forum. The first version of the TOGAF standard, developed in 1995, was based on the US Department of Defense Technical Architecture Framework for Information Management (TAFIM). Starting from this sound foundation, The Open Group Architecture Forum has developed successive versions of the TOGAF standard at regular intervals and published each one on The Open Group public website.
The TOGAF standard can be used for developing a broad range of different Enterprise Architectures. It complements, and can be used in conjunction with, other frameworks that are more focused on specific deliverables for particular vertical sectors such as Government, Telecommunications, Manufacturing, Defense, and Finance. A key part of the TOGAF standard is the method – the TOGAF Architecture Development Method (ADM) – for developing an Enterprise Architecture that addresses business needs.
2.4.1 Structure of the TOGAF Documentation
The TOGAF documentation consists of the TOGAF standard, and a portfolio of guidance material, known as the TOGAF Library, to support the practical application of the standard. The TOGAF standard is at the heart of the TOGAF Library, as shown in Figure 1.
Figure 1: The TOGAF Library
The standard is divided into parts, each addressing distinct topics including methods, techniques, etc. This is summarized in Table 1.
Table 1: Structure of the TOGAF Standard
| TOGAF Part | Summary |
| Part I: Introduction | This part provides a high-level introduction to the key concepts of Enterprise Architecture and, in particular, to the TOGAF approach. It contains the definitions of terms used throughout the standard. |
| Part II: Architecture Development Method (ADM) | This part is
|
