When created the StV-3 view can be used to assist in the identification of capability gaps/shortfalls (no fielded capability to fulfil a particular capability function) or capability duplication/overlap (multiple fielded capabilities for a single capability function). The identification of either a gap or duplication on the StV-3 view should be used as the start point for a more in-depth analysis, to consider, for example, the different echelons that delivered Capability will be available to and the different performance characteristics delivered and required. In addition, it where a Capability cannot be equated on a one-to-one mapping with a particular System; further analysis can be assisted using the information provided in the Capability to Systems Deployment Mapping (StV-5) view.
The StV-3 view is most easily presented in a tabular form – typically with the structured list of required capability functions (derived from the Capability Functions (StV-2) view) running in one direction and timescale/epochs running in the other. At each row-column intersection, the System that delivers the Capability within that epoch/time period is displayed - if the availability of the Capability span multiple epochs then this is indicated by an elongated colour-coded 'bar'. If there are no Systems that satisfy the Capability in that epoch then a blank space should be left.
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|MODAF White Paper on Strategic View 3.pdf||application/pdf||509.57 KB||English||DOWNLOAD!|
The purpose of this paper is to describe the initial content and layout of the Capability Phasing (StV-3) 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).