Class/Interface Attribute Checks

PowerDesigner provides default model checks to verify the validity of class and interface attributes.

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.
Detect inconsistencies within check parameters	The values entered in the check parameters tab are inconsistent for numeric and string data types: default does not respect minimum and maximum values, or default does not belong to list of values, or values in list are not included in minimum and maximum values, or minimum is greater than maximum value. Check parameters must be defined consistently. Manual correction: Modify default, minimum, maximum or list of values in the check parameters tab Automatic correction: None
Data type assignment	The data type of an attribute should be defined. Moreover, its type cannot be void. Manual correction: Assign a valid data type to the attribute Automatic correction: None
Initial value for final attribute	The final attribute of a classifier must be initialized. Manual correction: Give a default value to the final attribute Automatic correction: None
Domain divergence	The definition of the attribute definition is diverging from the definition of the domain. Manual correction: Modify attribute type to respect domain properties Automatic correction: Corrects attribute type to prevent divergence from domain For more information about domain divergence, see Setting OOM Model Options.
Event parameter data type	[VB 2005] An interface attribute with a stereotype of Event must have a delegate as its data type. Manual correction: set the data type to an appropriate delegate Automatic correction: None