Introduction to UML Modeling

The ability of an object to take on more than one form.

An operation can exhibit different behavior based on the data used.

Operators can have different behaviors in different situations.

A request to execute a function within an object.

A thing or entity with its own data and methods.

A blueprint or template for creating objects.

Showing only essential features and hiding complexities.

Creating new classes based on existing ones, inheriting features.

Bundling data and methods that operate on the data together.

Sending requests to objects for specific actions.

Data or information the system receives as input.

Information or data produced by the system as a result of processing inputs.

A specific task or action performed by a system.

A user or external entity interacting with the system.

Connection indicating which actor initiates which use case.

Relationship where a use case incorporates functionality from another use case.

Relationship showing variations or exceptions in the normal flow of a use case.

UML is built from things, relationships, and diagrams.

Four types of fundamental elements in UML models (structural, behavioral, grouping, annotational).

Static elements; nouns in the system, representing physical or conceptual parts.

An abstraction of similar things in a system with similar attributes and methods.

Describes operations a class can perform.

Interaction between elements in a system.

Set of actions performed by a system for a specific goal.

UML elements related to system behavior and actions.

UML elements that group other elements.

UML elements used to add additional information.

Connections between UML things.

A relationship where a change in one thing affects another.

Represents a relationship between things.

Shows an inheritance relationship.

Shows that one thing implements specific behavior.

Visual representations of UML elements.

Diagrams showing static parts of a system.

Diagrams showing how a system behaves.

Diagrams showing interactions between elements in a system.

A behavior an object carries out while in a particular state.

Used to denote parallel or concurrent activities.

Used to indicate choices in an activity diagram.

Partitions in an activity diagram, showing who performs activities.

A diagram that shows interactions between objects in a system.

An entity with data and methods, involved in interactions.

A vertical line representing an object's existence during interaction.

A sequence diagram message where the sender waits for a response.

A sequence diagram message where the sender doesn't wait for a response.

A class diagram models the static structure of an object-oriented system, showing classes, their attributes, operations, and relationships.

A class diagram consists of classes, interfaces, and relationships between them, defining the structure and behavior of a system's components.

Class diagrams are frequently used in the construction of applications, aiding in system design to construct classes, interfaces, their relationships, responsibilities, and operations.

A class diagram shows the static view of an application, not its dynamic behavior.

A class in a class diagram is a rectangle with compartments: the top compartment holds the class name; the middle, attributes; and the bottom, operations.

UML, like many object-oriented languages, has visibility modes (like public, private, protected) to control access to class components.

Characteristics or properties of a class that describe its state.

How the attributes and methods of a class are accessible from outside the class.

Connections between classes, showing how they interact or depend on each other.

A type of relationship representing an inheritance hierarchy.

A relationship where a change in one class affects another.

A whole-part relationship where a part can belong to more than one whole.

A strong whole-part relationship where a part belongs to exactly one whole. Part cannot exist without whole.

A static diagram that shows classes and their relationships in a system.