MODAF Meta-Model Support for StV-2:
The MODAF Meta-Model defines a UML profile for exchanging information between MODAF tools using the XMI file format. For StV-2 the appropriate section of meta-model needed to exchange that view’s information is shown in Figure 5. It should be noted that the classes shown for one view may be used in several other views.
The classes defined in the MODAF Meta-Model specify the allowable UML stereotypes that may be exchanged in an XMI file. As it is a meta-model, all relationships that feature in the view are also modelled as classes. Rather than define a class for every conceivable item that could appear in a view, the meta-model defines generic classes and allows references to the MODAF Taxonomy. For example, the MOD would be represented in XMI as a Organization stereotype, with a tagged value referring to the element in the taxonomy which says “Ministry of Defence”.
Replaced/Superseded by document(s)
The purpose of this paper is to describe the initial content and layout of the Capability Functions (StV-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 for publication in July 2005.
The MOD Architecture 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, the 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.