External
Policies Policy 1: Personal Data Must Be Stored Onshore Description: .........................................................
National Privacy Policies
Policy 2: Destroy Personal Data When Not Needed Description: .........................................................
Policy 3: Log All Accesses to Accounting Systems Sarbanes- Description: ......................................................... Oxley Policy 4: Retain Audit Trails and Emails for 5 Years Policies Description: ......................................................... Policy 5: No Sensitive Data on Mobile Devices Description: .........................................................
Data Security Policies
Internal
Principles
Data Exchange Policies
Statement: .............................................
Overarching organizational norms typically of a restrictive nature providing compulsory prescriptions in certain areas
Factory at Location 1
Principle 3: Business Continuity
Analytics Reporting System
Orders Forecast
Regional Managers
ERP System Financial Data
Customers
All Orders
Orders Retail Outlet at Location 4
4. Anticipated Outcomes ......................................
Implications: ........................................... Global high-level guidelines influencing all decisionmaking and planning in an organization
Customers
Conceptual messages communicating major organizationwide decisions with far-reaching consequences
Capability 1.1
Business Drivers:
Strategic Links:
Key Decisions:
· Driver 1 · Driver 2 · Driver 3
· Link to Strategy 1 · Link to Strategy 2 · Link to Strategy 3
· Decision 1 · Decision 2 · Decision 3
CRM System
Client Data
Operations
Outbound Logistics
Marketing and Sales
Service
Activity 1
Activity 1
Activity 1
Activity 1
Activity 1
Activity 2
Activity 2
Activity 2
Capability 1.2
Capability 1.3
Capability 1.4
Capability 2.1
Customer Group 1
Non-Strategic
High-level graphical descriptions of the current operational flows of an organization
Local System 2
Channel 2
Capability 3
Activity 2
Capability 3.1
Capability 4
Capability 3.2
Capability 4.1
Capability 4.2
Capability 4.3
Strategic
Core Activities
Regular
Structured graphical representations of the added value chain of an organization
Important
Capability 2
Strategic
Structured graphical representations of all organizational business capabilities, their relationship and hierarchy
Initiative 3.2
Real-Time Predictive Analytics
Channel 2
Architecture Changes:
Business Outcomes:
Customer Outcomes:
· Change 1 · Change 2 · Change 3
· Outcome 1 · Outcome 2 · Outcome 3
· Outcome 1 · Outcome 2 · Outcome 3
High-level graphical descriptions of the desired longterm future state of an organization
System 2
Initiative 3.1
System 3
Planned
Approved
Structured graphical views of all planned IT initiatives in specific business areas having direct business value
Business
Technology 2 Technology 3
Technology 5 Technology 8
How Artifacts Describe?
Technology 6
Technology 11 Technology 10
No Change
Moved
New
Executive-level analyses of relevant technology trends and their potential impact on the business of an organization
IT Principles IT Principle 1: Prefer Open Source Solutions Description: ......................................................
Applications
IT Principle 2: Log All Main Operations Description: ...................................................... IT Principle 3: Use Scalable Storage Description: ......................................................
Data
IT Principle 5: Use Middleware for Integration Description: ......................................................
Integration
IT Principle 6: Avoid Binary Integration Protocols Description: ...................................................... IT Principle 7: Host in the Cloud Description: ......................................................
Infrastructure
IT Principle 8: Dedicated Server for Each System Description: ...................................................... IT Principle 9: Place Public Systems in DMZ Description: ......................................................
Security
Specific
Rules
Structures
Changes
Considerations
Visions
Outlines
Content: Global conceptual rules and fundamental considerations important for business and relevant for IT Format: Expressed in simple intuitive formats, often as brief written statements Represent: Overarching organizational context for information systems planning Focus: Do not focus on specific points in time or focus on the longterm future Usage: Developed collaboratively by senior business leaders and architects and then used to influence all architectural decisions Lifecycle: Developed once and then updated according to the ongoing changes in the business environment Purpose: Help achieve the agreement on basic principles, values, directions and aims Benefits: Improved overall consistency between business and IT
Content: High-level conceptual descriptions of an organization from the business perspective Format: Expressed in brief informal formats, often as simple onepage diagrams Represent: Shared views of an organization and its future agreed by business and IT Focus: Often focus on the long-term future up to 3-5 years ahead Usage: Developed collaboratively by senior business leaders and architects and then used to guide IT investments, identify, prioritize and launch new IT initiatives Lifecycle: Developed once and then updated according to the ongoing
Very early idea-level descriptions of proposed IT initiatives and their justifications
Options Assessments
Content: High-level descriptions of specific IT initiatives understandable to business leaders Format: Expressed as a mix of textual descriptions and simple diagrams Represent: Benefit, time and price tags for proposed IT initiatives Focus: Usually focus on the mid-term future up to 1-2 years ahead Usage: Developed collaboratively by architects and business leaders and then used to evaluate, approve and fund specific IT initiatives Lifecycle: Developed at the early stages of IT initiatives to support decision-making and then archived Purpose: Help estimate the overall business impact and value of proposed IT initiatives Benefits: Improved efficiency and ROI of IT investments
changes in strategic business priorities
Purpose: Help achieve the alignment between IT investments and long-term business outcomes Benefits: Improved strategic effectiveness of IT investments
6. Preliminary Estimations Time: 6-12 months Cost: $1.5-3.0 million
Language: Technology-neutral business language Domains: Business domain and often other relevant domains at a high level Format: Brief, largely informal and include only the most essential information Stakeholders: Business leaders and architects Role: Communication interfaces between business and IT Purpose: Help business leaders manage IT
Option
IT Principle 10: Secure by Default Description: ......................................................
Process Users Old System
New System
Time: 8-13 months Cost: $2.0-3.5 million Advantages: ............. Disadvantages: ......... Risks: ........................
Functionality: 5 Feasibility: 2 Alignment: 4
Time: 4-7 months Cost: $1.0-1.7 million Advantages: ............. Disadvantages: ......... Risks: ........................
Functionality: 3 Feasibility: 3 Alignment: 1
Time: 3-5 months Cost: $0.7-1.3 million Advantages: ............. Disadvantages: ......... Risks: ........................
Functionality: 2 Feasibility: 5 Alignment: 2
Total Score: 11
Solution 2: Process Users Old System
Extra System
Total Score: 7
Solution 3: Process Users Enhanced System
Total Score: 9
Lists of high-level implementation options for specific IT initiatives with their pros and cons
Solution Overviews
Standards
Landscapes
Designs
Content: Global technical rules, standards, patterns and best practices relevant for IT systems Format: Can be expressed in various formats, often using strict notations Represent: Proven reusable means for IT systems implementation Focus: Do not focus on specific points in time or focus on the current state Usage: Developed collaboratively by architects and technical subjectmatter experts and used to shape architectures of all IT initiatives Lifecycle: Developed on an as-necessary basis and updated according to the ongoing technology progress Purpose: Help achieve technical consistency, technological homogeneity and regulatory compliance Benefits: Faster initiative delivery, reduced costs, risks and complexity
Content: High-level technical descriptions of the organizational IT landscape Format: Expressed in strict formats, often as complex one-page diagrams using formal modeling notations Represent: Knowledge base of reference materials on the IT landscape Focus: Often focus on the current state Usage: Developed and maintained by architects and used to rationalize the IT landscape, manage the lifecycle of IT assets and plan new IT initiatives Lifecycle: Developed on an as-necessary basis and updated according to the ongoing evolution of the IT landscape Purpose: Help understand, analyze and modify the structure of the IT landscape Benefits: Increased reuse and agility, reduced duplication and legacy
Content: Detailed technical and functional descriptions of specific IT projects actionable for project teams Format: Expressed as a mix of text, tables and complex diagrams, can be voluminous and often use formal modeling notations Represent: Communication interfaces between architects and project teams Focus: Usually focus on the short-term future up to 1 year ahead Usage: Developed collaboratively by architects, project teams and business representatives and then used by project teams to implement IT projects Lifecycle: Developed at the later stages of IT initiatives to support implementation and then archived Purpose: Help implement approved IT projects according to business and architectural requirements Benefits: Improved quality of the project delivery
1. Overview and Goals .................................. 2. Scope and Stakeholders ......................................... 3. Essential Requirements ........................................ 4. Business Benefits .............................. 5. Capability Impact
Language: Technical IT-specific language Domains: Various technical domains and sometimes also business domain Format: Can be voluminous, formal and include comprehensive details Stakeholders: Architects and other IT specialists Role: Internal IT tools invisible to business Purpose: Help architects organize IT
8. Business Process Changes Process 1 Now (10 days in total): Step 1
Step 2
Step 3
3 days
5 days
2 days
Process 1 Will Be (5 days in total): Step 1
Step 2
2 days
3 days
9. Architectural Overview
· Order Fulfilment (High) · Order Management (Low) · Customer Analytics (Low) 6. Involved Partners
Process 1 Step 1
Client 1
· IBM · Accenture 7. Estimations Time: 6-8 months Cost: $1.2-1.5 million
Step 2
App 1
App 2
DB 1
DB 2
10. Key Risks ...................
High-level descriptions of specific proposed IT solutions understandable to business leaders
IT
Global high-level IT-specific guidelines influencing all ITrelated decisions and plans in an organization
Score
Solution 1:
Enterprise Architecture IT-Focused
IT Principle 4: Backup All Permanent Data Description: ......................................................
Business-Focused
Adopt Technology 1
Technology 13
New ERP Module
Clients
What Artifacts Describe?
Generic
Analytical Reports
Technology 12
System 2
Funded
Process 1
Abstract definitions of the main data entities critical for the business of an organization and their relationship
Technology 9
Capability 4
1. Initiative Summary ................................. 2. Goals and Objectives .................................... 3. Anticipated Benefits ................................... 4. Scope and Stakeholders ......................................... 5. Solution Sketch
Title Type Price
Technology 4
Initiative 3.5
Initiative 4.1
System 2
Product
Technology 7
System 4
Initiative 4.2
Bank Card
Trial
Capability 3
Initiative Proposals
Date Quantity Discount
Assess
System 3
Initiative 3.4
Capability 4
Order
Hold
System 1
Initiative 3.3
System 2
Global System
Customer
Type Number Expiry Date
Capability 2 Initiative 2.2
Conceptual Data Models
Name Date of Birth Location Phone
System 2
Initiative 2.1
System 1
Capability 4.4
System 1
Initiative 1.3
System 1
Activity 3 Capability 3.4
Capability 1
Initiative 1.2
Capability 3
Channel 1
Customer Group 2
Future State
2018
System 2
Capability 2.4
Customer Group 1
2017
Now
Capability 1
System 1
Head Office at Location 3
Retail Outlet at Location 5
Simple Reporting
Capability 2.2
Capability 2.3
2016
Initiative 1.1
Local System 1
Channel 1
Current State System 1
3-Year Target Architecture:
Capability 3.3
Orders
Capability 2
Customer Group 2
Inbound Logistics
Activity 3 Goods
Rationale: ...............................................
Goal 3
Capability 1
Information Technology Services
Analysts
Statement: .............................................
Goal 2
Roadmaps
Current Architecture:
Logistic Information
Goods Data Warehouse
Goal 1
Procurement and Supplier Management
Executives All Transactional IT Systems
Business Strategy
Financial and Administrative Management
Transportation
Introduce a data warehouse aggregating relevant data from all IT systems to enable the analytical capability
Statement: .............................................
Target States
Warehouse at Location 2
3. Recommended Strategic Direction for IT
Implications: ...........................................
Policy 10: Do Not Store Health Data in the Cloud Description: .........................................................
Inability to provide a timely and comprehensive trends analysis to relevant business stakeholders
Principle 2: Single Customer View
Business Capability Models
Human Resource Management
2. Identified IT Capability Gaps
Implications: ...........................................
Policy 7: Do Not Share Key Data with Third Parties Description: .........................................................
Value Chains
Goods Delivery
Rationale: ...............................................
Rationale: ...............................................
Policy 9: Use Only the PCI DSS Compliant Cloud Description: .........................................................
Context Diagrams
1. Current Business Strategy ...........................................
Principle 1: Standardized Business Processes
Policy 6: Store Credit Cards in Encrypted Formats Description: .........................................................
Policy 8: Share Client Data with Trusted Partners Description: .........................................................
Cloud Hosting Policies
Direction Statements
Technology Reference Models Delivery Technology 1
Describe: Broad global rules defining an organization or its divisions Scope: Very wide, often cover an entire organization Format: Often textual Question: How do we work or want to work? Lifecycle: Permanent, created once and then periodically updated Role: Basis for all other planning decisions Purpose: Help achieve consistency and homogeneity of all planning decisions
Channels
Technology 2
Technology 1
Technology 2
Applications and Integration Technology 1
Technology 2
Technology 3
Technology 4
Databases and Information Management Technology 1
Technology 2
Technology 3
Technology 4
Describe: High-level structures of an organization or its parts Scope: Wide, often cover large parts of an organization Format: Usually graphical Question: What approximately do we have or want to have? Lifecycle: Permanent, created once and then continuously updated Role: High-level “maps” facilitating decision-making Purpose: Help understand what changes are desirable and how to implement them
Preliminary Solution Designs
Describe: Specific proposed incremental changes to an organization Scope: Narrow, limited to separate IT initiatives or projects Format: Mix of textual and graphical Question: What exactly are we going to change right now? Lifecycle: Temporary, created for specific purposes and then discarded Role: Tactical plans of an organization Purpose: Help plan separate changes in detail
1. Brief Overview .......................... 2. Goals and Objectives .................................... 3. Scope and Stakeholders ......................................... 4. Business Requirements ........................................ 5. Involved Partners · IBM · Accenture
Security and Access Management Technology 1
Technology 2
Technology 3
6. Key Technologies Technology 4
· Java EE Platform · IBM BPM and DB2
Infrastructure and Networks Technology 1
Technology 2
Unsupported
Technology 3
Current
7. Accurate Estimations
8. Technical Risks ..........................
Emerging
Structured graphical representations of all technologies used in an organization
Patterns
Guideline 1: Run Applications as OS Services
Network Protocol Standards
Guideline 3: Avoid Using UDP Multicast Description: .........................................................
Data Encryption Standards
Guideline 5: Use 256-Bit Encryption Keys Description: .........................................................
Guideline 4: Prefer REST Over SOAP Description: .........................................................
Guideline 6: Store MD5 Hashes of Passwords Description: .........................................................
Interface Design Guidelines
Guideline 7: Use Web-Safe Colours Description: .........................................................
Secure Coding Guidelines
Guideline 9: Initialize Variables to Safe Defaults Description: .........................................................
Guideline 8: Place Menu in the Top Right Corner Description: .........................................................
Guideline 10: Validate All Incoming Data Description: .........................................................
IT-specific implementation-level prescriptions applicable in narrow technology-specific areas or domains
Essential
(Used in the majority of EA practices)
Common
Step 1
Step 2
Client 1
App 1
App 2
DB 1
DB 2
Server 1
Server 2
10. Application Interaction App 1
DB 1
App 2
DB 2
Preliminary high-level technical and functional designs of specific approved IT solutions
Logical Data Models
Server Description: ......................................................... Deployment Guideline 2: Store Deployment Packages in VCS Standards Description: .........................................................
Process 1
Time: 8-9 months Cost: $2.1-2.3 million
Technology 4
Guidelines
9. High-Level Architecture
Order
Customer id: Integer name: String date_of_birth: Date location: String phone: String 1
* Bank_Card id: Integer customer_id: Integer type: String number: String expiry_date: Date
1
*
id: Integer customer_id: Integer product_id: Integer date: Date quantity: Integer discount: Float
Product id: Integer title: String type: String price: Float
Logical or even physical platform-specific definitions of the key data entities and their relationship
(Used in 25-50% of EA practices)
Uncommon
(Used in 10-25% of EA practices)
Enterprise System Portfolios
1. Description: Simple Failover Cluster ..........................
Asset
Application 1 .............
............
.......
...............
2. Applicability ..........................
Application 2 .............
............
.......
...............
Application 3 .............
............
.......
...............
Application 4 .............
............
.......
...............
System 1
.............
............
.......
...............
Capability 1.3
System 2
.............
............
.......
...............
System 1
System 3
.............
............
.......
...............
3. Rationale ..........................
* 1
Inventories
Inbound Requests
JBoss
Nginx Load Balanced
Application
JBoss Application
Red Hat Linux
Replication
MySQL (Slave)
Red Hat Linux
Generic reusable solutions to commonly occurring problems in the design of IT systems
Owners
Cost
Problems
System 4
.............
............
.......
...............
System 5
.............
............
.......
...............
Database 1
.............
............
.......
...............
Database 2 MySQL (Master)
Purpose
.............
............
.......
.............
............
.......
...............
Database 4
.............
............
.......
...............
Reuse
Capability 2
Capability 1.1
Capability 1.2
Capability 2.1
Capability 2.2
System 1
System 1
System 1
System 1
System 2 System 3
System 2
System 2
Capability 1.4
Capability 2.3
System 1
System 1
System 2
Capability 3
Invest
Structured catalogs of currently available IT assets describing their essential properties and features
Capability 2.4 System 1 Update
System 2
Capability 4.1
Capability 4.2
System 1
System 1
System 1
Capability 4.3
Capability 4.4
System 1
System 1
System 2
System 2
System 1
Legacy
Active
RPC
App 3 Binary
EJB
App 4
App 5
App 7 (Plan)
Reporting
DB 4 (Plan) DB 3
ETL
Warehouse
Solution Designs
Q3-4 2016 Q1-2 2017 Q3-4 2017 Q1-2 2018
Office Workstations and Infrastructure
Now
Initiative 4
Initiative 2
Initiative 10 Initiative 6
Application and Integration Platforms
Initiative 9
Network and Cloud Infrastructure Security and Identity Management
Process 1
Initiative 7
Step 1 Initiative 3
Initiative 11
Not Sponsored
Structured high-level mappings of all essential IT systems to relevant business capabilities
Technical “boxes and arrows” schemes of different scopes and granularities describing the organizational IT landscape
5. Data Architecture Table 1 Column 1: Int Column 2: Char Column 3: Byte
Table 2
DB 1 1
*
Column 1: Char Column 2: Clob Column 3: Blob
6. Application Architecture Call
App 1
Store
DB 1
Step 2
Client 1
App 2 Reply
Read
7. Infrastructure Architecture Internet
Initiative 5 App 1
App 2
DB 1
DB 2
Server 1
Server 2
Initiative 1 Initiative 8
DB 2
Strategic
1. Brief Overview .......................... 2. Goals and Objectives .................................... 3. Detailed Requirements ....................................... 4. Solution Context
Form
Server Operating Systems and Hardware
Messaging
REST
SOA
Capability 3.2
System 1
App 2
Calls from Partners
Enterprise Service Bus
System 1
Capability 3.4
App 6 (Plan)
Capability 4
System 2
App 1
BU
Queue
Capability 3.1
Capability 3.3
DB 1
IT Roadmaps Domain
Backup
CRM
System 3
...............
Database 3
Decommission
Capability 1
Landscape Diagrams
CIO
Linux Server 1 VM 1
Firewall
Linux Server 2
Switch
Hot Standby
VM 2
Business
Structured graphical views of all planned IT initiatives of a purely technical nature having no visible business impact
Detailed technical and functional specifications of approved IT solutions actionable for project teams
Enterprise Architecture on a Page v1.2 (http://eaonapage.com), Svyatoslav Kotusev (
[email protected])
