Top Banner

Click here to load reader

TOGAF 9 Methodology Ver1 0

Jan 28, 2015



TOGAF 9 Methodology - pdf format

  • 1. Summarised Approach - 2010

2. Architecture Approach Architecture Development 3. 1. Objectives2. Approach 5. Outputs Preliminary4. Steps 3. Inputs 4. 1.Organisational Context10. Architecture 2.Identify PrinciplesStakeholders Objectives3. Stakeholder9. Supporting ToolsInvolvement8. Governance4. Work Requirements Framework7. Architectural5. Identify ScopeFramework 6. ArchitectureFootprint 5. WHEREThe EnterpriseWHATDefine Organisational Context ApproachWHYRequirements for Architecture WorkWHOArchitectural PrinciplesHOWManagement Frameworks 6. Management FrameworksDetermines how a companymanages its change initiatives. Approach Determines what businesscapabilities are required todeliver business value includingthe definition of return oninvestment and the requisitecontrol/performance measures. Describes how a company runs its Formalizes the way that business day-to-day operations, including IT. systems are delivered in accordancewith the structures developed in theIT architectureInteroperability andRelationships betweenManagement Frameworks 7. Reference MaterialsNon-Architectural InputsExternal to the1. IT StrategyEnterprise 2. Governance Inputs 1. TOGAF Frameworks, etc,2. Other FrameworksArchitectural Inputs1. Existing Frameworks 2. Existing Principles3. Organisational ModelInput 8. ImplementArchitecture ToolsSelect and TailorArchitecture Framework(s) StepsIdentify and Establish Architecture Principles Define and Establish Enterprise Architecture Team andOrganisation Confirm Governance and Support Frameworks Scope the Enterprise Organisations Impacted 9. 2 34 1OrganisationalTailored ArchitectureModel for ArchitectureRestatement RepositoryEnterpriseFrameworkArchitectureOutputInclusive ofInclusive of Populated with Business additionaladditional frameworkprinciples, goals, information informationcontentand drivers6 5Request forGovernanceArchitecture FrameworkWork 10. 1. Objectives2. Approach 5. Outputs ArchitectureVision4. Steps 3. Inputs 11. 1. Recognitionand10. Endorsement2.Impact of Define and ParallelOrganiseArchitectures Objectives9.3.FormalValidateApproval to Business ProceedKPIs8.4.CreateScope andComprehensiPrioritiseve PlanBaseline5. 7.Define Articulate StakeholdersArchitecture and their Vision 6.concernsKey BusinessRequirements 12. What is in, and What is outside the scope of the architecture effort Constraints informed by the business principles and architectureGeneral principlesApproachArchitecture Vision describes how the new capability will meet thebusiness goals and strategic objectives and address theArchitecturestakeholder concerns when implemented. Vision Identifying and articulating the business requirements implied innew business capability to address key business drivers, and the Business implied architecture requirements. Scenarios 13. Non-Architectural InputsReference Materials 1. Request forExternal to the Architecture WorkEnterprise Inputs2. Business principles,1. Architecture goals, and driversReference MaterialsArchitectural Inputs1. Organisational Modelfor EA 2. Tailored ArchitectureFramework3. Populated Architecture Repository Input 14. SAW Businesstransformation Target Architecture and KPIsStepsDevelop Architecture Vision Architecture principles, includingbusiness principles Define scope Assess readiness for business transformation Evaluate business capabilitiesBusiness goals, drivers, and constraints Identify stakeholders, concerns, and business requirements Establish the Architecture Project 15. 23 41Approved Tailored Refined ArchitectureStatement of Architecture StatementsVisionArchitecture FrameworkWorkOutputScope, Plan, Roles,Stakeholder Requirements Business Principles, Tailored architecture Risks, Assessment, Baseline and Target Goals, Drivers method, and content. Business Case andBusiness, Technology,Configured and KPIsData, Applicationdeployed toolsArchitecture 65ArchitectureCommunicationsRepositoryPlan Additional Content 16. 1. Objectives2. Approach 5. OutputsBusiness Architecture4. Steps 3. Inputs 17. 1.Baseline BusinessArchitectureObjectives5.2. Tools andTechniquesTarget Business Architecture4. Architecture 3. Viewpoints Gap Analysis 18. The Business Strategy typically defines What to achieve Business Architectures role is to define Howto get thereGeneral The analysis of the current state often has to be done bottom-up, particularly where little or noarchitecture assets exist ApproachBaselineThe goal should be to re-use existing material as much as possibleDescription Business models should be logical extensions of the business scenarios from the Architecture Vision,so that the architecture can be mapped from the high-level business requirements down to the more Business detailed ones ModellingGeneric business models relevant to the organizations industry sector Business models relevant to common high-level business domains Architecture Enter prise-specific building blocks RepositoryApplicable standards 19. Non-Architectural InputsReference Materials Request for Architecture WorkExternal to the Enterprise Business principles, goals, andArchitecture Referencedrivers MaterialsCapability AssessmentCommunication Plan InputsArchitectural Inputs Organisational Model for EA Tailored Architecture Framework Populated ArchitectureRepository Approved SAW Enterprise Continuum Architecture Repository Architecture VisionInput 20. CreateArchitecture Definition DocumentFinalize theBusinessArchitecture Conduct for mal stakeholderreviewStepsResolve impacts across the ArchitectureLandscapeDefine roadmap componentsPerform gap analysisDevelop Target Business Architecture DescriptionDevelop Baseline Business Architecture DescriptionSelect reference models, viewpoints, and tools 21. 23 4 1 DraftDraftBusiness Architecture Architecture Architecture Architecture Definition Requirements Vision Updates Components Document Specifications OutputSAW, ValidateBaseline, Target and Gap Analysis, TechnicalBusiness principles, Of an ArchitectureViews for Business Requirements, Updateddrivers, ArchitectureRoadmapArchitecture Business RequirementsPrinciples 22. 1. Objectives2. Approach 5. Outputs Information Systems Architecture4. Steps 3. Inputs 23. 1. TargetArchitectures Objectives b.Application a. SystemData System DomainDomain 24. Combination of Data and Application Architecture Development Approach implementation approach is top-down design and bottom-upImplementation implementation 25. Non-ArchitecturalReference MaterialsInputsExternal to theEnterprise Request for Architecture WorkArchitecture Inputs Capability Assessment Reference MaterialsCommunication Plan Architectural Inputs Organisational Model for EA Tailored Architecture Framework Architecture Repository Approved SAW Enterprise Continuum Architecture Repository Architecture Vision Data and Application Principles Draft Architecture Document Input 26. Application Architecture StepsData Architecture 27. 23 41 DraftDraft Information Architecture ArchitectureSystem ArchitectureDefinition RequirementsArchitecture Vision UpdatesDocument SpecificationsComponentsOutputGap Analysis Results,Statement ofBaseline, Target and Technical Requirements, Of an ArchitectureArchitecture Work Views for Application Updated BusinessRoadmap(SAW) and Data Architectures Requirements 28. 1. Objectives2. Approach 5. OutputsData Architecture4. Steps 3. Inputs 29. 1.Data Sourcesunderstandable by Objectives Stakeholders2. 3. Data Sources thatData Sources that are complete and are stable consistent 30. Data Management Data Migration Key Considerationsfor Data Architecture Data GovernanceApproach generic data models relevant to theArchitectureorganizations industry vertical sector Repository 31. Reference Materials Non-ArchitecturalExternal to theInputsEnterprise Request forArchitectureArchitecture WorkReference Capability AssessmentArchitectural Inputs InputsMaterials Communication PlanOrganisational Model for EATailored Architecture FrameworkArchitecture RepositorySAWEnterprise ContinuumArchitecture RepositoryArchitecture VisionData PrinciplesDraft Architecture DocumentDraft Arch. Req. SpecBus Arch. Road Map Input 32. DefinitionDocument Finalize the Data ArchitectureConduct for mal stakeholderreviewStepsResolve impacts across the ArchitectureLandscapeDefine roadmap componentsPerform gap analysisDevelop Target Data Architecture DescriptionDevelop Baseline Data Architecture DescriptionSelect reference models, viewpoints, and tools 33. 23 4 1 DraftDraftData Architecture Architecture Architecture Architecture Definition Requirements Vision Updates Components Document SpecificationsOutput Statement of Gap Analysis Results,Baseline, Target andArchitecture WorkTechnical Requirements, Of an ArchitectureViews for Data(SAW), Validated DataUpdated BusinessRoadmapArchitecturesPrinciples Requirements 34. 1. Objectives2. Approach 5. Outputs Application Architecture4. Steps 3. Inputs 35. 1.Define theapplication system to process data and support businessObjectives 5.2.applications Define whatthat are stable application and relativelysystems areunchangingrelevant to the organisation4.3.TechnologyLogical groups agnostic of Capabilities that manage data objects 36. Generic business models relevant to theArchitecture Repository organizations industry sector Approach 37. Non-ArchitecturalReference Materials InputsExternal to theEnterprise Request for Architecture WorkArchitecture Capability Assessment InputsReference Materials Architectural Inputs Communication Plan Organisational Model for EA Tailored Architecture Framework Architecture Repository Approved SAW Enterprise Continuum Architecture Repository Architecture Vision Application Principles Draft Architecture Document Draft Architecture Req. Spec. Bus and Data Components Input 38. Create ArchitectureDefinitionDocument Finalize the Application ArchitectureConduct for mal stakeholder review StepsRe