Search Results for: 2

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-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 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