Search Results for: 2

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

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

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

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