DoDAF Architecting

The DIV-1 Conceptual Data Model addresses the information concepts at a high-level on an operational architecture.  The DIV-1 is used to document the business information requirements and structural business process rules of the architecture. It describes the information that is associated with the information of the architecture. Included are information items, their attributes or characteristics, […]

The CV-7 “Capability to Services Mapping” describes the mapping between the capabilities required and the services that enable those capabilities. It provides a bridge between capability analyzed using Capability Viewpoints (CV) and services analyzed using Service Viewpoint (SvcV).  Specifically, it identifies how services can be performed using various available capability elements. It is similar in

The CV-5 “Capability to Organizational Development Mapping” addresses the fulfillment of capability requirements. It shows the planned capability deployment and interconnection for a particular phase and should provide a more detailed dependency analysis than is possible using the CV-3 “Capability Phasing” model. It’s used to support the capability management process and, in particular, assist the

The CV-4 “Capability Dependencies” describes the dependencies between planned capabilities and also defines logical groupings of capabilities.   It’s intended to provide a means of analyzing the dependencies between capabilities. The groupings of capabilities are logical, and the purpose of the groupings is to guide enterprise management. In particular, the dependencies and groupings may suggest

The CV-6 “Capability to Operational Activities Mapping” describes the mapping between the capabilities required and the activities that enable those capabilities. It provides a bridge between capability analyzed using Capability Viewpoints (CV) and operational activities analyzed using Operational Viewoints (OV). Specifically, it identifies how operational activities can be performed using various available capability elements. It

The CV-1 Vision addresses the enterprise concerns associated with the overall vision for transformational endeavors and thus defines the strategic context for a group of capabilities. The purpose of a CV-1 is to provide a strategic context for the capabilities described in the Architectural Description. It also provides a high-level scope for the Architectural Description

The CV-2 “Capability Taxonomy” 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. The CV-2 specifies all the capabilities that are referenced throughout one or more architectures. In addition, it can be used as a source

The CV-3 “Capability Phasing” addresses the planned achievement of capability at different points in time or during specific periods of time. The CV-3 supports the capability audit processes and similar processes used across the different COIs by providing a method to identify gaps or duplication in capability provision. The CV-3 indicates capability increments, which should

Systems Viewpoint (SV) describes systems and interconnections providing for, or supporting, DoD functions. DoD functions include both warfighting and business functions. The Systems Models associate systems resources to the operational and capability requirements. These systems resources support the operational activities and facilitate the exchange of information. The Systems Models are available for support of legacy

The AV-1 provides executive-level summary and overview information in a consistent form that allows quick reference and comparison between Architectural Descriptions. The written content of the AV-1 describes the concepts contained in the pictorial representation of the Operational View (OV)-1. [1] Guide: DoDAF Architecture Framework Version 2.02 – Page 110 The AV-1 frames the context

The AV-2 presents all the metadata used in an architecture and presents all the data as a hierarchy, provides a text definition for each one and references the source of the. It also shows elements from the DoDAF Meta-model that have been described in the Architectural Description and new elements that have been introduced by

The Data and Information Viewpoint (DIV) provides a means of portraying the operational and business information requirements and rules that are managed within and used as constraints on the organizations business activities. The appropriate level or levels of abstraction for a given architecture are dependent on the use and the intended users of the architecture.

The Operational Viewpoint (OV) describes the tasks and activities, operational elements, and resource flow exchanges required to conduct operations. It may be used to describe a requirement for a “To-Be” architecture in logical terms or as a simplified description of the key behavioral and information aspects of an “As-Is” architecture. The OV Models re-use the

The Capability Viewpoint (CV) describes the taxonomy and capability evolution. It’s provides visualizations of the evolving capabilities so that Portfolio Managers can synchronize the introduction of capability increments across a portfolio of projects. The Capability Models included within DoDAF are based on the program and capability information used by Portfolio Managers to capture the increasingly

The DoDAF Architecture Design Process has 6-steps.  These steps provide guidance and guiding rules to the architect and Architectural Description development team.  The process is data-centric rather than product-centric and ensures synchronization between views while ensuring that all essential data relationships are captured to support a wide variety of analysis tasks. The views created as

Architecting is a tool used by Program Managers (PM) and Systems Engineers in developing a system to help designers meet all stated function and physical requirements, collaborate across organizations, and provides valuable information for decision-makers. There are a number of types of Architectures that are used in system development: Functional Architecture: model that identifies system