Category: Unified Modeling Language

The behavioral things is the dynamic part of the UML model. These are the verbs of a model. Represents actions in time and space. In general, there are two main kinds of behavioral things. (1) Interactions (2) state machines. They are the basic behavioral things that you may include in a UML model, typically the state machine diagram. Semantically, these elements are usually connected to various structural elements, primarily classes, collaborations, and objects.

State Machine Diagram Note from OMG State Machine Slides – Lecture Notes by B. Beckert  What is State Machine Diagram?

A Use Case describes a task that is performed by an actor yielding a result of business value for a business. A use case may be visualized as a use case diagram or/and in structured textual specification format:

UML activity diagram is another common tool used by UML to model the dynamic behavior of the system. It describes the sequence of activities and shows the flow of control from one activity to another. UML activity diagram is essentially a flow chart.

A use case approach is a kind of technique for identifying the business goals of a system. The identification of use cases helps define system scope, ensuring that the requirements to be found will all be aligned with the business values, needs and strategy.

A use case is a requirements capture and documentation technique that can be written in plain text to describe in a narrative manner the actions and interactions of participants using the system. Finally, the functionality of the system should satisfy the purpose for which stakeholders use the system.

Use cases are often graphical, and use case diagrams are supported by text descriptions, including use case and participant descriptions, as well as scenarios associated with use case templates that make use case methods simple and intuitive and ideal tools for discussing and clarifying developers’ understanding of user needs.

Use case modeling is a technique for capturing, modeling, and specifying system requirements that correspond to a set of behaviors that the system may perform when interacting with actors. These behaviors produce observable results and help achieve their goals. Use cases are named for the specific user goals of the principal actors, which in turn describe or explain the general order of activities and events, as well as variations in special conditions, exceptions, or error conditions, through textual description.