View
258
Download
4
Category
Preview:
Citation preview
Enterprise Architecture – An Overview
Frank TanXiangshen Kong
Agenda
IntroductionJohn Zachman’s Enterprise Architecture (EA) Framework Walk ThroughEA Quality AttributesReference ModelsCase StudyQ & A
Agenda
IntroductionJohn Zachman’s Enterprise Architecture (EA) Framework Walk ThroughEA Quality AttributesReference ModelsCase StudyQ & A
EA Definition
Enterprise Architecture is:“… set of descriptive representations (i.e. models) that are relevant for describing an Enterprise …” (John Zachman)“A blueprint that explains how information technology and management elements works as whole” (US Federal Government)
Enterprise Architecture draws analogy from building architecture
Why EA?
Changing business environment requires highly integrated IT capabilitiesDemand for IT strategy to align with business strategyEver more complex IT projects
EA and Software Architecture
SimilaritiesAbstract approachesEA overarches SA
DifferencesGoals and objectivesEnterprise views vs. System centric viewQuality Attributes
Agenda
IntroductionJohn Zachman’s Enterprise Architecture (EA) Framework Walk ThroughEA Quality AttributesReference ModelsCase StudyQ & A
John Zachman’s EA Framework (diagram)
Zachman Framework – Row 1Scope/Planner’s View
External Requirements and DriversBusiness Function Modeling
Motivation/WhyBusiness goals, objectives and performance measures related to each function Function/How
High-level business functionsData/What
High-level data classes related to eachfunction
People/WhoStakeholders related to each function
Network/WhereOrganization locations related to each
function
Time/WhenCycles and events related to eachfunction
1 Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Zachman Framework – Row 2Enterprise Model/Designer’s View
Business Process ModelsBusiness Function AllocationElimination of Function Overlap and Ambiguity
Motivation/WhyPolicies, procedures and standards for each process
Function/HowBusiness processes
Data/WhatBusiness data
People/WhoRoles and responsibilities in eachprocess
Network/WhereLocations related to each process
Time/WhenEvents for each process and sequencingof integration and process improvements
2
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Zachman Framework – Row 3System Model/Designer’s View
Logical ModelsProject ManagementFunctional RequirementsDefinition
Motivation/WhyPolicies, standards and proceduresassociated with a business rule model
Function/HowLogical representation of informationsystems and their relationships
Data/WhatLogical data models of data and datarelationships underlying information
People/WhoLogical representation of access privilegesconstrained by roles and responsibilities
Network/WhereLogical representation of the distributedsystem architecture for locations
Time/WhenLogical events and their triggered responses constrained by business events and their responses
3
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Zachman Framework – Row 4Technology Model/Builder’s View
Physical ModelsTechnology ManagementSolution Definition and Development
Motivation/WhyBusiness rules constrained by information systems standards
Function/HowSpecifications of applications that operateon particular technology platforms
Data/WhatDatabase management system (DBMS) typerequirements constrained by logical data models
People/WhoSpecification of access privileges tospecific platforms and technologies
Network/WhereSpecification of network devices and theirrelationships within physical boundaries
Time/WhenSpecification of triggers to respond to systemevents on specific platforms and technologies
4
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Zachman Framework – Row 5As Built/Integrator’s View
As BuiltConfiguration ManagementDeployment
Motivation/WhyBusiness rules constrained by specific technology standards
Function/HowPrograms coded to operate on specific technology platforms
Data/WhatData definitions constrained by physical data models
People/WhoAccess privileges coded to control access to specific platforms and technologies
Network/WhereNetwork devices configured to conform to node specifications
Time/WhenTiming definitions coded to sequence activities on specific platforms and technologies
5
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Zachman Framework – Row 6Functioning Enterprise/User’s View
Functioning EnterpriseOperations ManagementEvaluation
Motivation/WhyOperating characteristics of specific technologies constrained by standards
Function/HowFunctioning computer instructions
Data/WhatData values stored in actual databases
People/WhoPersonnel and key stakeholders working within their roles and responsibilities
Network/WhereSending and receiving messages
Time/WhenTiming definitions operating to sequence activities
6
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Agenda
IntroductionJohn Zachman’s Enterprise Architecture (EA) Framework Walk ThroughEA Quality AttributesReference ModelsCase StudyQ & A
EA Quality AttributesMulti-layer view
Scope: business goal, IT strategy, visionContextual: collaborative parties, interoperability Standards,
ownership of the information, etcConceptual: deliverables at logical level, Logical StandardsLogical: deliverables at physical level, etc.Physical: critical Design Decisions, etc.
2-layer viewBusiness viewe.g. business goal, interoperability, processes reusability, etcInformation Systems viewsoftware architecture attributes, e.g. reusability,
interoperability, usability, traceability, etc.
Agenda
IntroductionJohn Zachman’s Enterprise Architecture (EA) Framework Walk ThroughEA Quality AttributesReference ModelsCase StudyQ & A
EA Reference Models
Tool for Enterprise Architecture developmentDescribe generic Enterprise Architecture (usually by industry/sector) independent of organizationProvide common reference points for key performance areasFederal Enterprise Architecture (FEA) Reference Models by the federal government of the USA
FEA Reference Models
Business Reference Model
Technical Reference Model
Agenda
IntroductionJohn Zachman’s Enterprise Architecture (EA) Framework Walk ThroughEA Quality AttributesReference ModelsCase StudyQ & A
Case Study
Walt Disney Enterprise Architecture Overview
Issues
Diverse business myriad of theme parks, media holdings, and film studios with largelydecentralized IT infrastructure1500 applications with many duplicationsExisting applications incapable of supporting new business models and explosion of digital mediaHigh operational costs
Solutions
Establish CIO Board to map business processes to applicationsEstablish Architecture Council with technology leaders from all major business unitsCreate and implement an architectural master plan
Results
Identified applications that are core business enablersEliminated application duplicationsCreated a new services-based layer to insulate Disney’s transaction systems and provide for future growthEstablished blueprint for industry wide collaboration
Before
Theater Operators
“Hold” or “Final”Placed via Fax, Phone, or E-Mail
Sales Manager(human proxy)
Core BusinessSystem
(ShowBiz)
Now
Theater Operators
“Hold” or “Final”Placed via Fax, Phone, or E-Mailor Web Browser,or other interface
(assume almost any UI)Document-based, agile, flexible
Services-basedLayer
Why not this?(services-based architecture/layer)
Coa
rse-
Gra
ined
In/o
ut
Fine-G
rained
In/out
AdditionalSystems / Services
Now
AMC
Theatre Operators to More Distributors
Regal Loews Famous Others…
More work, too hard, lost value
BVPD Warner Bros Universal Sony Others…
FutureAggregated 3rd Party Site
BVPD
AMC Regal Loews Famous Others
Warner Bros Universal Sony
theatrical-distribution.com ?
Future
Coarse-Grained Interfaces In/out
Fine-Grained Interfaces In/out
Core Business Systems
Services Based Layer
Focus awayfrom UI
Documents Orchestration Process WorkflowFocus for new
investment
Cross segmentCross business unit
External partnersFocus on
self serviceanywhere
Think 3rd Party Sites! Think beyond the Browser!
Catalogs/Cache
PDA/Telephone PDA/Telephone and Other and Other Emerging Emerging DevicesDevices
Q & A
Thank You!
Recommended