Source: emi-webel/roadmap/factsheet.pdf

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

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. BSP: Business Systems Planning

4. Zackman Framework Source: http://www.zifa.com/framework.pdf

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

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

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. 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. 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. Major Components in the ISP Organization Structure Information Strategy ISP Business Strategy Information Technology

11. Business-Driven Planning START give priorities to support Business Objectives Information Systems Business Functions are fulfilled by Information Needs determine

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. 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. 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. 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. 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. Information Strategy Planning Tasks Information Architecture Definition • Activity Model (AHD & ADD) • Data Model (ERD) • Entity Type/Function (CRUD) Matrix Initial Assessment Project Planning ISP Project Completion • Organization Model • Business Objectives • Information Needs Business System Architecture Definition • Cluster CRUD Matrix • Business Area List • Ranked BAA Projects Current Environment Assessment Technical Architecture Definition • Current Systems & Data • Current Information Architecture Coverage • IS Organization Using RAEW Matrix • Current Technical Environment • BAA Distribution Analysis • Technical Requirements • Technical Direction

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

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

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. 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. 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. 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. 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. Purpose of Analyzing Current and Planned Systems and Data Stores • Develop transition plan • Determine development priority • Confirm information 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. 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. Modeling Aspects of IE • Function Hierarchy Diagram • Function Dependency Diagram • Process Hierarchy Diagram • Process Dependency Diagram • Dialog Flow Diagram • Load Module Package • Subject Area Diagram • Entity Relationship Diagram • Data Structure Diagram • DDL: Data Definition Language • Installed Database Data Activity Interaction • 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. Activity Models Software on Us Marketing Market Analysis Advertising Manufacturing Inventory Control Production Planning

30. Data Models customer product is ordered by places Entity Type ORDERS is placed by has contains order item order is part of Subject Area

31. Interaction Models: Matrix Function/Entity Type Matrix Entity Order Employee Inventory Vendor Func. Marketing C R Manufacture R C Finance Human Resource C Purchasing U C Adminis-tration R C: Create; R: Read; U: Update; D: Delete

32. Systems As Planned Organizational Change Figure 12-1 Process/Data Class Matrix

33. Cluster Analysis Activity Model Data Model Interaction Model Entity Type Software on Us customer product FUNCTION Marketing is ordered by places Market Analysis CRUD is placed by Advertising has contains Manufacturing order item order is part of Inventory Control Practical Issues Domain Experiences Cluster Analysis Data Clusters Activity Clusters Business Areas / Business Systems

34. Business Systems Architecture Diagram Strategic Planning Planning & Analysis Management Control Operational Control Operational Processing High Level Business Function Function 5 Function 1 Function 2 Function 3 Function 4 Systems Category Information Flow Business System 1 Business System 2 Business System 3

35. Information Systems Framework Accounts Receivable Database Marketing Customers order zero, Credit one, or more products. Products may be ordered Order Picking Customer Order Management Warehouse by zero, one, or more Advertising Sales Order System customers. Credit Voucher Orders Cancellations Services Bank rejected order St. PRODUCT catalog EDI Products order Louis changes Cust Catalog CUSTOMER credit Check product-no HQ Customers credit customer-no product-name Firecracker Sales customer-name unit-of-measure customer approved order customer-rating number order with ship unit-price West East order valid products Customers Customers balance-due quantity-available order Validate valid order Validate credit credit Orders customer products Indy LA ship NY approved ship order Ware- ORDER order Office Office order without order prices house order-no valid customer service order-date picking products-ordered quantity ticket Release Products Maintenance in stock quantities-ordered order Records Customer Order New Customer Form Processing Program PRODUCT CUSTOMER Logon Order Accepted product_no [Alpha(10)] INDEX Change customer_no [Alpha (10)] INDEX product_name [Alpha(32)] St. Louis Initiation Process Shutdown of customer_name [Alpha(32)] Mainframe Routine an Order Routine unit_of_measure [Alpha(2)] Address New Order customer_rating [Alpha(1)] INDEX unit_price [Real(3,2)] balance_due [Real(5,2)] quantity_available [Integer(4)] Get an Validate File an Order Help Complete Order Form First Order Order an Order Order Request Request Order Help Product Check Check Check Release Lookup ORDER_PRODUCT ORDER Customer Product Credit an ORDER.order_no Credit Data Data Order Help + order_no [Alpha(12)] INDEX Request Product Lookup Help PRODUCT.product_no Indy AIX Server order_date [Date(mmddyyyy) quantity_ordered [Integer(2) CUSTOMER.customer_no Product Product Lookup Help Complete Orders Customers Products Lookup On Event Help.ButtonClick Do Create AccountType = Change Focus HelpDialog SalesClerk customer_name CHAR(32) NOT NULL On Event OKButton Do Set OrderDir.Rights=full customer _rating CHAR(1) NOT NULL Begin Set CustomerDir.Rights=full balance_due DECIMAL(5,2) {proecdure} Set ProductDir.Rights=read End CREATE INDEX cust_no_idx on CUSTOMER Set OrderAppDir.Rights=copy On Event CancelButton Do CREATE INDEX cust_rt_idx on CUSTOMER Data Processes Interfaces Geography (Networks) Business Subjects Business Functions System Context Operating Locations System Owners (Scope) Data Requirements Interface Requirements Communication Reqts. Business Processes System Users (Requirements) System Analysts Database Schema Application Schema Interface Schema Network Schema System Designers (Specification) Communications Controller NT Server LA PBX NT Server NY Ethernet LAN/NT (facilitation) Ethernet LAN/NT Client PC Client PC Client PC Client PC Enternet LAN AIX/Lan Manager Database Structures Application Programs Component Programs Network Programs CREATE TABLE CUSTOMER VALIDATE_AN_ORDER. REPEAT UNTIL NO_MORE_ORDERS (customer_no CHAR(10) NOT NULL System Builders (Components) PERFORM CUSTOMER_VALIDATIO REPEAT UNTIL NO_MORE_ORDER PERFORM PRODUCT_VALIDATI END REPEAT. PERFORM CREDIT_CHECK. IF CREDIT_CHECK 'BAD' THEN Interface Software Technology Networking Database Technology (and Hardware) Technology Technology

36. Zachman Framework Row 1 – Scope External Requirements and Drivers Business Function Modeling What How Where Who When Why 1 Contextual Contextual 2 Conceptual Conceptual 3 Logical Logical 4 Physical Physical 5 As Built As Built 6 Functioning Functioning What How Where Who When Why • 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

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

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 What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why • Function/How High-level business functions • Data/What High-level data classes related to each function 1 • People/Who Stakeholders related to each function • Network/Where VA locations related to each function • Time/When Cycles and events related to each function

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 What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why • Function/How Business processes • Data/What Business data • People/Who VA roles and responsibilities in each process 2 • Network/Where VA locations related to each process • Time/When Events for each process and sequencing of integration and process improvements

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 What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why • 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 3 • 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

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 What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why • 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 4 • Time/When Specification of triggers to respond to system events on specific platforms and technologies

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 What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why • 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 5 • Time/When Timing definitions coded to sequence activities on specific platforms and technologies

43. Zachman Framework – Row 6Functioning Enterprise/User’s View Functioning Enterprise Operations Management Evaluation Motivation/Why Operating characteristics of specific technologies constrained by standards What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical Integrated Integrated Functioning Functioning What How Where Who When Why • 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

44. VA Zachman Framework Portal

45. IBM's Business Systems Planning Methodology Business Objectives Business Objectives Business Organization Business Process Business Process Application Data Bases Business Data Information Architecture Source: IBM, Business Systems Planning, GE20-0527-04, 1984. Top-down planning & analysis Bottom-up design & implementation

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

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

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

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

50. Overall FEA Schema Source: http://www.actgov.org/actiac/documents/ sigs/easig/EAMaturityWP013105.pdf