View DNDAF:CV-2 Integrated Data Dictionary Subview

dnd.gif

Title

CV-2 Integrated Data Dictionary Subview

Version & Date

1.6 See DNDAF Release History

Introduction

The CV-2 subview is part of the DNDAF Common View.

CV-2 provides the means to define terms and acronyms used in the architecture.

Purpose

CV-2 provides a means for terms and information to be visible from within sub-views and the architecture. It gathers these terms and definitions based upon context, and traces them to authoritative sources.

Background

CV-2 allows architects to make relevant information visible and accessible. The information is traced to authoritative sources and more readily available, which enables the timeliness and reuse of the information.

Description

Definition

CV-2 captures key information, such as acronyms, terms, definitions and the source of the definition from a given architectural sub-view.

Detailed Description

The need for standard terms derives from lessons learned in early US Department of Defense Architecture Framework, (DoDAF) development whereby multiple operational architectures could not be integrated as different terminology and definitions were used.

Subview DADM Elements

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

 

Note that the SecV-2 and CV-2 are defined as being responsible for the creation of the Data Attribute entity.

Presentation

  • Tabular

 

 

Examples

See:

  • p24 Figure 3.3.1 and 3.3.2 in DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views
  • Figure 2.4.1 in DND/CF Architecture Framework (DNDAF) Volume 4 - User Guide

Prerequisites

The CV-2 is produced when any sub-view is produced.

See DNDAF Subview Dependencies

It is therefore the second subview produced when modelling using DNDAF (the CV-1 being the first which triggers the creation of the CV-2).

Comments

Potentially confusing use of ‘architecture’ since in most cases here it probably means ‘architecture model’ (or description) rather than the real-life architecture that is being represented and analysed. The confusion occurs because the CV-2 will deal with terminology used both in the model (architecture description) and may include terminology used in the real-world architecture itself.

Other Frameworks

See also:

References


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

Categories:

 

© 2010 Eclectica Systems Ltd.