Rules Check errors

The Reports > Rules Check command invokes the rules checking mechanism. A visible indication is displayed on the diagram for each error encountered. Multiple errors are indicated with an asterisk next to the rule number.

No data expression definition.

Leveled diagram name does not match process name.

No process description definition.

Only one connection.

No process at either connection.

Empty definition expression.

Invalid Definition syntax for property label.

Entry data element is undefined in property attribute.

Data Flow or Data Stores has a number of errors.

Data Flow has a number of undefined data element(s)/structure(s).

Data Flows or Data Stores has recursive definition.

Data Flow, Data Store, or Event has no definition.

Leveled diagram name of a child diagram on a Structure Chart does not match module name.

No module description definition.

No module at either connection.

No input flow and no output flow

Symbol is involved in a circular Super/Sub Type relationship

Symbol has more than one Super Type

Symbol is involved in a Super/Sub Type relationship too large to check for circularity

Element data element name violates second or third normal forms criterion

Subordinate is undefined or improperly defined

Utility not used by any Class

Class has more than one relationship with some other Class

Object’s Class not defined

Subject has no content

Warning - Object is not related to any other object

More than one start state

More than one stop state

Improper Generalization / Specialization connection

Input flow should enter from left

Control flow should enter from top

Mechanism flow should enter from bottom

Output flow should exit from right

No input control flow

Transition has no condition

Transition has no event

Condition not connected

Action not connected

Event flow into data transform

Prompt out of data transform

Data flow into control transform

Data flow out of control transform

Attribute name violates 2NF.

Attribute name violates 3NF.

Must be connected to Processes only

Warning - class has no attributes.

Warning - class has no operations.

Destructor operation scope attrib must be ‘Instance’.

Ternary association must have 3 or more lines attached.

State has multiple exit transitions with the same name.

State diagram not child of a class symbol.

State diagram ‘Class’ property not filled in.

State diagram ‘Class’ property not same as parent symbol name.

Diagram ‘Scenario’ property not filled in.

Scenario missing Need, Purpose, or Scope properties.

Diagram has no leftmost UOB or junction.

Diagram has multiple leftmost UOBs or junctions.

Diagram has no rightmost UOB or junction.

Diagram has multiple rightmost UOBs or junctions.

Symbol linked back to itself.

Scenario has no definition.

Parent Class or Package does not match does not match diagram properties.

Diagram has no Class or no Package.

This node must have a parent.

Sequence, Parallel, Selection nodes must have at least 2 child nodes.

UOB can have only one input link.

Sequence, Parallel, Selection, Iteration nodes must have exactly 1 child node.

UOB can have only one output link.

Sequence, Parallel, Selection nodes can have no child nodes.

Only one hierarchy structure is permitted.

An Operation must have a structure node as its parent.

Diagram should have 3 - 6 Activities.

Context Diagram should have 1 Activity.

Model property missing.

Only one Call Arrow is allowed.

Activity with Call Arrow cannot have a child diagram.

Arrow has no connections.

State has no action.

Invalid flow direction.

Warning - Association has aggregation at both ends.