| Name | Description |
|---|
DODAF 2 - OV-5b - Operational Activity Model | 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. |
|
DODAF2 - All Viewpoint | The AV DoDAF-described Models provide information pertinent to the entire Architectural Description rather than representing a distinct viewpoint. AV DoDAF-described Models provide an overview of the architecturectural effort including such things as the scope, context, rules, constraints, assumptions, and the derived vocabulary that pertains to the Architectural Description. It captures the intent of the Architectural Description to help ensure its continuity in the face of leadership, organizational, and other changes that can occur over a long development effort. |
|
DODAF2 - Capability Viewpoint | The Capability Viewpoint and the DoDAF-described Models within the viewpoint are introduced into DoDAF V2.0 to address the concerns of Capability Portfolio Managers. In particular, the Capability Models describe capability taxonomy and capability evolution. |
|
DODAF2 - CV-1: Capability Vision | Addresses the enterprise concerns associated with the overall vision for transformational endeavors and thus defines the strategic context for a group of capabilities. |
|
DODAF2 - CV-2 : Capability Taxonomy | 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. |
|
DODAF2 - CV-4: Capability Dependencies | The dependencies between planned capabilities and the definition of logical groupings of capabilities. |
|
DODAF2 - CV-6: Capability to Operational Activities Mapping | A mapping between the capabilities required and the operational activities that those capabilities support. |
|
DODAF2 - Data and Information Viewpoint | DoDAF-described Models within the Data and Information Viewpoint provide 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. |
|
DODAF2 - DIV-1 - Conceptual Data Model | The required high-level data concepts and their relationships. |
|
DODAF2 - DV-2 - Logical Data Model | The documentation of the data requirements and structural business process (activity) rules. In DoDAF V1.5, this was the OV-7. |
|
DODAF2 - DV-3 - Physical Data Model | 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. |
|
DODAF2 - Operational Viewpoint | DoDAF-described Models in the Operational Viewpoint describe the tasks and activities, operational elements, and resource flow exchanges required to conduct operations. A pure operational model is materiel independent. However, operations and their relationships may be influenced by new technologies, such as collaboration technology, where process improvements are in practice before policy can reflect the new procedures. There may be some cases, as well, in which it is necessary to document the way activities are performed, given the restrictions of current systems, to examine ways in which new systems could facilitate streamlining the activities. In such cases, operational models may have materiel constraints and requirements that need to be addressed. For this reason, it may be necessary to include some high-level system architectural data to augment information onto the operational models. |
|
DODAF2 - OV-1 - High-Level Operational Concept Graphic | The high-level graphical/textual description of the operational concept. |
|
DODAF2 - OV-2 - Operational Resource Flow Description | The OV-2 DoDAF-described Model 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. |
|
DODAF2 - OV-3 - Operational Resource Flow Matrix | A description of the resources exchanged and the relevant attributes of the exchanges. |
|
DODAF2 - OV-4 - Organizational Relationships Chart | The organizational context, role or other relationships among organizations. |
|
DODAF2 - OV-5a - Operational Activity Decomposition Tree | The capabilities and activities (operational activities) organized in a hierarchal structure. |
|
DODAF2 - OV-6a: Operational Rules Model | One of three models used to describe activity (operational activity). It identifies business rules that constrain operations. |
|
DODAF2 - Project Viewpoint | The DoDAF-described Models within the Project Viewpoint describe how programs, projects, portfolios, or initiatives deliver capabilities, the organizations contributing to them, and dependencies between them. Previous versions of DoDAF took a traditional model of architecture in which descriptions of programs and projects were considered outside scope. To compensate for this, various DoDAF models represented the evolution of systems, technologies and standards (e.g., Systems and Services Evolution Description, Systems Technology Forecast, and Technical Standards Forecast). |
|
DODAF2 - PV-1 - Project Portfolio Relationships | It describes the dependency relationships between the organizations and projects and the organizational structures needed to manage a portfolio of projects. |
|
DODAF2 - PV-2 - Project Timelines | A timeline perspective on programs or projects, with the key milestones and interdependencies. |
|
DODAF2 - PV-3 - Project to Capability Mapping | A mapping of programs and projects to capabilities to show how the specific projects and program elements help to achieve a capability. |
|
DODAF2 - SV-1 Systems Interface Description | The identification of systems, system items, and their interconnections. |
|
DODAF2 - SV-2 Systems Resource Flow Description | A description of Resource Flows exchanged between systems. |
|
DODAF2 - SV-3 Systems-Systems Matrix | 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). |
|
DODAF2 - SV-4 Systems Functionality Description | The functions (activities) performed by systems and the system data flows among system functions (activities). |
|
DODAF2 - SV-5a Operational Activity to Systems Function Traceability Matrix | A mapping of system functions (activities) back to operational activities (activities). |
|
DODAF2 - SV-5b Operational Activity to Systems Traceability Matrix | A mapping of systems back to capabilities or operational activities (activities). |
|
DODAF2 - System Viewpoint | he DoDAF-described Models within the Systems Viewpoint 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 DoDAF-described Models are available for support of legacy systems. |
|
SysFEAT- DoDAF 2 | The Department of Defense Architecture Framework (DoDAF), Version 2.0 is the overarching, comprehensive framework and conceptual model enabling the development of architectures to facilitate the ability of Department of Defense (DoD) managers at all levels to make key decisions more effectively through organized information sharing across the Department, Joint Capability Areas (JCAs), Mission, Component, and Program boundaries. |
Systemic Framework for Enterprise Architecture & Transformation
Dictionary of SysFEAT concepts 
Document
NeedLine Requirement