Transcription
The Open Group Architecture Framework (TOGAF 9.1) Certification – Level 1 andLevel 2M 1: Management OverviewObjectivesAgendaThe Open GroupArchitecture Forum – MissionStakeholders and ValueWhat is an Enterprise?What is an Architecture?What is Enterprise Architecture?Architecture TypesWhy Enterprise Architecture?Pressure to develop Enterprise ArchitectureBusiness Benefits of Enterprise ArchitectureThe Importance of GovernanceWhat do we mean by Governance?What is an Architecture Framework?The Value of a FrameworkEnterprise Architecture Development MethodTOGAF OriginsTOGAF DevelopmentTOGAF ScopeTOGAF GoalsTOGAF 9 Components01
TOGAF 9.1 StandardTOGAF Capability FrameworkADM—Basic PrinciplesPreliminary PhasePhase A : Architecture VisionPhase B : Business ArchitecturePhase D : Technology ArchitecturePhase E : Opportunities and SolutionsPhase F : Migration PlanningPhase G : Implementation GovernancePhase H : Architecture Change ManagementTOGAF CertificationTOGAF Foundation Target AudienceTOGAF Certified Target AudienceSummaryM 2: TOGAF 9 ComponentsObjectivesTOGAF 9 ComponentsRoadmapThe Architecture Development MethodADM Guidelines and TechniquesApplying Iteration to the ADMApplying the ADM across the Architecture LandscapeCategories of StakeholderArchitecture Content FrameworkDeliverables, Artifacts and Building BlocksFull Content Metamodel with Relationships02
The Enterprise ContinuumArchitecture RepositoryTOGAF Reference ModelsHigh-Level TRMDetailed TRMBoundaryless Information Flow The Integrated Information Infrastructure Reference Model (III-RM)Capability FrameworkEstablishing the Architecture Capability as an Operational EntitySummaryM 3: Introduction to the Architecture Development MethodObjectivesWhat is the TOGAF ADM?Architecture Development Method – ProcessRelationship to other Parts of TOGAFADM PhasesADM Phase Steps ExampleADM Inputs and OutputsAdapting the ADMGoverning the ADMGovernance RepositoryReasons to Constrain the Scope of Architectural ActivityScoping the Architecture ActivityArchitecture IntegrationSummaryM 4: The Enterprise Continuum and ToolsRoadmap03
ObjectivesTOGAF 9: ComponentsOverviewArchitecture ReuseEnterprise Continuum: ConstituentsThe Architecture ContinuumThe Solutions ContinuumRelationshipsThe Enterprise ContinuumUsing the ContinuumRelationshipsThe Need for ToolsTools can Model the Enterprise ArchitectureIssues in Tool StandardizationSummaryM 5: Architecture RepositoryObjectivesPurposeArchitecture RepositoryArchitecture LandscapeReference LibraryStandards Information BaseStandards ClassificationGovernance Log ContentsRelationship to other Parts of TOGAFSummaryExercise04
M 6: The Architecture Content FrameworkObjectivesIntroductionBenefits of the Architecture Content FrameworkDeliverables, Artifacts, and Building BlocksRelationship between Deliverables, Artifacts, and Building blocksArchitectural ArtifactsContent MetamodelMapping the Framework and the ADMContent Framework and the TOGAF ADMSummaryM 7: The Architecture Content MetamodelObjectivesWhat is a MetamodelWhy a MetamodelBenefits of Content MetamodelFormal and Informal ModelingCore Content Metamodel ConceptsTOGAF Content Metamodel and its ExtensionsCore Metamodel EntitiesCore Entities and their RelationshipsStakeholder NeedsThe Content MetamodelContent Metamodel (Simplified)Core TOGAF 9 ArtifactsFull Content MetamodelFull Content Metamodel with Relationships05
Full Content Metamodel ArtifactsMetamodel ExtensionsGovernance ExtensionServices ExtensionProcess Modeling ExtensionData ExtensionInfrastructure Consolidation ExtensionMotivation Extension & SummaryM 8: The Preliminary PhaseObjectivesPreliminary Phase: Objectives in detailApproachPreliminary Phase: Main inputsSteps1. Scope the enterprise organizations impacted2. Confirm governance and support frameworks3. Define the team and organization4. Identify and establish architecture principlesDefining Architecture PrinciplesTOGAF Template for PrinciplesAn Example Statement of PrinciplesExample: Primacy of PrinciplesExample: Self-ServeFive Qualities of Principles5. Tailor TOGAF and, if any, other Selected Architecture FrameworksTerminology TailoringProcess Tailoring06
Content TailoringArchitecture Principles, Requirements, and RoadmapImplement architecture toolsPreliminary Phase: OutputsSummaryTOGAF 9 ArtifactsCatalogsExercisesM 9: Architecture GovernanceObjectivesIntroduction to GovernanceGovernance and ADMNature of GovernanceGovernance – Basic PrinciplesLevels of GovernanceAn IT Governance Framework - COBITTOGAF Architecture Governance FrameworkConceptual StructureArchitecture Governance Framework - Conceptual StructureOrganizational StructureBenefits of Architecture GovernanceArchitecture Governance in PracticeArchitecture BoardArchitecture Board ValueArchitecture Board ResponsibilitiesArchitecture Board OperationsArchitecture Contracts07
Architecture Contracts and ADMArchitecture Compliance: TerminologyArchitecture ComplianceArchitecture Compliance ReviewsArchitecture Compliance Review ProcessEstablishing an Architecture CapabilitySummaryExercisesM 10: Business ScenariosObjectivesIntroductionWhat is a Business Scenario?Business ScenariosBusiness Scenarios and the ADMWhat is a Good Business Scenario?SMARTThe Benefits of Business ScenariosWho Contributes to a Business Scenario?Developing a Business ScenarioGetting Business Scenarios RightContents of a Business ScenarioTemplate for a Business ScenarioExerciseResourcesSummaryM 11: Stakeholder ManagementObjectives08
OverviewBenefitsStakeholder ManagementStep 1: Identify StakeholdersCategories of StakeholderStep 2: Classify Stakeholder PositionsStep 3: Determine Stakeholder Management ApproachStep 4: Tailor Engagement DeliverablesExample: Stakeholder MapSummaryExerciseM 12: Views and View pointsObjectivesConcepts and Views and ViewpointsWhat is an Architecture View?A Simple Example of a ViewpointA Simple Example of a ViewDeveloping Views in the ADMExercise—Views and Viewpoints for a Simple Airport SystemThe View Creation ProcessBenefits09
Using TOGAF ArtifactsCatalogsMatricesStakeholder Map MatrixDiagramsExample Business Footprint DiagramRecommended Architecture ViewsSummaryM 13: Building BlocksObjectivesBuilding Block CharacteristicsA Good Building BlockBuilding BlocksArchitecture Building Blocks (ABBs)ABB SpecificationsSolution Building Blocks (SBBs)Building Blocks and the ADMBuilding Block DesignArchitecture PatternsF 6: ADM phases level 1ObjectivesPreliminary PhaseObjectives in detailApproachPhase A Architecture VisionObjectivesApproach10
Business ScenariosWhat is a Business Scenario?Business Scenarios and the ADMPhase B Business ArchitectureObjectivesApproachDeveloping the Baseline DescriptionBusiness Modeling ExamplesUsing the Architecture RepositoryPhase C Information Systems ArchitecturesData or Applications first ?Information Systems Architectures – ObjectivesApproachTop-Down Design—Bottom-up ImplementationData-Driven Sequence ImplementationArchitecture RepositoryConsiderations for the Data ArchitecturePhase D Technology ArchitectureObjectivesUsing the Architecture RepositoryPhase E Opportunities and SolutionsObjectivesApproachPhase F Migration PlanningObjectivesApproachPhase G Implementation Governance11
ApproachPhase H Architecture Change ManagementObjectivesApproachExercise—Drivers for Architecture ChangeChange Management ProcessMaintenance versus RedesignExercise—Change ImpactADM Requirements ManagementObjectivesApproachResourcesVolère Requirements Specification TemplateModule F7—ADM Guidelines and chitecture PrinciplesThe need for Architecture PrinciplesTemplateExample: Primacy of PrinciplesExample: Self-ServeWhat makes a good set of Architecture PrinciplesWhat is a business scenario?What is a good business scenario?The use of business scenarios in the ADM12
Gap AnalysisExampleInteroperabilityInteroperability and the ADMExamplesThe Business Transformation Readiness ProgramBusiness Transformation Readiness and the ADMExampleRisk Management in the ADMExampleCapability based planningCapabilitiesSummaryExerciseF 7: chitecture PrinciplesThe need for Architecture PrinciplesTemplateExample: Primacy of PrinciplesExample: Self-ServeWhat makes a good set of Architecture PrinciplesWhat is a business scenario?The use of business scenarios in the ADM13
Gap AnalysisExampleInteroperability and the ADMExamplesThe Business Transformation Readiness ProgramBusiness Transformation Readiness and the ADMExampleRisk Management in the ADMExampleCapability based planningCapabilitiesSummaryExerciseF 11: ADM DeliverablesObjectivesThe role of Architecture DeliverablesArchitecture DeliverablesRequest for Architecture WorkStatement of Architecture WorkArchitecture VisionCommunications PlanArchitecture Definition DocumentArchitecture Requirements DocumentArchitecture RoadmapF 12: Reference ModelsObjectivesTOGAF Foundation Architecture14
The Architecture ContinuumTRM ComponentsSummary of the TRMA common problemCustomer problem statementA Shared VisionHow Important Integrated Information Infrastructure Reference ModelThe Architecture ContinuumTOGAF TRM OrientationsBoundaryless Information Flow FocusIntegrated Information Infrastructure Reference Model – High-level ModelComponents of the III-RMSummary of the III-RMF 13: CertificationObjectivesTOGAF Certification for PeopleTOGAF 9 Certification LevelsLevel 1—TOGAF 9 Foundation Target AudiencePaths to Level 2Exam Paths to Level 2ComponentsLevel 1 Learning UnitsLevel 2 Learning UnitsLevel 1 Exam RequirementsLevel 2 Exam RequirementsLevel 2 Stepwise Development15
Level 2 DirectLevel 2 Exam Via Bridge RequirementsCombined Part 1 and 2 ExaminationCertificationM 14: Architecture Implementation Support ty and the ADMExamplesInteroperability Requirements and SolutionsBusiness Transformation Readiness AssessmentThe Business Transformation Readiness AssessmentReadiness FactorsAssess the Readiness FactorsReadiness Factor RatingReadiness Factor Risks & ActionsRisk ManagementRisk Management in the ADMInitial Risk AssessmentRisk Classification SchemeRisk Identification and Mitigation WorksheetCapability Based PlanningCapabilitiesSummaryExerciseM 15: Phase A: Architecture VisionObjectives16
Architecture Vision–ObjectivesApproachPhase A: InputsRequest for Architecture WorkStepsStep 1: Establish the ProjectStep 2: Identify Stakeholders, Concerns, and Business Requirements Stakeholder MapStep 3: Confirm Business Goals, Drivers and ConstraintsStep 4: Evaluate Business Capabilities Value Chain DiagramStep 5: Assess Readiness for Business TransformationStep 6: Define the ScopeStep 7: Confirm and Elaborate Architecture Principles and Business PrinciplesStep 8: Develop Architecture Vision Solution Concept DiagramStep 9: Define the Target Architecture Value Propositions and KPIsStep 10:Identify the Business Transformation Risks and Mitigation ActivitiesStep 11: Develop Statement of Architecture Work; Secure ApprovalStatement of Architecture WorkPhase A: OutputsSummaryM 16: Phase B: Business ArchitectureObjectivesBusiness Architecture ObjectivesApproachPhase B: InputsStepsStep 1: Select Reference Models, Viewpoints, and ToolsExample Artifacts17
Examples of ModelingStep 2: Develop Baseline Business Architecture DescriptionStep 3: Develop Target Business Architecture DescriptionStep 4: Perform Gap AnalysisGap Analysis ExerciseGap Analysis Exercise—AnswerStep 5: Define Candidate Roadmap ComponentsStep 6: Resolve Impacts across the Architecture LandscapeStep 7: Conduct Formal Stakeholder ReviewStep 8: Finalize the Business ArchitectureStep 9: Create Architecture Definition DocumentSummary of Building Block Usage in Phase BPhase B: OutputsArchitecture Definition DocumentArchitecture Definition Document – Business Architecture ComponentsArchitecture Requirements SpecificationArchitecture Requirements Specification—Business Architecture ComponentsSummaryExercisePhase B: Business ArchitectureM 16 A: Phase B: Business Architecture—Catalogs, Diagrams and MatricesCatalogs, Matrices and DiagramsCatalogsExerciseMatricesBusiness Interaction MatrixActor/Role Matrix18
DiagramsExample Business Footprint DiagramBusiness Service/Information DiagramExample Business Service/Information DiagramFunctional Decomposition DiagramExample Functional Decomposition DiagramProduct Lifecycle DiagramExample Product Lifecycle DiagramGoal/Objective/Service DiagramExample Goal/Objective/Service DiagramBusiness Use-case DiagramExample Business Use-case DiagramOrganization Decomposition DiagramExample Organization Decomposition DiagramProcess Flow DiagramExample Process Flow DiagramEvents DiagramExample Events DiagramExample Events MatrixM 17: Phase C: Information Systems ArchitecturesObjectivesInformation Systems Architectures—ObjectivesApproachTop-Down Design—Bottom-Up ImplementationAlternative Approach: Data-Driven Sequence ImplementationApproach: Architecture RepositoryConsiderations for Data Architecture19
Phase C: InputsSteps in Phase CPhase C: Outputs—Application ArchitectureSummaryM 18: Phase C: Data ArchitectureObjectivesData Architecture—ObjectivesPhase C—InputsSteps in Data Architecture PhaseStep 1: Select reference models, viewpoints, and toolsTOGAF 9 ArtifactsStep 2: Develop a Baseline Data Architecture DescriptionStep 3: Develop Target Data Architecture DescriptionStep 4: Perform Gap AnalysisStep 5: Define Candidate Roadmap ComponentsStep 6: Resolve impacts across the Architecture LandscapeStep 7: Conduct Formal Stakeholder ReviewStep 8: Finalize the Data ArchitectureStep 9: Create Architecture Definition DocumentOutputs of Data ArchitectureData Architecture Components—Architecture Definition DocumentData Architecture Components—Architecture Requirements SpecificationSummaryExerciseM 18 A: Phase C: Data Architecture—Catalogs, Matrices and DiagramsObjectivesTOGAF 9 Artifacts20
Catalogs, Matrices, and DiagramsCatalogsExerciseMatricesData Entity/Business Function MatrixExample Data Entity/Business Function MatrixApplication/Data MatrixExample Application/Data MatrixDiagramsConceptual Data DiagramLogical Data DiagramData Dissemination DiagramData Dissemination Diagram—ExampleData Lifecycle DiagramData Security DiagramData Security Diagram—ExampleData Security Matrix—ExampleData Migration DiagramData Migration Diagram—ExampleData Migration Mapping—ExamplePhase C: Data Architecture—Catalogs, Matrices, and DiagramsM 19: The Integrated Information Infrastructure Reference ModelObjectivesKey Business and Technical DriversIntegrated Information Infrastructure Reference ModelTOGAF TRMTOGAF TRM Orientations21
Boundaryless Information Flow FocusIntegrated Information Infrastructure Reference Model—A High-level ModelComponents of the III-RMComponents of the High-Level III-RMIntegrated Information Infrastructure Reference Model—A Detailed ModelSummaryExercisesThe Integrated Information Infrastructure Reference ModelM 20: Phase C: Applications ArchitectureModule ObjectivesPhase C: Inputs: Application ArchitectureStepsStep 1: Select Reference Models, Viewpoints and ToolsTOGAF 9 ArtifactsRecommended ProcessStep 1: Select Reference Models, Viewpoints, and ToolsExample – The Integrated Information Infrastructure ModelIII-RM Business and Technical DriversIII-RM FocusIII-RM High Level ViewStep 2: Develop a Baseline Application Architecture DescriptionStep 3: Develop Target Application Architecture DescriptionStep 4: Perform Gap AnalysisStep 5: Define Candidate Roadmap ComponentsStep 6: Resolve Impacts Across the Architecture LandscapeStep 7: Conduct Formal Stakeholder ReviewStep 8: Finalize the Application Architecture22
Step 9: Create Architecture Definition DocumentPhase C: Outputs: Application ArchitectureArchitecture Definition Document – Application Architecture ComponentsArchitecture Requirements Specification – Application Architecture ComponentsSummaryM 20 A: Phase C: Applications Architecture – Catalogs, Matrices and DiagramsModule ObjectivesTOGAF 9 ArtifactsCatalogs, Matrices and zation MatrixExample Application/Organization MatrixRole/Application MatrixExample Role/Application MatrixApplication/Function MatrixDiagramsApplication Communication DiagramApplication and User Location DiagramApplication Use Case DiagramEnterprise Manageability DiagramProcess/Application Realization DiagramSoftware Engineering DiagramApplication/Migration DiagramSoftware Distribution DiagramM 21: Foundation Architecture23
Module ObjectivesTOGAF Foundation ArchitectureTechnical Reference Model ComponentsThe Technical Reference ModelTaxonomy of Platform ServicesTaxonomy of Application Platform Service yCustomizing the TRMSummaryM 22:Phase D: Technology ArchitectureModule ObjectivesApproachTechnology Architecture: InputsStepsTOGAF 9 ArtifactsTechnology Architecture OutputsArchitecture Definition Document – Technology Architecture ComponentsSummaryM 22 A: Phase D: Technology Architecture – Catalogs, Matrices and DiagramsModule ObjectivesTOGAF 9 ArtifactsCatalogs, Matrices, and DiagramsM 23: Migration Planning TechniquesModule Objectives24
The Implementation Factor Assessment and Deduction MatrixThe Consolidated Gaps, Solutions and Dependencies MatrixArchitecture Definition Increments tableThe Transition Architecture State Evolution TableThe Business Value Assessment TechniqueSummaryM 24: Phase E: Opportunities and SolutionsModule ObjectivesStakeholdersApproachPhase E: InputsStepsPhase E OutputsSummaryTOGAF 9 ArtifactsProject Context DiagramBenefits DiagramM 25: Phase F: Migration PlanningPhase F ObjectivesApproachPhase F: InputsStepsPhase F OutputsSummaryM 26: Phase G: Implementation GovernanceModule ObjectivesPhase G Objectives25
ApproachPhase G: InputsStepsPhase G OutputsSummaryM 27: Phase H: Architecture Change ManagementModule ObjectivesPhase H ObjectivesApproachChange Management ProcessMaintenance versus RedesignChange Impact ExercisePhase H: InputsChange RequestsStepsPhase H OutputsBusiness Users’ Architecture ContractRequest for Architecture WorkSummaryM 28: ADM Requirements ManagementModule ObjectivesADM Requirements ManagementObjectivesApproachRequirements DevelopmentResourcesVolère Requirements Specifications Template26
Requirements Management: InputsStepsRequirements Management: OutputsRequirements Impact AssessmentSummaryM 29: Architecture PartitioningModule ObjectivesPartitioningPreliminary PhaseSummaryM 30: Guidelines for Adapting the ADM: Iteration and LevelsModule ObjectivesIteration and LevelsIteration and the ADMIteration to Manage the Architecture CapabilityApproaches to Architecture DevelopmentClasses of Architecture EngagementA Hierarchy of ADM ProcessesArchitecture Development Iteration “Baseline First”Architecture Development Iteration “Target First”Transition PlanningArchitecture GovernanceApplying the ADM Across the Architecture LandscapeSummaryM 31: Guidelines for Adapting the ADM: SecurityModule ObjectivesSecurity and the ADM27
Stakeholder ConcernsADM Requirements ManagementPreliminary PhasePhase A – Architecture VisionPhase B – Business ArchitecturePhase C Information Systems ArchitecturesPhase D Technology ArchitecturePhase E Opportunities and SolutionsPhase F Migration PlanningPhase G Implementation GovernancePhase H Architecture Change ManagementSummaryM 32: Guidelines for Adapting the ADM: SOAModule ObjectivesWhat is Service Oriented Architecture?Preliminary PhasePhase A: Architecture VisionArchitecture Development: Phases B,C, and DSummaryM 33: Architecture Maturity ModelsModule ObjectivesCapability Maturity ModelsCMMIUS Department of Commerce ACMMMaturity Assessments in the ADMSummaryM 34: Architecture Skills Framework28
Module ObjectivesRolesPurposeBenefits of using the Architecture Skills FrameworkThe structure of the Architecture Skills FrameworkSummary29
ADM Phase Steps Example ADM Inputs and Outputs Adapting the ADM Governing the ADM Governance Repository Reasons to Constrain the Scope of Architectural Activity Scoping the Architecture Activity Architecture Integration Summary M 4: The Enterprise Continuum and Tools Roadmap The Enterprise Continuum Architecture Repository TOGAF Reference Models
