The SV-10a specifies functional and non-functional constraints on the implementation aspects of the architecture (i.e., the structural and behavioral elements of the Systems Viewpoint).
The SV-10a described Model describes constraints on the resources, functions, data, and ports that make up the SV physical architecture. The constraints are specified in the text and maybe functional or structural (i.e., non-functional).
Usage
The intended usage of the SV-10a includes:
- Definition of implementation logic.
- Identification of resource constraints.
Product Description
The Systems Rules Model DoDAF-described Model describes the rules that control, constrain or otherwise guide the implementation aspects of the architecture. System Rules are statements that define or constrain some aspect of the business and may be applied to:
- Performers.
- Resource Flows.
- System Functions.
- System Ports.
- Data Elements.
In contrast to the OV-6a Operational Rules Model, SV-10a focuses on physical and data constraints rather than business rules.
Constraints can be categorized as follows:
- Structural Assertions – non-functional constraints governing some physical aspects of the architecture.
- Action Assertions – functional constraints governing the behavior of resources, their interactions, and Resource Flow exchanges.
- Derivations – these involve algorithms used to compute facts.
Where a System Rule is based on some standard, then that standard should be listed in the StdV-1 Standards Profile.
Some System Rules can be added as annotations to other models. The SV-10a then should provide a listing of the complete set of rules with a reference to any models that they affect.
Creating a Systems Rules Model
To create a Systems Rules Model:
- Click on Systems 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 system rules. Click on New Constraint above the table to create a new row of systems rule.
- Click on the cell of the Constrained Elements column and select the elements to be constrained (i.e. ResourceArchitecture, System, ResourceMitigation, SecurityEnclave, CapabilityConfiguration, Organization, Person, Post, Responsibility, Project, NaturalResource, ResourceArtifact, Software, Technology, KnownResource, DataElement, InformationElement, ResourcePort, ResourceRole, Function, FunctionAction).
- Enter the rule in the Rule Specification cell.