These 15 EA Landscape Slides represent a Summary View of many other Briefings over the last decade

1. Realizing The Enterprise of The Future – Today!!!™
Integrated Enterprise Architecture Capabilities EVAL
Achieving Competitive Advantage & Success Through The Corporate Blueprint
“Maintaining Global Standards while allowing for Local Differences.“
- SB; 2003 Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
Copyright Boettger 2002 to present http://www.gtra.org/blog/

2. Aligning Corporate Strategy & Goals
Organization of Value Chains and Lines of Business
given priorities through Priority Dimensions BUSINESS Goals, Products,
Customers
STRATEGY
Aligned Metrics are tied to each layer.
Frameworks and methodology for Enterprise Best Practices Tied to Each Specific Sub-
defining and improving value streams,
Business process or activity
processes, sub-processes and activities
Architecture
IT
Applications
IT Infrastructure Options Specific Applications
& IT Infrastructure
Adapted by Boettger 2007 to present

3. Enterprise Architecture Landscape Capabilities Framework
•Shared Access,
•Collaboration
•Shared Browse,
•Content Access •Managed Control
•Search Capability •Reports Distribution
•Report Generation •Dashboard Results
Indexing
S/W, H/W Development
•Request Mgmt •Real-time Asset Visibility
•… •…
Enterprise Source
Control
EA Business Driven Capability (Single View)
Planning, Performance, Market, Risk, Requirements, etal Analyses
•Relationship Visibility & Traceability
•Easily Realized Alignment to any desired depth
Full Traceability of Impact, Cause & Effect
Custom Queries of Configurations
•Planning Foundation for Innovation, Re-engineering…
Opportunities Analysis
•Object Oriented Management & Control Intranet Enterprise Data Stores
•Extensive OOTB Reporting (See Samples) (including EDW Capability)
Responsive to Real Business Questions
Results from
Business & IT
•Extensible Custom Reporting Reports, Dashboards, et al
•Predictive Analysis for Strategic Planning, etc.
•Full Integration of PPM, CMDB Capabilities
•Object Oriented Database Underpinning for EA
•Management, Control, Design, Object Exploitation
•…
Enterprise Architecture Models & Data
Capability Portfolio Mgmt
Project Alignment
Capability Assessment
Initiative Synchronization Name: Skip Boettger
Services Assessment Title: Enterprise Business Architect
Capital Planning
Investment Management Company: Independent Consultant
Capacity Analysis http://www.gtra.org/blog/
…
Copyright Boettger 2002 to 2008 (except as noted)

4. The Goal - Architect the relationships of interrelated parts
Business Driven Integration enabled by applying behavioral
Factors (pyramid) to the Enterprise Planning Reference Model (cube)
Factors: Behavioral Dimensions to consider:
1. Business Function (up and down the functional and organizational chart, silos)
2. Cross Functional (within and across units)
 Shared, common, core processes
3. Members and External Entities (suppliers, vendors) Point of View
 Impact of Enterprise actions on customer satisfaction, service and relationships
4. Time to Market
 Delivering new products and services to the market, to the customer
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/

5. Value of Reference Models
•Define & Reconcile Capability Processes
•Clarifies our Value Chains (Competitive
Advantage)
•Reveals Gaps in Enterprise Core Competencies
•Identifies gaps in Value Streams (Solution Candidates)
•Encourages true alignment between Business &
IT
•Ensures versioning and configuration control of
the IEA ‘known space’
•Ensures Integrity in support of the strategy and
tactics responding to the Vision, Mission,
Objectives, et al
•Baselines for Change/Innovation Impacts
Name: Skip Boettger
Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Measure, Measure, Measure
Copyright Boettger 2002 to present

6. Business & IT Transformation Ecosystem
Strategic Business & IT
Information Transformations
Value Chains & Value Streams
Toward Differentiation
Primary
Activities
BP BP
Run the Business Management Analytics
Plan the Business
ALM & SOA Governance Portfolio Management
Support ITSM
Activities
Excellence in Operational Name: Skip Boettger
IT Operations Information Title: Enterprise Business Architect
Company: Independent Consultant
http://www.gtra.org/blog/
Copyright Boettger 2002 to present
Copyright Boettger 2002 to present

7. EBA & Zachman
EBA DATA PROCESS LOCATION ROLE TIMING MOTIVATION
List of things important to the List of processes the business List of locations in which the List of business responsibilities. List of business events. List of business goals.
business. performs business operates
BUSINESS . . . . BUSINESS
SCOPE . . SCOPE
ENTITY: PROCESS: RESP.: class of business responsibilities EVENT: class of significant business
class of business thing class of business processes. NODE: business location. events. ENDS: mission(s)/goal(s).
Business entities & their inter- Flows between business processes Communications links between Business Organization. Business Cycles. Business Strategies
relationships locations
BUSINESS BUSINESS
MODEL MODEL
PROCESS: business process NODE: business unit
ENTITY: business entity LINK: business relationship RESP: work unit/structure EVENT: business event ENDS: goal(s)/mission(s)
I/O: business resource
REL'SHIP: business rule (org., product, information) WORK: business resources CYCLE: lapse/lag MEANS: tactics/plans
(including information)
Model of the business data Flows between application functions Distribution network Model of the access requirements. Model of the process control Service Support Environment
and inter-relationships structure.
INFORMATION INFORMATION
SYSTEMS ---------------------- SYSTEMS
MODEL MODEL
PROCESS: application function NODE: I.S. function (processor, ENDS: service level agreements
ENTITY: data entity I/O: user views (set of data storage, etc.). RESP: system privilege EVENT: logical process event MEANS: I/S plans & change tactics
RELTNSHIP: data relationship elements). LINK: line characteristics WORK: access requirements CYCLE: precedence/timing
Database Design System Design System Architecture Access Design Processing Environment Availability Design
IBM AS/400
TECHNOLOGY TECHNOLOGY
MODEL Mainf rame
MODEL
IBM Compat ible
ENDS: benchmark models
ENTITY: segment, row, record PROCESS: computer function NODE: hardware/system software RESP: access authorizations EVENT: physical process event MEANS: availability of windows
RELTNSHP: pointer, key, index I/O: screen/device formats LINK: line specifications WORK: access group CYCLE: processing calendar and measures
Database Schema and Program Code and Control Blocks Configuration Definition Access Definition Job Processing Definition Performance Definition
Subschema Definition
TECHNOLOGY TECHNOLOGY
DEFINITION DEFINITION
ENTITY: fields, access privledge EVENT: transactions, job submittal ENDS: benchmark targets
RELTNSHP: access methods, PROCESS: source code NODE: addresses RESP: access object
CYCLE: job & region schedules MEANS: benchmark testing, system
addresses I/O: control blocks LINK: protocols WORK: access profiles
monitoring/tuning
Data Storage Structures and Executable Code System Configuration Access Privileges Processing Schedules System Management Facilities
Access Mechanisms
INFORMATION INFORMATION
Databases, data ..... Programs, jobs, Processors, networks, User-id’s, access controls Batch jobs, transactions, Monitoring facilities, problem
SYSTEM SYSTEM
transactions..... switches. monitors..... ..... run/rerun instructions ..... management .....
Source: Zachman, John A.: “A Framework for Information Systems Architecture.” IBM Systems Journal. V26:N3 1987.
Modified by Boettger 2008

8. EBA/VCOR Overlay with Zachman
VCOR
DATA PROCESS LOCATION ROLE TIMING MOTIVATION
EBA
List of things important to the List of processes the business List of locations in which the List of business responsibilities. List of business events. List of business goals.
business. performs business operates
BUSINESS . . . . BUSINESS
SCOPE . . SCOPE
ENTITY: PROCESS: RESP.: class of business responsibilities EVENT: class of significant business
class of business thing class of business processes. NODE: business location. events. ENDS: mission(s)/goal(s).
Business entities & their inter- Flows between business processes Communications links between Business Organization. Business Cycles. Business Strategies
relationships locations
BUSINESS BUSINESS
MODEL MODEL
PROCESS: business process NODE: business unit
ENTITY: business entity LINK: business relationship RESP: work unit/structure EVENT: business event ENDS: goal(s)/mission(s)
I/O: business resource
REL'SHIP: business rule (org., product, information) WORK: business resources CYCLE: lapse/lag MEANS: tactics/plans
(including information)
Model of the business data Flows between application Distribution network Model of the access requirements. Model of the process control Service Support Environment
and inter-relationships functions structure.
INFORMATION INFORMATION
SYSTEMS ---------------------- SYSTEMS
MODEL MODEL
PROCESS: application function NODE: I.S. function (processor, ENDS: service level agreements
ENTITY: data entity I/O: user views (set of data storage, etc.). RESP: system privilege EVENT: logical process event MEANS: I/S plans & change tactics
RELTNSHIP: data relationship elements). LINK: line characteristics WORK: access requirements CYCLE: precedence/timing
Database Design System Design System Architecture Access Design Processing Environment Availability Design
IBM AS/400
TECHNOLOGY TECHNOLOGY
MODEL Mainf rame
MODEL
IBM Compat ible
ENDS: benchmark models
ENTITY: segment, row, record PROCESS: computer function NODE: hardware/system software RESP: access authorizations EVENT: physical process event MEANS: availability of windows
RELTNSHP: pointer, key, index I/O: screen/device formats LINK: line specifications WORK: access group CYCLE: processing calendar and measures
Database Schema and Program Code and Control Blocks Configuration Definition Access Definition Job Processing Definition Performance Definition
Subschema Definition
TECHNOLOGY TECHNOLOGY
DEFINITION DEFINITION
ENTITY: fields, access privledge EVENT: transactions, job submittal ENDS: benchmark targets
PROCESS: source code NODE: addresses RESP: access object
RELTNSHP: access methods, CYCLE: job & region schedules MEANS: benchmark testing, system
I/O: control blocks LINK: protocols WORK: access profiles
addresses monitoring/tuning
Data Storage Structures and Executable Code System Configuration Access Privileges Processing Schedules System Management Facilities
Access Mechanisms
INFORMATION INFORMATION
Databases, data ..... Programs, jobs, Processors, networks, User-id’s, access controls Batch jobs, transactions, Monitoring facilities, problem
SYSTEM SYSTEM
transactions..... switches. monitors..... ..... run/rerun instructions ..... management .....
Source: Zachman, John A.: “A Framework for Information Systems Architecture.” IBM Systems Journal. V26:N3 1987.
Modified by Boettger 2008

9. Business Driven Domain Stack
Business Area Architecture Structure
Enterprise Business Architecture
Strategy
Value Chain References
Value Stream Architectures, Operational Business Use Case, & Workflow References
Referential, Supportive, & Component Behavior Artifacts
Potential Industry Specific Business Domain (s)
Projects Landscape
IT & Infrastructure Landscape
Core Architectures: Inter-related Referential Architectures
Potential Industry Specific Technical Domain (s)
Copyright Boettger 2002 to present

10. Copyright Boettger 2002 to present

11. Enterprise Architecture is Iterative
Adapted by Boettger 2007 to present

12. Holistic Approach – Common Sense Steps
Instill Learning Circle Practices Adapted by Boettger 2007 to present

13. Integrated EA Reference Models
Steps to Get There
1. Identification and Confirmation of Enterprise Asset Capabilities
2. Identify/Clarify Value Chains, Map Core Processes to the Enterprise Asset Capabilities
3. Create Solution Candidates (Value Streams) supporting Value Chains, thereby identifying Core Processes, Common
Processes, and Shared Services
4. Create Current and Future Behavior Models
a. Enterprise Business Architecture; Business Capability Models, as well as a Meta Model of the Business
b. Create Reference Model Set
5. Iterate and Reconcile Asset Capabilities to Reference Models
6. Evaluate Strategic Prioritization Regarding Needed Business Capability(ies)
7. Evaluate and Build Plans Reflecting Prioritization
8. Build Capability(ies) From Reconciled Results Per Prioritization
a. Solution Scenario Sets (Candidate Value Streams)
9. Generate Use Cases working with IT
10. Generate IT Workflows that reflect #8 and #9
Result: Realize a „known solution space‟ that is Accountable, Measurable, Reconcilable, Most Importantly Credible
Note: Frameworks are not meant to be “templates”, but rather prescriptive guides
Copyright Boettger 2002 to present

14. Leadership develops and directs the Strategy
through Vision, Mission, and Goals
STRATEGY
Engineers and Maps Enterprise Value Chains
Name: Skip Boettger Competitive to the Strategy, deciding on Competitive
Title: Enterprise Business Architect Advantage Differentiation Initiatives
Value Chain(s)
Company: Independent Consultant
http://www.gtra.org/blog/
Designs, Builds and Integrates the Value Streams
Customer Centric Focus of the Enterprise and align with the Strategy
Value Streams
Designs and Builds Architectures
to support Business Strategic Initiatives Business Driven Design
Process, Organizational, Security, Technology Architectures
Optimization for
Effectiveness and Efficiency Operational Excellence
e.g.; workflows supporting Core Processes, etc.
Enabling Business Driven Excellence
Enabling Core Architectures
Infrastructure
Copyright Boettger 1999 to present

15. Thank you…
•Operational Excellence
•Member/Customer Service Name: Skip Boettger
•Better Decision Making
Title: Enterprise Business Architect
•Optimum Value
Company: Independent Consultant
http://www.gtra.org/blog/