HOPEX Aquila Doc FR

The primary purpose of the OV-2 is to define capability requirements within an operational context. The use of OV-2 is intended to be logical. It describes who or what (not how).

OV-2 is a description of the Resource Flows exchanged between operational activities (from an instance point of view). Information is exchanged with the aim of answering a use case.

OV-2 Implementation

Thee OV-2 relies on scenarios. For more information, see The Scenario Concept.

Operational resource hierarchy view

This tree enables you to navigate in the repository and view or create operational resource objects.

Operational scenario environments

An operational scenario environment represents communications between organizations and their partners. You can use it to describe the external use of an organization.

You can also create an operational scenario environment directly from an environment pop-up menu.

See OV-2 Operational Scenario Environment Diagram.

Operational scenarios

An operational scenario presents flows exchanged between organizations. A scenario can represent a specific use case or, globally, the set of all flow exchanges at the operational level.

You can also create an operational scenario directly from the pop-up menu of an organization.

It can be mapped to an organization and optionally to an operational activity. For more information see Defining the Subject of an OV-2 Scenario.

It can be described in several ways:

• through an operational scenario diagram

To create the diagram, see Creating OV-2 Operational Scenario Diagrams.

• through an operational sequence diagram (this is the same as the operational scenario diagram except that the operational participants are placed in columns, like swimlanes)

• through the operational scenario editor (which consists of a flow editor and a lifeline/participant editor)

For more information see Editing an Operational Scenario.