Transcript Business Architecture: Aligning Business & IT Stratagies

DPI – May 2003
Business Architecture:
Aligning Business and IT Strategies
Presenter: Mike Giovinazzo
1
No part of this presentation may be reproduced
or published without prior written permission
Our Objectives Today





2
Business architecture and the Zachman framework
Why Business modeling in a public sector enterprise
is different
How architecture becomes the foundation for
business / IT alignment
The value of using Business Architecture and a
Management Reference Model for government
services, and
The most recent trends in business architecture
across various levels of government in Canada and
abroad
Architecture is…

ANSI/IEEE Std 1471-2000:
"the fundamental organization of a
system, embodied in its components,
their relationships to each other and
the environment, and the principles
governing its design and evolution"
3
Policy
Design
Social
Goals
Clients
Business to IT
Architecture
Programs
& Services
Processes
Events
Resources
Architectural
frameworks
create structure and
formal alignment of
policy, work and systems
design to meet the goals
of an organization under
constant change.
4
Business
Design
Organization
Roles
Workflow
Locations
Domains
Application
Function
Nodes
Automation
Design
Interfaces
Information
Infrastructure
Components
Enterprise Architecture
Enterprise Architecture
Innovation
Opportunities
Business
Vision
Business
Architecture
Business
Requirements
Alignment &
Integration
Requirements
Information
Architecture
Application
Architecture
Integration
Requirements
Technology
Architecture
5
Business
Requirements
Security
Architecture
Integration
Requirements
Business & IM/IT
Innovation
Opportunities
Business &
IM/IT
Innovation
Opportunities
Zachman vs Business Architecture
ENTERPRISE ARCHITECTURE - A FRAMEWORK
DATA
SCOPE
(CONTEXTUAL)
List of Things Important
to the Business
Planner
ENTITY = Class of
Business Thing
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM
MODEL
(LOGICAL)
FUNCTION
How
List of Processes the
Business Performs
NETWORK
Where
List of Locations in which
the Business Operates
PEOPLE
Who
List of Organizations
Important to the Business
TIME
When
List of Events Significant
to the Business
Business Architecture
Function = Class of
Business Process
Node = Major Business
Location
e.g. Semantic Model
e.g. Business Process Model
e.g. Business Logistics
System
Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
e.g. Logical Data Model
e.g. Application Architecture
e.g. Distributed System
Architecture
People = Major Organizations
Time = Major Business Event
e.g. Work Flow Model
e.g. Master Schedule
People = Organization Unit
Work = Work Product
e.g. Human Interface
Architecture
Time = Business Event
Cycle = Business Cycle
e.g. Processing Structure
MOTIVATION
Why
List of Business Goals/Strat
SCOPE
(CONTEXTUAL)
Ends/Means=Major Bus. Goal/
Critical Success Factor
e.g. Business Plan
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
End = Business Objective
Means = Business Strategy
e.g., Business Rule Model
SYSTEM
MODEL
(LOGICAL)
Information Application Technology Organization Time Cycle
Rules
Architecture Architecture Architecture Architecture Architecture Architecture
Ent = Data Entity
Reln = Data Relationship
Proc .= Application Function
I/O = User Views
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
TECHNOLOGY
MODEL
(PHYSICAL)
e.g. Physical Data Model
e.g. System Design
e.g. Technology Architecture
e.g. Presentation Architecture
e.g. Control Structure
e.g. Rule Design
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
End = Condition
Means = Action
Builder
Designer
DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
SubContractor
6
What
TM
FUNCTIONING
ENTERPRISE
Proc.= Computer Function
I/O = Data Elements/Sets
Node = Hardware/System
Software
Link = Line Specifications
People = User
Work = Screen Format
e.g. Security Architecture
e.g. Data Definition
e.g. Program
e.g. Network Architecture
Ent = Field
Reln = Address
Proc.= Language Stmt
I/O = Control Block
Node = Addresses
Link = Protocols
People = Identity
Work = Job
e.g. DATA
e.g. FUNCTION
e.g. NETWORK
e.g. ORGANIZATION
John A. Zachman, Zachman International (810) 231-0531
Time = Execute
Cycle = Component Cycle
e.g. Timing Definition
Time = Interrupt
Cycle = Machine Cycle
e.g. SCHEDULE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. STRATEGY
Designer
DETAILED
REPRESENTATIONS
(OUT-OF
CONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
21
Government is Different

Mandate
Retailer closes East Coast outlets
 Canada Post no longer delivers to Nunavut

Jurisdiction
Commercial product competes with consumer model
 RCMP decides to expand to provinces

Expectations
Door Crasher Special – 50% off to first 500 clients
 E-File promo – first 500 users get 10% income tax rebate

Service Level
Lavish Service is desired and appreciated
 Over Serving is deemed wasteful and extravagant
7
PSRM & Zachman
ENTERPRISE ARCHITECTURE - A FRAMEWORK
DATA
What
SCOPE
(CONTEXTUAL)
List of Things Important
to the Business
Planner
ENTITY = Class of
Business Thing
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
FUNCTION
How
List of Processes the
Business Performs
NETWORK
Where
List of Locations in which
the Business Operates
PEOPLE
Who
List of Organizations
Important to the Business
Function = Class of
Business Process
Node = Major Business
Location
e.g. Business Process Model
e.g. Business Logistics
System
Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
e.g. Logical Data Model
e.g. Application Architecture
e.g. Distributed System
Architecture
e.g. Human Interface
Architecture
e.g. Semantic Model
TIME
When
List of Events Significant
to the Business
TM
MOTIVATION
Why
List of Business Goals/Strat
People = Major Organizations
Time = Major Business Event
Ends/Means=Major Bus. Goal/
Critical Success Factor
e.g. Work Flow Model
e.g. Master Schedule
e.g. Business Plan
Business Architecture
SYSTEM
MODEL
(LOGICAL)
SCOPE
(CONTEXTUAL)
Time = Business Event
Cycle = Business Cycle
e.g. Processing Structure
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
End = Business Objective
Means = Business Strategy
e.g., Business Rule Model
SYSTEM
MODEL
(LOGICAL)
Ent = Data Entity
Reln = Data Relationship
Proc .= Application Function
I/O = User Views
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
TECHNOLOGY
MODEL
(PHYSICAL)
e.g. Physical Data Model
e.g. System Design
e.g. Technology Architecture
e.g. Presentation Architecture
e.g. Control Structure
e.g. Rule Design
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
Proc.= Computer Function
I/O = Data Elements/Sets
Node = Hardware/System
Software
Link = Line Specifications
Time = Execute
Cycle = Component Cycle
End = Condition
Means = Action
Builder
e.g. Program
e.g. Network Architecture
Designer
DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
Governance
Outcomes
e.g. Data Definition
Ent = Field
Reln = Address
e.g. DATA
Proc.= Language Stmt
I/O = Control Block
e.g. FUNCTION
Node = Addresses
Link = Protocols
e.g. NETWORK
People = User
Work = Screen Format
e.g. Security Architecture
People = Identity
Work = Job
e.g. ORGANIZATION
e.g. Timing Definition
Time = Interrupt
Cycle = Machine Cycle
e.g. SCHEDULE
Zachman Framework
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. STRATEGY
Client
Organizations
Designer
Accomplish
Accountability
John A. Zachman, Zachman International (810) 231-0531
8
Provider
Organizations
DETAILED
REPRESENTATIONS
(OUT-OF
CONTEXT)
SubContractor
Roles
Responsibility
Deliver
Outputs
Authority
Used
in
FUNCTIONING
ENTERPRISE
21
Public Service Reference Model
Public Service Reference Model
Provider
Organization
Jurisdictions
Governance
Outcomes
& Impacts
Client
Organizations
Programs
Accomplish
Roles
Accountability
Services
Outputs
Responsibility
Deliver
Processes
Authority
9
Used in
Resources
Individual
Clients
Zachman Rows 1 & 2
DATA
SCOPE
(CONTEXTUAL)
Planner
What
List of Things Important to be
Business
Entity = Class of Business Thing
e.g. Semantic Model
FUNCTION
How
List of Processes the Business
Performs
Process = Class of Business Process
e.g. Process Model
NETWORK
Where
List of Locations in which the
Business operates
Node = Major Business Location
e.g. Business Logistics System
PEOPLE
Who
TIME
When
MOTIVATION
List of Organizations Important to the
Business
List of Events/Cycle Significant to the
Business
People = Major Organizations
Time = Major Business Event/Cycle
End/Means = Major Business Goal/
Strategy
e.g. Master Schedule
e.g. Business Plan
e.g Work Flow Model
List of Business Goals/Strategies
BUSINESS MODEL
(CONCEPTUAL)
Owner
10
Entity = Business Entity
Relationship = Business Relationship
Node = Business Location
Link = Business Linkage
Node = Business Location
Link = Business Linkage
Why
People = Organizational Unit
Work = Work Product
Time = Business Event
Cycle = Business Cycle
End = Business Objective
Means = Business Strategy
PSRM Elements in the
Zachman Framework
What
How
Where
Who
When
Why
Row 1:
Programs
Parties
Resources
Services
Jurisdictions
Events
Needs
Roles
Locations
Areas
Goals
Target
Groups
Cycles
Workflows
Schedules
Strategies
Row 2:
Semantic
Model
Service
Process
Models
Business
Network
Model
Scenarios
Other Models
Service Integration
and Alignment Model
11
Program Service
Alignment Models
State Transition
Models
Performance
Metrics
Business Architecture is not
just for IT alignment
Common Business View
Business Plane
Automation Plane
12
Three Dimensions of
Alignment
Planners care about Strategic Alignment
Business
Drivers
Values
Opportunities
Options
Goals
Design
Standards
Design
Elements
Architects care about
Design Alignment
13
Joint Interests
Priorities
Objectives
Target
Designs
Current
Designs
Strategies
Justifications
Human
Factors
Change Status
Initiatives
Readiness
Scope
Linkages
State
Capabilities
Resources
Milestones
Implementation
Dependencies
Delivery Managers care about
Logistical Alignment
Business Architecture – (CMM)
Capability Maturity Model
No
Standard
Framework
Independent
Project
Frameworks
MultiProject
Alignment
Change
Management
WideSpread
MultiProgram
Re-Use
• Business architecture and IT architecture capability
maturity may evolve at different rates
• Methodology maturity is also evolving
EWTA
14
Zachman
PSRM
Enterprise/Program/Project
Governance
Enterprise
ENTERPRISE ARCHITECTURE - A FRAMEWORK
DATA
What
FUNCTION
How
Where
PEOPLE
Who
TIME
When
TM
MOTIVATION
Why
List of Things Important
to the Business
Planner
ENTITY = Class of
Business Thing
Function = Class of
Business Process
Node = Major Business
Location
e.g. Semantic Model
e.g. Business Process Model
e.g. Business Logistics
System
Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
e.g. Logical Data Model
e.g. Application Architecture
e.g. Distributed System
Architecture
e.g. Human Interface
Architecture
e.g. Processing Structure
Ent = Data Entity
Reln = Data Relationship
Proc .= Application Function
I/O = User Views
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
e.g. Physical Data Model
e.g. System Design
e.g. Technology Architecture
e.g. Presentation Architecture
e.g. Control Structure
e.g. Rule Design
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
Proc.= Computer Function
I/O = Data Elements/Sets
Node = Hardware/System
Software
Link = Line Specifications
e.g. Program
e.g. Network Architecture
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
List of Processes the
Business Performs
NETWORK
SCOPE
(CONTEXTUAL)
SYSTEM
MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
e.g. Data Definition
List of Locations in which
the Business Operates
List of Organizations
Important to the Business
List of Business Goals/Strat
People = Major Organizations
Time = Major Business Event
Ends/Means=Major Bus. Goal/
Critical Success Factor
e.g. Work Flow Model
e.g. Master Schedule
e.g. Business Plan
Time = Business Event
Cycle = Business Cycle
End = Business Objective
Means = Business Strategy
People = Organization Unit
Work = Work Product
People = User
Work = Screen Format
e.g. Security Architecture
Ent = Field
Reln = Address
Proc.= Language Stmt
I/O = Control Block
Node = Addresses
Link = Protocols
People = Identity
Work = Job
e.g. DATA
e.g. FUNCTION
e.g. NETWORK
e.g. ORGANIZATION
John A. Zachman, Zachman International (810) 231-0531
List of Events Significant
to the Business
Time = Execute
Cycle = Component Cycle
e.g. Timing Definition
Time = Interrupt
Cycle = Machine Cycle
e.g. SCHEDULE
e.g., Business Rule Model
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Designer
End = Sub-condition
Means = Step
e.g. STRATEGY
Project 3
TECHNOLOGY
MODEL
(PHYSICAL)
ENTERPRISE ARCHITECTURE - A FRAMEWORK
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
End = Condition
Means = Action
e.g. Rule Specification
Program
Owner
SYSTEM
MODEL
(LOGICAL)
DATA
SCOPE
(CONTEXTUAL)
What
List of Things Important
to the Business
FUNCTION
How
List of Processes the
Business Performs
NETWORK
Where
List of Locations in which
the Business Operates
PEOPLE
Who
List of Organizations
Important to the Business
TIME
When
List of Events Significant
to the Business
MOTIVATION
Why
List of Business Goals/Strat
What
Planner
21
ENTERPRISE
MODEL
(CONCEPTUAL)
ENTITY = Class of
Business Thing
Function = Class of
Business Process
Node = Major Business
Location
e.g. Semantic Model
e.g. Business Process Model
e.g. Business Logistics
System
People = Major Organizations
Time = Major Business Event
Ends/Means=Major Bus. Goal/
Critical Success Factor
e.g. Work Flow Model
e.g. Master Schedule
e.g. Business Plan
Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
e.g. Logical Data Model
e.g. Application Architecture
e.g. Distributed System
Architecture
e.g. Human Interface
Architecture
Ent = Data Entity
Reln = Data Relationship
Proc .= Application Function
I/O = User Views
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
e.g. Physical Data Model
e.g. System Design
e.g. Technology Architecture
e.g. Presentation Architecture
e.g. Control Structure
e.g. Rule Design
SYSTEM
MODEL
(LOGICAL)
Time = Business Event
Cycle = Business Cycle
e.g. Processing Structure
DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
e.g. Data Definition
Proc.= Computer Function
I/O = Data Elements/Sets
Node = Hardware/System
Software
Link = Line Specifications
e.g. Program
e.g. Network Architecture
People = User
Work = Screen Format
e.g. Security Architecture
Ent = Field
Reln = Address
Proc.= Language Stmt
I/O = Control Block
Node = Addresses
Link = Protocols
People = Identity
Work = Job
e.g. DATA
e.g. FUNCTION
e.g. NETWORK
e.g. ORGANIZATION
Time = Execute
Cycle = Component Cycle
e.g. Timing Definition
Planner
Time = Interrupt
Cycle = Machine Cycle
e.g. SCHEDULE
End = Sub-condition
Means = Step
e.g. STRATEGY
e.g. Business Process Model
e.g. Business Logistics
System
Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
e.g. Logical Data Model
e.g. Application Architecture
e.g. Distributed System
Architecture
e.g. Human Interface
Architecture
Designer
Ent = Data Entity
Reln = Data Relationship
Proc .= Application Function
I/O = User Views
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
e.g. Physical Data Model
e.g. System Design
e.g. Technology Architecture
e.g. Presentation Architecture
e.g. Control Structure
e.g. Rule Design
TECHNOLOGY
MODEL
(PHYSICAL)
TECHNOLOGY
MODEL
(PHYSICAL)
DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
SubContractor
SubContractor
FUNCTIONING
ENTERPRISE
FUNCTIONING
ENTERPRISE
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
List of Things Important
to the Business
FUNCTION
How
List of Processes the
Business Performs
NETWORK
Where
List of Locations in which
the Business Operates
PEOPLE
Who
List of Organizations
Important to the Business
ENTITY = Class of
Business Thing
Function = Class of
Business Process
Node = Major Business
Location
e.g. Semantic Model
e.g. Business Process Model
e.g. Business Logistics
System
Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
e.g. Logical Data Model
e.g. Application Architecture
e.g. Distributed System
Architecture
e.g. Human Interface
Architecture
SYSTEM
MODEL
(LOGICAL)
TIME
Proc.= Computer Function
I/O = Data Elements/Sets
e.g. Program
e.g. Network Architecture
Ent = Field
Reln = Address
Proc.= Language Stmt
I/O = Control Block
Node = Addresses
Link = Protocols
People = Identity
Work = Job
e.g. DATA
e.g. FUNCTION
e.g. NETWORK
e.g. ORGANIZATION
Builder
DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
When
List of Events Significant
to the Business
DATA
Why
List of Business Goals/Strat
People = Major Organizations
Time = Major Business Event
Ends/Means=Major Bus. Goal/
Critical Success Factor
e.g. Work Flow Model
e.g. Master Schedule
e.g. Business Plan
Time = Business Event
Cycle = Business Cycle
e.g. Processing Structure
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SubContractor
FUNCTIONING
ENTERPRISE
Proc .= Application Function
I/O = User Views
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
e.g. System Design
e.g. Technology Architecture
e.g. Presentation Architecture
e.g. Control Structure
e.g. Rule Design
Proc.= Computer Function
I/O = Data Elements/Sets
Node = Hardware/System
Software
Link = Line Specifications
e.g. Program
e.g. Network Architecture
e.g. Security Architecture
Ent = Field
Reln = Address
Proc.= Language Stmt
I/O = Control Block
Node = Addresses
Link = Protocols
People = Identity
Work = Job
e.g. DATA
e.g. FUNCTION
e.g. NETWORK
e.g. ORGANIZATION
John A. Zachman, Zachman International (810) 231-0531
15
People = User
Work = Screen Format
Time = Execute
Cycle = Component Cycle
e.g. Timing Definition
Time = Interrupt
Cycle = Machine Cycle
e.g. SCHEDULE
End = Sub-condition
Means = Step
e.g. STRATEGY
FUNCTION
How
NETWORK
Where
PEOPLE
Who
List of Things Important
to the Business
List of Processes the
Business Performs
List of Locations in which
the Business Operates
Planner
ENTITY = Class of
Business Thing
Function = Class of
Business Process
Node = Major Business
Location
e.g. Semantic Model
e.g. Business Process Model
e.g. Business Logistics
System
Ent = Business Entity
Reln = Business Relationship
Proc. = Business Process
I/O = Business Resources
Node = Business Location
Link = Business Linkage
People = Organization Unit
Work = Work Product
e.g. Logical Data Model
e.g. Application Architecture
e.g. Distributed System
Architecture
e.g. Human Interface
Architecture
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM
MODEL
(LOGICAL)
List of Organizations
Important to the Business
TIME
When
List of Events Significant
to the Business
TM
MOTIVATION
Why
List of Business Goals/Strat
Builder
DETAILED
REPRESENTATIONS
(OUT-OF
CONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
21
People = Major Organizations
Time = Major Business Event
Ends/Means=Major Bus. Goal/
Critical Success Factor
e.g. Work Flow Model
e.g. Master Schedule
e.g. Business Plan
Proc .= Application Function
I/O = User Views
Node = I/S Function
(Processor, Storage, etc)
Link = Line Characteristics
TECHNOLOGY
MODEL
(PHYSICAL)
e.g. Physical Data Model
e.g. System Design
e.g. Technology Architecture
Builder
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
Proc.= Computer Function
I/O = Data Elements/Sets
Node = Hardware/System
Software
Link = Line Specifications
e.g. Data Definition
e.g. Program
e.g. Network Architecture
Ent = Field
Reln = Address
Proc.= Language Stmt
I/O = Control Block
Node = Addresses
Link = Protocols
People = Identity
Work = Job
e.g. DATA
e.g. FUNCTION
e.g. NETWORK
e.g. ORGANIZATION
Ent = Data Entity
Reln = Data Relationship
TECHNOLOGY
MODEL
(PHYSICAL)
End = Condition
Means = Action
e.g. Rule Specification
What
SCOPE
(CONTEXTUAL)
SYSTEM
MODEL
(LOGICAL)
Designer
List of Events Significant
to the Business
List of Business Goals/Strat
DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
John A. Zachman, Zachman International (810) 231-0531
Time = Business Event
Cycle = Business Cycle
e.g. Processing Structure
SCOPE
(CONTEXTUAL)
People = Role
Work = Deliverable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means =Action Assertion
e.g. Control Structure
e.g. Rule Design
Time = Execute
Cycle = Component Cycle
End = Condition
Means = Action
e.g. Security Architecture
e.g. Timing Definition
Time = Interrupt
Cycle = Machine Cycle
e.g. SCHEDULE
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
End = Business Objective
Means = Business Strategy
e.g., Business Rule Model
e.g. Presentation Architecture
People = User
Work = Screen Format
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. STRATEGY
Time = Major Business Event
Ends/Means=Major Bus. Goal/
Critical Success Factor
SCOPE
(CONTEXTUAL)
e.g. Master Schedule
e.g. Business Plan
Time = Business Event
Cycle = Business Cycle
End = Business Objective
Means = Business Strategy
e.g. Processing Structure
Time = Execute
Cycle = Component Cycle
e.g., Business Rule Model
Owner
SYSTEM
MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
End = Condition
Means = Action
e.g. Timing Definition
e.g. Rule Specification
Time = Interrupt
Cycle = Machine Cycle
End = Sub-condition
e.g. SCHEDULE
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Means = Step
e.g. STRATEGY
DETAILED
REPRESENTATIONS
(OUT-OF
CONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
21
SCOPE
(CONTEXTUAL)
End = Business Objective
Means = Business Strategy
e.g., Business Rule Model
e.g. Physical Data Model
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
e.g. Security Architecture
TM
MOTIVATION
Ent = Data Entity
Reln = Data Relationship
e.g. Data Definition
People = User
Work = Screen Format
John A. Zachman, Zachman International (810) 231-0531
Designer
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
e.g. Work Flow Model
e.g. Data Definition
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
Builder
DETAILED
REPRESENTATIONS
(OUT-OF
CONTEXT)
People = Major Organizations
Node = Hardware/System
Software
Link = Line Specifications
ENTERPRISE ARCHITECTURE - A FRAMEWORK
What
Why
e.g. Semantic Model
List of Organizations
Important to the Business
Project 2
ENTERPRISE ARCHITECTURE - A FRAMEWORK
MOTIVATION
Node = Major Business
Location
SYSTEM
MODEL
(LOGICAL)
Project 1
DATA
When
Function = Class of
Business Process
Owner
SYSTEM
MODEL
(LOGICAL)
21
John A. Zachman, Zachman International (810) 231-0531
TIME
ENTITY = Class of
Business Thing
ENTERPRISE
MODEL
(CONCEPTUAL)
ENTERPRISE
MODEL
(CONCEPTUAL)
End = Condition
Means = Action
e.g. Rule Specification
Who
Planner
Builder
Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.
Builder
PEOPLE
Where
List of Locations in which
the Business Operates
Designer
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
NETWORK
List of Processes the
Business Performs
SCOPE
(CONTEXTUAL)
End = Business Objective
Means = Business Strategy
e.g., Business Rule Model
How
List of Things Important
to the Business
Owner
Owner
FUNCTION
SCOPE
(CONTEXTUAL)
SubContractor
FUNCTIONING
ENTERPRISE
TM
TM
DATA
DETAILED
REPRESENTATIONS
(OUT-OF
CONTEXT)
SYSTEM
MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF
CONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE
21
Architecture Helps







16
Re-invent service delivery to constituents
and government employees
Enable improves information sharing across
government departments
Maximize return on IT investments
Anticipate infrastructure requirements
Leverage critical and secure data
Promote mission-driven selection of new
technologies
Shrink solution delivery time
Source: Metadata Vice-President Scott Bittler May, 09,2003
The Value
66% • Business is constrained by IT
inability to quickly adapt to
its changing needs
30% • IT a strategic partner with
the business
15% • IT made no contribution at all
10% • IT as expensive overhead
17
Source: Fujitsu’s 2002 Information Technology
Services Management Survey
Food for thought


… focusing on alignment with business
strategy is irrelevant if your "technology
portfolio" is leaking oil, spitting gas and
spewing smoke
… make sure you have your lower level
architectural needs under control before
you start worrying about being the lofty
goals of alignment
Jeff Tash (aka ITscout)
Flashmap Systems
18
Management
Reference Model for IS
Service Delivery Strategies
IT Services
Assessment
Detailed
Analysis
and Design
Performance Metrics Definition
IT Services Mapping
Target IT
Organization
Definition
Roles & Accountabilities
Mapping & Design
IT Services Mapping
IT Mandate Review
19
Organization Design
Detailed Process Design
Roles & Accountabilities
Mapping & Review
Client Satisfaction
Analysis
Customer Relations Strategies
IT Services
Performance
Measurement
Performance Mgmt Programs
Continuous Improvement Prog.
Skills
Requirements
Review
Job Definitions
Training & Development Plans
Architecture Trends
20
Meta Group
– By 2005, 70% of Global 2000 enterprises
will move beyond a pure technology
architecture focus to include enterprise
business architecture (50%), enterprise
information architecture (60%), and
enterprise solution architecture (70%).
Architecture teams that fail to move
beyond a technical focus will come under
increasing pressure to demonstrate
business value.

21
META Trend (March 2003):
In the USA


Legislated or mandated EA initiatives
Established Federal EA PMO
– http://www.feapmo.gov/


Most still struggle with “how-to”
Other trends & signs
– George Bush allocates $1 Billion to EA (Feb 2003)
– Government EA conference – June
– Business Reference Model
22
Clinger-Cohen Act (CCA)
of 1996

CCA has three strong focus areas:
capital planning and investment control,
enterprise architecture, and the resources to
accomplish these processes.
The target goals of the CCA include:
– Establish an EA that includes its current and target states,
– Establish a systematic Capital Planning and Investment
Control (CPIC) process to manage the IT investments,
– Use the EA and CPIC process to maintain the current
architecture and to build the “to be” architecture,
– Use costs, schedule and performance goals to monitor
and mitigate risks, and
– Continuously update and manage the EA and CPIC to
improve success.
23
FEAPMO - USA
“To facilitate efforts to transform the
Federal Government to one that is
citizen-centered, results-oriented, and
market-based, the Office of
Management and Budget (OMB) is
developing the Federal Enterprise
Architecture (FEA), a business-based
framework for Government-wide
improvement”
24
FEAPMO - USA
Performance Reference Model
Business Driven Approach
25
Business Reference Model
Service Component Reference Model
Data Reference Model
Technical Reference Model
Canadian Municipalities

Municipal Reference Model
– Generic business model of municipal
programs and services
– Adopted by MISA (Municipal Information
Systems Association)
– Used by 27+ Canadian municipalities and
at least 2 foreign municipalities
– Proved to be extremely valuable during
the many municipal amalgamations
26
Canadian Provinces

Ontario – perceived leader
– Using PSRM for past 8 years
– Formal architecture and planning process and
governance structure for the province
– Have detailed architecture framework and
standards for Ontario’s Enterprise Information
Architecture

27
Alberta, N.B. & B.C. and perhaps others also
embarking on similar initiatives
Canadian Federal Govmt

Started with FAP (Federated Architecture
Program)
– Iteration One: Connectivity, Access to electronic
information, Public assurances of confidentiality,
improvement of government administration

BTEP (Business Transformation Enablement
Program)
– Next Iteration of FAP
– Much stronger business focus
– BTEP overviews being given to individual
departments, ARB, …
28
More Trends

Business Architecture (BA) still evolving
– Bottom Up trend still evident
– Methods and models being refined
– Tools like artifact repositories are immature

Control & Interest is shifting
– Today: CIO’s to promote BA as part of the
overall Enterprise Architecture
– Business is fast adopting BA and making it part
of the strategic and business planning
29
Some Resources

Business Architecture SIG
– First meeting: target Fall 2003

Enterprise Architecture Open House
– Ontario Public Sector – June 16-18
“Business Transformation through Architecture”


30
www.eacommunity.com
www.zifa.com
Thank You
31