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

Key Togaf Deliverables

No description
by

Patrice Kerremans

on 4 January 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Key Togaf Deliverables

Key TOGAF
deliverables Contractual or formal
work products
of an
architecture project RAW - Request for Architecture Work

Contains the request for Architecture Work and is sent by a Sponsor.
Created as an output from the Preliminary Phase, or
Created as an output from an approved Architecture Change Request
Can also come from Migration Planning
High-level information RAW - Request for Architecture Work
SAW - Statement of Architecture Work
Architecture Vision
Communications Plan
Architecture Definition Document
Architecture Requirements Document
Architecture Roadmap SAW - Statement of Architecture Work

Deliverable output of Phase A
Defines scope and approach of used to complete an architecture development cycle
Contents:
Title
Architecture project request and background
Architecture project description and scope
Overview of Architecture Vision
Specific change of scope procedures
Roles, responsibilities, and deliverables
Acceptance criteria and procedures
Architecture project plan and schedule
Approvals Architecture Vision

Produced in Phase A
provides a summary of the changes to the enterprise that will accrue from successful deployment of the Target Architecture
purpose of the Architecture Vision is to provide key stakeholders with a formally agreed outcome. Early agreement on the outcome enables the architects to focus on the detail necessary to validate feasibility. Communications Plan

Effective communication of targeted information to the right stakeholders at the right time is a critical success factor for enterprise architecture.
Development of a Communications Plan for architecture allows for this communication to be carried out within a planned and managed process. ADD - Architecture Definition Document
Deliverable container for core Artifacts:
Business, Data, Application and Technology architectures
Includes baseline, transition and target architectures
Developed through phases A,B,C,D
Provides QUALITATIVE view of the solution ARD - Architecture Requirements Document
Deliverable container for requirements for an architecture:
Companion to ADD
Often used in the Architecture Contract
Provides QUANTATIVE view of the solution that the implementation must comply to Architecture Roadmap
Lists individual work packages that will realize the target architecture
shows the progression from baseline to target on a time line
highlights business value of each work package at each stage
developed incrementally throughout Phases E and F including roadmap components from Phase B, C, and D Architecture Roadmap - Work package portfolio:
Work package description (name, description, objectives, deliverables)
Functional requirements
Dependencies
Relationship to opportunity
Relationship to Architecture Definition Document and Architecture Requirements Specification
Business value Architecture Roadmap - Implementation Factor Assessment and Deduction matrix, including:
Risks
Issues
Assumptions
Dependencies
Actions
Inputs Architecture Roadmap - Consolidated Gaps, Solutions, and Dependencies matrix, including:
Architecture domain
Gap
Potential solutions
Dependencies Architecture Roadmap - Implementation recommendations:
Criteria measures of effectiveness of projects
Risks and issues
Solution Building Blocks (SBBs) Architecture Vision - Typical Contents
Problem description:
Stakeholders and their concerns
List of issues/scenarios to be addressed
Objective of the Statement of Architecture Work
Summary views necessary for the Request for Architecture Work and the Version 0.1 Business, Application, Data, and Technology Architectures created; typically including:
Value Chain diagram
Solution Concept diagram
Mapped requirements
Reference to Draft Architecture Definition Document Statement of Architecture Work - Typical Contents
Title
Architecture project request and background
Architecture project description and scope
Overview of Architecture Vision
Specific change of scope procedures
Roles, responsibilities, and deliverables
Acceptance criteria and procedures
Architecture project plan and schedule
Approvals Requests for Architecture Work - typically include:
Organization sponsors
Organization’s mission statement
Business goals (and changes)
Strategic plans of the business
Time limits
Changes in the business environment
Organizational constraints
Budget information, financial constraints
External constraints, business constraints
Current business system description
Current architecture/IT system description
Description of developing organization
Description of resources available to developing organization Communications Plan - Typical Contents

List of stakeholders, and
how to contact them (email, phone...)
frequency
information to share (status, diagrams...) ADD - Typical Contents
Scope
Goals, objectives, and constraints
Architecture principles
Baseline Architecture
Architecture models (for each state to be modeled)
Rationale and justification for architectural approach
Mapping to Architecture Repository:
Mapping to Architecture Landscape
Mapping to reference models
Mapping to standards
Re-use assessment
Gap analysis
Impact assessment
Transition Architecture:
Definition of transition states
Business Architecture for each transition state
Data Architecture for each transition state
Application Architecture for each transition state
Technology Architecture for each transition state ARD - Typical contents:
Success measures
Architecture requirements
Business service contracts
Application service contracts
Implementation guidelines
Implementation specifications
Implementation standards
Interoperability requirements
IT Service Management requirements
Constraints
Assumptions Output from: Preliminary, F, H
Input for: A, G Output from: A, B, C, D, E, F, G, H
Input for: B, C, D, E, F, G, H, Requirements Management Output from: A, E
Input for: B, C, D, E, F, G, H Output from: A
Input for: B, C, D, E, F Output from: B, C, D, E, F
Input for: C, D, E, F, G, H Output from: B, C, D, E, F, Requirements Management
Input for: C, D, Requirements Management Typical Contents:
Work package portfolio
Implementation Factor Assessment and Deduction matrix
Consolidated Gaps, Solutions, and Dependencies matrix
Any Transition Architectures
Implementation recommendations Output from: B, C, D, E, F
Input for: B, C, D, E, F
Full transcript