|
Rule
|
Type of Rule
|
Metaclass concerned
|
Rule description
|
|
An organizational process should not contain more than one operation with the same name
|
Recommendation
|
Organizational Process
|
An organization process having two or more operations with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
A system process should not contain more than one task having the same
|
Recommendation
|
System Process
|
A system process having two or more tasks with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
Development Note: This already existing rule should be adapted to manage task and operation in a system process
|
|
A capability should not contain more than one capability composition having the same name
|
Recommendation
|
Capability
|
A capability having two or more capability compositions with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
An operational node should not contain more than one operational component having the same name
|
Recommendation
|
Business Function
(Operational Node)
|
An operational node having two or more components with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
A functional process should not contain more than one functional activity having the same name
|
Recommendation
|
Functional Process
|
A functional process having two or more activities with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
An artifact should not contain more than one artifact component having the same name
|
Recommendation
|
Artifact
|
An artifact having two or more components with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
An artifact should not contain more than one application host having the same name
|
Recommendation
|
Artifact
|
An artifact having two or more application hosts with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
A resource architecture should not contain more than one architecture use having the same name
|
Recommendation
|
Resource Architecture
|
A resource architecture having two or more architecture uses with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
A resource architecture should not contain more than one physical asset having the same name
|
Recommendation
|
Resource Architecture
|
A resource architecture having two or more physical assets with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
A resource architecture should not contain more than one human asset having the same name
|
Recommendation
|
Resource Architecture
|
A resource architecture having two or more human assets with the same may lead to confusing report since it is not possible to distinguish one from the other.
List the objects having the same names.
|
|
Rule
|
Type of Rule
|
Metaclass concerned
|
Rule description
|
|
An operation must be defined in the context of a organizational process
|
Requirement
|
Operation
|
An operation is a component defining an organization process. It cannot be defined outside the scope of an organizational process.
|
|
A task must be defined in the context of system process
|
Requirement
|
Task
|
A task is a component defining a system process. It cannot be defined outside the scope of a system process.
|
|
A capability composition must be defined in the context of a capability
|
Requirement
|
Capability Composition
|
A capability composition is a component defining a capability. It cannot be defined outside the scope of a capability.
|
|
A capability dependency must be defined in the context of a capability
|
Requirement
|
Capability Dependency
|
A capability dependency determines what components of a capability are dependent from each-other. This definition must be established in the context of the components owner (the upper capability).
|
|
An operational component must be defined in the context of an operational node
|
Requirement
|
Operational Component
|
An operational component is a component defining an operational node. It cannot be defined outside the scope of an operational node.
|
|
A functional activity must be defined in the context of an functional process
|
Requirement
|
Functional Activity
|
A functional activity is a component defining a functional process. It cannot be defined outside the scope of a functional process.
|
|
An artifact component must be defined in the context of an artifact
|
Requirement
|
Artifact Component
|
An artifact component is a component defining an artifact. It cannot be defined outside the scope of an artifact.
|
|
An application host must be defined in the context of an artifact
|
Requirement
|
Application Host
|
An application host is a component defining an artifact. It cannot be defined outside the scope of an artifact.
|
|
An architecture use must be defined in the context of a resource architecture
|
Requirement
|
Architecture Use
|
An architecture use is a component defining a resource architecture. It cannot be defined outside the scope of a resource architecture.
|
|
An physical asset must be defined in the context of a resource architecture
|
Requirement
|
Physical Asset
|
A physical asset is a component defining a resource architecture. It cannot be defined outside the scope of a resource architecture.
|
|
An human asset must be defined in the context of a resource architecture
|
Requirement
|
Human Asset
|
A human asset is a component defining a resource architecture. It cannot be defined outside the scope of a resource architecture.
|
|
Rule
|
Type of Rule
|
Metaclass concerned
|
Rule description
|
|
The use of the Entity (DM) / Data Model relationship is not recommended in the DoDAF 2 context
|
Recommendation
|
Entity (DM)
|
The relationship allowing the linking of an data entity to a detailing data model does not belong to the UML notation. It is not recommended to use to create data model since it will not be handle by the DoDAF 2 reports.
|
|
Rule
|
Type of Rule
|
Metaclass concerned
|
Rule description
|
|
A participant of an organizational process should only be assigned by org-units or human assets
|
Requirement
|
Participant
|
It is recommended to not assign architecture items that are not org-units or human assets to the organizational process participants since the exchange compliance reports will not able to establish proper analysis.
List assigned objects that are not conformed to the rule.
|
|
A participant of an functional process should only be assigned by operational nodes or operational components
|
Requirement
|
Participant
|
It is recommended to assign architecture items that are not operational nodes or operational components to the functional process participants since the exchange compliance reports will not able to establish proper analysis.
List assigned objects that are not conformed to the rule.
|
|
A participant of an system process should only be assigned by artifacts, artifact components, applications, application hosts, org-units, human assets, resource architectures or architecture uses
|
Requirement
|
Participant
|
It is recommended to assign architecture items that are not artifacts, artifact components, applications, application hosts, org-units, human assets, resource architectures or architecture uses to the system process participants since the exchange compliance reports will not able to establish proper analysis.
List assigned objects that are not conformed to the rule.
|
|
Rule
|
Type of Rule
|
Metaclass concerned
|
Rule description
|
|
A message must be connected to one producer and one consumer role of the service definition
|
Requirement
|
Message
|
Development Note: Check that there is a message rule that checks that a message is not connected to two roles. This rule must be updated to include the protocol context exception.
|
|
A service point must play a provider role of a service definition.
|
Requirement
|
Service Point
|
A service point plays one of the roles of a service definition. This role must be a provider role so that the service point is a supporter for the exposed service.
List the wrong roles.
Appliance Condition: The service point is linked to any role that is not a provider role of a service definition (protocol).
|
|
A request point must be play a consumer role of a service definition
|
Requirement
|
Request Point
|
A request point plays one of the roles of a service definition. This role must be a consumer role so that the request point is a consumer of the requested service.
List the wrong roles.
Appliance Condition: The request point is linked to any role that is not a consumer role of a service definition (protocol).
|
|
A service point should be linked to a service definition role.
|
Suggestion
|
Service Point
|
A service point is designed to explain what service is exposed to the consumers. It is more accurately defined if a provider role of a service definition is connected.
Appliance Condition: The service point is not connected to a role.
|
|
A request point should be linked to a service definition role.
|
Suggestion
|
Request Point
|
A request point is designed to explain what service is requested by the interacting item. It is more accurately defined if a consumer role of a service definition is connected.
Appliance Condition: The service point is not connected to a role.
|
|
Rule
|
Type of Rule
|
Metaclass concerned
|
Rule description
|
|
A functional process must include only functional activities that can be based on sub-processes
|
Requirement
|
Functional Process
|
In order to ensure process analyses, each functional process is described by sequencing and interacting functional activities. If a sibling functional process is involved then a call to it is specified linking the appropriate activity. This enables the separation between the functional process definition and the references to other existing processes.
|
|
An organizational process must include only operations that can be based on sub-processes
|
Requirement
|
Organizational Process
|
In order to ensure process analyses, each organizational process is described by sequencing and interacting operations. If a sibling organizational process is involved then a call to it is specified linking the appropriate operation. This enables the separation between the organizational process definition and the references to other existing processes.
|
|
An system process must include only tasks that can be based on sub-processes
|
Requirement
|
System Process
|
In order to ensure process analyses, each system process is described by sequencing and interacting tasks. If a sibling system process is involved then a call to it is specified linking the appropriate task. This enables the separation between the system process definition and the references to other existing processes.
|
|
Rule
|
Type of Rule
|
Metaclass concerned
|
Rule description
|
|
Only one dependency should be set between two capability compositions
|
Recommendation
|
Capability Dependency
|
There is more than one capability dependency that links the same capability sources and targets.
List all the dependencies.
Development Note: Check all the sources and targets thinking that more than one source can exist.
|
|
Only one dependency should be set between two projects
|
Recommendation
|
Project Dependency
|
There is more than one project that links the same project sources and targets.
List all the dependencies.
Development Note: Check all the sources and targets thinking that more than one source can exist.
|