Capability Architect Model Structure

The database template for each project includes a set of example nodes that illustrate how the capability model needs to be constructed within Capability Architect. A specific set of top-level nodes are always required as the basis for any capability model.

The first step when building a model is to establish this top-level set of relationships. All of the detailed design will then be built under each of these top-level nodes. These top-level nodes are shown below.

The Architecture Node

Within the Architecture  class a node is required to represent the entire capability architecture. As shown above, this node, named as the Capability, is used to capture links to the three principal elements that form the capability description:

1. The Existing System (ES). This is a top-level Component node that describes the existing system that is usually being replaced.
2. The System of Interest (SoI). This is a top-level Component node that describes the proposed new system.
3. The Campaign node. This is a top-level Operational Activity that contains all of the operational scenarios used to define the end-user needs that the capability must satisfy.

The default Capability Architecture template already has an Architecture node created, as shown below. The default Architecture node /Contains/ the default Component nodes, the System of Interest and the Existing System, and /Describes/ the default Operational Activity Campaign node.

• Inspect your Capability Architect template file and identify the Capability node within the Architecture class. Confirm it is the same as shown above.

The System of Interest Node

The default SoI node is the top-level Component within the new system design. It represents the entire new system. The SoI node can be renamed to something suitable for your project, such as Alarm System, or Infantry Fighting Vehicle, or Global Satellite System.

The SoI node must be connected to the top-level SoI Function using the /Performs/ relationship.

• Inspect your Capability Architect template file and identify the System of Interest node within the Component class. Confirm that it /Performs/ a top-level SoI Function.

The Existing System Node

The default Existing System node is the top-level Component used to describe elements of an existing system, if it exists. The Existing System node can be renamed to something suitable for your project, or it can be deleted if it is not required. For this tutorial we will leave the Existing System node in place.

The Existing System node must be connected to the top-level Existing System Function using the /Performs/ relationship.

• Inspect your Capability Architect template file and identify the Existing System node within the Component class. Confirm that it /Performs/ a top-level Existing System Function.

The Campaign Node

The default Campaign node is the top-level Operational Activity used to describe the operational scenarios considered in the development of the System of Interest. Within the Architecture, the Campaign node relates the operational analysis to the system analysis that will produce the System of Interest.

The Campaign node must be connected to the top-level Operational Need using the /Results in/ relationship.

• Inspect your Capability Architect template file and identify the Campaign node within the Operational Activity class. Confirm that it /Results in/ a top-level Operational Need called ‘Consolidated Operational Needs’.