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 will at least embody the concepts of operations defined in OV-1a, High-Level Operational Concept Graphic. These will also provide guidelines for the definition of more detailed rules and behavioural definitions that will be captured as the architecture is developed. (Rules can also be shown as constraints on other diagrams)
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 business is done in the enterprise. Whilst the other OVs 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, such as those contained in doctrine, guidance, rules of engagement, etc. At lower levels, 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).”
These rules are contrasted with the business or doctrinal standards themselves, which provide authoritative references and provenance for the rules (see TV-1, Technical Standards View).
The rules captured in OV-6a are logical whereas constraints that are specific to resources are defined in SV-10a, Resource Constraints Specification. 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 authorised to proceed with a specific activity.
From a modelling perspective, operational constraints may act upon nodes, operational activities, missions and entities (OV-7). Consequently, OV-6a rules may be associated with activities in OV-5 and it is often useful to overlay the rules on an OV-5, Operational Activity Model. OV-6a can also be used to extend the capture of business requirements by constraining the structure and validity of OV-7, Information Model, elements.
Creating an Operational Rules Model (table)
To create an Operational Rules Model (table):
- 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 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.
MODAF in Visual Paradigm
The MODAF is brought to you by Visual Paradigm, a full-featured development platform. Visual Paradigm provides an easy-to-use, model-driven MODAF tool that supports the development of MODAF views and models. You can create integrated MODAF products and generate architectural documents that facilitate organizations to efficiently coordinate enterprise architecture initiatives.