Enterprise Architecture on a Page

(A one-page aggregated view of popular EA artifacts used in organizations with their most essential properties, including their informational content, representation format, high-level structure, overall meaning, typical usage, temporal lifecycle, general role, key purpose and associated benefits)

Analytical Reports Principles Policies Architecture Strategies Business Capability Models Process Maps Value Chains Target States Roadmaps Initiative Proposals
Hold Assess Trial Adopt Policy 1: Personal Data Must Be Stored Onshore
Principle 1: Standardized Business Processes National Description: ......................................................... Supply Chain Strategy 1. Supplier-to-Stock Process Business Drivers: Strategic Links: Key Decisions: Current Future 1. Initiative Summary
Privacy Business Strategy Human Resource Management
• Driver 1 • Link to Strategy 1 • Decision 1 State
2021 2022 2023
State
Technology 1.1 Statement: ............................................. Policy 2: Destroy Personal Data When Not Needed 1.1. Subprocess 1.2. Subprocess
• Driver 2 • Link to Strategy 2 • Decision 2
.................................

External
Technology 1.3 Policies 1. Current Drivers and Challenges Capability 1 Today Capability 1
Description: ......................................................... 1.1.1. Subprocess 1.2.1. Subprocess • Driver 3 • Link to Strategy 3 • Decision 3 2. Goals and Objectives
Goal 1 Goal 2 Goal 3 Financial and Administrative Management Initiative 1.2
Rationale: ............................................... ................................................... System 1 System 1
Technology 1.2 Policy 3: Log All Accesses to Accounting Systems 1.1.2. Subprocess (Add) Current Architecture: ....................................
Technology 3.1 Sarbanes- Description: ......................................................... Initiative 1.1 Initiative 1.3 System 2
Implications: ........................................... Capability 1 Capability 2 Procurement and Supplier Management
Category 1 Oxley 2. Long-Term Business Objectives Customer
Channel 1
Local Simple 3. Anticipated Benefits
Policies Policy 4: Retain Audit Trails and Emails for 5 Years Group 1 System 1 Reporting Capability 2 Capability 2
Description: .........................................................
................................................... 2. Stock-to-Order Process Initiative 2.1 ...................................
Technology 3.2 Capability 1.1 Capability 1.2 Capability 2.1 Capability 2.2 System 1 System 1
Technology 1.4 Principle 2: Single Customer View 2.1. Subprocess 2.3. Subprocess Information Technology Services
Customer Local
Policy 5: No Sensitive Data on Mobile Devices Channel 2 System 2 Initiative 2.2 System 3 4. Scope and Stakeholders
Technology 2.1 Statement: ............................................. Data Description: .........................................................
3. Existing IT Capability Gaps 2.1.1. Subprocess
2.2. Subprocess
2.3.1. Subprocess Group 2 System 2
Security ........................................... Capability 1.3 Capability 1.4 Capability 2.3 Capability 2.4 Inbound
Operations
Outbound Marketing
Service Capability 3 Capability 3
.........................................
Rationale: ............................................... Policies Policy 6: Store Credit Cards in Encrypted Formats 2.1.2. Subprocess 2.3.2. Subprocess Logistics Logistics and Sales Three-Year Target Architecture: Initiative 3.2 Initiative 3.4
Description: .........................................................
System 1 System 2 5. Solution Sketch
Technology 2.2 Customer
Technology 2.3 Implications: ........................................... 4. Proposed Architectural Direction Capability 3 Capability 4 Activity 1 Activity 1 Activity 1 Activity 1 Activity 1
Group 1
Channel 1 System 2
Initiative 3.3
System 4
Technology 3.3 Policy 7: Do Not Share Key Data with Third Parties

Internal
3. Order-to-Cash Process Global Real-Time
Data Description: .........................................................
Current Logistics Platform: Future Logistics Platform:
System 3 Initiative 3.1 Initiative 3.5 New ERP
Activity 2 Activity 2 Activity 2 Activity 2 System Predictive
Category 2 Technology 3.4 Exchange Capability 3.1 Capability 3.2 Capability 4.1 Capability 4.2 3.2. Subprocess Customer Analytics
Process 1
Module
Principle 3: Business Continuity Policies Policy 8: Share Client Data with Trusted Partners 3.2.1. Subprocess Group 2
Channel 2
Capability 4 Capability 4
Description: ......................................................... 3.1. Subprocess Activity 3 Activity 3 Initiative 4.2 Clients
System 1 System 2
New Statement: ............................................. Capability 3.3 Capability 3.4 Capability 4.3 Capability 4.4 3.2.2. Subprocess
Technology 3.5 Policy 9: Use Only the PCI DSS Compliant Cloud Architecture Changes: Business Outcomes: Customer Outcomes:
System 2 Initiative 4.1 6. Preliminary Estimations
Cloud Description: ......................................................... • Change 1 • Outcome 1 • Outcome 1
Moved Rationale: ............................................... Time: 6-12 months
Hosting 5. Key Architectural Decisions • Change 2 • Outcome 2 • Outcome 2
Category 3 Policies Policy 10: Do Not Store Health Data in the Cloud Regular Important Strategic Run Improve Redefine Non-Strategic Strategic Core Activities • Change 3 • Outcome 3 • Outcome 3 Planned Approved Funded Cost: $1.5-3.0 million
No Change Implications: ........................................... Description: .........................................................
.............................................

Executive-level analyses of relevant technology trends and Global high-level guidelines influencing all decision- Overarching organizational norms typically of a restrictive Abstract conceptual directions for an organization from the Structured graphical representations of all organizational Structured graphical representations of all high-level Structured graphical representations of the added High-level graphical descriptions of the desired Structured graphical views of all planned IT initiatives in Very early idea-level descriptions of proposed
their potential impact on the business of an organization making and planning in an organization nature providing compulsory prescriptions in certain areas standpoint of the relationship between business and IT business capabilities, their relationship and hierarchy business processes, their relationship and hierarchy value chain of an organization long-term future state of an organization specific business areas having direct business value IT initiatives and their justifications

Conceptual Data Models Options Assessments

Option Score
Order Solution 1:
Customer Time: 8-13 months Functionality: 5
Date Process Cost: $2.0-3.5 million Feasibility: 2
Name Quantity Advantages: ............. Alignment: 4
Users
Date of Birth Discount Disadvantages: .........
Old New
Location System System Risks: ........................ Total Score: 11
Phone
Solution 2:
Time: 4-7 months Functionality: 3
Process Cost: $1.0-1.7 million Feasibility: 3
Advantages: ............. Alignment: 1
Users
Disadvantages: .........
Old Extra
System System Risks: ........................ Total Score: 7
Product
Bank Card Solution 3:
Title Time: 3-5 months Functionality: 2
Type
Number
Type
Price Generic What EA Artifacts Describe? Specific Users
Process Cost: $0.7-1.3 million
Advantages: .............
Feasibility: 5
Alignment: 2
Expiry Date Disadvantages: .........
Enhanced
System Risks: ........................ Total Score: 9

Abstract definitions of the main data entities critical for

Rules Structures Changes Lists of available high-level implementation options for
the business of an organization and their relationship specific IT initiatives with their pros and cons

Business
Technology Reference Models Considerations Visions Outlines Language: Technology-neutral
Solution Overviews
Delivery Channels Content: Global conceptual rules and fundamental considerations important Content: High-level conceptual descriptions of an organization from the Content: High-level descriptions of separate IT initiatives understandable to business language 1. Overview and Goals 8. Business Process Changes

Business-Focused
for business and relevant to IT business perspective business leaders
Technology 1 Technology 2 Technology 1 Technology 2 Domains: Business domain and .................................. Process 1 Now (10 days in total):
Focus: Do not refer to specific points in time or focus on the long-term future Focus: Often focus on the long-term future up to 3-5 years ahead Focus: Usually focus on the mid-term future up to 1-2 years ahead 2. Scope and Stakeholders
often other relevant domains Step 1 Step 2 Step 3
Applications and Middleware Format: Expressed in simple intuitive formats, often as brief written Format: Expressed in brief informal formats, often as large but simple one- Format: Expressed as a mix of textual descriptions and simple diagrams .........................................
statements page diagrams at a high level 3. Essential Requirements
3 days 5 days 2 days

Technology 1 Technology 2 Technology 3 Vendor 1 Process 1 Will Be (5 days in total):

Format: Brief, intuitive, largely ........................................
Meaning: Decisions on how an organization needs to work from the business Meaning: Decisions on what IT should deliver to an organization in the long Meaning: Decisions on how approximately specific IT initiatives should be 4. Business Benefits
Step 1 Step 2
Databases and Information Management and IT perspective run implemented
informal and include only the 2 days 3 days
..............................
most essential information 9. Architectural Overview
Technology 1 Technology 2 Product 1 Product 2 Usage: Developed collaboratively by senior business leaders and architects Usage: Developed collaboratively by senior business leaders and architects Usage: Developed collaboratively by architects and business leaders and then 5. Capability Impact
and then used to influence all architectural decisions (see Enterprise and then used to guide IT investments, identify, prioritize and launch new IT used to evaluate, approve and fund specific IT initiatives (see Enterprise Stakeholders: Business leaders • Order Fulfilment (High) Process 1
Infrastructure and Networks Architecture Practice on a Page) initiatives (see Enterprise Architecture Practice on a Page) Architecture Practice on a Page) and architects • Order Management (Low) Step 1 Step 2
• Customer Analytics (Low)
How EA Artifacts Describe?
Technology 1 Technology 2 Hardware 1 Hardware 2 Lifecycle: Established once and then updated according to the ongoing Lifecycle: Created once and then updated according to the ongoing changes in Lifecycle: Produced at the early stages of IT initiatives to support decision- Role: Communication 6. Involved Partners
changes in the business environment strategic business priorities making and then archived interfaces between business Client 1 App 1 App 2
Security and Access Management • IBM
and IT • Accenture
Technology 1 Technology 2 Product 1 DB 1 DB 2
Role: Overarching organizational context for information systems planning Role: Shared views of an organization and its future agreed by business and IT Role: Benefit, time and price tags for proposed IT initiatives 7. Estimations
Purpose: Help business leaders
Time: 6-8 months 10. Key Risks
Purpose: Help achieve the agreement on basic principles, values, directions Purpose: Help achieve the alignment between IT investments and long-term Purpose: Help estimate the overall business impact and value of proposed IT manage IT
Unsupported Current Emerging Cost: $1.2-1.5 million ...................
and aims business outcomes initiatives
Benefits: Improved overall consistency between business and IT Benefits: Improved strategic alignment and effectiveness of IT investments Benefits: Improved efficiency and ROI of IT investments
Structured graphical representations of all technologies High-level descriptions of specific proposed IT solutions
used in an organization understandable to business leaders

Technology Inventories*
Enterprise Architecture Preliminary Solution Designs
Technology Vendor Version(s) Category Function
Standards Landscapes Designs 1. Brief Overview
..........................
9. High-Level Architecture
Technology 1 ............ ................ .............. .............. Language: Technical IT-specific Process 1
Content: Global technical rules, norms, patterns and best practices relevant to Content: High-level technical descriptions of the organizational IT landscape Content: Detailed technical and functional descriptions of separate IT projects 2. Goals and Objectives
Technology 2 ............ ................ .............. .............. information systems actionable for project teams language Step 1 Step 2
Focus: Focus mainly on the current state, sometimes looking into the future ....................................
Technology 3 ............ ................ .............. .............. 3. Scope and Stakeholders
Focus: Do not refer to specific points in time or focus on the current state Format: Expressed in strict formats, often as complex one-page diagrams Focus: Normally focus on the short-term future up to one year ahead Domains: Various technical Client 1
Technology 4 ............ ................ .............. .............. .........................................
Format: Can be expressed in various formats, often using strict notations using formal modeling notations, e.g. ArchiMate Format: Expressed as a mix of text, tables and complex diagrams, can be domains and sometimes also
IT-Focused

Technology 5 ............ ................ .............. .............. 4. Business Requirements

voluminous and often use formal modeling notations, e.g. UML business domain App 1 App 2
........................................
Technology 6 ............ ................ .............. ..............
Technology 7 ............ ................ .............. ..............
Meaning: Decisions on how all IT systems should be implemented and some Meaning: Facts on the current IT landscape and some decisions on its future Meaning: Decisions on how exactly specific IT projects should be Format: Can be voluminous, 5. Involved Partners
facts on the current approaches and technologies evolution implemented formal, use strict notations and • IBM DB 1 DB 2
Technology 8 ............ ................ .............. .............. • Accenture
Product 1 ............ ................ .............. ..............
Usage: Developed collaboratively by architects and technical subject-matter Usage: Developed and maintained by architects and used to rationalize the IT Usage: Developed collaboratively by architects, project teams and business include comprehensive details 6. Key Technologies
Server 1 Server 2

experts and used to shape the architectures of all IT initiatives (see Enterprise landscape, manage the lifecycle of IT assets and plan new IT initiatives (see representatives and then used by project teams to implement IT projects (see
Product 2 ............ ................ .............. .............. Stakeholders: Architects and • Java EE Platform 10. Application Interaction
Architecture Practice on a Page) Enterprise Architecture Practice on a Page) Enterprise Architecture Practice on a Page) • IBM BPM and DB2
Product 3 ............ ................ .............. .............. other IT specialists
Lifecycle: Established on an as-necessary basis and updated according to the Lifecycle: Created on an as-necessary basis and updated according to the Lifecycle: Produced at the later stages of IT initiatives to support 7. Accurate Estimations App 1 DB 1
Product 4 ............ ................ .............. .............. ongoing technology progress ongoing evolution of the IT landscape implementation and then archived Role: Internal IT tools invisible Time: 8-9 months
Product 5 ............ ................ .............. .............. to business Cost: $2.1-2.3 million
Purpose: Help architects 8. Technical Risks App 2 DB 2
Obsolete Up-to-date Cutting-edge Role: Proven reusable means for IT systems implementation Role: Knowledge base of reference materials on the corporate IT landscape Role: Communication interfaces between architects and project teams ..........................
Purpose: Help achieve technical consistency, technological homogeneity and Purpose: Help understand, analyze and modify the structure of the IT Purpose: Help implement approved IT projects according to business and organize IT
Structured catalogs of currently deployed technologies regulatory compliance landscape architectural requirements Preliminary high-level technical and functional designs
describing their essential properties and features Benefits: Faster initiative delivery, reduced costs, risks and complexity Benefits: Increased reuse and agility, reduced duplication and legacy Benefits: Improved quality of project delivery of specific approved IT solutions
IT

Technology Roadmaps* Solution Designs

Describe: General global rules defining an organization or its divisions Describe: High-level structures of an organization or its parts Describe: Specific proposed incremental changes to an organization
Networks
2022 2023 2024 Scope: Very broad, often relate to an entire organization Scope: Broad, often cover large areas of an organization Scope: Narrow, limited to separate IT initiatives or projects 1. Brief Overview 5. Data Architecture
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Format: Often textual Format: Usually graphical Format: Mix of textual and graphical ..........................
Table 1 Table 2
Software 1
2. Goals and Objectives DB 1
v3.0
Question: How do we work or want to work? Question: What approximately do we have or want to have? Question: What exactly are we going to change right now? Column 1: Int Column 1: Char
.................................... Column 2: Char Column 2: Clob
Column 3: Byte Column 3: Blob
v3.1 Lifecycle: Permanent, created once and then periodically updated Lifecycle: Permanent, created once and then continuously updated Lifecycle: Temporary, created for specific purposes and then 3. Detailed Requirements 1 *

v3.2 Role: Basis for all other planning decisions Role: High-level “maps” facilitating decision-making discarded ....................................... 6. Application Architecture
4. Solution Context
Software 2
Purpose: Help achieve consistency and homogeneity of all planning Purpose: Help understand what changes are desirable and how to Role: Tactical plans of an organization Call
Form

Technology 1 decisions implement them Purpose: Help plan separate changes in detail Process 1 App 1 App 2 Store

Step 1 Step 2 DB 1
Reply Read
Technology 2 Pilot
Client 1
7. Infrastructure Architecture
Hardware 1 Internet

Hardware 2 App 1 App 2 Linux Linux

Firewall
Server 1 Server 2
Model A
VM 1 Hot
Model B DB 1 DB 2 Switch
Standby
Server 1 Server 2 VM 2
Phasing In Endorsed Phasing Out

Structured graphical views of the projected lifecycles Detailed technical and functional specifications of
of technologies used in an organization approved IT solutions actionable for project teams

IT Principles Guidelines Patterns Logical Data Models* Landscape Diagrams* Asset Inventories* System Portfolio Models Landscape Maps IT Roadmaps Asset Roadmaps*
IT Principle 1: Prefer Open Source Solutions Guideline 1: Run Applications as OS Services
Description: ......................................................
Server Description: .........................................................
1. Name: Enriched Asynchronous Request/Reply Backup Asset Purpose Owners Cost Problems Capability 1 Capability 2 Activity Logistics & Production & Sales & Delivery & Domain Q1-2 2021 Q3-4 2021 Q1-2 2022 Q3-4 2022 Area 2022 2023 2024 Notes
Applications Deployment Order CRM DB 1 BU App 1
Capability 1.1 Capability 1.2 Capability 2.1 Capability 2.2
Region Procurement Quality Marketing Distribution
Now
IT Principle 2: Log All Main Operations
Standards
Guideline 2: Store Deployment Packages in VCS
2. Context:
Customer Application 1 ............. ............ ....... ............... Office
Workstations
Initiative 4 Capability 1
Description: ...................................................... Description: ......................................................... System 1 System 1 System 1 System 1 System 1 v5.0 v5.1 Comments
id: Integer Queue Application 2 ............. ............ ....... ............... Region A and
.......................... id: Integer Calls from
System 2 System 2 System 2 Business
System 1 System 9
Infrastructure
Initiative 2 Initiative 10
IT Principle 3: Use Scalable Storage Guideline 3: Avoid Using UDP Multicast customer_id: Integer Partners Application 3 ............. ............ ....... ............... Database 1 Comments
Network name: String [30] App 6
App 2 App 3
Capability 2.4
Description: ...................................................... Description: ......................................................... 1 product_id: Integer
Data Protocol 3. Problem: date_of_birth: Date * date: Date
(Plan)
Application 4 ............. ............ ....... ...............
System 3
Capability 1.4 Capability 2.3
System 1
System 10
Application and Initiative 6 System 2
IT Principle 4: Backup All Permanent Data Guideline 4: Prefer REST Over SOAP location: String [30] Region B Integration
Description: ......................................................
Standards Description: .........................................................
.......................... phone: String [15]
quantity: Integer Update RPC Binary EJB
System 1 ............. ............ ....... ............... Capability 1.3
System 1 System 1 System 2 Business
System 2
Platforms Initiative 9
Capability 2
discount: Float System 1 Upgrade
System 2 ............. ............ ....... ............... System 1 System 2 System 3 System 7 System 11 System 13
IT Principle 5: Use Middleware for Integration Guideline 5: Use 256-Bit Encryption Keys 1 Enterprise Service Bus Server
Description: ......................................................
Data Description: .........................................................
4. Solution: * System 3 Operating
System 2 Comments
Metadata System 3 ............. ............ ....... ............... Region C Initiative 7
Integration Encryption XML Repository Messaging Capability 3 Capability 4 Business System 4
Systems and System 3 v1.0 v1.1 v2.0
IT Principle 6: Avoid Binary Integration Protocols Guideline 6: Store MD5 Hashes of Passwords Extra
SOA REST System 4 ............. ............ ....... ............... Hardware
Description: ......................................................
Standards Description: .........................................................
File Data
Capability 3.1 Capability 3.2 Capability 4.1 Capability 4.2 Database 1 Comments
App 7
* (Plan) Reporting System 5 ............. ............ ....... ............... System 12
System 14 Network Initiative 3 Initiative 11
IT Principle 7: Host in the Cloud Guideline 7: Use Web-Safe Colours Message ID 1 App 5 System 1 System 1 System 1 System 1 Region D System 4 Comments
Interface App 4 and Cloud
Outgoing Database 1 ............. ............ ....... ............... Business
Description: ...................................................... Description: ......................................................... Bank_Card System 2 System 5 Infrastructure Initiative 5 Database 2
Infrastructure
IT Principle 8: Dedicated Server for Each System
Design
Guideline 8: Place Menu in the Top Right Corner
Message Product Database 2 ............. ............ ....... ............... Capability 4.3 Capability 4.4
System 15
Migration
Sender Message DB 4
Description: ......................................................
Guidelines Description: ......................................................... Validation Receiver id: Integer (Plan) Capability 3.3 Capability 3.4
System 1 System 1
Initiative 1
Capability 3
Incoming id: Integer Database 3 ............. ............ ....... ............... Region E Security System 1 Comments
Correlation ID customer_id: Integer System 1 System 1 System 2 System 2 Business
System 8 No systems
and Identity
DB 3 ETL Warehouse System 6 System 16
IT Principle 9: Place Public Systems in DMZ Guideline 9: Initialize Variables to Safe Defaults type: String [4] title: String [20] Database 4 ............. ............ ....... ...............
Description: ......................................................
Secure Description: ......................................................... type: String [10]
Management Initiative 8 System 2 Trial
Error number: String [16]
Security Coding Processor
Invalid Binary
expiry_date: Date price: Float DB 2
IT Principle 10: Secure by Default Guideline 10: Validate All Incoming Data Error Code Payload Decommission Reuse Invest Legacy Active Strategic Weak Fit Medium Fit Strong Fit Not Sponsored CIO Business Development Production Withdrawal
Description: ......................................................
Guidelines Description: .........................................................

Global high-level IT-specific guidelines influencing all IT-specific implementation-level prescriptions applicable Generic reusable solutions to commonly occurring Logical or even physical platform-specific definitions of Technical “boxes and arrows” schemes of different scopes Structured catalogs of currently available IT assets Structured high-level mappings of all core information Structured high-level mappings of key IT systems to Structured graphical views of all planned IT initiatives of a Structured graphical views of the projected lifecycles
IT-related decisions and plans in an organization in narrow technology-specific areas or domains problems in the design of information systems common data entities and their relationship and granularities describing the corporate IT landscape describing their essential properties and features systems to relevant business capabilities relevant functional and organizational areas purely technical nature having no visible business impact of IT assets existing in an organization

Essential Popular Common Uncommon Mature EA practices usually use pragmatic

sets of 10-15 value-adding EA artifacts, or
Templates demonstrate only the most typical
contents, structure and format of EA artifacts,
[*] These EA artifacts are often stored
in specialized tool-based architectural
(Used in virtually every EA practice) (Used in 50-75% of EA practices) (Used in 25-50% of EA practices) (Used in 10-25% of EA practices) only about a half of all the shown artifacts they should be adapted, not copied mindlessly repositories and extracted as views