Product Detailed Description – SV-1 links together the OV and SV by depicting which operational nodes are deployed at each system node, and the systems resident at those systems nodes. SV-1 also shows the key interfaces between systems, and indicates which needlines (specified in OV-2) are satisfied by each of the interfaces. OV-2 depicts the operational nodes representing organizations, organization types, and/or human roles, and the required communications (needlines) between those nodes. SV-1 depicts how those operational nodes are deployed at systems nodes, which systems make up the systems
nodes and the interfaces which implement the needlines specified in OV-2.
The term system in the framework is used to denote a family of systems (FoS), system of systems (SoS), nomenclatured system, or a subsystem. An item denotes a hardware or software item. The term system node describes a logical or physical deployment for operational nodes – e.g. locations, platforms, units, facilities, etc. The following are documented in an SV-1:
• Systems and the interfaces between them
• System nodes and the operational nodes deployed at them
• Hardware/software items and their associated standards
Replaced/Superseded by document(s)
The purpose of this paper is to describe the initial content and layout of the modified SV-1 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.