|
|
Once you have completed a diagram, you can check whether its components are specified adequately from the Check menu.
The UML suite provides a set of rules for each command on the Check menu. Which rules are checked when you use a particular Check menu command depends on the current phase. For example, the set of rules for the Local Model command includes the following:
If you are in the Analysis phase, only the first of these rules is checked. If you are in the Object Design phase, both rules are checked.
This remainder of this section describes each Check menu command briefly. For a complete list of the rules provided for each Check menu command, see The UML Suite Customization Guide. That guide also describes several ways to customize Check menu commands:
Check Contents checks the semantics of a diagram. Each diagram has a unique set of rules.
To select Check Contents from the Browser, you must first select a diagram in the information area. Selecting Check Contents from the diagram editor checks the entire diagram regardless of whether you have selected objects in it.
For example, Check Contents for the CD includes a rule to verify that all link attribute symbols are connected to associations. Check Contents for the SD includes a rule to verify that each event trace has exactly one initiator.
Check Global Model checks all classes (and all associated events) in the current package.
To use Check Global Model, you must be at Package level in the Browser. It does not matter whether you have selected items in the information area.
The rules for Check Global Model are the same as the rules for Check Local Model. See the sample rules for Check Local Model.
Check Local Model checks selected classes or all classes in a selected diagram.
To run Check Local Model from the Browser, you must first select a diagram or CDM.
When you run Check Local Model from a diagram, the UML suite checks all classes selected; if no classes are selected, it checks all classes. The events checked depend on which diagram is active, as shown in the following table.
| Diagram Editor | Type Of Events Checked |
|---|---|
| CD (or CDM) | Events of all types |
| COD | Communication Messages |
| SD | Trace Events |
| STD | STD Events and Event Messages |
For example, Check Local Model includes a rule to check that no class has an attribute with the same name as a received event. It also includes a rule to ensure that special classes (such as enum and typedef) do not receive events.
Check Use Case Model checks all UCDs.
To select Check Use Case Model from the Browser, you must first select a UCD in the information area.
For example, the Check Use Case Model option includes a rule to check that each UCD has exactly one initiating actor and at least one associated SD.