View DNDAF:SV-6 Systems Data Exchange Matrix Subview

dnd.gif

Title

SV-6 Systems Data Exchange Matrix Subview

Version & Date

1.6 See DNDAF Release History

Introduction

The SV-6 subview is part of the DNDAF System View.

The System View-6 (SV-6): Systems Data Exchange Matrix describes, in tabular format, data exchanges between systems within a node and across nodes. Systems data exchanges express the relationships across the three basic data elements of an SV (system functions, systems, and data flow).

Purpose

The Systems Data Exchange Matrix specifies the characteristics and requirements of the data exchanged between systems. This sub-view describes automated information and data exchanges that will be implemented in systems. SV-6 focuses on the specific aspects of the data flow. Certain aspects of the data exchange can be crucial to the operational mission and should be tracked as attributes in the Systems Data Exchange Matrix.

Note: Non-automated information exchanges, such as verbal orders, are captured in the OV sub-views.

Background

The traceability of data exchanges between systems that participate in an operational information exchange is not represented in a comprehensive logical way. Hence SV-6 representation becomes necessary. This sub-view is related to, and grows out of, the Operational Information Exchange Matrix (OV-3). Each of the system data exchanges is derived from the operational information exchange that is part of the architecture project (there may be multiple system data exchanges that collectively constitute a given operational information exchange). Using this traceability from system-exchange to operational-exchange, one can further trace a system data exchange all the way back to the notional needline it helps satisfy.

Description

Definition

The Systems Data Exchange Matrix is the tabular representation of data exchanges properties (attributes) between systems at the component level.

Detailed Description

The Systems Data Exchange Matrix describes data exchanges between systems in tabular format. The focus of the Systems Data Exchange Matrix is on how the data exchanges are implemented in system- specific details covering such characteristics as specific protocols and data standard or media format. The data exchanges documented in this matrix should trace to the information exchanges detailed in the Information Exchange Matrix (OV-3), and are carried by the system interfaces of the Systems Interface Description (SV-1). These interfaces, in turn, correlate to the OV-1 and OV-2 needlines. The performance and security attributes for the data exchange are also described in the matrix. These aspects of exchanges are critical to understanding the potential for overhead and constraints introduced by the physical aspects of the implementation.

The Systems Data Exchange Matrix relates to, and grows out of, the OV-3 and SV-4. That is, the portion(s) of each information exchange is associated with the systems interface that carries the corresponding system data. The operational characteristics for that information exchange are replaced with the corresponding system data characteristics. Similarly, performance attributes for the operational information exchanges are replaced by the actual system performance attributes. Automation may introduce characteristics that are not intrinsic to the operational information exchange. For example, automation may introduce an aerospace component (e.g., a satellite link) into the physical environment of an information exchange between two land-based operational nodes.

On the Systems Data Exchange Matrix, each operational needline is decomposed into the interfaces that implement (or will implement) the automated portions of the needline. (The interfaces are shown on the SV-1 Systems Interface Description.) Further, each Information Exchange (IE) from the OV-3 that is automated is assigned to the appropriate SV-1 interface(s) and is decomposed into the Systems Data Exchanges that constitute the automated portion of the data exchange. Some Systems Data Exchanges may represent automated system “housekeeping” or administrative data exchanges and will not map to any operational information exchanges. That is, these Systems Data Exchanges are an artefact of the automation. These Systems Data Exchanges are related to the interfaces they are carried by and are not related to any needlines.

Subview DADM Elements

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

 

 

Presentation

  • table/matrix

From section 2.21, volume 4:

The System View-6 (SV-6): Systems Data Exchange Matrix describes, in tabular format, data exchanges between systems within a node and across nodes. Systems data exchanges express the relationships across the three basic data elements of an SV (system functions, systems, and data flow).
..

This sub-view is represented as a matrix of data exchanges in tabular format. These exchanges comprise several related DADM predefined attributes and others that might be specific to the project architecture. These attributes are organized in groups that belong to the same information topic or area and are assembled in six two-dimensional tables with cross-reference identifiers.

Examples

See:

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

Prerequisites

The SV-1 and SV-4 are the prerequisites for this sub-view:

  • SV-1. Defines the systems under consideration. It sets the scope for this sub-view
  • SV-4. Systems Data Exchange Matrix is validated through Systems Functionality Description.

 

See DNDAF Subview Dependencies

 

Comments

 

Other Frameworks

See also:

References


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

Categories:

 

© 2010 Eclectica Systems Ltd.