Upload
dotu
View
278
Download
21
Embed Size (px)
Citation preview
Avancier
DoDAF in a nutshell
Copyright Avancier Ltd 2013
Part three: Viewpoints and Models
You may share http://avancier.co.uk as the link to this presentation If you want to share or show the pdf, email [email protected]
Sources include
ArchiMate 2.0 standard.
Copyright © 2009-2012 The Open Group, All Rights Reserved.
ArchiMate is a registered trademark of The Open Group.
IBM web site
http://pic.dhe.ibm.com/infocenter/rsysarch/v11/index.jsp?topic=%2Fcom.ibm.sa.dodaf.doc%2Ftopics%2Ft_D2_creat_cv-
03_proj_timel_diag.html
Avancier 3rd of three slide shows
► An attempt to distil DoDAF into c100 slides
■ Part one: DoDAF as applied system theory
■ Part two: DoDAF terms and concepts
■ Part three: DoDAF viewpoints and models
Copyright Avancier Ltd 2013
Avancier Acknowledgements
► “The slide shows are pretty good.
► References to the source material would be helpful.”
► The illustrations are drawn from
■ Avancier Methods (models drawn by me)
■ MoDAF (models presented in the MoDAF template)
■ The ArchiMate v2 standard (see title page)
■ The IBM web site (see title page)
■ Some individual pics grabbed from the internet
► Do email if you find better ones elsewhere
Copyright Avancier Ltd 2013
Avancier DoDAF viewpoints
► DoDAF groups models into eight viewpoints:
■ All Viewpoint (AV).
■ Capability Viewpoint (CV).
■ Operational Viewpoint (OV).
■ Data and Information Viewpoint (DIV).
■ Services Viewpoint (SvcV).
■ Systems Viewpoint (SV).
■ Project Viewpoint (PV).
■ Standard Viewpoint (StdV).
► “The decision-maker and process owners will determine the
DoDAF-described Models that are required for their purposes.”
Copyright Avancier Ltd 2013
Avancier The DoDAF graphic of the eight viewpoints
Copyright Avancier Ltd 2013
Avancier Six of the eight DoD viewpoints
These viewpoints
are illustrated
hereafter
Copyright Avancier Ltd 2013
Operational operational scenarios, processes,
activities & requirements
Services the performers, activities, services,
and their exchanges providing for,
or supporting, DoD functions
Systems the legacy systems or independent
systems, their composition,
interconnectivity, and context
providing for, or supporting, DoD
functions
Data and
Information
the data
relationships
and alignment
structures in the
architecture
content
Project
Describes the
relationships
between operational
and capability
requirements and
the various projects
being implemented;
Details
dependencies
between capability
management and
the Defense
Acquisition System
Process
Capability manager’s view of capability
taxonomy and evolution.
Avancier All viewpoints
► Executive-level vision and summary
Copyright Avancier Ltd 2013
Avancier
► Executive-level summary information in a consistent form
► Allows quick reference and comparison between Architectural
Descriptions.
► Describes concepts in the pictorial representation of the OV-1.
► Scope the architecture effort.
► Provide context to the architecture effort.
► Define the architecture effort.
► Summarize the findings from the architecture effort.
► Assist search of an architecture repository.
Copyright Avancier Ltd 2013
AV-1: Overview
and Summary
Information
Describes a Project's Visions, Goals, Objectives, Plans,
Activities, Events, Conditions, Measures, Effects
(Outcomes), and produced objects.
Avancier
Copyright Avancier Ltd 2013
Objective Objective
Driver Mission Vision
Activities
Goal Goal
Effects
Systems
► The text document might be supported by some graphics
AV-1: Overview
and Summary
Information
Describes a Project's Visions, Goals, Objectives, Plans,
Activities, Events, Conditions, Measures, Effects
(Outcomes), and produced objects.
Avancier
Copyright Avancier Ltd 2013
► Provides consistency across populated views, based on
DoDAF-described Models.
► Provides consistency across Architectural Descriptions.
► Facilitates Architectural Description development, validation,
maintenance, and re-use.
► Traces architectural data to authoritative data sources.
AV-2: Integrated
Dictionary
An architectural data repository with definitions of all
terms used throughout the architectural data and
presentations.
Avancier Capability Viewpoint
► the capability requirement,
► delivery timing, and
► deployed capability
► Introduced into DoDAF V2.0 to address the concerns of
Capability Portfolio Managers.
► The Capability Models describe capability taxonomy and
capability evolution.
Copyright Avancier Ltd 2013
Avancier
Copyright Avancier Ltd 2013
► Structured text document
■ Capability
■ Description
■ Goal
■ Outcome
■ Benefit
► Hmm.. So what is a capability?
■ An architecture artefact: a persistent (logical) system?
■ A management artefact: the aim of transient project?
CV-1: Vision The overall vision for transformational endeavors, which provides
a strategic context for the capabilities described and a high-level
scope.
Avancier
CV-2: Capability
Taxonomy
A hierarchy of capabilities which specifies all the capabilities
that are referenced throughout one or more Architectural
Descriptions.
Copyright Avancier Ltd 2013
Product and service delivery
Manage and support the business
Vendor management Finance Business management Business support
Proposition management
Distribution and sales
Service customers
Policy administration Customer management Claims
Channel strategy
Panel management
Channel management
Lead management
Quotes and agreements to buy
On sell and retention
Sales performance management
Distribution support
Aka capability map or
functional decomposition
“Business functions — a detailed, recursive step involving successive decomposition of major functional
areas into sub-functions… outputs may include Functional Decomposition diagram” TOGAF
Avancier
Copyright Avancier Ltd 2013
► Here, a capability is the outcome of a transient project
CV-3: Capability
Phasing
The planned achievement of capability at different points in time or
during specific periods of time. Shows the capability phasing in terms
of the activities, conditions, desired effects, rules complied with,
resource consumption and production, and measures, without
regard to the performer and location solutions.
Capability Phasing
Capability increment Phase 1 Phase 2 Phase 3
A V.1 activities, conditions,
desired effects, rules
complied with,
resource consumption
and production, and
measures
V. 2
B V. 1
C V. 1 V. 2
D V. 1 Retire
E V. 1
F V. 1
Avancier
CV-4: Capability
Dependencies
The dependencies between planned capabilities and the
definition of logical groupings of capabilities.
Copyright Avancier Ltd 2013
Aka goods and services
flow diagram - where
services inc. data flows.
Avancier
Copyright Avancier Ltd 2013
► Shows the planned capability deployment and interconnection
for a particular phase.
► A more detailed dependency analysis than the CV-3
► Supports the capability management process
■ Fielding planning.
■ Capability integration planning.
■ Capability options analysis.
■ Capability redundancy/overlap/gap analysis.
■ Identification of deployment level shortfalls.
CV-5: Capability to
Organizational
Development
Mapping
The fulfillment of capability requirements shows the planned
capability deployment and interconnection for a particular Capability
Phase. The CV-5 shows the planned solution for the phase in terms
of performers and locations and their associated concepts.
Avancier
CV-6: Capability to
Operational Activities
Mapping
A mapping between the capabilities required and the operational
activities that those capabilities support.
CV-7: Capability to
Services Mapping
A mapping between the capabilities and the services that these
capabilities enable.
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
Service enabled
by Capability
Required
Capability
Operational
Activity
Avancier
CV-6: Capability to
Operational Activities
Mapping
A mapping between the capabilities required and the operational
activities that those capabilities support.
CV-7: Capability to
Services Mapping
A mapping between the capabilities and the services that these
capabilities enable.
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The
Open Group, All Rights
Reserved. ArchiMate is a
registered trademark of The
Open Group.
DoDAF Service
enabled…
By required
Capability
Activity in Capability
Role (activities)
supported by capability
Avancier Operational views
Copyright Avancier Ltd 2013
► operational scenarios,
► processes,
► activities & requirements
Business
Operations
Service
Performer
Person
Activity
Information & Materiel
Avancier
OV-1: High-Level Operational
Concept Graphic
The high-level graphical/textual description
of the operational concept.
Avancier
Copyright Avancier Ltd 2013
► Based around a “rich picture” or cartoon
OV-1: High-Level Operational
Concept Graphic
The high-level graphical/textual description
of the operational concept.
Avancier
Copyright Avancier Ltd 2013
OV-1: High-Level Operational
Concept Graphic
The high-level graphical/textual description
of the operational concept.
Avancier
Copyright Avancier Ltd 2013
► Less formal than a flow chart with step-to-step transitions.
Customer
identification
Payment Delivery Order
Vision
& Strategy
Product
identification
Marketing Customer
Service Sales
Product
Supply
OV-1: High-Level Operational
Concept Graphic
The high-level graphical/textual description
of the operational concept.
Avancier
Copyright Avancier Ltd 2013
OV-2: Operational
Resource Flow Description
A description of the Resource Flows
exchanged between operational activities.
Avancier
Copyright Avancier Ltd 2013
OV-2: Operational
Resource Flow Description
A description of the Resource Flows
exchanged between operational activities.
Avancier
OV-2: Operational
Resource Flow Description
A description of the Resource Flows
exchanged between operational activities.
Copyright Avancier Ltd 2013
Avancier
► This ArchiMate diagram shows resources passing between functions,
which encapsulate operational activities
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
OV-2: Operational
Resource Flow Description
A description of the Resource Flows
exchanged between operational activities.
Avancier
► This ArchiMate diagram shows resource flows exchanged between
managed organisation units, which perform operational activities
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
OV-2: Operational
Resource Flow Description
A description of the Resource Flows
exchanged between operational activities.
Avancier
Copyright Avancier Ltd 2013
► No example yet
OV-3: Operational
Resource Flow Matrix
A description of the resources exchanged and
the relevant attributes of the exchanges.
Avancier
Copyright Avancier Limited
OV-4: Organizational
Relationships Chart
The organizational context, role or other
relationships among organizations.
Avancier
► ArchiMate diagram
example uses the actor
symbol for an organisation
unit in a hierarchical
structure
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
Actor = Org Unit
OV-4: Organizational
Relationships Chart
The organizational context, role or other
relationships among organizations.
Avancier
Copyright Avancier Ltd 2013
OV-4: Organizational
Relationships Chart
The organizational context, role or other
relationships among organizations.
Avancier
Copyright Avancier Ltd 2013
OV-5a: Operational Activity
Decomposition Tree
The capabilities and operational activities
organized in a hierarchal structure.
“Business functions — a detailed, recursive step involving successive decomposition of major functional
areas into sub-functions… outputs may include Functional Decomposition diagram” TOGAF
Avancier
Copyright Avancier Limited
OV-5b:
Operational
Activity Model
The context of capabilities and operational activities and their
relationships among activities, inputs, and outputs … can show
cost, performers, or other pertinent information.
Avancier
OV-5b:
Operational
Activity Model
The context of capabilities and operational activities and their
relationships among activities, inputs, and outputs … can show
cost, performers, or other pertinent information.
Copyright Avancier Ltd 2013
Avancier
OV-6a: Operational
Rules Model
One way to describe operational activity. It identifies
business rules that constrain operations.
Copyright Avancier Ltd 2013
Avancier
OV-6a: Operational
Rules Model
One way to describe operational activity. It identifies
business rules that constrain operations.
Copyright Avancier Ltd 2013
UML activity diagram notation
[Yes]
[No]
[Yes]
[No]
Drink coffee
Cup empty
Do crossword
Get up
Complete
Got to work
Avancier
Copyright Avancier Limited
OV-6b: State
Transition
Description
One way to describe operational activity (activity). It
identifies business process (activity) responses to
events (usually, very short activities).
Avancier
Event diagram
Sales Billing Delivery
Copyright Avancier Ltd 2013
► Draw here using the style of a UML sequence diagram
► Could drawn as a process flow diagram with swim lanes
Sale
p
r
o
c
e
s
s
p
r
o
c
e
s
s
p
r
o
c
e
s
s
Event Event Event
Event
p
r
o
c
e
s
s
Event
OV-6c: Event-Trace
Description
One way to describe operational activity. It traces
actions in a scenario or sequence of events.
Avancier Data and Information Viewpoint
► the data relationships and
alignment structures in the
architecture content
Copyright Avancier Ltd 2013
Operational
Services
Systems
Data and
Information
the data
relationships
and alignment
structures in the
architecture
content
Avancier
DIV-1:Conceptual
Data Model
The required high-level data concepts and their
relationships.
Copyright Avancier Ltd 2013
City Council
Conceptual/Business
Data diagram
Member
Of Public
Directorate
Worker
Building Claimant
Transaction
Enquiry
Ward
Business
* *
* * * *
* *
Avancier
DIV-2: Logical
Data Model
The documentation of the data requirements and
structural business process (activity) rules.
Copyright Avancier Ltd 2013
CACI Entity Relationship Diagram
► Optional
► Multiple
Woman
Child
May bear
Was born to
Coach Trip
Passenger
Carries
Takes
Choir Performance
Singer Performance
Needs
May belong
to
Avancier
Copyright Avancier Limited
DIV-2: Logical
Data Model
The documentation of the data requirements and
structural business process (activity) rules.
Avancier
► Entities
► Attributes &
► Relationships
► Usually defining the
content of one persistent
data store
Copyright Avancier Ltd 2013
OLTP
database CUSTOMER entity
Customer number Primary Key
Customer name
Customer address
ORDER entity
Customer number Foreign Key
Order number Primary Key
Order amount
Product type Foreign Key
PRODUCT entity
Product type Primary Key
Product description
Unit price
DIV-2: Logical
Data Model
The documentation of the data requirements and
structural business process (activity) rules.
Avancier
Copyright Avancier Ltd 2013
► This graphical
summary of a
logical data model
is drawn as an
entity relationship
diagram using the
IDEF data model
notation
DIV-2: Logical
Data Model
The documentation of the data requirements and
structural business process (activity) rules.
Avancier
Copyright Avancier Ltd 2013
► No example yet
DIV-3: Physical
Data Model
The physical implementation format of the Logical Data
Model entities, e.g., message formats, file structures,
physical schema. (In DoDAF V1.5, the SV-11.)
Avancier Service/System Views
Copyright Avancier Ltd 2013
Business
Operations
Information
Systems
Service
Performer
System
Technology
Service
Performer
System
Activity
Information & Materiel
Activity
Information & Materiel
Avancier
Copyright Avancier Ltd
Service/System Views
► Services Viewpoint? ■ the performers, activities,
services, and their
exchanges providing for, or
supporting, DoD functions
► Systems Viewpoint? ■ the legacy systems or
independent systems, their
composition,
interconnectivity, and context
providing for, or supporting,
DoD functions
Business
Operations
Information
Systems
Service
Performer
System
Technology
Service
Performer
System
Activity
Information & Materiel
Activity
Information & Materiel
Avancier
Copyright Avancier Limited
SvcV-1
Services
Context
Description
The identification
of services,
service items,
and their
interconnections.
SV-1
Systems
Interface
Description
The identification
of systems,
system items,
and their
interconnections.
Avancier
SvcV-1 Services Context
Description
The identification of services, service items,
and their interconnections.
SV-1 Systems Interface
Description
The identification of systems, system items,
and their interconnections.
Copyright Avancier Ltd 2013
Avancier
Copyright Avancier Ltd 2013
SvcV-1 Services Context
Description
The identification of services, service items,
and their interconnections.
SV-1 Systems Interface
Description
The identification of systems, system items,
and their interconnections.
Avancier
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
SvcV-1 Services Context
Description
The identification of services, service items,
and their interconnections.
SV-1 Systems Interface
Description
The identification of systems, system items,
and their interconnections.
Avancier
Copyright Avancier Ltd 2013
SvcV-1 Services Context
Description
The identification of services, service items,
and their interconnections.
SV-1 Systems Interface
Description
The identification of systems, system items,
and their interconnections.
Copyright © 2009-2012 The Open Group, All Rights Reserved.
ArchiMate is a registered trademark of The Open Group.
Avancier
SvcV-2 Services Resource Flow
Description
A description of Resource Flows
exchanged between services.
SV-2 Systems Resource Flow
Description
A description of Resource Flows
exchanged between systems.
Copyright Avancier Ltd 2013
Avancier
SvcV-2 Services Resource Flow
Description
A description of Resource Flows
exchanged between services.
SV-2 Systems Resource Flow
Description
A description of Resource Flows
exchanged between systems.
Copyright Avancier Ltd 2013
Avancier Related matrices
Copyright Avancier Ltd 2013
SvcV-3a Systems-
Services Matrix
The relationships among or between systems
and services in a given Architectural Description.
SvcV-3b Services-
Services Matrix
The relationships among services in a given
Architectural Description.
It can be designed to show relationships of
interest, (e.g., service-type interfaces, planned
vs. existing interfaces).
SV-3 Systems-
Systems Matrix
The relationships among systems in a given
Architectural Description.
It can be designed to show relationships of
interest, (e.g., system-type interfaces, planned
vs. existing interfaces).
Avancier
SvcV-4 Services
Functionality Description
The functions performed by services and the service
data flows among service functions (activities).
SV-4 Systems
Functionality Description
The functions (activities) performed by systems and the
system data flows among system functions (activities).
Copyright Avancier Ltd 2013
Avancier
SvcV-4 Services
Functionality Description
The functions performed by services and the service
data flows among service functions (activities).
SV-4 Systems
Functionality Description
The functions (activities) performed by systems and the
system data flows among system functions (activities).
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
Avancier
SvcV-4 Services
Functionality Description
The functions performed by services and the service
data flows among service functions (activities).
SV-4 Systems
Functionality Description
The functions (activities) performed by systems and the
system data flows among system functions (activities).
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
Avancier Related matrices
Copyright Avancier Ltd 2013
SvcV-5 Operational Activity to
Services Traceability Matrix
A mapping of services (activities) back to
operational activities (activities).
SV-5b Operational Activity to
Systems Traceability Matrix
A mapping of systems back to capabilities or
operational activities (activities).
SV-5a Operational Activity to
Systems Function Traceability Matrix
A mapping of system functions (activities)
back to operational activities (activities).
Avancier Related matrices
SvcV-5 Operational
Activity to Services
Traceability Matrix
A mapping of services
(activities) back to
operational activities
(activities).
SV-5b Operational
Activity to Systems
Traceability Matrix
A mapping of systems back
to capabilities or operational
activities (activities).
SV-5a Operational
Activity to Systems
Function Traceability
Matrix
A mapping of system
functions (activities) back to
operational activities
(activities).
Copyright Avancier Ltd 2013
Copyright © 2009-2012 The Open Group,
All Rights Reserved. ArchiMate is a
registered trademark of The Open Group.
DoDAF
Service?
Operational
Activity
Avancier Related matrices
SvcV-5 Operational Activity to
Services Traceability Matrix
A mapping of services (activities) back to
operational activities (activities).
SV-5b Operational Activity to
Systems Traceability Matrix
A mapping of systems back to capabilities or
operational activities (activities).
SV-5a Operational Activity to
Systems Function Traceability Matrix
A mapping of system functions (activities)
back to operational activities (activities).
Copyright Avancier Ltd 2013
Copyright © 2009-2012
The Open Group, All
Rights Reserved.
ArchiMate is a registered
trademark of The Open
Group.
DoDAF
Service?
Operational
Activity
Avancier
SvcV-6 Services
Resource Flow Matrix
details of service Resource Flow elements being
exchanged between services and the attributes of that
exchange.
SV-6 Systems
Resource Flow Matrix
details of system resource flow elements being exchanged
between systems and the attributes of that exchange.
Copyright Avancier Ltd 2013
1a
1b
1c
1d
2a
3a
3b
3c
3d
4b
4a
CRM
Sales
Stock
Billing
Data
Wrhs
Interface id Source App Destination App Data content Triggers event
1a CRM Sales Order request New sales order
1b Sales CRM Order confirmation Order created in backend Sales system
2a Sales Stock Requisition Subscribe/Publish timer
N2 model, or Node Connectivity diagram
Federal Enterprise Architecture Framework
Avancier
Copyright Avancier Ltd 2013
Details could include
► Port
► Protocol
► Time out
► Maximum connections
SvcV-6 Services
Resource Flow Matrix
details of service Resource Flow elements being
exchanged between services and the attributes of that
exchange.
SV-6 Systems
Resource Flow Matrix
details of system resource flow elements being exchanged
between systems and the attributes of that exchange.
Avancier Related matrices
SvcV-7 Services
Measures Matrix
The measures (metrics) of Services Model
elements for the appropriate time frame(s).
SV-7 Systems
Measures Matrix
The measures (metrics) of Systems Model
elements for the appropriate timeframe(s).
Copyright Avancier Ltd 2013
Avancier
Copyright Avancier Ltd 2013
SvcV-8 Services
Evolution Description
The planned incremental steps toward migrating a suite of
services to a more efficient suite or toward evolving current
services to a future implementation.
SV-8 Systems
Evolution Description
The planned incremental steps toward migrating a suite of
systems to a more efficient suite, or toward evolving a
current system to a future implementation.
Service/system evolution
Service/system Version Description Phase created Phase retired
A V. 1 Phase 1 Phase 2
V. 2 Phase 2
B V. 1 Phase 1
C V. 1 Phase 1 Phase 2
V. 2 Phase 2 Phase 3
V. 3 Phase 3
D V. 1 Phase 2 Phase
E V. 1 Phase 3
F V. 1 Phase 3 Phase 4
V. 2 Phase 4
G V. 1 Phase 4
H V. 1 Phase 4
Avancier
SvcV-9 Services
Technology & Skills
Forecast
The emerging technologies, software/hardware products, and
skills that are expected to be available in a given set of time
frames and that will affect future service development.
SV-9 Systems
Technology & Skills
Forecast
The emerging technologies, software/hardware products, and
skills that are expected to be available in a given set of time
frames and that will affect future system development.
Copyright Avancier Ltd 2013
Avancier
SvcV-10a
Services Rules
Model
One way to describe service functionality.
It identifies constraints that are imposed on systems functionality due to
some aspect of system design or implementation.
SV-10a
Systems Rules
Model
One way to describe system functionality.
It identifies constraints that are imposed on systems functionality due to
some aspect of system design or implementation.
Copyright Avancier Ltd 2013
UML activity diagram notation
[Yes]
[No]
[Yes]
[No]
Enter
Order data Valid
Enter Payment data
Open Data Entry
Form
Valid
Commit Data Entry
Avancier
Copyright Avancier Ltd 2013
► Boxes = states
► Lines = transitions between states
► Annotations = events that trigger
transitions
UML State Chart
First State
State State
State machine
Last State
Event
Asset Lifecycle
Specified
Scrapped
Scrap
Specify
Made
In stock
Retired
Make
Receive
Loan Retire
On loan
Renew
Return
SvcV-10b Services State
Transition Description
One way to describe service functionality.
It identifies responses of services to events.
SV-10b Systems State
Transition Description
One way to describe system functionality.
It identifies responses of systems to events.
Avancier
Copyright Avancier Ltd 2013
SvcV-10c Services Event-
Trace Description
One way to describe service functionality.
It identifies service-specific refinements of critical sequences
of events described in the Operational Viewpoint.
SV-10c Systems Event-
Trace Description
One way to describe system functionality.
It identifies system-specific refinements of critical sequences
Avancier Project Viewpoint
► Describes the
relationships between
operational and capability
requirements and the
various projects being
implemented;
► Details dependencies
between capability
management and the
Defense Acquisition
System Process
Copyright Avancier Ltd 2013
Operational
Services
Systems
Project
Describes the
relationships between
operational and
capability requirements
and the various projects
being implemented;
Details dependencies
between capability
management and the
Defense Acquisition
System Process
Avancier
PV-1: Project
Portfolio
Relationships
It describes the dependency relationships between the
organizations and projects and the organizational
structures needed to manage a portfolio of projects.
Copyright Avancier Ltd 2013
Avancier
PV-2: Project
Timelines
A timeline perspective on programs or projects, with
the key milestones and interdependencies.
Copyright Avancier Ltd 2013
IBM web site
Avancier
Copyright Avancier Ltd 2013
► No example yet
PV-3: Project to
Capability
Mapping
A mapping of programs and projects to capabilities to
show how the specific projects and program elements
help to achieve a capability.