MODAF. OV-6a Operational Rules Model

Description

The Operational Rules Model specifies operational or business rules that are constraints on an enterprise, a mission, operation, business, or an architecture. While other OV views (e.g., OV-1, OV-2, and OV-5) describe the structure of a business—what the business can do—for the most part, they do not describe what the business must do, or what it cannot do. At the mission level, an OV-6a may consist of doctrine, guidance, rules of engagement, and so forth. At the operation level, rules may include such things as a military Operational Plan (OPLAN). At lower levels, an OV-6a describes the rules under which the architecture or its nodes behave under specified conditions. Such rules can be expressed in a textual form, for example, “If (these conditions) exist, and (this event) occurs, then (perform these actions).” At a top level, rules should at least embody the concepts of operations defined in an OV-1, and should provide guidelines for the development and definition of more detailed
rules and behavioral definitions that will occur later in the architecture definition process.

Implementation

OV-6a can be represented using:

• An OV-6a table.
• An OV-6a spreadsheet report.

Sample

OV-6a Operational Rules Model

Related views

An OV-6a constrains the structure elements of OV-1, OV-2, and OV-5. OV-6a can also be used to extend the capture of business requirements by constraining the structure and validity of the OV-7 elements.

As the View name implies, the rules captured in an OV-6a are operational (i.e., mission-oriented) whereas resource-oriented rules are defined in an SV-10 (OV-6 is the “what” to SV-10’s “how”).