View DNDAF:OV-7 Logical Data Model Subview

dnd.gif

Title

OV-7 Logical Data Model Subview

Version & Date

1.6 See DNDAF Release History

Introduction

The OV-7 subview is part of the DNDAF Operational View.

The Operational View-7 (OV-7): Logical Data Model is used to document the data requirements and business process rules of the architecture project. It describes the data and information that is associated with the architecture project. Included are data entities, relationships and attributes.

Purpose

The purpose is to identify, describe and give visibility to the data components that are pertinent to the architecture project. The OV-7 defines the data structures and entity definitions of the architecture project, which will assist the design of the physical data schema by the sub-view physical schema (SV-11). These are key elements in supporting interoperability between architectures. The OV-7 can impose standard data elements and definitions since these may be used by other organizations to determine system data compatibility. The existing standard data elements and definitions in authoritative sources internally and externally to DND/CF can be used instead of creating a new one.

Background

The OV-7 complements the information in other sub-views, such as operational node (OV-2), information exchange requirement (OV-3), functional model (OV-5a) and interrelated activities. There may not be one- to-one mapping of these information items in other sub-views to the information/data elements that are described in OV-7. However, there is considerable mutual influence between these sub-views, and they should be developed together. The OV-7 defines the high-level interrelationships and rules, while the operational rules model (OV-6a) focuses on the internal operational rules.

The OV-7 provides a list of applicable metadata for the architecture project and makes visible the structure of this data.

Description

Definition

The Logical Data Model (OV-7) describes the structure system data types and the structural business process rules of architecture project that govern the system data. It provides the metadata of the data types, their attributes or characteristics, and their interrelationships pertinent to the architecture project.

Detailed Description

The OV-7 defines the architecture project data types (or entities) and the relationships among the system data types. For example, if the domain is missile defence, some possible system data types may be trajectory and target with a relationship that associates a target with a certain trajectory.

Subview DADM Elements

The DADM entities and attributes provided below are the elements that this sub-view is responsible for creating:

 

 

Presentation

Any graphical form where data concetps and relationships can be represented:

  • Entity Relationship Diagram
  • UML Class Diagram

Examples

See:

  • p76 Figure 3.14.1 in DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views

Prerequisites

The OV-5a and IV-1 are the prerequisites for this sub-view:

  • OV-5a. OV-5a is required in order to identify the scope of operational activities for data modeling.
  • IV-1. IV-1 is required in order to identify, describe and give visibility to the data components that are pertinent to the architecture project.

 

See DNDAF Subview Dependencies

 

Comments

 

Other Frameworks

See also:

References


Category:Framework -> Specification
Category:Framework -> Subview

Categories:

 

© 2010 Eclectica Systems Ltd.