Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

The Togaf Crop Circles

No description
by

Patrice Kerremans

on 9 November 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of The Togaf Crop Circles

Preliminary
Phase Phase A Architecture
Vision Phase B Business
Architecture Phase C Information
Systems
Architecture Phase D Technology
Architecture Phase E Opportunities
and
Solutions Phase F Migration Planning Phase G Implementation Governance Phase H Architecture
Change
Management Requirements
Management We start engineering here
We define the baseline and target architectures
We identify the gaps and roadmap components
Risks
Opportunities
We start writing the ADD steps - Phase B: Business Architecture
1. select reference models, viewpoints and tools
2. Develop baseline Business Architecture Description
3. Develop target Business Architecture Description
4. Perform gap analysis
5. Define candidate roadmap components
6. Resolve impacts across the architectural landscape
7. Conduct formal stakeholder review
8. Finalize the Business Architecture
9. Create Architecture Definition Document (ADD) steps:
1. select reference models, viewpoints and tools
2. Develop baseline Data Architecture Description
3. Develop target Data Architecture Description
4. Perform gap analysis
5. Define candidate roadmap components
6. Resolve impacts across the architectural landscape
7. Conduct formal stakeholder review
8. Finalize the data architecture
9. Update Architecture Definition Document (ADD) steps:
1. select reference models, viewpoints and tools
2. Develop baseline Technology Architecture Description
3. Develop target Technology Architecture Description
4. Perform gap analysis
5. Define candidate roadmap components
6. Resolve impacts across the architectural landscape
7. Conduct formal stakeholder review
8. Finalize the Technology Architecture
9. Update Architecture Definition Document (ADD) Collaborative effort Steps:
1. The Preliminary Phase describes the preparation and initiation activities required to create an Architecture Capability including customization of TOGAF and definition of Architecture Principles. Phase A: Architecture Vision describes the initial phase of an architecture development cycle. It includes information about defining the scope of the architecture development initiative, identifying the stakeholders, creating the Architecture Vision, and obtaining approval to proceed with the architecture development. Phase B: Business Architecture describes the development of a Business Architecture to support the agreed Architecture Vision. Phase C: Information Systems Architectures describes the development of Information Systems Architectures to support the agreed Architecture Vision. Phase D: Technology Architecture describes the development of the Technology Architecture to support the agreed Architecture Vision. Phase E: Opportunities & Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases. Phase F: Migration Planning addresses how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan. Phase G: Implementation Governance provides an architectural oversight of the implementation. Phase H: Architecture Change Management establishes procedures for managing change to the new architecture. Requirements Management examines the process of managing architecture requirements throughout the ADM. Steps - Phase A: Architecture Vision
1. Establish the architecture project
2. Identify stakeholders, concerns, and business requirements
3. Confirm and elaborate business goals, business drivers, and constraints
4. Evaluate business capabilities
5. Assess readiness for business transformation
6. Define scope
7. Confirm and elaborate architecture principles, including business principles
8. Develop Architecture Vision
9. Define the Target Architecture value propositions and KPIs
10. Identify the business transformation risks and mitigation activities
11. Develop Statement of Architecture Work; secure approval Steps - Phase E: Opportunities and Solutions
1. Determine/confirm key corporate change attributes
2. Determine business constraints for implementation
3. Review and consolidate gap analysis results from Phases B to D
4. Review consolidated requirements across related business functions
5. Consolidate and reconcile interoperability requirements
6. Refine and validate dependencies
7. Confirm readiness and risk for business transformation
8. Formulate Implementation and Migration Strategy
9. Identify and group major work packages
10. Identify Transition Architectures
11. Create Architecture Roadmap & Implementation and Migration Plan Steps - Phase F: Migration Planning
1. Confirm management framework interactions for Implementation and Migration Plan
2. Assign a business value to each work package
3. Estimate resource requirements, project timings, andavailability/delivery vehicle
4. Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation
5. Confirm Architecture Roadmap and update Architecture Definition Document
6. Complete the Implementation and Migration Plan
7. Complete the development cycle and document lessons learned Phase G: Implementation Governance1. Confirm scope and priorities for deployment with development management2. Identify deployment resources and skills3. Guide development of solutions deployment4. Perform enterprise architecture compliance reviews5. Implement business and IT operations6. Perform post-implementation review and close the implementation Phase H: Architecture Change Management1. Establish value realization process2. Deploy monitoring tools3. Manage risks4. Provide analysis for architecture change management5. Develop change requirements to meet performance targets6. Manage governance process7. Activate the process to implement change Steps - Requirements Management
1. Identify/document requirements
2. Baseline requirements
3. Monitor baseline requirements
4. Identify changed requirement; remove, add, modify, and re-assess priorities
5. Identify changed requirement and record priorities; identify and resolve conflicts; generate requirements impact statements
6. Assess impact of changed requirement on current and previous ADM phases
7. Implement requirements arising from Phase H
8. Update the requirements repository
9. Implement change in the current phase
10. Assess and revise gap analysis for past phases Steps - Preliminary Phase
1. Scope the enterprise organizations impacted
2. Confirm governance and support frameworks
3. Define and establish enterprise architecture team and organization
4. Identify and establish architecture principles
5. Tailor TOGAF and, if any, other selected architecture frameworks
6. Implement architecture tools
Full transcript