Abstract Data Type Procedure Checks (PDM)

PowerDesigner provides default model checks to verify the validity of abstract data type procedures.

Check	Description and Correction
Name/Code contains terms not in glossary	[if glossary enabled] Names and codes must contain only approved terms drawn from the glossary. Manual correction: Modify the name or code to contain only glossary terms. Automatic correction: None.
Name/Code contains synonyms of glossary terms	[if glossary enabled] Names and codes must not contain synonyms of glossary terms. Manual correction: Modify the name or code to contain only glossary terms. Automatic correction: Replaces synonyms with their associated glossary terms.
Name/Code uniqueness	Object names must be unique in the namespace. Manual correction: Modify the duplicate name or code. Automatic correction: Appends a number to the duplicate name or code.
Abstract Data Type procedure code maximum length	The code of the ADT procedure is longer than the maximum allowed by the DBMS. Manual correction: Reduce the length of the code Automatic correction: Reduces the code to a permissible length
Procedure cannot have the same name as an attribute	An abstract data type procedure cannot have the same name as an attribute. Manual correction: Change the name of the ADT procedure Automatic correction: None
Abstract data type procedure definition empty	An abstract data type procedure must have a body defined. Manual correction: Create an ADT procedure definition in the Body tab of the ADT procedure property sheet Automatic correction: None
Inconsistent return type	If the abstract data type procedure is a function, a map or an order, you should define a return data type for the function, map or order. Manual correction: Select a return data type in the Return data type list Automatic correction: None