Enterprise Architecture An Overview. Frank Tan Xiangshen Kong

Transcription

1 Enterprise Architecture An Overview Frank Tan Xiangshen Kong

2 Agenda Introduction John Zachman s Enterprise Architecture (EA) Framework Walk Through EA Quality Attributes Reference Models Case Study Q & A

3 Agenda Introduction John Zachman s Enterprise Architecture (EA) Framework Walk Through EA Quality Attributes Reference Models Case Study Q & A

4 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

5 Why EA? Changing business environment requires highly integrated IT capabilities Demand for IT strategy to align with business strategy Ever more complex IT projects

6 EA and Software Architecture Similarities Abstract approaches EA overarches SA Differences Goals and objectives Enterprise views vs. System centric view Quality Attributes

7 Agenda Introduction John Zachman s Enterprise Architecture (EA) Framework Walk Through EA Quality Attributes Reference Models Case Study Q & A

8 John Zachman s EA Framework (diagram)

9 Zachman Framework Row 1 Scope/Planner s View Motivation/Why Business goals, objectives and performance measures related to each function Function/How High-level business functions Data/What High-level data classes related to each function People/Who Stakeholders related to each function External Requirements and Drivers Business Function Modeling 1 Contextual Conceptual What How Where Who When Why Contextual Conceptual Network/Where Organization locations related to each function Logical Physical Logical Physical Time/When Cycles and events related to each function As Built Functioning What How Where Who When Why As Built Functioning

10 Zachman Framework Row 2 Enterprise Model/Designer s View Motivation/Why Policies, procedures and standards for each process Function/How Business processes Data/What Business data Business Process Models Business Function Allocation Elimination of Function Overlap and Ambiguity What How Where Who When Why People/Who Roles and responsibilities in each process 2 Contextual Conceptual Contextual Conceptual Network/Where Locations related to each process Logical Physical Logical Physical Time/When Events for each process and sequencing of integration and process improvements As Built Functioning What How Where Who When Why As Built Functioning

11 Zachman Framework Row 3 System Model/Designer s View Motivation/Why Policies, standards and procedures associated with a business rule model Function/How Logical representation of information systems and their relationships Data/What Logical data models of data and data relationships underlying information People/Who Logical representation of access privileges constrained by roles and responsibilities Network/Where Logical representation of the distributed system architecture for locations Time/When Logical events and their triggered responses constrained by business events and their responses Logical Models Project Management Functional Requiremen Definition 3 Contextual Conceptual Logical Physical As Built Functioning What What How How Where Where Who Who When When Why Why Contextual Conceptual Logical Physical As Built Functioning

12 Zachman Framework Row 4 Technology Model/Builder s View Motivation/Why Business rules constrained by information systems standards Function/How Specifications of applications that operate on particular technology platforms Data/What Database management system (DBMS) type requirements constrained by logical data models People/Who Specification of access privileges to specific platforms and technologies Network/Where Specification of network devices and their relationships within physical boundaries Time/When Specification of triggers to respond to system events on specific platforms and technologies Physical Models Technology Management Solution Definition and Development 4 Contextual Conceptual Logical Physical As Built Functioning What What How How Where Where Who Who When When Why Why Contextual Conceptual Logical Physical As Built Functioning

13 Zachman Framework Row 5 As Built/Integrator s View Motivation/Why Business rules constrained by specific technology standards Function/How Programs coded to operate on specific technology platforms Data/What Data definitions constrained by physical data models People/Who Access privileges coded to control access to specific platforms and technologies Network/Where Network devices configured to conform to node specifications Time/When Timing definitions coded to sequence activities on specific platforms and technologies As Built Configuration Management Deployment 5 Contextual Conceptual Logical Physical As Built Functioning What What How How Where Where Who Who When When Why Why Contextual Conceptual Logical Physical As Built Functioning

14 Zachman Framework Row 6 Functioning Enterprise/User s View Motivation/Why Operating characteristics of specific technologies constrained by standards Function/How Functioning computer instructions Data/What Data values stored in actual databases Functioning Enterprise Operations Management Evaluation What How Where Who When Why People/Who Personnel and key stakeholders working within their roles and responsibilities Contextual Conceptual Contextual Conceptual Network/Where Sending and receiving messages Logical Physical Logical Physical Time/When Timing definitions operating to sequence activities 6 Integrated Functioning What How Where Who When Why Integrated Functioning

15 Agenda Introduction John Zachman s Enterprise Architecture (EA) Framework Walk Through EA Quality Attributes Reference Models Case Study Q & A

16 EA Quality Attributes Multi-layer view Scope: business goal, IT strategy, vision Contextual: collaborative parties, interoperability Standards, ownership of the information, etc Conceptual: deliverables at logical level, Logical Standards Logical: deliverables at physical level, etc. Physical: critical Design Decisions, etc. 2-layer view Business view e.g. business goal, interoperability, processes reusability, etc Information Systems view software architecture attributes, e.g. reusability, interoperability, usability, traceability, etc.

17 Agenda Introduction John Zachman s Enterprise Architecture (EA) Framework Walk Through EA Quality Attributes Reference Models Case Study Q & A

18 EA Reference Models Tool for Enterprise Architecture development Describe generic Enterprise Architecture (usually by industry/sector) independent of organization Provide common reference points for key performance areas Federal Enterprise Architecture (FEA) Reference Models by the federal government of the USA

19 FEA Reference Models

20 Business Reference Model

21 Technical Reference Model

22 Agenda Introduction John Zachman s Enterprise Architecture (EA) Framework Walk Through EA Quality Attributes Reference Models Case Study Q & A

23 Case Study Walt Disney Enterprise Architecture Overview

24 Issues Diverse business myriad of theme parks, media holdings, and film studios with largely decentralized IT infrastructure 1500 applications with many duplications Existing applications incapable of supporting new business models and explosion of digital media High operational costs

25 Solutions Establish CIO Board to map business processes to applications Establish Architecture Council with technology leaders from all major business units Create and implement an architectural master plan

26 Results Identified applications that are core business enablers Eliminated application duplications Created a new services-based layer to insulate Disney s transaction systems and provide for future growth Established blueprint for industry wide collaboration

27 Before Theater Operators Hold or Final Placed via Fax, Phone, or Sales Manager (human proxy) Core Busines System (ShowBiz)

28 Now Why not this? (services-based architecture/layer) Additional Systems / Services Coarse-Grained In/out Fine-Grained In/out Theater Operators Hold or Final Services-based Placed via Fax, Layer Phone, or or Web Browser, or other interface (assume almost any UI) Document-based, agile, flexible

29 Now Theatre Operators to More Distributors AMC Regal Loews Famous Others BVPD Warner Bros Universal Sony Others More work, too hard, lost value

30 Future Aggregated 3 rd Party Site AMC Regal Loews Famous Others theatrical-distribution.com? BVPD Warner Bros Universal Sony

31 Future Focus on self service anywhere Think 3 rd Party Sites! Cross segment Cross business unit External partners Think beyond the Browser! PDA/Telephone and Other Emerging Devices Coarse-Grained Interfaces In/out Focus for new investment Services Based Layer Documents Catalogs/Cache Orchestration Process Workflow Fine-Grained Interfaces In/out Core Business Systems Focus away from UI

32 Q & A Thank You!