Transcription

Extended Enterprise ArchitectureFramework (E2AF)

Agenda Introduction E2AF Development Process E2AF Full Blown View & ViewPoint Enterprise Architecture Approach Win Win Spiral Model Evaluation Tool Selection EA Maturity Model2E2AF

Introduction An enterprise architecture (EA) establishesthe organization-wide roadmap to achieve anorganization’s mission through optimalperformance of its core business processeswithin an efficient information technology(IT) environment. besides the choices for an EA framework atthe same time choices for supporting methodsand techniques has to be made.3E2AF

Elements of Frameworks 3 major elements of every Framework: Construction Function Style enterprise architecture is dealing withconstruction and function, without anyattention of the style aspect4E2AF

Why E2AF Every complex thing that has to operate as awhole has to be designed as a whole. This toguarantee integration and coherency of all itscomponents and to ensure the whole will operate theway required when it is created. Organization will be fully benefits from thealignment of business and IT by integrating allenterprise architecture aspect areas into one overallresult5E2AF

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

E2AF Development Process (1) Enterprise Architecture environment rules &principles Business Benefits are leading Business based choices Business centric thinking instead of technologycentric thinking Business Principles are mandatory Business Scenario thinking Technology enabling by business benefits (OrTechnology rationalised by business benefits)7E2AF

E2AF Development Process (2) Translating the rules & principles into acoherent 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 differentabstraction levels8E2AF

E2AF Development Process (3) Combining aspect areas with abstractionlevels Adding Viewpoints to the framework Integrating all these elements into aFramework9E2AF

E2AF Full Blown10E2AF

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

Decomposition of the Enterprise Business Information Information Systems Technology Infrastructure12E2AF

View & ViewPoint ViewPoint: defines the perspectives from which views aretaken. From an extended enterprise perspective these viewpointsare addressing generic and common concerns covering thewhole enterprise. Views: are representations of the overall enterprisearchitecture that are meaningful to all stakeholders in andoutside the organization. Enterprise Architectural Viewpoints Security GovernanceThe impact of viewpoints should be incorporated in theextended enterprise architecture results at all levels.13E2AF

Relations14E2AF

Enterprise Architecture Approach15E2AF

The E2AF WinWin Spiral Model16E2AF

Effective Factors on EA17E2AF

when is an EnterpriseArchitecture Good Enough ? “An Enterprise Architect knows he has achievedthe perfect solution not when there is nothing left toadd, but when there is, nothing left to take away.”[Saint-Exupery] Enterprise Architecture Score Card developedby Jaap Schekkerman18E2AF

Enterprise Architecture Score Card19E2AF

Validation Approach20E2AF

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.21E2AF

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

Tool Selection (3) The purpose of adopting an EA Tool: Supporting decision making of managementrequires another level of detail in models anddiagrams then supporting applicationdevelopment. Tool List & Candidate Tool RequirementsChecklist [4. Enterprise Architecture Tool Selection Guide] Gartner's Magic Quadrant for business process analysis 200623E2AF

Some Tools24E2AF

EA Maturity Model IFEAD Extended Enterprise ArchitectureMaturity Model (E2AMM) path for enterprise architecture procedural improvements within anorganization25E2AF

Resources (1)1.J. Schekkerman, “Extended Enterprise Architecture ViewPointsSupport Guide”, %20Support%20Guide%20v18.pdf, AT:2006/5/26; PT: 20062.J. Schekkerman, “Extended Enterprise Architecture FrameworkEssentials Guide”, 20Essentials%20Guide%20v1.5.pdf, AT:2006/5/26; PT: 20063.J. Schekkerman,”The (Enterprise) Architecture Process chitecture%20Process%20Cycle%202001-02-01.htm, AT:2006/5/23; PT: 20014.J. Schekkerman, “Enterprise Architecture Tool Selection 0Selection%20Guide%20v3.pdf, AT:2006/5/26; PT: 200626E2AF

Resources (2)5.J. Schekkerman,”Enterprise Architecture Assessment itecture%20Assessment%20Guide%20v2.2.pdf, AT:2006/5/26; PT: 20066.J. Schekkerman,”Extended Enterprise Architecture Maturity ModelSupport aturity%20Model%20Guide%20v2.pdf AT:2006/5/26; PT: 2006,7.J. Schekkerman, “Extended Enterprise Architecture Maturity ModelSupport Guide”, 0Model%20Guide%20v2.pdf , AT:2006/5/26; PT: 20068.J. Schekkerman, “Enterprise Architecture terpriseArchitectureValidationFullversion.pdf , AT:2006/6/7; PT: 2003/9/827E2AF

Enterprise Architecture results as well as E2AF itself can be used as an Atlas for management to navigate to all relevant topics. From E2AF, roadmaps can be defined to identify the . Gartner'