The elements in an StV-4 view are not intended to represent individual systems or items of equipment – a capability may be satisfied by a group of systems, and an individual system can satisfy more than one capability (see StV-53 Capability to Systems Deployment Mapping). Rather, the capability elements in an StV-4 view are elements of functionality elements defined by the capabilities under analysis. The preferred approach for describing an StV-4 view is graphical, and there are a number of potential approaches. Since the elements in an StV-4 view are essentially functional – i.e. they describe a required capability – the graphical notation is derived from the functional domain of systems engineering. The mandated notation is a functional dependency diagram which shows how functions are clustered together and the relationships between the individual functions or clusters of functions.
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|MODAF White Paper on Strategic Views.pdf||application/pdf||554.81 KB||English||DOWNLOAD!|
The purpose of this paper is to describe the initial content and layout of the StV-4 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.