O8_OCYM Operational Capability Mapping Viewpoint

Purpose

The Operational Capability Mapping Viewpoint describes the relationships of Operational Capabilities. The reasoning for Operational Capabilities as support for Operational Stories and the contribution of Operational Processes to Capabilities are described. Operational Capabilities encoded in Stakeholder Requirements are identified.

Applicability

The Operational Capability Mapping Viewpoint supports the “Business or Mission Analysis Process” activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§ 4.1] and contributes to the definition of Operational Capabilities.

Supported Processes

Supported Information Items

Presentation

A tabular format listing the relationships of Operational Capabilities to Stakeholder Requirements, Operational Stories, and Operational Process Activities.

Stakeholder

Concern

Exposed Concepts

The Diagram shows the concepts exposed by the viewpoint, and related concepts if necessary.

The Table shows the concepts exposed by the viewpoint, and related concepts if necessary.

ConceptDocumentation
OPSenablingOCYSpecifies the fact that an Operational Process contributes to the provision of one or more Operational Capabilities in the field. Aliases: UAF::MapsToCapability
Operational CapabilityA Operational Capability is a high-level description or specification of an organizational unit's ability to execute a specified course of action, to implement a business process or to provide a service. Operational Capabilities typically require people, processes, infrastructure, technology and supporting systems to be implemented. A Operational Capability is an enduring element, its implementation may change over time. A necessary or desired change of a Operational Capability triggers the updated of involved systems or the integration new systems. Aliases: UAF::Capability NAF4::Capability
OCYcomposedOFSpecifies the fact that an Operational Capability consists of other Operational Capabilites.
OCYspecializedBYSpecifies the fact that an Operational Capability is specialized by other Operational Capability. Aliases: UAF::CapabilityGeneralization
OCYdependingONSpecifies the fact that an Operational Capability depends on another Operational Capability. Aliases: UAF::CapabilityDependency
Operational StoryThe Operational Story represents one or more Operational Use Cases in the Usage Scenario identified by the Operational Context. The Operational Story is described as narrative story-telling.
OCYsupportingOSYSpecifies the fact that an Operational Story is supported by Operational Capabilities.
Operational ProcessAn Operational Process captures activity-based operational behavior including scenarios, activity actions, and operational exchange flows, e.g., including information, materials, natural resources, etc. Aliases: UAF::Operational Activity NAF::Logical Activity
Operational PerformerAn Operational Performer is an element of the Operational Context that is capable to perform Operational Process Activities contributing to a specific identified Operational Capability. An Operational Performer may be any kind of organization, person, or even a system playing a role in one or more Operational Contexts. Aliases: UAF::OperationalPerformer
OPRexhibitingOCYSpecifies the fact that an Operational Performer exhibits an Operational Capability under specific environmental conditions.
Stakeholder RequirementA Stakeholder Requirement is a Requirement imposed by a Stakeholder. Stakeholder Concerns are refined by Stakeholder Requirements applicable for the SOI. The Stakeholder Requirements are a result of discussions and agreements of how the SOI addresses the Concerns of the respective Stakeholder.
SHRrefiningOCYSpecifies the fact that an Operational Capability is refined by Stakeholder Requirements.

Realization of exposed Concepts

The Diagram shows the realization of exposed concepts.

The Table shows the realization of exposed concepts.

Required Viewpoints

Example