The SV-2 view is split into four views which define the communications links between systems. The views are:
• SV-2a System Port Specification – defines the ports on each system, and the protocol / hardware stack that is specified or implemented for each of those ports.
• SV-2b System to System Port Connectivity – defines the connections between individual ports and shows the protocols and hardware spec used for each connection.
• SV-2c System Connectivity Clusters – defines the bundles of system to system connections that go to make up an inter-nodal connection (see SV-1).
• SV-2d System Connection to Port Connection Matrix – specifies how the system to system connections in SV-1 are realised as port connections in SV-2b.
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|MODAF White Paper on Systems View 2.pdf||application/pdf||296.87 KB||English||DOWNLOAD!|
The purpose of this paper is to describe the initial content and layout of the modified SV-2 view in a way which would allow peer review from stakeholders. With the exception of this section, the rest of the paper follows the layout of the DODAF volume II document. The intention is that this format will be retained and used in the final MODAF documentation, currently scheduled to be published July 2005.
The MOD Architectural Framework (MODAF) is being developed with the intention of providing a rigorous way to specify systems of systems, and is a key enabler to NEC1. The framework will predominantly be used for acquisition purposes, and a key driver for its adoption is the need to improve interoperability between systems. However, MODAF could equally well be used to analyse existing, operational systems and better enable their integration with other systems (both new and existing).
An architectural framework defines a set of key business and technical information for describing a system of systems architecture. The purpose of an architectural framework is to define the operational context (organizations, locations, processes, information flows, etc.), the system architecture (interfaces, data specifications, protocols, etc.), and the supporting standards and documents that are necessary to describe the system of systems. The information presented in an architectural framework is split into logical groupings – usually known as views. The same system and business elements may be present in more than one view, but the purpose of each view is different and so each provides a different viewpoint on the information.