30/08/24_UML Relationships

What is an association relationship in UML?

• An association relationship in UML is a type of inheritance.

• An association relationship in UML is a method for data encapsulation.

• An association relationship in UML is a way to define class attributes.

• An association relationship in UML is a connection between classes that shows how they are related.

How does aggregation differ from association in UML?

• Aggregation and association are the same concepts in UML.

• Aggregation differs from association in that aggregation implies a whole-part relationship with independent lifecycles, while association indicates a general relationship without ownership.

• Association represents a whole-part relationship with dependent lifecycles.

• Aggregation is a type of association that requires ownership.

What defines a composition relationship in UML diagrams?

• A composition relationship is a weak association with no ownership.

• A composition relationship allows contained objects to exist independently.

• A composition relationship indicates a strong ownership where the contained objects cannot exist independently of the container.

• A composition relationship indicates a temporary link between objects.

Can you explain the concept of generalization in UML?

• Generalization is the method of defining a class that only contains abstract methods.

• Generalization is the process of creating a unique class without any parent classes.

• Generalization is the process of defining a general class from which more specific classes can inherit attributes and behaviors.

• Generalization refers to the specific attributes of a class that cannot be inherited.

What is the significance of dependency relationships in UML?

• Dependency relationships indicate the independence of elements.

• Dependency relationships have no impact on system performance.

• They are used solely for visual representation in UML diagrams.

• Dependency relationships in UML signify the reliance of one element on another, facilitating better design and maintenance.

In which scenario would you use aggregation over composition?

• Use composition when the contained objects can exist independently of the container.

• Use aggregation when the container is responsible for the lifecycle of the contained objects.

• Use composition when the contained objects can be shared among multiple containers.

• Use aggregation when the contained objects can exist independently of the container.

How do association relationships represent multiplicity?

• Association relationships do not indicate any numerical values.

• Multiplicity is represented by the color of the association line.

• Association relationships represent multiplicity by indicating the number of instances that can be associated between classes.

• Association relationships only represent the direction of the relationship.

What is the visual representation of a generalization relationship?

• A solid line with no arrows indicating a relationship.

• A dashed line with a filled triangle pointing to the subclass.

• A dotted line with a hollow square pointing to the superclass.

• A solid line with a hollow triangle pointing to the superclass.

__is not a valid graphics notation for visibility in a Class diagram.

• +

• =

• -

• #

What are the key characteristics that distinguish composition from aggregation?

• Aggregation is a strong relationship with dependent lifecycle; composition is a weak relationship with independent lifecycle.

• Composition allows for independent lifecycles; aggregation requires dependent lifecycles.

• Composition and aggregation are identical in terms of lifecycle management.

• Composition is a strong relationship with dependent lifecycle; aggregation is a weak relationship with independent lifecycle.