View MODAF:SV-6 Systems Data Exchange Matrix View

mod_logo_60.jpg

Overview

The SV-6 Systems Data Exchange Matrix View is part of the MODAF System Viewpoint and one of the 47 MODAF views*.

Version & Date

Version 1.2.004.

* =  changed at 1.2.004

+ =  new at 1.2.004

The change history is derived from the definition of each MODAF view within the The MODAF System Viewpoint viewpoint defining document from www.mod.uk/modaf.

See MODAF Release History.

Purpose*

From The MODAF System Viewpoint (SV) p27:

The SV-6 specifies the characteristics of the data exchanged between systems.

Subject to Crown Copyright

Background

From The MODAF System Viewpoint (SV) p27:

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

Subject to Crown Copyright

Description

The SV-6 specifies the characteristics of data exchanges between systems. SV-6 is the physical equivalent of the logical OV-3, Operational Information Exchange Matrix, and provides detailed information on the system connections that implement the information exchanges specified in an OV-3. Human communications, such as verbal orders, are captured in the SV-1, Resource Interaction Specification, and SV-3, Resource Interaction Matrix, products only.

SV-6 describes, in a tabular format, data exchanged between systems, and the functions that produce and consume that data. SV-6 also specifies properties of these system data exchanges. MODAF does not mandate a set of standard properties, but it is typical to see periodicity, timeliness, throughput, size, information assurance and security characteristics of the exchange. In addition, the data elements, their format and media type, accuracy, units of measurement, and system data standard may also be described in the matrix.

Where a suite of SVs provides a physical specification for a logical requirement specified in a suite of OVs, the SV-6 properties should cover all the information exchange properties specified in OV-3. Similarly, it is recommended that all data elements carried by the data exchanges are shown.

It should be noted that each data element exchanged may be related to the 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.

Because an SV-6 is about showing flows across system boundaries, data flows between system functions performed by the same systems may not be shown in the SV-6 matrix; there will be no corresponding system port connection.

Note: although flows of materiel, human resources and energy are permitted in SV-1 and SV-4, they are not permitted in SV-6.

Subject to Crown Copyright

Data Objects

From The MODAF System Viewpoint (SV) p27:

The data in an SV-6 can include:

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 through it. Any properties shown in an SV-6 table will be properties of the system port connector.

Note: System port connector was removed at 1.2.004 - this should be Resource port connector

MODAFSV-6_simplifiedMetamodel_400.jpg
Full size:File:MODAFSV-6 simplifiedMetamodel.jpg

Subject to Crown Copyright

 

Presentation

From The MODAF System Viewpoint (SV) p29:

  • Tabulation

Configuration History

Comments

As it says, you cannot describe flows of anything other than data/information. It probably therefore reflects a procurer’s view rather than a designer’s view of what is needed. It is therefore not suitable as a systems engineering tool as it can only describe part of the solution - unnecessarily so given the freedoms that the 1.2.004 metamodel now allows.

References

 

Other Frameworks

See also:

 

Category:Framework -> View
Category:MODAF -> View
Category:Solution

Categories:

 

© 2010 Eclectica Systems Ltd.