UML Component Diagram Online Quiz and Flashcards

Study Notes

A use case is a methodology used to capture the functional requirements of a system, describing the interactions between the system and its users.

An active class is a class that has its own thread of control, and can initiate control activity.
A component in a system is a self-contained part that represents a physically replaceable part of a system, and can be used to model a system's physical architecture.
A node is a physical or logical element that exists at a particular point in a system, and can be represented graphically as a rectangle.

A use case in UML is represented by an oval shape, and is used to model the functional requirements of a system.
A node in UML is represented by a rectangle, and can be used to model physical or logical elements in a system.
An active class in UML is represented by a class symbol with a vertical line inside, and is used to model classes with their own thread of control.
A collaboration in UML is represented by a dotted ellipse, and is used to model the interactions between elements in a system.

Common mechanisms in UML related to extensibility include stereotypes, tagged values, and constraints.
A stereotype is a way to extend the UML language to create a new modeling element, and is represented by a guillemet (« ») symbol. Example: «persistent» stereotype to mark a class that requires persistent storage.
Tagged values allow you to add additional information to a modeling element, providing a way to customize UML to a specific domain or problem.
UML can be extended in controlled ways by using profiles, which are a predefined set of stereotypes, tagged values, and constraints.