Extended Enterprise Architecture Framework E 2 AF Agenda

Extended Enterprise Architecture Framework (E 2 AF)

Agenda þ Introduction þ E 2 AF Development Process þ E 2 AF Full Blown þ View & View. Point þ Enterprise Architecture Approach þ Win Spiral Model þ Evaluation þ Tool Selection þ EA Maturity Model 2 E 2 AF

Introduction þ An enterprise architecture (EA) establishes the organization-wide roadmap to achieve an organization’s mission through optimal performance of its core business processes within an efficient information technology (IT) environment. þ besides the choices for an EA framework at the same time choices for supporting methods and techniques has to be made. 3 E 2 AF

Elements of Frameworks þ 3 major elements of every Framework: Ø Construction Ø Function Ø Style þ enterprise architecture is dealing with construction and function, without any attention of the style aspect 4 E 2 AF

Why E 2 AF þ Every complex thing that has to operate as a whole has to be designed as a whole. This to guarantee integration and coherency of all its components and to ensure the whole will operate the way required when it is created. þ Organization will be fully benefits from the alignment of business and IT by integrating all enterprise architecture aspect areas into one overall result 5 E 2 AF

What does it do for us? þ Enterprise Architecture results as well as E 2 AF itself can be used as an Atlas for management to navigate to all relevant topics. þ From E 2 AF, roadmaps can be defined to identify the necessary tasks and activities. þ E 2 AF can show the complexity of elements to be addressed. þ E 2 AF can show the people to be involved in the process. þ E 2 AF shows the relations and dependencies. þ E 2 AF is your Guide in all Architectural Activities. 6 E 2 AF

E 2 AF Development Process (1) þ Enterprise Architecture environment rules & principles Ø Business Benefits are leading Ø Business based choices Ø Business centric thinking instead of technology centric thinking Ø Business Principles are mandatory Ø Business Scenario thinking Ø Technology enabling by business benefits (Or Technology rationalised by business benefits) 7 E 2 AF

E 2 AF Development Process (2) þ Translating the rules & principles into a coherent framework þ Separation of levels of abstraction Ø Separate the Strategy from Requirements Ø Separate Requirements from solutions Ø Separate solutions from implementations Ø Separate implementations from transformations þ Enterprise Architectures exist at different abstraction levels 8 E 2 AF

E 2 AF Development Process (3) þ Combining aspect areas with abstraction levels þ Adding Viewpoints to the framework þ Integrating all these elements into a Framework 9 E 2 AF

E 2 AF Full Blown 10 E 2 AF

Separation of concerns þ Contextual (Why? ) þ Environmental (With Who? ) þ Conceptual (What? ) þ Logical (How? ) þ Physical (With what? ) þ Transformational (When? ) 11 E 2 AF

Decomposition of the Enterprise þ Business þ Information Systems þ Technology Infrastructure 12 E 2 AF

View & View. Point þ View. Point: defines the perspectives from which views are taken. From an extended enterprise perspective these viewpoints are addressing generic and common concerns covering the whole enterprise. þ Views: are representations of the overall enterprise architecture that are meaningful to all stakeholders in and outside the organization. þ Enterprise Architectural Viewpoints Ø Security Ø Governance The impact of viewpoints should be incorporated in the extended enterprise architecture results at all levels. 13 E 2 AF

Relations 14 E 2 AF

Enterprise Architecture Approach 15 E 2 AF

The E 2 AF Win Spiral Model 16 E 2 AF

Effective Factors on EA 17 E 2 AF

when is an Enterprise Architecture Good Enough ? þ “An Enterprise Architect knows he has achieved the perfect solution not when there is nothing left to add, but when there is, nothing left to take away. ” [Saint-Exupery] þ Enterprise Architecture Score Card developed by Jaap Schekkerman 18 E 2 AF

Enterprise Architecture Score Card 19 E 2 AF

Validation Approach 20 E 2 AF

Tool Selection (1) þ tools basic functionality: Ø Methodologies and Models; Ø Model Development Interface; Ø Tool Automation; Ø Extendibility and Customization; Ø Analysis and Manipulation; Ø Repository; Ø Deployment Architecture; Ø Costs and Vendor Support. 21 E 2 AF

Tool Selection (2) þ tool’s utility to different professionals: Ø Enterprise Architects; Ø Strategic Planners; Ø Enterprise Program Managers. 22 E 2 AF

Tool Selection (3) þ The purpose of adopting an EA Tool: Ø Supporting decision making of management requires another level of detail in models and diagrams then supporting application development. þ Tool List & Candidate Tool Requirements Checklist [4. Enterprise Architecture Tool Selection Guide] þ Gartner's Magic Quadrant for business process analysis 2006 23 E 2 AF

Some Tools 24 E 2 AF

EA Maturity Model þ IFEAD Extended Enterprise Architecture Maturity Model (E 2 AMM) Ø path for enterprise architecture Ø procedural improvements within an organization 25 E 2 AF

Resources (1) 1. J. Schekkerman, “Extended Enterprise Architecture View. Points Support Guide”, http: //www. enterprise- architecture. info/Images/E 2 AF/Extended%20 Enterprise%20 Architecture%20 View. Points%20 Sup port%20 Guide%20 v 18. pdf, AT: 2006/5/26; PT: 2006 2. J. Schekkerman, “Extended Enterprise Architecture Framework Essentials Guide”, http: //www. enterprise- architecture. info/Images/E 2 AF/Extended%20 Enterprise%20 Architecture%20 Framework%20 Ess entials%20 Guide%20 v 1. 5. pdf, AT: 2006/5/26; PT: 2006 3. J. Schekkerman, ”The (Enterprise) Architecture Process Cycle”, 4. J. Schekkerman, “Enterprise Architecture Tool Selection Guide”, http: //www. enterprisearchitecture. info/Images/WEB%20 Architecture%20 Process%20 Cycle/WEB%20 Architecture%2 0 Process%20 Cycle%202001 -02 -01. htm, AT: 2006/5/23; PT: 2001 http: //www. enterprisearchitecture. info/Images/EA%20 Tools/Enterprise%20 Architecture%20 Tool%20 Selection%20 Gu ide%20 v 3. pdf, AT: 2006/5/26; PT: 2006 26 E 2 AF

Resources (2) 5. J. Schekkerman, ”Enterprise Architecture Assessment Guide”, 6. J. Schekkerman http: //www. enterprisearchitecture. info/Images/Architecture%20 Score%20 Card/Enterprise%20 Architecture%20 Assess ment%20 Guide%20 v 2. 2. pdf, AT: 2006/5/26; PT: 2006 , ”Extended Enterprise Architecture Maturity Model Support Guide”, http: //www. enterprisearchitecture. info/Images/E 2 AF/Extended%20 Enterprise%20 Architecture%20 Maturity%20 Model %20 Guide%20 v 2. pdf 7. , AT: 2006/5/26; PT: 2006 J. Schekkerman, “Extended Enterprise Architecture Maturity Model Support Guide”, http: //www. enterprise- architecture. info/Images/E 2 AF/Extended%20 Enterprise%20 Architecture%20 Maturity%20 Model %20 Guide%20 v 2. pdf , AT: 2006/5/26; PT: 2006 8. J. Schekkerman, “Enterprise Architecture Validation” http: //www. serc. nl/lac/2003/papers/Enterprise. Architecture. Validation. Fullversion. pdf , AT: 2006/6/7; PT: 2003/9/8 27 E 2 AF