Tweet
EA/TOGAF/ITIL
The Open Group Architecture Framework (TOGAF) is followed by IT Architects. The framework provides a consistent set of steps that give a ‘road map’ of stages that allows people to take a business problem and convert it at the other end to a set of activities and possible solutions that may address it.
Prince 2 is a methodology on how to conduct a project from beginning to end and includes every phase/step you can think of. Like most things there is no hard and fast rule that states you need to use all of the steps – it is up to you to decide which ones apply. For example, a small project costing 1000 dollars is unlikely to warrant having a project manager spend 300 days in the project management phase.
ITIL is predominantly service delivery and management. Examples such as Change Mangement, Release Management etc come under here. If you want to know more, look at the Microsoft Operations Framework or Service Management Framework (you can Google links to this). ITIL comes into play when you actually get to the point of wanting to make the changes in your environment.
- TOGAF is used to construct the architecture – what you have in place now, what you want it to look like in the future, what business benefits are brought
- Prince 2 is used to plan and prepare for the projects necessary to deliver against the new architecture designed via TOGAF
- ITIL is the process you follow in ‘delivering’ the project(s) actions that were designed and agreed under the Prince 2 methodology.
The Preliminary Phase describes the preparation and initiation activities required to prepare to meet the business directive for a new enterprise architecture, including the definition of an Organization-Specific Architecture framework and the definition of principles.
Phase A: Architecture Vision describes the initial phase of an Architecture Development Cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.
Phase B: Business Architecture describes the development of a Business Architecture to support an agreed Architecture Vision.
Phase C: Information Systems Architectures describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.
Phase D: Technology Architecture describes the development of the Technology Architecture for an architecture project.
Phase E: Opportunities and Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases.
Phase F: Migration Planning addresses the formulation of a set of detailed sequence of Transition Architectures with a supporting 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.
P Preliminary Phase
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To review the organizational context for conducting enterprise architecture To identify the stakeholders, their requirements, and priorities To confirm the commitment of the stakeholders To identify and scope the elements of the enterprise organizations affected and define the constraints and assumptions; this is particularly important for large organizations with a federated architecture environment To define an organization’s “architecture footprint”; that is, the people responsible for performing architecture work, where they are located, and their responsibilities To define the framework and detailed methodologies to be used to develop the enterprise architecture in the organization; typically an adaptation of the ADM To set up a governance and support framework to provide business process and architecture governance through the ADM cycle; confirm the fitness-for-purpose and ongoing effectiveness of the Target Architecture; and run an initial pilot project To select and implement supporting tools and other infrastructure to support the activity To define the constraining architecture principles
|
Scope the enterprise organizations impacted Confirm governance and support frameworks Define and establish enterprise architecture team and organization Identify and establish architecture principles Select and tailor architecture framework(s) Implement architecture tools
|
TOGAF Other architecture framework(s) Business principles, business goals, and business drivers Architecture governance strategy IT strategy Existing organizational model for Eenterprise architecture Existing Architecture Framework, if any Existing architecture principles, if any Existing Architecture Repository, if any
|
Organizational Model for Enterprise Architecture Tailored Architecture Framework, including architecture principles Initial Architecture Repository Restatement of, or reference to,business principles, business goals,and business drivers Request for Architecture Work Governance Framework
|
R Requirements Management
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To provide a process to manage architecture requirements throughout the phases of the ADM cycle To identify requirements for the enterprise, store them, and feed them in and out of the relevant ADM phases, which dispose of, address, and prioritize requirements
|
Identify/document requirements Baseline requirements Monitor baseline requirements Identify changed requirement; remove, add, modify, and re-assess priorities Identify changed requirement and record priorities; identify and resolve conflicts; generate Requirements Impact Statements Assess impact of changed requirements on current and previous ADM phases Implement requirements arising from Phase H Update the requirements repository Implement change in the current phase Assess and revise gap analysis for past phases
|
The inputs to the Requirements Management process are the requirements-related outputs from each ADM phase. The first high-level requirements are produced as part of the Architecture Vision. Each architecture domain then generates detailed requirements. Deliverables in later ADM phases contain mappings to new types of requirements (for example, conformance requirements).
|
Changed requirements Requirements Impact Assessment, which identifies the phases of the ADM that need to be revisited to addressany changes. The final version must include the full implications of therequirements (e.g., costs, timescales, and business metrics).
|
A Architecture Vision
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To obtain commitment for this particular cycle of the ADM To define and organize an ADM cycle To validate business principles, goals, drivers, and Key Performance Indicators (KPIs) To define, scope, and prioritize architecture tasks To identify stakeholders, their concerns, and objectives To define business requirements and constraints To articulate an Architecture Vision and value proposition to respond to the requirements and constraints To create a comprehensive plan in line with the project management frameworks adopted by the enterprise To obtain formal approval to proceed To understand the influence on, and from, parallel architecture developments
|
Establish the architecture project Identify stakeholders, concerns, and business requirements Confirm and elaborate business goals, business drivers, and constraints Evaluate business capabilities Assess readiness for business transformation Define scope Confirm and elaborate architecture principles, including business principles Develop Architecture Vision Define the Target Architecture value propositions and KPIs Identify business transformation risks and mitigation activities Develop enterprise architecture plans and Statement of Architecture Work; secure approval
|
Request for Architecture Work Business principles, business goals, and business drivers Organizational Model for Enterprise Architecture Tailored Architecture Framework, including architecture principles Populated Architecture Repository; that is, existing architecture documentation (framework description, architecture descriptions, existing baseline descriptions, etc.)
|
Approved Statement of Architecture Work Refined statements of business principles, business goals, and business drivers Architecture principles Capability Assessment Tailored Architecture Framework Architecture Vision, including: • Refined key high-level stakeholder requirements • Baseline Business Architecture (vision) • Baseline Data Architecture (vision) • Baseline Application Architecture (vision) • Baseline Technology Architecture (vision) • Target Business Architecture (vision) • Target Data Architecture (vision) • Target Application Architecture (vision) • Target Technology Architecture (vision) Communications Plan Additional content populating the Architecture Repository
|
B Business Architecture
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To describe the Baseline Business Architecture To develop a Target Business Architecture To analyze the gaps between the Baseline and Target Business Architectures To select architecture viewpoints to demonstrate how stakeholder concerns are addressed in the Business Architecture To select tools and techniques for viewpoints
|
Select reference models, viewpoints, and tools Develop Baseline Business Architecture Description Develop Target Business Architecture Description Perform gap analysis Define roadmap components Resolve impacts across the Architecture Landscape Conduct formal stakeholder review Finalize the Business Architecture Create Architecture Definition Document
|
Request for Architecture Work Business principles, business goals, and business drivers Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Tailored Architecture Framework Approved Statement of Architecture Work Architecture principles, including business principles, when pre-existing Enterprise Continuum Architecture Repository Architecture Vision, including: • Refined key high-level stakeholder requirements • Baseline Business Architecture (vision) • Baseline Data Architecture (vision) • Baseline Application Architecture (vision) • Baseline Technology Architecture (vision) • Target Business Architecture (vision) • Target Data Architecture (vision) • Target Application Architecture (vision) • Target Technology Architecture (vision)
|
Statement of Architecture Work, updated if necessary Validated business principles, business goals, and business drivers Elaborated Business Architecture principles Draft Architecture Definition Document containing content updates: • Baseline Business Architecture (detailed), if appropriate • Target Business Architecture (detailed) • Views corresponding to selected viewpoints addressing key stakeholder concerns Draft Architecture Requirements Specification including content updates: • Gap analysis results • Technical requirements • Updated business requirements Business Architecture components of an Architecture Roadmap
|
C Data Architecture
valign=”top”>Request for Architecture WorkCapability AssessmentCommunications PlanOrganizational Model for Enterprise ArchitectureTailored Architecture FrameworkData principlesStatement of Architecture WorkArchitecture VisionArchitecture RepositoryDraft Architecture Definition Document containing:• Baseline Business Architecture (detailed)• Target Business Architecture (detailed)• Baseline Data Architecture (vision)• Target Data Architecture (vision)• Baseline Application Architecture (detailed orvision)• Target Application Architecture (detailed orvision)• Baseline Technology Architecture (vision)• Target Technology Architecture (vision)Draft Architecture Requirements Specificationincluding:• Gap analysis results• Relevant technical requirementsBusiness Architecture components of anArchitecture Roadmap
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To define the types and sources of data needed to support the business, in a way that can be understood by the stakeholders |
Select reference models, viewpoints, and tools Develop Baseline Data Architecture Description Develop Target Data Architecture Description Perform gap analysis Define roadmap components Resolve impacts across the Architecture Landscape Conduct formal stakeholder review Finalize the Data Architecture Create Architecture Definition Document
|
Statement of Architecture Work, updated if necessary Validated data principles, or new data principles Draft Architecture Definition Document containing content updates: • Baseline Data Architecture • Target Data Architecture • Data Architecture views corresponding to the selected viewpoints, addressing key stakeholder concerns Draft Architecture Requirements Specification including content updates: • Gap analysis results • Data interoperability requirements • Relevant technical requirements that will apply to this evolution of the architecture development cycle • Constraints on the Technology Architecture • Updated business requirements • Updated application requirements Data Architecture components of an Architecture Roadmap |
C Application Architecture
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To define the kinds of application systems necessary to process the data and support the business
|
Select reference models, viewpoints, and tools Develop Baseline Application Architecture Description Develop Target Application Architecture Description Perform gap analysis Define roadmap components Resolve impacts across the Architecture Landscape Conduct formal stakeholder review Finalize the Application Architecture Create Architecture Definition Document |
Request for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Tailored Architecture Framework Application principles Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document containing: • Baseline Business Architecture (detailed) • Target Business Architecture (detailed) • Baseline Data Architecture (detailed or vision) • Target Data Architecture (detailed or vision) • Baseline Application Architecture (vision) • Target Application Architecture (vision) • Baseline Technology Architecture (vision) • Target Technology Architecture (vision) Draft Architecture Requirements Specification including: • Gap analysis results • Relevant technical requirements Business and Data Architecture components of an Architecture Roadmap
|
Statement of Architecture Work, updated if necessary Validated application principles, or new application principles Draft Architecture Definition Document containing content updates: • Baseline Application Architecture • Target Application Architecture • Application Architecture views corresponding to the selected viewpoints, addressing key stakeholder concerns Draft Architecture Requirements Specification including content updates: • Gap analysis results • Application interoperability requirements • Relevant technical requirements that will apply to this evolution of the architecture development cycle • Constraints on the Technology Architecture • Updated business requirements • Updated data requirements Application Archite
|
D Technology Architecture
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To develop a Target Technology Architecture that will form the basis of the following implementation and migration planning
|
Select reference models, viewpoints, and tools Develop Baseline Technology Architecture Description Develop Target Technology Architecture Description Perform gap analysis Define roadmap components Resolve impacts across the Architecture Landscape Conduct formal stakeholder review Finalize the Technology Architecture Create Architecture Definition Document
|
Request for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Tailored Architecture Framework Technology principles Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document containing: • Baseline Business Architecture (detailed) • Target Business Architecture (detailed) • Baseline Data Architecture (detailed) • Target Data Architecture (detailed) • Baseline Application Architecture (detailed) • Target Application Architecture (detailed) • Baseline Technology Architecture (vision) • Target Technology Architecture (vision) Draft Architecture Requirements Specifi including: • Gap analysis results • Relevant technical requirements Business, Data, and Application Architecture components of an Architecture Roadmap |
Statement of Architecture Work, updated if necessary Validated technology principles or new technology principles (if generated here) Draft Architecture Definition Document containing content updates: • Baseline Technology Architecture • Target Technology Architecture • Technology Architecture views corresponding to the selected viewpoints, addressing key stakeholder concerns Draft Architecture Requirements Specification including content updates: • Gap analysis results • Requirements output from Phases B and C • Updated technology requirements Technology Architecture components of an Architecture Roadmap
|
E Opportunities & Solutions
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To review the target business objectives and capabilities, consolidate the gaps from Phases B to D, and then organize groups of building blocks to address these capabilities To review and confirm the enterprise’s current parameters for and ability to absorb change To derive a series of Transition Architectures that deliver continuous business value (e.g., capability increments) through the exploitation of opportunities to realize the building blocks To generate and gain consensus on an outline Implementation and Migration Strategy
|
Determine/confirm key corporate change attributes Determine business constraints for implementation Review and consolidate gap analysis results from Phases B to D Review IT requirements from a functional perspective Consolidate and reconcile interoperability requirements Refine and validate dependencies Confirm readiness and risk for business transformation Formulate high-level Implementation and Migration Strategy Identify and group major work packages Identify Transition Architectures Create portfolio and project charters and update the architectures
|
Product information Request for Architecture Work Capability Assessment Communications Plan Planning methodologies Organizational Model for Enterprise Architecture Governance models and frameworks Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document Draft Architecture Requirements Specification Change Requests for existing programs and projects
|
Statement of Architecture Work, updated if necessary Architecture Vision, updated if necessary Draft Architecture Definition Document, including content updates for: • Identification of increments • Interoperability and co-existence requirements • Inclusion of project list and project charters Draft Architecture Requirements Specification, updated if necessary Consolidated and validated Architecture Roadmap Capability Assessment, including content updates for: • Enterprise Architecture Maturity Profile • Transformation Readiness Report Transition Architectures, including: • Consolidated Gaps, Solutions, and Dependencies Assessment • Risk Register • Impact analysis – project list • Dependency Analysis Report • Implementation Factor Assessment and Deduction Matrix Implementation and Migration Plan (outline) |
F Migration Planning
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To ensure that the Implementation and Migration Plan is coordinated with the various management frameworks in use within the enterprise To prioritize all work packages, projects, and building blocks by assigning business value to each and conducting a cost/business analysis To finalize the Architecture Vision and Architecture Definition Documents, in line with the agreed implementation approach To confirm the Transition Architectures defined in Phase E with relevant stakeholders To create, evolve, and monitor the detailed Implementation and Migration Plan providing necessary resources to enable the realization of the Transition Architectures, as defined in Phase E
|
Confirm management framework interactions for Implementation and Migration Plan Assign a business value to each project Estimate resource requirements, project timings, and availability/delivery vehicle Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation Confirm Transition Architecture increments/phases and update Architecture Definition Document Generate the Architecture Implementation Roadmap (Time-Lined) and Migration Plan Establish the architecture evolution cycle and document lessons learned
|
Request for Architecture Work Capability Assessment Communications Plan Organizational Model for Enterprise Architecture Governance models and frameworks Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Draft Architecture Definition Document, including: • Strategic Migration Plan • Impact analysis – project list and charters Draft Architecture Requirements Specification Change Requests for existing programs and projects Consolidated and validated Architecture Roadmap Transition Architecture
|
Implementation and Migration Plan (outline) Implementation and Migration Plan (detailed) Finalized Architecture Definition Document Finalized Architecture Requirements Specification Finalized Architecture Roadmap Finalized Transition Architecture Re-Usable Architecture Building Blocks Requests for Architecture Work for the architecture aspects of implementation projects (if any) Architecture Contracts for implementation projects Implementation Governance Model Change Requests arising from lessons learned
|
G Implementation Governance
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To formulate recommendations for each implementation project To govern and manage an Architecture Contract covering the overall implementation and deployment process To perform appropriate governance functions while the system is being implemented and deployed To ensure conformance with the defined architecture by implementation projects and other projects To ensure that the program of solutions is deployed successfully, as a planned program of work To ensure confor deployed solution with the Target Architecture To mobilize supporting operations that will underpin the future working lifetime of the deployed solution
|
Confirm scope and priorities for deployment with development management Identify deployment resources and skills Guide development of solutions deployment Perform enterprise architecture compliance reviews Implement business and IT operations Perform post-implementation review and close the implementation
|
Request for Architecture Work Capability Assessment Organizational Model for Enterprise Architecture Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Architecture Definition Document Architecture Requirements Specification Architecture Roadmap Transition Architecture Implementation Governance Model Architecture Contract Request for Architecture Work identified in Phases E and F Implementation and Migration Plan
|
Architecture Contract (signed) Compliance Assessments Change Requests Architecture-compliant solutions deployed, including: • The architecture-compliant implemented system • Populated Architecture Repository • Architecture compliance recommendations and dispensations • Recommendations on service delivery requirements • Recommendations on performance metrics • Service Level Agreements (SLAs) • Architecture Vision, updated postimplementation • Architecture Definition Document, updated post-implementation • Transition Architecture, updated post-implementation • Business and IT operating models for the implemented solution |
H Architecture Change Management
|
Objectives |
Steps |
Inputs |
Outputs
|
|
To ensure that baseline architectures continue to be fit-for-purpose To assess the performance of the architecture and make recommendations for change To assess changes to the framework and principles set up in previous phases To establish an architecture change management process for the new enterprise architecture baseline that is achieved with completion of Phase G To maximize the business value from the architecture and ongoing operations To operate the Governance Framework |
Establish value realization process Deploy monitoring tools Manage risks Provide analysis for architecture change management Develop change requirements to meet performance targets Manage governance process Activate the process to implement change
|
Request for Architecture Work identified in Phases E and F Organizational Model for Enterprise Architecture Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository Architecture Definition Document Architecture Requirements Specification Architecture Roadmap Change Requests due to technology changes Change Requests due to business changes Change Requests from lessons learned Transition Architecture Implementation Governance Model Architecture Contract (signed) Compliance Assessments Implementation and Migration Plan
|
Architecture updates Changes to architecture framework and principles New Request for Architecture Work, to initiate another cycle of the ADM Statement of Architecture Work, updated if necessary Architecture Contract, updated if necessary Compliance Assessments, updated if necessary
|
