Generalization property sheet General tab

Chapter 3 Building Structural Diagrams

Generalization property sheet General tab

The General tab contains the following properties:

Property	Description
Name	Specifies the name of the item, which should be clear and meaningful, and should convey the item's purpose to non-technical users.
Code	Specifies the technical name of the object, which is used for generating code or scripts.
Comment	Descriptive comment for the object.
Parent	Specifies the parent object. Click the Properties tool to the right of this box to access the property sheet of the specified object.
Child	Specifies the child object. Click the Properties tool to the right of this box to access the property sheet of the specified object.
Stereotype	Extends the semantics of the object beyond the core UML definition. The stereotype <<implementation>> means that the child object inherits the implementation of the parent object but does not make its interfaces public, nor support them (thus violating its substitutability).
Visibility	Specifies the visibility of the object, how it is seen outside its enclosing namespace. You can choose between: Private – only to the generalization itself Protected – only to the generalization and its inherited objects Package – to all objects contained within the same package Public – to all objects (option by default)
Generate parent class as table	Selects the "Generate table" persistence option in the Detail tab of the parent class property sheet. If this option is not selected, the "Migrate columns" persistence option of the parent class is selected.
Generate child class as table	Selects the "Generate table" persistence option in the Detail tab of the child class property sheet. If this option is not selected, the "Migrate columns" persistence option of the child class is selected.
Discriminant Attribute	Specifies a persistent attribute (with a stereotype of <<specifying>>) in the parent table. Click the New tool to create a new attribute. This attribute will only be generated if the child table is not.

If the generalization is created in a use case diagram, you cannot change the type of objects linked by the generalization. For example, you cannot attach the dependency coming from a use case to a class, or an interface.