1. © Minder Chen, 1997-2008 Enterprise Architecture - 1 Source: http://emi-web.inel.gov/roadmap/factsheet.pdfhttp://emi-web.inel.gov/roadmap/factsheet.pdf Use EA as a roadmap to supports good IT planning, investment decisions Mount surprise Contingency Drive Regulatory Mountain Data rich and information poor Uncertainty Gap Successful Program and project management Current Resources / Systems Migration path Business Applications Service building blocks Technical architecture

2. © Minder Chen, 1997-2008 Enterprise Architecture - 2 Evolution of EA BSP: Business Systems Planning ISF: Zachman Information Systems Framework ISP: Information Systems Planning EAP: Enterprise Architecture Planning EA: Enterprise Architecture

3. © Minder Chen, 1997-2008 Enterprise Architecture - 3 BSP: Business Systems Planning

4. © Minder Chen, 1997-2008 Enterprise Architecture - 4 Zackman Framework Source: http://www.zifa.com/framework.pdf

5. © Minder Chen, 1997-2008 Enterprise Architecture - 5 Information Strategy Planning Tasks Initial Assessment Project Planning Information Architecture Definition Business System Architecture Definition Current Environment Assessment Technical Architecture Definition ISP Project Completion  Organization Model  Business Objectives  Information Needs  Activity Model (AHD & ADD)  Data Model (ERD)  Entity Type/Function (CRUD) Matrix  Current Systems & Data  Current Information Architecture Coverage  IS Organization Using RAEW Matrix  Current Technical Environment  Cluster CRUD Matrix  Business Area List  Ranked BAA Projects  BAA Distribution Analysis  Technical Requirements  Technical Direction

6. © Minder Chen, 1997-2008 Enterprise Architecture - 6 Levels of Enterprise Architecture Planning Planning Initiation Existing Business Model Current Systems & Technology Data Architecture Applications Architecture Technology Architecture Implementation and Migration Plans Getting started Where we are today The vision of where we want to be How we plan to get there Source: Steven H. Spewak, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, John Wiley & Sons, Inc., 1992, p. 16.

7. © Minder Chen, 1997-2008 Enterprise Architecture - 7 References 1. Texas Instruments, A Guide to IE Using IEF, 2nd edition, Part No. 2739756-0001, 1990. 2. Martin, James, Information Engineering Book I: Introduction, Prentice-Hall Inc., 1989. 3. James Martin with Joe Leben, Strategic Information Planning Methodologies, 2nd edition, Prentice-Hall, Inc., 1989. 4. Spewak, Steven H. with Steven C. Hill, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, New York: John Wiley & Sons, Inc., 1992. 5. IBM, Business Systems Planning: Information Systems Planning Guide, Fourth edition, Order Number: GE20- 0527-04, July 1984. 6. IBM Systems Journal: A Special Issue on Enterprise Analysis, Vol. 21, No. 1, 1982, Order Number: G321-0068.

8. © Minder Chen, 1997-2008 Enterprise Architecture - 8 Introduction to ISP Develop a high-level view of the enterprise-wide information requirements and furnish a plan to fulfill these requirements. Central task: Define an architectural framework for future applications

9. © Minder Chen, 1997-2008 Enterprise Architecture - 9 ISP Purposes Gain top level commitment to information systems Develop IS strategy based on business strategy Manage data as corporate resource Coordinate IS plans: –Business strategies and goals –Systems plans –Technical plans »Hardware »Software »Networking –IS organization and resource plans

10. © Minder Chen, 1997-2008 Enterprise Architecture - 10 Major Components in the ISP ISP Organization Structure Information Technology Business Strategy Information Strategy

11. © Minder Chen, 1997-2008 Enterprise Architecture - 11 Business-Driven Planning Business Objectives Business Functions Information Needs Information Systems give priorities to determine are fulfilled by support START

12. © Minder Chen, 1997-2008 Enterprise Architecture - 12 Linking ISP with Business Strategies Understand the environments culture of existing business Identify information requirements in the long run Develop a baseline to determine systems development priority Link IS with organizational strategies and objectives

13. © Minder Chen, 1997-2008 Enterprise Architecture - 13 Categories of Information Used in ISP Business Objects –Mission –Objective –Strategy –Goal –Critical Successful Factor –Plan –Performance Measure Organizational Objects –Organizational Unit –Organizational Structure Activity Object –Business Function –Business Process Data Object –Subject Area –Entity Type –Information Need

14. © Minder Chen, 1997-2008 Enterprise Architecture - 14 Key Elements in ISP Information Architecture –Specifications of activities performed by the enterprise and the information required to perform these activities –Basis for the Business Area Analysis stage Business System Architecture –Descriptions of Business Systems and Data Stores required to support the Information Architecture –Basis for the Business System Design stage Technical Architecture –Requirements of hardware and software environments needed to support the Business System Architecture –Basis for the Technical Design stage Information Management Organization –The organization of IS organization to implement proposed ISP

15. © Minder Chen, 1997-2008 Enterprise Architecture - 15 Deliverables: ISP Facts about the enterprise –A Mission Statement; an Information Needs map; a list of Objectives, CSF, and Strategies by Organization Unit, a ranked list of objectives. Facts about the current environment –IS organization; software/hardware/application systems Information Architecture –Subject Area Diagram and high level ERD; a overall Function Hierarchy Diagram; a set of Function Dependency Diagram, supporting matrices. Business System Architecture –A prioritized list of BAA projects in an Implementation Plan Technical Architecture –A statement of technical direction ISP Report

16. © Minder Chen, 1997-2008 Enterprise Architecture - 16 Information Strategy Planning 1.Planning the ISP Project 2. Making the initial assessment 3.Defining the Information Architecture 4. Assessing the current environment 5.Defining the Business System Architecture 6.Defining the Technical Architecture 7. Planning for the BAA and Completing ISP

17. © Minder Chen, 1997-2008 Enterprise Architecture - 17 Information Strategy Planning Tasks Initial Assessment Project Planning Information Architecture Definition Business System Architecture Definition Current Environment Assessment Technical Architecture Definition ISP Project Completion  Organization Model  Business Objectives  Information Needs  Activity Model (AHD & ADD)  Data Model (ERD)  Entity Type/Function (CRUD) Matrix  Current Systems & Data  Current Information Architecture Coverage  IS Organization Using RAEW Matrix  Current Technical Environment  Cluster CRUD Matrix  Business Area List  Ranked BAA Projects  BAA Distribution Analysis  Technical Requirements  Technical Direction

18. © Minder Chen, 1997-2008 Enterprise Architecture - 18 Levels of Enterprise Architecture Planning Planning Initiation Existing Business Model Current Systems & Technology Data Architecture Applications Architecture Technology Architecture Implementation and Migration Plans Getting started Where we are today The vision of where we want to be How we plan to get there Source: Steven H. Spewak, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, John Wiley & Sons, Inc., 1992, p. 16.

19. © Minder Chen, 1997-2008 Enterprise Architecture - 19 Relationship of The Three Architecture Data Model Activity Model Interaction Model Information Architecture Business Areas Natural Business Systems Business Systems Architecture Current Systems Analysis Existing & Proposed IS Hardware Platforms Software Development Environments Technical Architecture Data Management Security Networks Adapted from: Elaine Sill, "Information Engineering and Its Architectures," CASE Trends, Vol. 4, No. 3, May 1992, pp. 15-17

20. © Minder Chen, 1997-2008 Enterprise Architecture - 20 Planning the ISP Project Setting the scope of the project –Managing expectation –Establishing organizational and time boundaries –Determining information technologies boundaries –Formulating the statement of objectives Forming the project task force –The project sponsor –The project team: Project manager, ISP expert, Business expert, Technical Expert. –Reference team, administrative and clerical support Developing the project schedule –Establishing a detailed task list and project checkpoints –Estimating task duration: »80 person-days for interviewing (40 interviews; 1 day & two persons per interview) »30-80 man-days for specifying an information architecture Interviewing and constructing Information architecture take 1/2 of the project time

21. © Minder Chen, 1997-2008 Enterprise Architecture - 21 Making the Initial Assessment Specify Organization Structure –Organizational Units: Name & Person-in-charge Identify and rank Objectives and CSFs –Identify the following Entities by Organizational Unit: Mission, Objective, Strategy, Critical Success Factor (CSF), Goal, Plan –Develop Enterprise/Organizational Unit Objective Matrix –Prioritize List of Objectives for the enterprise and each major Organizational Unit Determine Information Needs and Performance Measures –Construct Information Needs List: Description, Usage, Objectives supported, Supporting systems, Important factor, Satisfaction factor, Requirements weight –Develop Information Needs/Organization Matrix and Performance Measure/Organization Matrix

22. © Minder Chen, 1997-2008 Enterprise Architecture - 22 Examples of Mission, Objectives, CSF Missions –To provide high quality PC products to satisfy ever-changing customer needs and achieve maximum return for stakeholders. Objectives –Maintain peripheral business at 25% of total sales –15% market share in the Unite States –Sales growth of at least 10% per year –ROI of 15% per year Critical Success Factors –Effective OEM relationships with major PC suppliers in Asia –Effective research and development of emerging technologies –Understand customer needs and industry trends –Accurate prediction of customer demands –Management of major marketing channels

23. © Minder Chen, 1997-2008 Enterprise Architecture - 23 Making the Initial Assessment (Continued) Assess potential impacts of information technology –Include Hardware Items and Software Products –Assess the role of IT: »Become (part of) a product or service »Deliver a product or service »Gain competitive advantage Define a preliminary Information Architecture –Identify the following Entities by Organizational Unit: Mission, Objective, Strategy, Critical Success Factor (CSF), Goal, Plan –Develop Enterprise/Organizational Unit Objective Matrix –Prioritize List of Objectives for the enterprise and each major Organizational Unit

24. © Minder Chen, 1997-2008 Enterprise Architecture - 24 Tasks of Assessing the Current Environment List all the current and planned systems and data stores. Determine the coverage of current information architecture (consisting of current systems and data stores) against entity types and functions. Define a list of information needs. Assess IS organization using RAEW Matrix. –R: Responsibility; A: Authority –E: Expertise; W: Work Analyze current technical environment.

25. © Minder Chen, 1997-2008 Enterprise Architecture - 25 Purpose of Analyzing Current and Planned Systems and Data Stores Develop transition plan Determine development priority Confirm information architecture

26. © Minder Chen, 1997-2008 Enterprise Architecture - 26 On Modeling Modeling the system that the user wants is the primary job of a systems analyst. Models of the system-to-be is abstract representations of what will eventually become a combination of computer hardware and software. Examples of models in our daily life: –Maps –Globes –Flowcharts –Architect’s drawing

27. © Minder Chen, 1997-2008 Enterprise Architecture - 27 On Modeling Models are abstract representations of real world systems. A model is used to emphasize important system features while other aspects of the system are de-emphasized. One should avoid analysis paralysis. Sometimes we need to use several modeling techniques to describe various aspects of a system in order to present a complete picture of the system. Models are used as media to facilitate the communication between systems developers and users. A model should be used as a strawman. Changes and corrections can be made to the model with low cost and minimal risk.

28. © Minder Chen, 1997-2008 Enterprise Architecture - 28 Modeling Aspects of IE Data Activity Interaction Subject Area Diagram Entity Relationship Diagram Data Structure Diagram DDL: Data Definition Language Installed Database Function Hierarchy Diagram Function Dependency Diagram Process Hierarchy Diagram Process Dependency Diagram Dialog Flow Diagram Load Module Package Expected Effects of a Process on Entity Types Function/Entity Type Matrix Elementary Process/Entity Type Matrix Process Action Diagram & Process Action Block Procedure Action Diagram Screen/Window Layout

29. © Minder Chen, 1997-2008 Enterprise Architecture - 29 Activity Models Software on Us Marketing Manufacturing Market Analysis Advertising Inventory Control Production Planning

30. © Minder Chen, 1997-2008 Enterprise Architecture - 30 Data Models order is part of contains customer places is placed by is ordered by has ORDERS Subject Area Entity Type product order item

31. © Minder Chen, 1997-2008 Enterprise Architecture - 31 Interaction Models: Matrix OrderEmployeeInventoryVendor Marketing C R Manufacture R C Finance Human Resource C Purchasing U C Adminis- tration R Func. Entity C: Create; R: Read; U: Update; D: Delete Function/Entity Type Matrix

32. © Minder Chen, 1997-2008 Enterprise Architecture - 32 Systems As Planned Organizational Change Process/Data Class Matrix Figure 12-1

33. © Minder Chen, 1997-2008 Enterprise Architecture - 33 Cluster Analysis order item is part of contains customer product places is placed by is ordered by has order Data Model Marketing Manufacturing Market Analysis Advertising Inventory Control Software on Us Activity Model Interaction Model FUNCTIONFUNCTION Entity Type CRUD Domain Experiences Practical Issues Activity Clusters Data Clusters Business Areas / Business Systems Cluster Analysis

34. © Minder Chen, 1997-2008 Enterprise Architecture - 34 Business Systems Architecture Diagram Strategic Planning & Analysis Management Control Operational Control Operational Processing Function 1Function 2Function 3Function 4 High Level Business Function Systems Category Business System 1 Business System 2 Business System 3 Information Flow Function 5

35. © Minder Chen, 1997-2008 Enterprise Architecture - 35 (facilitation) Database Technology Database Structures Database Schema Data Requirements Business Subjects Data Application Programs Application Schema Business Processes Business Functions Processes Component Programs Interface Schema Interface Requirements System Context Interfaces Software (and Hardware) Technology Interface TechnologyNetworking Technology Network Programs Network Schema Communication Reqts. Operating Locations Geography (Networks) CREATE TABLE CUSTOMER (customer_no CHAR(10) NOT NULL NT Server LA NT Server NY Communications Controller PBX Enternet LAN AIX/Lan Manager Ethernet LAN/NT Client PC VALIDATE_AN_ORDER. REPEAT UNTIL NO_MORE_ORDERS PERFORM CUSTOMER_VALIDATIO REPEAT UNTIL NO_MORE_ORDER PERFORM PRODUCT_VALIDATI END REPEAT. PERFORM CREDIT_CHECK. IF CREDIT_CHECK 'BAD' THEN Information Systems Framework System Analysts System Owners (Scope) System Users (Requirements) System Designers (Specification) System Builders (Components)

36. © Minder Chen, 1997-2008 Enterprise Architecture - 36 Zachman Framework Row 1 – Scope External Requirements and Drivers Business Function Modeling Row 2 – Enterprise Model Business Process Models Row 3 – System Model Logical Models Requirements Definition Row 4 – Technology Model Physical Models Solution Definition and Development Row 5 – As Built As Built Deployment Row 6 – Functioning Enterprise Functioning Enterprise Evaluation 123456 Contextual Conceptual Logical Physical As Built Functioning Contextual Conceptual Logical Physical As Built Functioning Why Who When Where What How

37. © Minder Chen, 1997-2008 Enterprise Architecture - 37 Framework Rules Rule 1: Columns have no order Contextual Conceptual Logical Physical As Built Functioning Contextual Conceptual Logical Physical As Built Functioning Why Who When Where What How Rule 2: Each column has a simple, basic model Rule 3: Basic model of each column is unique Rule 4: Each row represents a distinct view Rule 5: Each cell is unique Rule 6: Combining the cells in one row forms a complete description from that view Basic Model = Entities and Relationships Entity Relationship Entity

38. © Minder Chen, 1997-2008 Enterprise Architecture - 38 Zachman Framework – Row 1 Scope/Planner’s View External Requirements and Drivers Business Function Modeling 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 Network/Where VA locations related to each function Time/When Cycles and events related to each function 1 Contextual Conceptual Logical Physical As Built Functioning Contextual Conceptual Logical Physical As Built Functioning Why Who When Where What How

39. © Minder Chen, 1997-2008 Enterprise Architecture - 39 Zachman Framework – Row 2 - Enterprise Model/Designer’s View Business Process Models Business Function Allocation Elimination of Function Overlap and Ambiguity Motivation/Why Policies, procedures and standards for each process Function/How Business processes Data/What Business data People/Who VA roles and responsibilities in each process Network/Where VA locations related to each process Time/When Events for each process and sequencing of integration and process improvements 2 Contextual Conceptual Logical Physical As Built Functioning Contextual Conceptual Logical Physical As Built Functioning Why Who When Where What How

40. © Minder Chen, 1997-2008 Enterprise Architecture - 40 Zachman Framework – Row 3 System Model/Designer’s View Logical Models Project Management Requirements Definition Motivation/Why VA 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 VA information People/Who Logical representation of access privileges constrained by roles and responsibilities Network/Where Logical representation of the distributed system architecture for VA locations Time/When Logical 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 Who When Where What How

41. © Minder Chen, 1997-2008 Enterprise Architecture - 41 Zachman Framework – Row 4 Technology Model/Builder’s View Physical Models Technology Management Solution Definition and Development Motivation/Why VA 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 4 Contextual Conceptual Logical Physical As Built Functioning Contextual Conceptual Logical Physical As Built Functioning Why Who When Where What How

42. © Minder Chen, 1997-2008 Enterprise Architecture - 42 Zachman Framework – Row 5 As Built/Integrator’s View As Built Configuration Management Deployment Motivation/Why VA 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 5 Contextual Conceptual Logical Physical As Built Functioning Contextual Conceptual Logical Physical As Built Functioning Why Who When Where What How

43. © Minder Chen, 1997-2008 Enterprise Architecture - 43 Zachman Framework – Row 6 Functioning Enterprise/User’s View Functioning Enterprise Operations Management Evaluation Motivation/Why Operating characteristics of specific technologies constrained by standards Function/How Functioning computer instructions Data/What Data values stored in actual databases People/Who VA personnel and key stakeholders working within their roles and responsibilities Network/Where Sending and receiving messages Time/When Timing definitions operating to sequence activities 6 Contextual Conceptual Logical Physical Integrated Functioning Contextual Conceptual Logical Physical Integrated Functioning Why Who When Where What How

44. © Minder Chen, 1997-2008 Enterprise Architecture - 44 VA Zachman Framework Portal

45. © Minder Chen, 1997-2008 Enterprise Architecture - 45 IBM's Business Systems Planning Methodology Business Objectives Business Objectives Business Organization Business Process Business Process Application Business Data Bases Information Architecture Top-down planning & analysisBottom-up design & implementation Source: IBM, Business Systems Planning, GE20-0527-04, 1984.

46. © Minder Chen, 1997-2008 Enterprise Architecture - 46 Operation Database Transaction Processing System Management Information Systems Data Data & messages Read-only data Data snapshots Data Problem Manager Information need Management information Relevant User Transaction Data Transaction information DSS Database Decision Support System Executive Information System Read-only data Decision support information Executive information Decision maker or executive Expert System Comminations between users and within groups Office Information System Problem Solution Knowledge Database Personal Files & Database Personal Information System Personal data Personal information User Captured data Shared data Knowledge Information Systems Types and Their Relationships

47. © Minder Chen, 1997-2008 Enterprise Architecture - 47 Technical Architecture Information Technology Areas CIM CAD/CAM Transaction Processing Office Automation Messaging/ Networking Scope Inter- organization Enterprise Wide Departmental Computing Workgroup Computing Personal Computing Information technology area Scope Technical facilities Networks among facilities Location

48. © Minder Chen, 1997-2008 Enterprise Architecture - 48 The Real and Conceptual Worlds Information Architecture Business Areas/ Natural Business Systems Conceptual World Organization Models Current Technical Environ. Real World Technical Architecture Proposed IS Current Systems Technical Directions Adapted from: Elaine Sill, "Information Engineering and Its Architectures," CASE Trends, Vol. 4, No. 3, May 1992, pp. 15-17

49. © Minder Chen, 1997-2008 Enterprise Architecture - 49 Transformation through Enterprise Architecture George Paras, "Embrace Enterprise Transformation as a Core Concept," Architecture & Governance, Summer 2005, pp. 15-17.

50. © Minder Chen, 1997-2008 Enterprise Architecture - 50 Overall FEA Schema Source: http://www.actgov.org/actiac/documents/ sigs/easig/EAMaturityWP013105.pdf

51. © Minder Chen, 1997-2008 Enterprise Architecture - 51 Federal Enterprise Architecture The FEA was established by OMB, with support from GSA and the Federal CIO Council

52. © Minder Chen, 1997-2008 Enterprise Architecture - 52 The Business Reference Model

53. © Minder Chen, 1997-2008 Enterprise Architecture - 53

54. © Minder Chen, 1997-2008 Enterprise Architecture - 54 Structure of the FEAF Components

55. © Minder Chen, 1997-2008 Enterprise Architecture - 55 PRM Articulates Line of Sight

56. © Minder Chen, 1997-2008 Enterprise Architecture - 56 Performance Reference Model

57. © Minder Chen, 1997-2008 Enterprise Architecture - 57 Service Component Reference Model

58. © Minder Chen, 1997-2008 Enterprise Architecture - 58 Conceptual/Process Model

59. © Minder Chen, 1997-2008 Enterprise Architecture - 59 Technical Reference Model

60. © Minder Chen, 1997-2008 Enterprise Architecture - 60 U.S. Customs Technical Reference Model

61. © Minder Chen, 1997-2008 Enterprise Architecture - 61 Technical Reference Model

62. © Minder Chen, 1997-2008 Enterprise Architecture - 62

63. © Minder Chen, 1997-2008 Enterprise Architecture - 63

64. © Minder Chen, 1997-2008 Enterprise Architecture - 64

65. © Minder Chen, 1997-2008 Enterprise Architecture - 65 IT Infrastructure as a Centrally Coordinated Set of Shared and Reliable Services

66. © Minder Chen, 1997-2008 Enterprise Architecture - 66 IT Infrastructure can be deployed at multiple levels

67. © Minder Chen, 1997-2008 Enterprise Architecture - 67 IT Infrastructure Services in 10 Clusters Local I T Applications Standardized Interfaces Agreed-upon Standards

68. © Minder Chen, 1997-2008 Enterprise Architecture - 68

69. © Minder Chen, 1997-2008 Enterprise Architecture - 69

70. © Minder Chen, 1997-2008 Enterprise Architecture - 70

71. © Minder Chen, 1997-2008 Enterprise Architecture - 71

72. © Minder Chen, 1997-2008 Enterprise Architecture - 72

73. © Minder Chen, 1997-2008 Enterprise Architecture - 73