1. Optimizing Value to the Enterprise with Integrated Enterprise Architecture Brian James Director of Product Management Metastorm

3. What is Enterprise Architecture? “ In a large modern enterprise, a rigorously defined framework is necessary to be able to capture a vision of the ‘ entire system’ in all its dimensions and complexity. Enterprise Architecture (EA) is a framework which is able to coordinate the many facets that make up the fundamental essence of an enterprise. It is the master plan which ‘ acts as an integrating force’ between aspects of business planning such as goals, visions, strategies and governance principles; aspects of business operations such as business terms, organisation structures, processes and data; aspects of automation such as application systems and databases; and the enabling technological infrastructure of the business such as computers, operating systems and networks.” Dennis A. Stevenson, Senior Editor, IS World Research

4. Building Enterprise Architecture

6. Enterprise Architecture Framework Strategic Direction Business Architecture System Architecture Technology Architecture Data / Object Product / Service People Process Service / Application Software Hardware Interface Network Data Architecture Capability Environment Goal Application Architecture

8. Business Interaction Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

9. Strategy Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

10. Goal Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

12. Organization Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

13. Workflow Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

15. Class Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

17. System Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

18. Use Case Model Business Architecture Strategic Direction Data Architecture Application Architecture Technology Architecture

19. Storyboard Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

21. Location Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

22. System Interaction Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

23. Deployment Model Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

24. Using Enterprise Architecture

25. A Pile of Documents does not Make an Enterprise Architecture “ An Enterprise Architecture is a tool to help executives think about the organization as a whole. An Enterprise Architecture captures a wide variety of information, establishes relationships among the various documents and diagrams and stores all of the information together in a single repository, so that managers can then see the relationships, ask questions, identify problems, or run simulations to help make decisions about changes they are considering .” Developing an Enterprise Architecture Paul Harmon, Business Process Trends

26. The Value of Enterprise Architecture is in the Relationships Enterprise Architecture is more than a collection of the constituent architectures (Business, Application, Technology, and Information). The interrelationships among these architectures , and their joint properties , are essential to the Enterprise Architecture. Enterprise-Wide IT Architecture (EWITA)

27. Association Matrices Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

28. Navigator Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture Strategic Direction Business Architecture Data Architecture Application Architecture Technology Architecture

29. Enterprise Architecture Provides Many Possibilities Strategy Model Goal Model Business Interaction Model Location Model Corporate Strategy Application Architecture State Chart Use Case Model Operation Model Storyboard Model System Model Communication Model Software Development Tools Organization Model Data Architecture Deliverable Model Logical Data Model Physical Data Model Data Modeling Tools XMI Interface Technology Architecture Technical Architecture Model Deployment Model Infrastructure Management Tools XML Interface Strategic Direction Business Architecture Systems Architecture Technology Architecture Technical Tools EA Associations Process Validation by Simulation Process Architecture Business Process Management Tools Process Hierarchy Workflow Model Business Rules XMI Interface The model relationships to be analyzed depend upon your specific objectives. BPEL Interface

30. Enterprise Architecture Benefits Process Effectiveness Operational Efficiency Opportunity Creation Automation Efficiency Current Future Revenue Generation Cost Reduction

31. Different Objectives will Emphasize Different Architectures Process Effectiveness Operational Efficiency Opportunity Creation Development Efficiency Current Future Revenue Generation Cost Reduction Strategic Direction Business Architecture System Architecture Technology Architecture System Architecture Business Architecture Technology Architecture Strategic Direction

32. Getting Started

33. Steps to Enterprise Architecture Step 1: Define “Enterprise” Scope “ Enterprise” Scope, Direction Current

34. Step 2: Define Strategic Direction Strategic Direction Future “ Enterprise” Scope, Direction Current

35. Step 3: Define Current Architecture Business Architecture System Architecture Technology Architecture Process Effectiveness Operational Efficiency Strategic Direction Future “ Enterprise” Scope, Direction Current

36. Step 4: Define Future Architecture Future System Architecture Business Architecture Technology Architecture Strategic Direction Business Architecture System Architecture Technology Architecture Opportunity Creation Automation Efficiency Justification “ Enterprise” Scope, Direction Current

37. Step 5: Gap Analysis Gap Analysis Future ? ? ? System Architecture Business Architecture Technology Architecture Strategic Direction Business Architecture System Architecture Technology Architecture Process Improvements System Enhancements Infrastructure Changes “ Enterprise” Scope, Direction Current

38. Step 6: Strategy Evaluation Gap Analysis Future Process Improvements System Enhancements Infrastructure Changes System Architecture Business Architecture Technology Architecture Strategic Direction Business Architecture System Architecture Technology Architecture + + Cost, Timing & Resources needed to achieve Strategic Direction = “ Enterprise” Scope, Direction Current

39. Key Planning Decisions What are my current EA objectives and how will my architecture be utilized in the future?

40. Different Objectives Emphasize Different Architectures Process Effectiveness Operational Efficiency Opportunity Creation Development Efficiency Current Future Strategic Direction Business Architecture System Architecture Technology Architecture System Architecture Business Architecture Technology Architecture Strategic Direction Revenue Generation Cost Reduction

41. Key Planning Decisions What are my current EA objectives and how will my architecture be utilized in the future? How much organizational commitment is required for success?