An OV-6a specifies operational or business rules that are constraints on the way that business is done in the enterprise.
At a top-level, rules should at least embody the concepts of operations defined in OV-1 High-Level Operational Concept Graphic and provide guidelines for the development and definition of more detailed rules and behavioral definitions that should occur later in the Architectural definition process.
Usage
The intended usage of the OV-6a includes:
- Definition of doctrinally correct operational procedures.
- Definition of business rules.
- Identification of operational constraints.
Product Description
The OV-6a specifies operational or business rules that are constraints on the way businesses are done in the enterprise. While other OV Models (e.g., OV-1 High-Level Operational Concept Graphic, OV-2 Operational Resource Flow Description, and OV-5b Operational Activity Model) describe the structure and operation of a business, for the most part, they do not describe the constraints and rules under which it operates.
At the mission-level, OV-6a may be based on business rules contained in doctrine, guidance, rules of engagement, etc. At lower levels, OV-6a describes the rules under which the architecture 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).”
These rules are contrasted with the business or doctrinal standards themselves, which provide authoritative references and provenance for the rules (see StdV-1 Standards Profile).
The rules captured in OV-6a are operational (i.e., mission-oriented) whereas resource-oriented rules are defined in the SV-10s or the SvcV-10s (OV-6 is the what to the SV-10’s or SvcV-10’s how). OV-6a rules can include such guidance as the conditions under which operational control passes from one entity to another or the conditions under which a human role is authorized to proceed with a specific activity.
Rules defined in an OV-6a may optionally be presented in any other OV. Consequently, OV-6a rules may be associated with activities in OV-5a Operational Activity Decomposition Tree and OV-5b Operational Activity Model and can be useful to overlay the rules on an OV-5a Operational Activity Decomposition or OV-5b Operational Activity Model. OV-6a can also be used to extend the capture of business requirements by constraining the structure and validity of DIV-2 Logical Data Model elements.
Creating an Operational Rules Model (table)
To create an Operational Rules Model:
- Click on Operational Rules Model in the Action Artifact area, and then select Create New Diagram.
- Type the diagram name and press Enter.
- This opens a table where you can create and manage operational rules. Click on New Constraint above the table to create a new row of an operational rule.
- Click on the cell of the Constrained Elements column and select the elements to be constrained (i.e. OperationalActivity, InformationElement, OperationalPerformer, KnownResource).
- Enter the rule in the Rule Specification cell.
DoDAF in Visual Paradigm
The DoDAF is brought to you by Visual Paradigm, a full-featured development platform. Visual Paradigm provides an easy-to-use, model-driven DoDAF tool that supports the development of DoDAF 2.02 views and models. You can create integrated DoDAF products and generate architectural documents that facilitate organizations to efficiently coordinate enterprise architecture initiatives.