Acq Notes

The OV-5a “Operational Activity Model” and the OV-5b describe the operations that are normally conducted in the course of achieving a mission or a business goal. It describes operational activities (or tasks); Input/Output flows between activities, and to/from activities that are outside the scope of the Architectural Description. Guide: DoDAF Architecture Framework Version 2.02 – […]

The OV-3 “Operational Resource Flow Matrix” addresses operational Resource Flows exchanged between Operational Activities and locations. Resource Flows provide further detail of the interoperability requirements associated with the operational capability of interest. The focus is on Resource Flows that cross the capability boundary. The intended usage of the OV-3 includes: Definition of interoperability requirements Guide: DoDAF

The OV-4 “Organizational Relationship Chart” shows organizational structures and interactions and may be civil or military. The OV-4 exists in two (2) forms: Role-based (e.g., a typical brigade command structure) and Actual (e.g., an organization chart for a department or agency). Guide: DoDAF Architecture Framework Version 2.02 – Page 150  A role-based OV-4 shows the possible

The OV-2 “Operational Resource Flow Description” applies the context of the operational capability to a community of anticipated users. The primary purpose of the OV-2 is to define capability requirements within an operational context. The OV-2 may also be used to express a capability boundary. Guide: DoDAF Architecture Framework Version 2.02 – Page 144 New

The OV-1 “High Level Operational Concept Graphic” describes a mission, class of mission, or scenario. It shows the main operational concepts and interesting or unique aspects of operations. It describes the interactions between the subject architecture and its environment, and between the architecture and external systems. The OV-1 is the pictorial representation of the written

A Functional Architecture is an architectural model that identifies system functions and their interactions. It defines how the functions will operate together to perform the system mission(s) and is a framework for organizing information, processes, or different solution modules into an enterprise system. A functional architecture depicts a system that emphasizes its functions and how they

An Enterprise Architecture (EA) describes the “current architecture” and “target architecture,” and provides a strategy that will enable an agency to transition from its current state to its target environment. The Office of Management and Budget defines enterprise architecture as the explicit description and documentation of the current and desired relationships among business and management

The DoDAF Meta Model (DM2) defines architectural data elements and enables the integration and federation of Architectural Descriptions. It establishes a basis for semantic (i.e., understanding) consistency within and across Architectural Descriptions. Website: DoDAF Meta Model (DM2) The purposes of the DM2 are: Establish and define the constrained vocabulary for description and discourse about DoDAF

The DIV-2 Logic Data Model allows analysis of an architecture’s data definition aspect, without consideration of implementation specific or product specific issues.  Another purpose is to provide a common dictionary of data definitions to consistently express models wherever logical-level data elements are included in the descriptions. Guide: DoDAF Architecture Framework Version 2.02 – Page 135

The DIV-3 defines the structure of the various kinds of system or service data that are utilized by the systems or services in the Architectural Description. The Physical Schema is one of the models closest to actual system design in DoDAF. It’s used to describe how the information represented in the DIV-2 “Logical Data Model”

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

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

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