System Views (SV) [Physical, Specification or Solution Views]

SV-6 Systems Data Exchange Matrix v1.2

The Systems Data Exchange Matrix specifies the characteristics of the system data exchanged between systems. The focus is on data crossing the system boundary.

Background:

SV-6 focuses on the specific aspects of the system data flow and the system data content in a tabular format.

Usage:

Data objects:

The data in an SV-6 can include:



Relationships Between Key Data Objects (Simplified from M3)

Note: The term “System Data Exchange” does not refer to one M3 element. A data exchange as described in SV-6 is a combination of a System Port Connector and the Data Elements that flow across it. Any properties shown in an SV-6 table will be properties of the System Port Connector.

Representation:

Detailed Product Description:

The Systems Data Exchange Matrix specifies the characteristics of data exchanges between systems. SV-6 is the physical equivalent of the logical OV-3 table and provides detailed information on the system connections which implement the information exchanges specified in OV-3. Non-automated information exchanges, such as verbal orders, are captured in the SV-1 and SV-3 Products only.

System data exchanges express the relationship across the three basic Architecture data elements of an SV (systems, system functions, and system data flows) and focus on the specific aspects of the system data flow and the system data content. These aspects of the system data exchange can be crucial to the operational mission and are critical to understanding the potential for overhead and constraints introduced by the physical aspects of the implementation such as security policy and communications limitations.

SV-6 describes, in tabular format, system data exchanged between systems. The focus of SV-6 is on how the system data exchange is effected, in system-specific details covering periodicity, timeliness, throughput, size, information assurance, and security characteristics of the exchange. In addition, the system data elements, their format and media type, accuracy, units of measurement, and system data standard are also described in the matrix.


Example SV-6 Based on GPRS SV-2b Example

MODAF does not currently prescribe the column headings in an SV-6 Matrix. It is recommended that the identifiers of the information exchanges (OV-3) that are implemented by the System Data Exchanges are included in the table. Similarly, it is recommended that all Data Elements carried by the data exchanges are also shown.

Modelling discipline is needed to ensure that the architecture models are coherent. Each system data exchange listed in the SV-6 table should be traceable to at least one information exchanged listed in the corresponding OV-3 table and these in turn trace to operational needlines (OV-2). The Needline corresponding to the system connection that the system data exchange supports should be the same as the Needline that is the ‘parent’ of the operational information exchange that the system data exchange traces to.

It should be noted that each data element exchanged may be related to the system function (from SV-4) that produces or consumes it. However, there need not be a one-to-one correlation between data elements listed in the SV-6 matrix and the data flows (inputs and outputs) that are produced or consumed in a related SV-4.

Data flows between system functions performed by the same systems may not be shown in the SV-6 matrix, as there will be no corresponding System Port Connection – i.e. SV-6 is about showing flows across system boundaries.

The tabular nature of SV-6 View Products provides significant potential for sorting, arranging and viewing the interface characteristics in multiple ways to meet specific user and developer needs.

The System Performance Parameters Matrix (SV-7) product builds on the SV-6 and should be developed at the same time.

Page version 1.2, dated 1st July 2008

Top of Page