Скачать презентацию Enterprise Architecture Planning EAP Office of Information Technology Скачать презентацию Enterprise Architecture Planning EAP Office of Information Technology

47c51b36052793b9a8bc5d0d1cdb31d4.ppt

  • Количество слайдов: 19

Enterprise Architecture Planning (EAP) Office of Information Technology and System Strategy Enterprise Architecture Planning (EAP) Office of Information Technology and System Strategy

Discussion • What is Enterprise Architecture Planning (EAP)? • What is an EA used Discussion • What is Enterprise Architecture Planning (EAP)? • What is an EA used for? • Why should we do it? 23 FEB 2001 2

What is an Enterprise Architecture? A comprehensive blueprint of an organization. The structure of What is an Enterprise Architecture? A comprehensive blueprint of an organization. The structure of (Enterprise) components and their relationships, as well as principles and guidelines governing their evolution over time. A common understanding by all, of the names and definitions of an organization’s entities. 23 FEB 2001 3

What is an Enterprise Architecture? The EA is a strategic asset repository which defines What is an Enterprise Architecture? The EA is a strategic asset repository which defines the current and target architecture environments, including: • the business, • the information, • the technology, and • the transitional processes. Source: Federal Conceptual Architecture model 23 FEB 2001 4

Examples - Entities A distinguishable - person - about which information is kept. place, Examples - Entities A distinguishable - person - about which information is kept. place, thing, event, concept Source: U. S. Coast Guard Information Architecture 23 FEB 2001 5

Architecture Layers PERSONNEL WLB PLATFORMS WPB T 1 Lines OSC HQ WMEC FINCEN MLCP Architecture Layers PERSONNEL WLB PLATFORMS WPB T 1 Lines OSC HQ WMEC FINCEN MLCP ISC Honolulu ISC NOLA PPC ELC TISCOM ISC Ports CAA MLCA ISC Boston D 17 ISC St Louis ISC Cleve. ISC Mia. INFRASTRUCTURE AR&SC FACILITIES AOR 23 FEB 2001 6

Some EAP Components • A standard methodology • A standard set of templates • Some EAP Components • A standard methodology • A standard set of templates • A repository • A configuration management process • Easy access • Ability to export 23 FEB 2001 7

Zachman’s Framework for Information Systems Architecture Data Planner’s View Owner’s View Function Network People Zachman’s Framework for Information Systems Architecture Data Planner’s View Owner’s View Function Network People Time Motivation List of Things Important to Business List of Processes the Business Performs List of Locations Important to Business List of Organizations Important to Business List of Events Significant to Business List of Business Goals/Strategies Entity=Class of Business Thing Function=Class of Business Process Node=Major Business Location Agent=Major Org Unit Time=Major Business Event End/Means=Major Business Goal/CSF e. g. , Function Flow Diagram e. g. , Logistics Network e. g. , Entity Relationship Diagram Ent=Business Entity Rel=Business Rule e. g. , Data Model Designer’s View Function=Business Process e. g. , Data Flow Diagram Node=Business Location Link=Business Linkage e. g. , Distributed System Architecture Entity=Data Entity Relationship= Data Relationship Subcontractor’s View 23 FEB 2001 Node=Info Sys Funct Link=Line Char e. g. , Data Design Builder’s View Funct=Appl Function Arg=User Views e. g. , Structure Chart e. g. , System Architecture e. g. , Organization Chart e. g. , Master Schedule Agent=Org Unit Work=Work Product Time= Business Event Cycle=Business Cycle e. g. , Human Interface Architecture Analyst Engineer Secretary Agent=Role Work=Deliverable e. g. , Human/ Technology Interface Analyst Engineer e. g. , Business Plan End=Business Objectives Means=Business Strategy e. g. , Processing Structure e. g. , Knowledge Architecture Time=System Event Cycle=Processing Cycle End=Criterion Means=Option e. g. , Control Structure Secretary e. g. , Knowledge Design Entity=Segment/Row Relationship=Pointer/ Key Funct=Computer Funct Arg=Screen/Device Formats Node=Hardware/ System Software Link=Line Specification e. g. , Data Definition Description e. g. , Program e. g. , Network Architecture e. g. , Security Architecture e. g. , Timing Definition e. g. , Knowledge Definition Ent=Fields Rel=Addresses Funct=Language Stmts Arg=Control Blocks Node=Addresses Link=Protocols Agent=Identity Work=Transaction Time=Interrupt Cycle=Machine Cycle End=Subcondition Means=Step Agent=User Work=Job Time=Execute Cycle=Component Cycle End=Condition Means=Action 8

What is an EA used for? • Acquisition • Investment decisions • Modeling & What is an EA used for? • Acquisition • Investment decisions • Modeling & Simulation • Analysis • Requirements definition • Plan baseline • Describing and understanding baseline 23 FEB 2001 9

Do. D C 4 ISR Architecture Framework 2. 0 23 FEB 2001 10 Do. D C 4 ISR Architecture Framework 2. 0 23 FEB 2001 10

Do. D C 4 ISR Architecture Framework 2. 0 23 FEB 2001 11 Do. D C 4 ISR Architecture Framework 2. 0 23 FEB 2001 11

What is an EA used for? • Promote interoperable and cost-effective systems • Provide What is an EA used for? • Promote interoperable and cost-effective systems • Provide the rules, guidance and product descriptions for developing and presenting architectural descriptions • Ensure a common denominator for understanding, comparing, and integrating architectures. • Enable architectures to contribute more effectively to engineering interoperable and cost-effective systems. • Provide a mechanism for managing complexity. 23 FEB 2001 12

IT Life Cycle and CM Policy Consolidation USCG Common Operation Environment (USCG COE) Standard IT Life Cycle and CM Policy Consolidation USCG Common Operation Environment (USCG COE) Standard Workstation III Configuration Management Policy COMDTINST 5200. 16 Planning Approval for Automated Information Systems (AIS) Information Systems Technical Architecture COMDTINST 5230. 45 A COMDTINST 5231. 2 COMDTINST 5230. 59 A Information Technology Life Cycle and Configuration Management Policy IT Systems Development Plan (DRAFT) COMDTINST 9999. 99 Information Resource Management (cancelled) COMDTINST 5230. 41 USCG C 4 ISR Baseline Architecture COMDTINST 3090. 6 23 FEB 2001 Standard Terminal Application Software Deployment. COMDTINST 5234. 3 Other Policy TBD 13

Benefits Facilitates information services that provide: flexibility, interoperability, reliability, survivability, affordability, sustainability, portability, reusability, Benefits Facilitates information services that provide: flexibility, interoperability, reliability, survivability, affordability, sustainability, portability, reusability, Adaptability, Compatibility 23 FEB 2001 14

Business Benefits of EAP • • • • Focus on strategic use of technology Business Benefits of EAP • • • • Focus on strategic use of technology for managing data as an asset Standard vocabulary facilitates communication and reduces inconsistency and data redundancy Documentation increases understanding of the business Models can be used to explain the business and assess the impact of business changes Decision making policies can be reviewed Integration of current systems with new systems is considered. It allows for a comprehensive, objective and impartial approach The long range systems plan compliments the business plan A cost-effective long term solution considers rate of return It involves a feasible migration strategy with short term achievements it is easier to assess the benefits of impact of new systems and software it allows easier accommodation of dynamic business changes such as mergers, acquisitions, new products, lines of business. etc. Management participation provides a business prospective, credibility, confidence, and demystifies system development. Source: 23 FEB 2001 Enterprise Architecture Planning Steven Spewak 15

Benefits to the Business of planned systems • • • More responsive to customer’s Benefits to the Business of planned systems • • • More responsive to customer’s needs Reduced data-entry costs Head-count is reduced Increased productivity of personnel permits increased level of business and containment of costs Improved skills raise enthusiasm and loyalty Efficient systems maintenance means improved service. Architectures eliminate complex costly interfaces incongruent systems Management decisions in all functional areas will be based on more accurate and timely data, leading to various improvements and cost-saving measures End user has direct access to shared data New systems are developed faster and at less cost due to common data, common code, and a shortened requirements phase Easier to evaluate and select vendor SW packages Effective use of repository and CASE products Source: 23 FEB 2001 Enterprise Architecture Planning Steven Spewak 16

Zachman reflections on EA Planning Zachman reflections on EA Planning "You may think this is too much work… Or, it takes too long And it costs too much Or is too theoretical Or too high risk Or too whatever. However, if that’s your assessment… You can’t complain that the systems aren’t “aligned” with the enterprise, or are inflexible, or cost too much, or that vital information is not available, or that the data you get isn’t any good, or too late, or you can’t change anything, or that I/S is slow and unresponsive… and, I am here to tell you Outsourcing isn’t going to fix the problem. Packages (in themselves) won’t fix the problem. Decentralization won’t fix the problem. And, the Internet isn’t going to fix the problem. No amount of money, Or technology is going to fix the problem! It is NOT a technical problem, it is an ENTERPRISE problem. Only ACTUAL WORK is going to fix the problem, and “Someday, you are going to wish you had all those models, Enterprise wide, horizontally and vertically integrated, at excruciating level of detail. ” You might as well start working on them TODAY!!! John Zachman 23 FEB 2001 17

Next Steps • CKO Charter an Enterprise Architecture Configuration Control Board (EACCB) • Identify Next Steps • CKO Charter an Enterprise Architecture Configuration Control Board (EACCB) • Identify goals, objective, principles • Establish membership • Identify a methodology • Identify a framework • Identify resources • Define deliverables • Establish a timeline • CKO Charter an Enterprise Data Dictionary Configuration Control Board (EDDCCB) 23 FEB 2001 18

DISCUSSION 23 FEB 2001 19 DISCUSSION 23 FEB 2001 19