Linked.Archi

DoDAF 2.02 Architecture Viewpoints (DoDAF-described Models)

Viewpoint Definitions

https://meta.linked.archi/dodaf/viewpoints#

v2.02 draft dodafvp: Kalin Maldzhanski Linked.Archi Modified: 2026-05-03 License

DoDAF 2.02 viewpoints modeled as arch:Viewpoint individuals. Each viewpoint corresponds to a DoDAF-described Model (AV, CV, DIV, OV, PV, SvcV, StdV, SV). DoDAF 2.0 uses "Fit-for-Purpose" presentation — these viewpoints define the data content, not rigid visual templates.

Contents

Other

AV-1: Overview and Summary Information

Describes a project's visions, goals, objectives, plans, activities, events, conditions, measures, effects, and produced objects.
Purpose: Informing
View type: Diagram, Catalog

AV-2: Integrated Dictionary

An architectural data repository with definitions of all terms used throughout the architectural data and presentations.
Purpose: Governing
View type: Catalog

CV-1: Vision

The overall vision for transformational endeavors, providing a strategic context for the capabilities described and a high-level scope.
Purpose: Informing
View type: Diagram
Included concepts:
Capability DesiredEffect

CV-2: Capability Taxonomy

A hierarchy of capabilities specifying all capabilities referenced throughout one or more architectural descriptions.
Purpose: Informing
View type: Diagram
Included concepts:
Capability

CV-3: Capability Phasing

The planned achievement of capability at different points in time or during specific periods of time.
Purpose: Deciding
View type: Diagram
Included concepts:
Capability CapabilityIncrement

CV-4: Capability Dependencies

The dependencies between planned capabilities and the definition of logical groupings of capabilities.
Purpose: Deciding
View type: Diagram, Matrix
Included concepts:
Capability

CV-5: Capability to Organizational Development Mapping

The planned capability deployment and interconnection for a particular capability phase, showing the planned solution in terms of performers and locations.
Purpose: Deciding
View type: Matrix
Included concepts:
Capability Organization Location

CV-6: Capability to Operational Activities Mapping

A mapping between the capabilities required and the operational activities that those capabilities support.
Purpose: Deciding
View type: Matrix
Included concepts:
Capability OperationalActivity

CV-7: Capability to Services Mapping

A mapping between the capabilities and the services that these capabilities enable.
Purpose: Deciding
View type: Matrix
Included concepts:
Capability Service

DIV-1: Conceptual Data Model

The required high-level data concepts and their relationships. Intended for non-technical stakeholders.
Purpose: Informing
View type: Diagram
Included concepts:
ConceptualDataEntity

DIV-2: Logical Data Model

The documentation of the data requirements and structural business process rules. Bridges the conceptual and physical levels.
Purpose: Designing
View type: Diagram
Included concepts:
LogicalDataEntity

DIV-3: Physical Data Model

The physical implementation format of the logical data model entities — message formats, file structures, physical schema.
Purpose: Designing
View type: Diagram
Included concepts:
PhysicalDataEntity

OV-1: High-Level Operational Concept Graphic

The high-level graphical/textual description of the operational concept.
Purpose: Informing
View type: Diagram
Included concepts:
OperationalNode Performer Location

OV-2: Operational Resource Flow Description

A description of the resource flows exchanged between operational activities.
Purpose: Designing
View type: Diagram
Included concepts:
OperationalNode ResourceFlow

OV-3: Operational Resource Flow Matrix

A description of the resources exchanged and the relevant attributes of the exchanges.
Purpose: Designing
View type: Matrix
Included concepts:
OperationalNode ResourceFlow

OV-4: Organizational Relationships Chart

The organizational context, role, or other relationships among organizations.
Purpose: Informing
View type: Diagram
Included concepts:
Organization Performer

OV-5a: Operational Activity Decomposition Tree

The capabilities and activities organized in a hierarchical structure.
Purpose: Designing
View type: Diagram
Included concepts:
OperationalActivity

OV-5b: Operational Activity Model

The context of capabilities and activities and their relationships among activities, inputs, and outputs.
Purpose: Designing
View type: Diagram
Included concepts:
OperationalActivity ResourceFlow Performer

OV-6a: Operational Rules Model

Identifies business rules that constrain operations.
Purpose: Governing
View type: Catalog
Included concepts:
OperationalRule OperationalActivity

OV-6b: State Transition Description

Identifies business process responses to events.
Purpose: Designing
View type: Diagram
Included concepts:
OperationalActivity Condition

OV-6c: Event-Trace Description

Traces actions in a scenario or sequence of events.
Purpose: Designing
View type: Diagram
Included concepts:
OperationalActivity OperationalNode

PV-1: Project Portfolio Relationships

Describes the dependency relationships between organizations and projects and the organizational structures needed to manage a portfolio of projects.
Purpose: Informing
View type: Diagram
Included concepts:
Project Organization

PV-2: Project Timelines

A timeline perspective on programs or projects, with key milestones and interdependencies.
Purpose: Deciding
View type: Diagram
Included concepts:
Project Milestone

PV-3: Project to Capability Mapping

A mapping of programs and projects to capabilities to show how specific projects help achieve a capability.
Purpose: Deciding
View type: Matrix
Included concepts:
Project Capability

StdV-1: Standards Profile

The listing of standards that apply to solution elements.
Purpose: Governing
View type: Catalog
Included concepts:
Standard

StdV-2: Standards Forecast

The description of emerging standards and potential impact on current solution elements, within a set of time frames.
Purpose: Deciding
View type: Catalog
Included concepts:
Standard StandardsForecast