Class and Sequence Diagrams

What is a class diagram used for in UML?

• To represent the structure of a system and its classes.

• To show the sequence of operations in a process.

• To illustrate the behavior of a system's components.

• To define the interactions between different systems.

Define a sequence diagram and its purpose.

• A sequence diagram is a visual representation of object interactions in a specific scenario, used to illustrate the order of messages exchanged over time.

• A sequence diagram is a tool for database design and optimization.

• A sequence diagram shows the physical layout of a system's components.

• A sequence diagram is a type of flowchart used for project management.

What are the main components of a class diagram?

• Classes, attributes, methods, relationships

• Entities, attributes, actions, states

• Modules, functions, variables, loops

• Objects, properties, events, interfaces

How do you represent a relationship between two classes?

• Use associations, aggregations, or compositions to represent relationships between classes.

• Use inheritance to represent relationships between classes.

• Use interfaces to define relationships between classes.

• Use methods to establish relationships between classes.

What is the difference between aggregation and composition?

• Composition allows parts to exist independently; aggregation does not.

• Aggregation and composition are the same concept.

• Both aggregation and composition require parts to depend on the whole.

• Aggregation allows independent existence of parts; composition requires parts to depend on the whole.

Explain the role of lifelines in a sequence diagram.

• Lifelines are used to represent data storage in a sequence diagram.

• Lifelines represent participants in a sequence diagram, showing the flow of messages and the order of interactions.

• Lifelines show the physical location of participants in a system.

• Lifelines indicate the duration of a process in a diagram.

What does a dashed line represent in a sequence diagram?

• A return message or response.

• A conditional branch

• A synchronous message

• An activation box

How can you depict method calls in a sequence diagram?

• Method calls are indicated by circles at the end of lifelines.

• Method calls are represented by dashed lines with no labels.

• Method calls are shown as vertical lines connecting lifelines.

• Method calls are depicted as horizontal arrows between lifelines, with the method name above the arrow.

What is the significance of the '<>' stereotype in class diagrams?

• The '<>' stereotype denotes a class that has no methods or properties.

• The '<>' stereotype signifies that a class is an interface, defining a contract for implementing classes.

• The '<>' stereotype indicates a class is abstract and cannot be instantiated.

• The '<>' stereotype is used to represent a concrete class with specific attributes.

Describe the concept of visibility in class diagrams.

• Visibility refers to the order of class members in a diagram.

• Visibility determines the color of class diagrams.

• Visibility in class diagrams defines the accessibility of class members using modifiers like public, private, protected, and package-private.

• Visibility is only relevant for interface diagrams.