MODAF. AcV-1 Acquisition Clusters

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 organizational relationships between multiple acquisition projects, each of which is 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, the AcV-1 is an organizational breakdown consisting of actual organizations (see OV-4). The view is strongly linked with the 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 programmes 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.

Implementation

AcV-1 can be represented using:

• An AcV-1 Acquisition Clusters diagram which is based on the UML Class diagram.
• An AcV-1 Responsibility Matrix which is an editable Dependency Matrix.

Sample

AcV-1 Responsibility Matrix

Related views

In essence, the AcV-1 is an organizational breakdown consisting of actual organizations (see OV-4). The view is strongly linked with the StV-4 which shows capability clusters and dependencies.