Checking an OOM

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

A valid OOM conforms to the following kinds of rules:

You can check your model in any of the following ways:

The Check Model Parameters dialog opens, allowing you to specify the kinds of checks to perform, and the objects to apply them to. The following sections document the OOM -specific checks available by default. For information about checks made on generic objects available in all model types and for detailed information about using the Check Model Parameters dialog, see Core Features Guide > The PowerDesigner Interface > Objects > Checking Models.

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