FRAMEWORKS - HOPEX DoDAF V2 > HOPEX Implementation of DoDAF V.2.02 > The DoDAF 2.02 Models
The DoDAF 2.02 Models
 
DoDAF 2.02 Viewpoint Models
DoDAF 2 Capability Viewpoint Models
DoDAF 2 Data and Information Viewpoint Models
DoDAF 2 Operational Viewpoint Models
DoDAF 2 Project Viewpoint Models
DoDAF 2 Services Viewpoint Models
DoDAF 2 Standards Viewpoint Models
DoDAF 2 Systems Viewpoint Models
Each of the eight viewpoints defined above groups models. In DoDAF 2 vocabulary, a model is either a graphical, textual or tabular deliverable that describes the characteristics that are relevant to the architecture product. Each model is associated to a short name created from the abbreviation of the viewpoint to which it belongs (AV, CV, DIV, OV, PV, SvcV, StdV, SV) and suffixed by a number.
DoDAF 2.02 Viewpoint Models
 
Code
Model Name
Comment
AV-1
 
Describes a Project's Visions, Goals, Objectives, Plans, Activities, Events, Conditions, Measures, Effects (Outcomes), and produced objects.
AV-2
An architectural data repository with definitions of all terms used throughout the architectural data and presentations.
DoDAF 2 Capability Viewpoint Models
 
Code
Model Name
Comment
CV-1
Addresses the enterprise concerns associated with the overall vision for transformational endeavors and thus defines the strategic context for a group of capabilities.
CV-2
Captures capability taxonomies. The model presents a hierarchy of capabilities. These capabilities may be presented in context of a timeline - i.e., it can show the required capabilities for current and future capabilities.
CV-3
The planned achievement of capability at different points in time or during specific periods of time. The CV-3 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
CV-4
The dependencies between planned capabilities and the definition of logical groupings of capabilities.
CV-5
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.
CV-6
A mapping between the capabilities required and the operational activities that those capabilities support.
DoDAF 2 Data and Information Viewpoint Models
 
Code
Model Name
Comment
DIV-1
The required high-level data concepts and their relationships.
DIV-2
The documentation of the data requirements and structural business process (activity) rules. In DoDAF V1.5, this was the OV-7.
DIV-3
The physical implementation format of the Logical Data Model entities, e.g., message formats, file structures, physical schema. In DoDAF V1.5, this was the SV-11.
DoDAF 2 Operational Viewpoint Models
 
Code
Model Name
Comment
OV-1
The high-level graphical/textual description of the operational concept.
OV-2
A description of the Resource Flows exchanged between operational activities.
OV-3
A description of the resources exchanged and the relevant attributes of the exchanges.
OV-4
The organizational context, role or other relationships among organizations.
OV-5a
The capabilities and activities (operational activities) organized in a hierarchal structure.
OV-5b
The context of capabilities and activities (operational activities) and their relationships among activities, inputs, and outputs; Additional data can show cost, performers or other pertinent information.
OV-6a
One of three models used to describe activity (operational activity). It identifies business rules that constrain operations.
OV-6b
One of three models used to describe operational activity (activity). It identifies business process (activity) responses to events (usually, very short activities).
OV-6c
One of three models used to describe activity (operational activity). It traces actions in a scenario or sequence of events.
DoDAF 2 Project Viewpoint Models
 
Code
Model Name
Comment
PV-1
It describes the dependency relationships between the organizations and projects and the organizational structures needed to manage a portfolio of projects.
PV-2
A timeline perspective on programs or projects, with the key milestones and interdependencies.
PV-3
A mapping of programs and projects to capabilities to show how the specific projects and program elements help to achieve a capability.
DoDAF 2 Services Viewpoint Models
 
Code
Model Name
Comment
SvcV-1
The identification of services, service items, and their interconnections.
SvcV-2
A description of Resource Flows exchanged between services.
SvcV-3a
The relationships among or between systems and services in a given Architectural Description.
SvcV-3b
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).
SvcV-4
The functions performed by services and the service data flows among service functions (activities).
SvcV-5
A mapping of services (activities) back to operational activities (activities).
SvcV-6
It provides details of service Resource Flow elements being exchanged between services and the attributes of that exchange.
SvcV-7
The measures (metrics) of Services Model elements for the appropriate timeframe(s)
SvcV-8
The planned incremental steps toward migrating a suite of services to a more efficient suite or toward evolving current services to a future implementation.
SvcV-9
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.
SvcV-10a
One of three models used to describe service functionality. It identifies constraints that are imposed on systems functionality due to some aspect of system design or implementation.
SvcV-10b
One of three models used to describe service functionality. It identifies responses of services to events.
SvcV-10c
One of three models used to describe service functionality. It identifies service-specific refinements of critical sequences of events described in the Operational Viewpoint.
DoDAF 2 Standards Viewpoint Models
 
Code
Model Name
Comment
StdV-1
The listing of standards that apply to solution elements.
StdV-2
The description of emerging standards and potential impact on current solution elements, within a set of time frames.
DoDAF 2 Systems Viewpoint Models
 
Code
Model Name
Comment
SV-1
The identification of systems, system items, and their interconnections.
SV-2
A description of Resource Flows exchanged between systems.
SV-3
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).
SV-4
The functions (activities) performed by systems and the system data flows among system functions (activities).
SV-5a
A mapping of system functions (activities) back to operational activities (activities).
SV-5b
A mapping of systems back to capabilities or operational activities (activities).
SV-6
Provides details of system resource flow elements being exchanged between systems and the attributes of that exchange.
SV-7
The measures (metrics) of Systems Model elements for the appropriate timeframe(s).
SV-8
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.
SV-9
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.
SV-10a
One of three models used to describe system functionality. It identifies constraints that are imposed on systems functionality due to some aspect of system design or implementation.
SV-10b
One of three models used to describe system functionality. It identifies responses of systems to events.
SV-10c
One of three models used to describe system functionality. It identifies system-specific refinements of critical sequences of events described in the Operational Viewpoint.