presentation (ppt-750k)
TRANSCRIPT
11
DPI – May 2003DPI – May 2003Business Architecture: Business Architecture: Aligning Business and IT Aligning Business and IT StrategiesStrategiesPresenter: Mike Giovinazzo
No part of this presentation may be reproduced or published without prior written permission
22
Our Objectives TodayOur Objectives Today Business architecture and the Zachman Business architecture and the Zachman
frameworkframework Why Business modeling in a public sector Why Business modeling in a public sector
enterprise is differententerprise is different How architecture becomes the foundation for How architecture becomes the foundation for
business / IT alignmentbusiness / IT alignment The value of using Business Architecture and a The value of using Business Architecture and a
Management Reference Model for government Management Reference Model for government services, andservices, and
The most recent trends in business architecture The most recent trends in business architecture across various levels of government in Canada across various levels of government in Canada and abroadand abroad
33
Architecture is…Architecture is… ANSI/IEEE Std 1471-2000:ANSI/IEEE Std 1471-2000:
"the fundamental organization of "the fundamental organization of a system, embodied in its a system, embodied in its components, their relationships to components, their relationships to each other and the environment, each other and the environment, and the principles governing its and the principles governing its design and evolution"design and evolution"
44
Business to IT Architecture
Architectural frameworks create structure and formal alignment of policy, work and systems design to meet the goals of an organization under constant change.
PolicyDesign
BusinessDesign
AutomationDesign
Social GoalsClients
Programs & Services
Processes
Workflow
Organization
Roles
LocationsResources
Events
Domains
Nodes
InfrastructureComponents
ApplicationFunction
Information
Interfaces
55
BusinessArchitecture
Enterprise Enterprise ArchitectureArchitecture
Enterprise Architecture
TechnologyArchitecture
Business & IM/ITInnovation
Opportunities
ApplicationArchitecture
BusinessVision
InnovationOpportunities
InformationArchitecture
BusinessRequirements
Security Architecture
BusinessRequirements
IntegrationRequirements
IntegrationRequirements
Business &IM/IT
InnovationOpportunities
Alignment &Integration
Requirements
66 21
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Contractor
FUNCTIONING
MOTIVATIONPEOPLE
e.g. Rule Specification
End = Sub-conditionMeans = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
ZachmanZachman vs vs Business Business ArchitectureArchitecture
TechnologyArchitecture
ApplicationArchitecture
InformationArchitecture
OrganizationArchitecture
Time CycleArchitecture
RulesArchitecture
Business Architecture
77
Government is Government is DifferentDifferent MandateMandate
Retailer closes East Coast outletsRetailer closes East Coast outlets Canada Post no longer delivers to NunavutCanada Post no longer delivers to Nunavut
JurisdictionJurisdictionCommercial product competes with consumer modelCommercial product competes with consumer model RCMP decides to expand to provincesRCMP decides to expand to provinces
ExpectationsExpectationsDoor Crasher Special – 50% off to first 500 clientsDoor Crasher Special – 50% off to first 500 clients E-File promo – first 500 users get 10% income tax E-File promo – first 500 users get 10% income tax
rebaterebate Service LevelService Level
Lavish Service is desired and appreciatedLavish Service is desired and appreciated Over Serving is deemed wasteful and extravagantOver Serving is deemed wasteful and extravagant
88
21e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-conditionMeans = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Business Architecture
Zachman Framework Public Service Reference Model
ClientOrganizations
OutcomesOutcomes
OutputsOutputs
GovernanceGovernanceProviderOrganizations
Authority
Accountability
Roles Responsibility
AuthorityAuthority
Accountability
Roles
AccountabilityAccountability
Roles ResponsibilityResponsibility
Usedin
Deliver
Accomplish
PSRM & ZachmanPSRM & Zachman
99
ProviderOrganization
Authority
AccountabilityRoles
Responsibility
GovernanceClient
Organizations
IndividualClientsOutputs
Outcomes& Impacts
Public Service Reference Public Service Reference ModelModel
Used in
Deliver
Accomplish
Jurisdictions
Programs
Services
Processes
Resources
1010
Zachman Rows 1 & 2Zachman Rows 1 & 2
List of Things Important to beBusiness
Entity = Class of Business Thing
List of Locations in which theBusiness operates
Node = Major Business Location
List of Organizations Important to theBusiness
People = Major Organizations
List of Events/Cycle Significant to theBusiness
Time = Major Business Event/Cycle
List of Business Goals/Strategies
End/Means = Major Business Goal/Strategy
List of Processes the BusinessPerforms
Process = Class of Business Process
DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why
SCOPE(CONTEXTUAL)
Planner
e.g. Semantic Model
Entity = Business EntityRelationship = Business Relationship
e.g. Process Model
Node = Business LocationLink = Business Linkage
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g Work Flow Model
People = Organizational UnitWork = Work Product
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
e.g. Business Plan
End = Business ObjectiveMeans = Business Strategy
BUSINESS MODEL(CONCEPTUAL)
Owner
1111
PSRM Elements in the PSRM Elements in the Zachman FrameworkZachman Framework
What How Where Who When Why
ResourcesResources
SemanticSemanticModel Model
ServicesServices JurisdictionsJurisdictionsPartiesParties
RolesRoles
TargetTargetGroupsGroups
Row 2:Row 2:
Row 1:Row 1:
SchedulesSchedules
CyclesCyclesLocationsLocations
ScenariosScenarios
WorkflowsWorkflowsBusinessBusinessNetworkNetworkModelModel
ServiceServiceProcessProcessModelsModels
AreasAreas
EventsEvents
PerformancePerformanceMetricsMetrics
Other ModelsService Integration Service Integration
and Alignment Modeland Alignment ModelState TransitionState Transition
ModelsModelsProgram ServiceProgram Service
Alignment ModelsAlignment Models
ProgramsPrograms
NeedsNeeds
GoalsGoals
StrategiesStrategies
1212
Business Architecture is Business Architecture is not just for IT alignmentnot just for IT alignment
Common Business View
Automation Plane
Business Plane
1313
Three Dimensions of Three Dimensions of AlignmentAlignment
ChangeInitiatives
Milestones
Priorities
Resources
ImplementationDependencies
BusinessDrivers
Objectives
Goals
Strategies
Justifications
Options
Linkages
DesignStandards
TargetDesigns
CurrentDesigns
DesignElements
Planners care about Strategic Alignment
Architects care about Design Alignment
Opportunities
Delivery Managers care about Logistical Alignment
Joint Interests
Capabilities
HumanFactors
Readiness
Values
State
Scope
Status
1414
Business Architecture – Business Architecture – (CMM)(CMM)Capability Maturity ModelCapability Maturity Model
NoStandard
Framework
Independent Project
Frameworks
Multi- Project
Alignment
Change Manage-
ment
Wide- Spread Multi- ProgramRe-Use
• Business architecture and IT architecture capability maturity may evolve at different rates• Methodology maturity is also evolving
PSRMEWTA Zachman
1515
Enterprise/Program/Enterprise/Program/ProjectProject Governance Governance
Enterprise
Program
Project 1 Project 2
21e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Defin ition
Ent = Fie ldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/ etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List o f Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Perf orms
Function = Class ofBusiness Process
e.g. Application Arch itecture
I/O = User ViewsProc .= Appl ication Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
Lis t of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specif ications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-conditionMeans = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Act ion Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends /Means= Major Bus. Goal/Critica l Success Factor
List of Events Significant
Time = Majo r Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = S ystem Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Defin ition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human In terface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architec ture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
21e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definit ion
Ent = Fie ldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logi cal Data Model
Ent = Da ta EntityReln = Data Relationship
e.g. Semantic Model
Ent = Bus iness E ntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Da ta Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= La nguage Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteris tics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETW ORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIO NTIMEPEOPLE
e.g. Rule Specificati on
End = Sub-conditionMeans = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Asserti on
End = Business Objec tiveMeans = Busi ness Strategy
List of Business Goals /Strat
Ends /Means=Major Bus. Goal/Crit ical Success Factor
List of Events Signif icant
Time = Major Business E vent
e.g. Processing Structure
Cycle = Processing CycleTime = System E vent
e.g. Control Structure
Cycle = Component Cyc leT ime = Execute
e.g. Timing Definit ion
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Securi ty Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATE GYENTERPRISE
e.g. Business Plan
TM
21e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logica l Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Appl ication Function
e.g. System Design
I/O = Data Elements/SetsProc.= Comput er Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operat es
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e. g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETW ORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-conditionMeans = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g. , Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Defin ition
Cycle = Machine CycleTime = Int errupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organizat ion UnitWork = Work Product
e. g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Formate.g. Security Architecture
People = Ident ityWork = Job
e.g. ORGANI ZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
21e. g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Defini tion
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Element s/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTI ON
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, e tc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Archi tecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-conditionMeans = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Defini tion
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List o f Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Formate. g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
21e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Defini tion
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of T hings Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Arch itecture
I/O = User ViewsProc . = Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Contro l BlockProc. = Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specif ications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Archi tecture
Planner
Owner
Builde r
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condit ionMeans = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/St rat
Ends/Means=Major Bus. Goal /Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Defini tion
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Mast er Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architect ure
People = UserWork = Screen Formate.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZ ATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Project 3
1616
Architecture HelpsArchitecture Helps Re-invent service delivery to Re-invent service delivery to
constituents and government employeesconstituents and government employees Enable improves information sharing Enable improves information sharing
across government departmentsacross government departments Maximize return on IT investmentsMaximize return on IT investments Anticipate infrastructure requirementsAnticipate infrastructure requirements Leverage critical and secure dataLeverage critical and secure data Promote mission-driven selection of new Promote mission-driven selection of new
technologiestechnologies Shrink solution delivery timeShrink solution delivery time
Source: Metadata Vice-President Scott Bittler May, Source: Metadata Vice-President Scott Bittler May, 09,200309,2003
1717
The ValueThe Value
• Business is constrained by IT inability to quickly adapt to its changing needs
• IT a strategic partner with the business
• IT made no contribution at IT made no contribution at allall
• IT as expensive overhead
66%
30%
15%10%
Source: Fujitsu’s 2002 Information Technology Source: Fujitsu’s 2002 Information Technology Services Management SurveyServices Management Survey
1818
Food for thoughtFood for thought … … focusing on alignment with business focusing on alignment with business
strategy is irrelevant if your strategy is irrelevant if your "technology portfolio" is leaking oil, "technology portfolio" is leaking oil, spitting gas and spewing smokespitting gas and spewing smoke
… … make sure you have your lower level make sure you have your lower level architectural needs under control architectural needs under control before you start worrying about being before you start worrying about being the lofty goals of alignment the lofty goals of alignment
Jeff Tash (aka ITscout)Jeff Tash (aka ITscout)Flashmap SystemsFlashmap Systems
1919
Detailed Analysis
and Design
IT ServicesPerformanceMeasurement
SkillsRequirements
Review
Service Delivery Strategies
Customer Relations Strategies
Organization Design
Performance Mgmt Programs
Detailed Process Design
Performance Metrics Definition
Continuous Improvement Prog.
Job Definitions
Training & Development Plans
Client Satisfaction Analysis
IT Services Mapping
IT ServicesAssessment
Roles & Accountabilities Mapping & Review
IT Mandate Review
IT Services Mapping
Target ITOrganization
DefinitionRoles & Accountabilities
Mapping & Design
Management Reference Model for IS
2020
Architecture TrendsArchitecture Trends
2121
Meta GroupMeta Group– By 2005, 70% of Global 2000 enterprises By 2005, 70% of Global 2000 enterprises
will move beyond a pure technology will move beyond a pure technology architecture focus to include enterprise architecture focus to include enterprise business architecture (50%), enterprise business architecture (50%), enterprise information architecture (60%), and information architecture (60%), and enterprise solution architecture (70%). enterprise solution architecture (70%). Architecture teams that fail to move Architecture teams that fail to move beyond a technical focus will come beyond a technical focus will come under increasing pressure to under increasing pressure to demonstrate business value.demonstrate business value.
META Trend (March 2003): META Trend (March 2003):
2222
In the USAIn the USA Legislated or mandated EA initiatives Legislated or mandated EA initiatives Established Federal EA PMOEstablished Federal EA PMO
– http://www.feapmo.gov/http://www.feapmo.gov/ Most still struggle with “how-to”Most still struggle with “how-to” Other trends & signsOther trends & signs
– George Bush allocates $1 Billion to EA George Bush allocates $1 Billion to EA (Feb 2003)(Feb 2003)
– Government EA conference – JuneGovernment EA conference – June– Business Reference Model Business Reference Model
2323
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.
2424
FEAPMO - USAFEAPMO - USA
““To facilitate efforts to transform To facilitate efforts to transform the Federal Government to one the Federal Government to one that is citizen-centered, results-that is citizen-centered, results-oriented, and market-based, the oriented, and market-based, the Office of Management and Budget Office of Management and Budget (OMB) is developing the Federal (OMB) is developing the Federal Enterprise Architecture (FEA), a Enterprise Architecture (FEA), a business-based framework for business-based framework for Government-wide improvement” Government-wide improvement”
2525
FEAPMO - USAFEAPMO - USA
Performance Reference Model
Business Reference Model
Service Component Reference Model
Data Reference Model
Technical Reference Model
Business Driven Approach
2626
Canadian Canadian MunicipalitiesMunicipalities Municipal Reference ModelMunicipal Reference Model
– Generic business model of municipal Generic business model of municipal programs and servicesprograms and services
– Adopted by MISA (Municipal Adopted by MISA (Municipal Information Systems Association) Information Systems Association)
– Used by 27+ Canadian municipalities Used by 27+ Canadian municipalities and at least 2 foreign municipalitiesand at least 2 foreign municipalities
– Proved to be extremely valuable Proved to be extremely valuable during the many municipal during the many municipal amalgamationsamalgamations
2727
Canadian Canadian ProvincesProvinces Ontario – perceived leaderOntario – perceived leader
– Using PSRM for past 8 yearsUsing PSRM for past 8 years– Formal architecture and planning process Formal architecture and planning process
and governance structure for the provinceand governance structure for the province– Have detailed architecture framework and Have detailed architecture framework and
standards for Ontario’s Enterprise standards for Ontario’s Enterprise Information ArchitectureInformation Architecture
Alberta, N.B. & B.C. and perhaps others Alberta, N.B. & B.C. and perhaps others also embarking on similar initiatives also embarking on similar initiatives
2828
Canadian Federal Canadian Federal GovmtGovmt Started with FAP (Federated Started with FAP (Federated
Architecture Program) Architecture Program) – Iteration One: Connectivity, Access to Iteration One: Connectivity, Access to
electronic information, Public assurances of electronic information, Public assurances of confidentiality, improvement of confidentiality, improvement of government administration government administration
BTEP (Business Transformation BTEP (Business Transformation Enablement Program) Enablement Program) – Next Iteration of FAPNext Iteration of FAP– Much stronger business focusMuch stronger business focus– BTEP overviews being given to individual BTEP overviews being given to individual
departments, ARB, … departments, ARB, …
2929
More TrendsMore Trends Business Architecture (BA) still evolvingBusiness Architecture (BA) still evolving
– Bottom Up trend still evidentBottom Up trend still evident– Methods and models being refinedMethods and models being refined– Tools like artifact repositories are immatureTools like artifact repositories are immature
Control & Interest is shiftingControl & Interest is shifting– Today: CIO’s to promote BA as part of the Today: CIO’s to promote BA as part of the
overall Enterprise Architectureoverall Enterprise Architecture– Business is fast adopting BA and making it Business is fast adopting BA and making it
part of the strategic and business planningpart of the strategic and business planning
3030
Some ResourcesSome Resources Business Architecture SIGBusiness Architecture SIG
– First meeting: target Fall 2003First meeting: target Fall 2003 Enterprise Architecture Open HouseEnterprise Architecture Open House
– Ontario Public Sector – June 16-18Ontario Public Sector – June 16-18““Business Transformation through Architecture”Business Transformation through Architecture”
www.eacommunity.comwww.eacommunity.com www.zifa.comwww.zifa.com
3131
Thank YouThank You