Use case diagram
A use case diagram is a UML behavioral diagram depicting actors, use cases, and their externally visible interactions with a system.
Functional Design and Architecture: Examples in Haskell
A use case diagram is a requirements-modeling diagram that shows actors, the actions they trigger, and the context of those actions.
- How it is used
- Organizes requirements and establishes a shared agreement about system functionality between developers and customers.
- How deep it goes
- Defines actors, actions, and boundaries, but stops short of exposing functional properties or implementation structure.
- Examples
- Uses astronaut engine control and Minecraft main-menu interactions as concrete diagram examples.
- What you can do after
- Evaluate/understand required actors, actions, and subsystem boundaries before selecting an implementation approach.
Read how Functional Design and Architecture: Examples in Haskell explains use case diagram →
Software Design for Python Programmers
A use case diagram is a UML behavioral diagram that represents an application's externally visible interactions through actors and use cases.
- How it is used
- Uses visual models to document design and connect requirements with externally visible application behavior.
- How deep it goes
- Defines boundaries, actors, names, and interactions, while deferring detailed flows to separate use case descriptions.
- Examples
- Uses a book catalogue with customers, librarians, a database, and six named use cases.
- What you can do after
- Evaluate application scope and actor interactions through a compact visual requirements model.
Read how Software Design for Python Programmers explains use case diagram →
Related concepts
- Unified Modeling Languagepart of · The Unified Modeling Language is a standardized visual modeling language for specifying, visualizing, constructing, and documenting software and other systems.
- use casehas part · A use case is a description of a situation or interaction in which a system, method, or capability is applied to achieve or support a goal or outcome.
- use case documentationpart of · Use case documentation is a collection of artifacts, including diagrams and written descriptions, that records an application's use cases.
- mind mapcontrasts with · A mind map is a visual diagram that organizes ideas and their relationships around a central topic through branching connections.
- functional specificationused by · A functional specification is a document describing a system’s externally observable purpose, capabilities, required behavior, requirements, and use cases without prescribing implementation details.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.