Acquisition Views (AcV) [Programme Views]
AcV-1 Acquisition Clusters v1.2
AcV-1 view products represent an organisational perspective on programmes.
Note: the name of this MODAF view was changed from ‘SoS Acquisition Clusters’ following the MODAF Technical Group meeting on 9 February 2007.
Background:
The Acquisition Clusters View enables the user to model the organisational structures needed to manage a portfolio of projects. It shows dependency relationships between the actual organisations that own projects. While this View could be used to represent organisational relationships associated with transformation initiatives, it is primarily of interest to those who are responsible for programmes of acquisition projects.
This view provides a means of analysing the main dependencies between acquisition elements.
Usage:
- Programme management (specified acquisition programme structure)
- Project organisation
Data objects:
The data in an AcV-1 can include:
- Project
- Project Owner
- Enterprise Phase
Relationships Between Key Data Objects (Simplified from M3)
Representation:
- Topological (Connected Shapes)
- ‘Nested box’ Diagram
- UML Composite Structure Diagram
- UML Class Diagram
Detailed Product Description:
The Acquisition Clusters (AcV-1) View describes how acquisition projects are grouped in organisational terms as a coherent portfolio of acquisition programmes.
The AcV-1 View provides a way of describing the organisational relationships between multiple acquisition projects, each of which are responsible for delivering individual systems or capabilities. By definition, this View covers acquisition programmes consisting of multiple projects and will generally not be developed by those building Architectures for an individual project.
In essence, AcV-1 is an organisational breakdown consisting of actual organisations (see OV-4). The view is strongly linked with StV-4 which shows capability clusters and dependencies.
The AcV-1 View is hierarchical in nature. Higher level groupings of projects (or, rather the organisations that own these projects) form acquisition clusters.
The intent of an AcV-1 View Product is to show:
- All of the acquisition projects delivering systems or system of systems (SoS) within the acquisition programme under consideration
- Other systems and SoS which may have a bearing on the Architecture
- How the systems will be best integrated into acquisition clusters
- The nesting of acquisition clusters to form a hierarchy.
Example AcV-1
An AcV-1 View Product is specific to a particular point in the Enterprise lifeline. This may change through time i.e. the clusters may change as new systems and capabilities are introduced into the acquisition programme. Hence, it is possible that an acquisition programme could have more than one AcV-1 View Product, each showing how the acquisition clusters are arranged for relevant periods of time. This is achieved by tying the AcV-1 View Product to an Enterprise Phase.
Page version 1.2, dated 14th August 2008