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

Introduction to SV-2a, SV-2b and SV-2c v1.2

The Systems Communications Description (SV-2a/2b/2c) series of views is intended for the representation of communications networks and pathways that link communications systems, and provides details regarding their configuration. This means that although the M3 shows Artefact as the central element in this view, we will refer to Systems when documenting the SV-2 series.

The networks and pathways documented through these views represent the physical implementation of the information needlines identified in an Operational Node Connectivity Description (OV-2).

The SV-2 series focuses on the physical characteristics of each link, to include specification of such attributes as the geographic location of network components (eg routers, switches, amplifiers and repeaters). Attributes such as capacities (eg bandwidth, throughput), frequencies used, security encryption methods used, and other descriptive information is usually presented in a corresponding SV-6 product (though most architecture tools would prompt the architect to enter such data as the SV-2 products are being developed). The SV-2 View is split into three Views which define the communications links between systems:

The goal of these Views is to provide a comprehensive specification of how systems are connected, what interfaces each system exposes (ports), the hardware interface used, and the protocols which are transmitted across the interface. Key elements are repeated from View to View, and are also common to the SV-1 View. These key elements are:

The elements are shown in different perspectives in the different Views. In an SV-1 View, the resources (which includes systems) are logically grouped by the Artefact they belong to (or are located at). The SV-1 View also shows how human operators (Roles) interact with systems. In the SV-2 Views, more information is added – particularly about the ports on each system and the protocols which each port supports. In addition, the SV-2 Views describe which protocols are supported for specific system-to-system connections. Of the resources in MODAF, only systems may be shown in SV-2 (i.e. no roles). Other Artefacts and Capability Configurations may be shown in SV-2c for informative purposes only (i.e. they cannot have ports or connectors themselves).

It is important to understand the differences between SV-1 and SV-2 to ensure that the correct detail is captured in each view. In essence, the SV-2 series expands on the SV-1 by providing more detail of the physical characteristics of those interactions specified in the SV-1 that are between systems. For example, the SV-1 interaction perspective shows a single-line representation of interfaces between nodes, whereas the SV-2 would show a more detailed representation of the communications infrastructure that provides the connections.

The SV-2 Views are key to implementing the MOD’s Network Enabled Capability strategy. They enable acquisition specialists and systems engineers to quickly plan and visualise how communications between systems are to be implemented. When MODAF is used as an analytical tool for existing systems, the SV-2 Views provide a detailed way to document the interfaces exposed by those systems.

The SV-2 views use the common term Protocol as a specialisation of Standard to describe the standards specifically used in interface and communication specifications.

Page version 1.2, dated 13th June 2008

Top of Page