NOV-6a Operational Rules Model
NOV-6a specifies the operational or business rules that are constraints to an enterprise, a mission, operation, business, or an architecture.
While other NOV subviews (NOV-1, NOV-2, and NOV-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.
Rules are modeled in relation to the constraining objects. A constraint can be potentially linked to any object of the architecture. This is done within the different diagrams showing the objects to be constrained or by adding new constraints via the property pages.
Constraints retrieved from a deep exploration of the architecture are displayed in the NAF navigation tree. You can also create constraints from these locations. The constraints displayed are those attached to the operational items of the architecture.
The NOV-6a Report Template
The NOV-6a Report Template
The NOV-6a report template is supplied with one parameter only: the architecture for which the report is required. There are no additional parameters.
The template comes with two chapters:
• the NOV-6a Operational Rule Model chapter
• the NOV-6a Rules Linked to Operational Items chapter.
The NOV-6a Operational Rule Model Chapter
This chapter lists the constraints and requirements attached to the operational items of the architecture.
Constraints are the external constraining elements that set the terms for whatever solutions are implemented.Requirements are the needs and requests of the user that define the contract or agreement to be carried out. The lists of requirements and constraints are displayed in alphabetical order with an additional column for the comments. A paragraph is added for each listed constraint and requirement to explain their constrained objects.
If constraints and requirements are created from objects in Operational node structure diagrams (NOV-2), these constraints and requirements can be retrieved in the Optional Rules Model chapter provided the "View Type" property is set to Operational.
For more information, see NOV-2 Operational Node Connectivity Description.The constraints are retrieved in the Operational Constraints folder while the requirements are retrieved in the Operational Requirements folder of the NOV-6a navigation tree.
For more information, see NOV-6a Operational Rules Model.
Example of the NOV-6a Operational Rule Model Chapter
The NOV-6a Rules Linked to Operational Items Chapter
It is also possible to generate a chapter that lists the potential constraints linked to an operational item.
This helps the user determine if the type of constraints linked are defined according to the scope defined for this operational architecture.
This definition is based on the "View Type" property.Viewing the scope of the constraint
If a constraint is not typed as Operational, a warning icon is displayed for this constraint in the Scope column. Although not typed as operational, the constraint appears in the table because it is linked to an operational item. This happens if the constraint was not created from the NAF navigation tree but from a diagram and then attached to an operational item of this diagram.
Example of a Rules Linked to Operational Items Chapter
Setting a constraint as operational
The "View Type" property for constraints with a warning can be changed. To do so:
1. from the table, right-click the constraint and open its property page.
2. Select the NAF sub-page then NAF State Level.
3. From the NAF Architecture View Type, select "Operational Activity View".
4. Refresh the report to show the changes.