UML notation used during the development and analysis of requirements to represent the functionality of the system use case describes a function of the system in terms of a sequence of interactions between an actor and the system. A use case also includes entry conditions that need to be true before executing the use case and the exit conditions that are true at the completion of the use case.
a diagram that documents which use cases are used by which externals and any relationships between the use cases.
A UML diagram showing the relationships between Actors and Use Cases. See Section 3.3, "Output of the Requirements Capture Process" for more information.
One type of UML diagram. Often used by software developers to define the software requirements for a system. Use case diagrams focus on scenarios that describe how users use the application.
a collection of actors, use cases, and their communications
a diagram that shows a set of use cases and actors and their relationships
a diagram that shows a set of use case s and actor s and the relationship s among them
a graph in which the nodes represent actors and use cases, and the lines represent connections between use cases and actors
a graph of actors, a set of use cases enclosed by a system boundary, communication (participation) associations between the actors and the use cases, and generalizations among the use cases
an artifact of the UML language that can help you modeling use cases
a very simple method of modeling one particular use case
A diagram that shows relations between Actors and Use Cases.
A diagram that shows the relationships among actors and use cases within a system.
In the Unified Modeling Language, a use case diagram is a sub class of behavioral diagrams.
