1.1 The Enterprise, the Purpose of EA & Its Benefits
Key Takeaways
- The TOGAF Standard, 10th Edition considers an enterprise to be any collection of organizations that have common goals, such as a corporation, government department, consortium, or supply chain.
- The purpose of Enterprise Architecture is to optimize the often fragmented legacy of manual and automated processes into an integrated environment that is responsive to change and supports business strategy.
- TOGAF groups EA benefits under five headings: strategic decision-making, business operations, Digital Transformation and operations, return on investment and reduced risk, and procurement.
- Architects address stakeholder concerns by refining requirements, developing views that show how concerns are met, and showing the trade-offs between conflicting concerns.
- TOGAF says Enterprise Architecture should be done early and throughout the change process; EA produced after decisions is only documentation or enforcement.
1.1 The Enterprise, the Purpose of Enterprise Architecture & Its Benefits
The first Learning Unit of the TOGAF Enterprise Architecture Foundation syllabus asks you to describe what an enterprise is, explain the purpose of Enterprise Architecture (EA), and list its key benefits. These look like "easy" definitions, but OGEA-101 questions often test the exact wording: an enterprise is defined by common goals, not by legal form, and EA exists to turn a fragmented legacy of processes into an integrated environment that is responsive to change.
What Is an Enterprise?
The TOGAF Standard, 10th Edition considers an enterprise to be any collection of organizations that have common goals. The standard gives examples of what an enterprise could be:
- A whole corporation or a division of a corporation
- A government agency or a single government department
- A chain of geographically distant organizations linked together by common ownership
- Groups of countries, governments, or governmental organizations (such as militaries) working together to create common or shareable deliverables or infrastructures
- Partnerships and alliances of businesses working together, such as a consortium or supply chain
The term "enterprise" in "Enterprise Architecture" can apply to the entire enterprise (all of its business activities, capabilities, information, and technology) or to one or more specific areas of interest within it. An enterprise may include partners, suppliers, and customers as well as internal business units. In every case the architecture crosses multiple systems and multiple functional groups.
The formal glossary entry adds a second angle: an enterprise is "the highest level (typically) of description of an organization," typically covering all missions and functions, and it will often span multiple organizations. The enterprise operating model helps decide the nature and scope of EA work — a large group may contain several enterprises, each with its own Enterprise Architecture, while still sharing a common framework, common building blocks, and a shareable Architecture Repository.
What Does "Architecture" Mean in TOGAF?
The standard uses two meanings of architecture, depending on context:
| Meaning | Wording in the standard | Source |
|---|---|---|
| 1 | The fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and in the principles of its design and evolution | ISO/IEC/IEEE 42010 |
| 2 | The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time | TOGAF's second meaning |
TOGAF "embraces but does not strictly adhere to" ISO/IEC/IEEE 42010 terminology, and it treats the enterprise itself as a system.
Why Is an Enterprise Architecture Needed?
The standard states the purpose directly:
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.
It then explains why that purpose matters:
- Information and Digital Transformation are key factors in business success. EA provides a strategic context for the evolution and reach of digital capability as business needs change.
- A good EA helps achieve the right balance between business transformation and continuous operational efficiency, letting individual business units innovate safely while the organization pursues an integrated strategy with the closest possible synergies.
- Privacy legislation increasingly demands that processes handling personal data are fully documented in a way untrained readers (data subjects, judges, lawyers) can understand — EA documentation supports this.
What Prompts an EA Effort?
The standard lists typical triggers for an EA review or development:
- Business-driven initiatives to enable business transformation (for example, leveraging digital services and products as revenue-generating assets)
- Technology-driven initiatives for efficiency and cost reduction (for example, technology consolidation)
- Mergers or acquisitions, where return on investment is realized only after technology efficiencies are achieved
- Management of technical debt accrued by agile development initiatives
In all of these, EA is needed to manage complexity when change involves multiple systems with multiple interdependencies.
The Key Benefits of Enterprise Architecture
TOGAF groups the potential benefits of an effective EA into five headings. Learn the headings; examples illustrate each:
| Benefit heading | Examples given by the standard |
|---|---|
| More effective strategic decision-making by C-level executives and business leaders | Quick response to change and support for enterprise agility; organizational transformation adopting new business and technology trends; change to support Digital Transformation; operating-model changes to improve efficiency |
| More effective and efficient business operations | Lower business operation costs; a more agile organization; business capabilities shared across the organization; lower change-management costs; a more flexible workforce; improved productivity; improved integration for mergers and acquisitions |
| More effective and efficient Digital Transformation and operations | Extending the reach of the enterprise through digital capability; a harmonized environment; lower development, operations, support, and maintenance costs; improved interoperability and system management; better handling of enterprise-wide issues such as security; easier upgrade and exchange of components |
| Better return on existing investment, reduced risk for future investment | Reduced complexity in business and IT; maximized ROI in existing business and IT; flexibility to make, buy, or outsource; understanding how ROI changes over time |
| Faster, simpler, and cheaper procurement | Simpler buying decisions because procurement information is in a coherent plan; faster procurement without sacrificing architectural coherence; ability to procure heterogeneous, multi-vendor open systems; more economic capabilities |
The Architect's Role and When EA Should Be Done
Key people who identify needed change are the stakeholders. TOGAF describes the architect's role as addressing stakeholder concerns by:
- Identifying and refining the requirements of the stakeholders
- Developing views of the architecture that show how concerns and requirements will be addressed
- Showing the trade-offs made in reconciling potentially conflicting concerns of different stakeholders
TOGAF also answers when EA should be done: early and throughout the change process, so decision-makers understand the implications of their decisions. EA done after decisions are made is "merely documentation of those decisions or at best enforcement of those decisions."
Scenario: A Regional Bank Merger
A bank acquires a regional lender. Without EA, each project team rebuilds its own customer data, integration, and security approach, and the promised synergies never appear. With EA started early, the architecture team identifies stakeholders (retail executives, risk, operations, IT), develops views showing overlapping loan platforms, and presents trade-offs (fast integration versus full platform consolidation) before the merger integration budget is committed — the "early and throughout" principle in action.
Common Exam Pitfalls
- Assuming an enterprise must be a single company. Consortia, supply chains, government departments, and alliances of countries all qualify when they share common goals.
- Treating EA as IT architecture under another name. The executive overview stresses that EA is not just another name for IT Architecture; it spans business, data, application, and technology.
- Mixing up the purpose with the benefits. The purpose is optimizing a fragmented legacy into an integrated, change-responsive environment that supports business strategy; the benefits are the five outcome headings.
- Thinking EA is best done after decisions. TOGAF says EA should be done early and throughout change; after-the-fact EA is only documentation or enforcement.
According to the TOGAF Standard, 10th Edition, what makes a group of organizations an "enterprise"?
Which statement best describes the purpose of Enterprise Architecture in the TOGAF Standard?
Which of the following is one of the five benefit headings the TOGAF Standard gives for an effective Enterprise Architecture?
A transformation program brings in architects only after the target platform has been purchased and the rollout plan is fixed. How does the TOGAF Standard characterize Enterprise Architecture performed at this point?