Checking an OOM

The Object-Oriented Model is a very flexible tool, which allows you quickly to develop your model without constraints. You can, however, check the validity of your OOM at any time.

You can check an OOM in any of the following ways:

The Check Model Parameters window opens, which allows you to specify the kinds of checks to perform, and the objects to apply them to. For detailed information about this window and correcting problems reported, see "Checking a Model" in the Models chapter of the Core Features Guide.

The following sections document the OOM-specific checks available by default. For information about checks made on generic objects available in all model types, see "Checking a Model" in the Models chapter of the Core Features Guide.

• Domain Checks
  The following OOM model checks are made on domains:
• Data Source Checks
  The following OOM model checks are made on data sources:
• Package Checks
  The following OOM model checks are made on packages:
• Actor/use Case Checks
  The following OOM model checks are made on actors and use cases:
• Class Checks
  The following OOM model checks are made on classes:
• Identifier Checks
  The following OOM model checks are made on identifiers:
• Interface Checks
  The following OOM model checks are made on interfaces:
• Class/interface Attribute Checks
  The following OOM model checks are made on class and interface attributes:
• Class/interface Operation Checks
  The following OOM model checks are made on class and interface operations:
• Realization Checks
  The following OOM model checks are made on realizations:
• Generalization Checks
  The following OOM model checks are made on generalizations:
• Object Checks
  The following OOM model checks are made on objects:
• Instance Link Checks
  The following OOM model checks are made on instance links:
• Message Checks
  The following OOM model checks are made on messages:
• State Checks
  The following OOM model checks are made on states:
• State Action Checks
  The following OOM model checks are made on state actions:
• Event Checks
  The following OOM model checks are made on events:
• Junction Point Checks
  The following OOM model checks are made on junction points:
• Activity Checks
  The following OOM model checks are made on activities:
• Decision Checks
  The following OOM model checks are made on decisions:
• Object Node Checks
  The following OOM model checks are made on object nodes:
• Organization Unit Checks
  The following OOM model checks are made on organization units:
• Start/end Checks
  The following OOM model checks are made on starts and ends:
• Synchronization Checks
  The following OOM model checks are made on synchronizations:
• Transition and Flow Checks
  The following OOM model checks are made on transitions and flows:
• Component Checks
  The following OOM model checks are made on components:
• Node Checks
  The following OOM model checks are made on nodes:
• Component Instance Checks
  The following OOM model checks are made on component instances:
• Interaction Reference Checks
  The following OOM model checks are made on interaction references:
• Class Part Checks
  The following OOM model checks are made on class parts:
• Class/component Port Checks
  The following OOM model checks are made on class and component ports:
• Class/component Assembly Connector Checks
  The following OOM model checks are made on class and component assembly connectors:
• Association Checks
  The following OOM model checks are made on associations:
• Activity Input and Output Parameter Checks
  The following OOM model checks are made on activity input and output parameters:

---

Created October 7, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com