DoDAF Architecting

DIV-2 Logical Data Model

FavoriteLoadingAdd to favorites


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.

DoDAF Architecture Framework Version 2.02 – Page 135

Data definitions in other models include:

  • Data described in a DIV-2 may be related to Information in an OV-1 “High Level Operational Concept Graphic” or and Activity Resource (where the Resource is Data) flow object in an OV-5b “Operational Activity Mode”. This relation may be a simple subtype, where the Data is a proceduralized (structured) way of describing something. Recall that Information describes something. Alternatively, the relation may be complex using Information and Data whole-part (and overlap) relationships.
  • The DIV-2 information entities and elements can be constrained and validated by the capture of business requirements in the OV-6a “Operational Rules Model”. The information entities and elements modeled in the DIV-2 also capture the information content of messages that connect life-lines in an OV-6c “Event-Trace Description”.
  • The DIV-2 may capture elements required due to Standards in the StdV-1 Standards Profile or StdV-2 Standards Forecast.

The DIV-2 is a generalized formal structure in computer science. It directly reflects the paradigm or theory oriented mapping from the DIV-1 “Conceptual Data Model” to the DIV-2.

Possible Construction Methods:
DoDAF does not endorse a specific data modeling methodology. The appropriate way to develop a logical data model depends on the technology chosen as the main design solution (e.g., relational theory or object-orientation). For relational theory, a logical data model seems best described using an entity relationship diagramming technique. For Object-Oriented, a logical data model seems best described using Class and/or Object diagrams.

In either case, attention should be given to quality characteristics for the data model.


  • The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
  • DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.

AcqLinks and References:

Become an AcqNotes Member to View Page Discussions