liveBook · Manning

Use case

A use case is a goal-oriented interaction or application scenario that describes how a system is expected to support an actor or practical objective.

How 8 Manning books explain it

Software Design for Python Programmers

A use case is a named interaction scenario describing a capability that an external actor can perform with a system.

How it is used
Connects functional and nonfunctional requirements to user goals, application behavior, and validation.
How deep it goes
Defines diagrams and detailed descriptions with actors, conditions, triggers, action paths, outcomes, and constraints, stopping short of implementation.
Examples
Uses a book catalogue’s Search Catalogue, Add Book, and Log In Customer interactions as concrete scenarios and diagram labels.
What you can do after
Evaluate application behavior against actor goals and requirements, while providing scenarios for functional specification and black-box testing.

Read how Software Design for Python Programmers explains use case →

Clean Applications with Hexagonal Architecture

A use case is an application operation that coordinates domain rules to accomplish a specific user or system goal.

How it is used
Coordinates application goals between external triggers and the domain while keeping infrastructure outside the core.
How deep it goes
Develops input-port contracts and handler orchestration, including explicit failure paths and framework-free cross-cutting boundaries.
Examples
Uses article publication to illustrate a command port, a handler, repository access, and domain delegation.
What you can do after
Builds use-case contracts and handlers from scratch with explicit failure results and framework-free boundaries.

Read how Clean Applications with Hexagonal Architecture explains use case →

The Design of Web APIs, Second Edition

A use case is a scenario describing a user goal and the interactions needed to achieve it.

How it is used
Uses user goals and their steps to identify API capabilities before choosing programming representations.
How deep it goes
Details step decomposition and review of alternative cases; defers programming-interface decisions and later flow optimization.
Examples
Illustrates product purchasing, social-network messaging, and a food-delivery order exercise.
What you can do after
Practice/perform it by listing user goals, decomposing their steps, identifying reusable operations, and checking overlooked alternatives.

Read how The Design of Web APIs, Second Edition explains use case →

Designing Deep Learning Systems: A guide for software engineers

A description of how an actor interacts with a system to achieve a goal.

How it is used
Uses stakeholder interactions and application requirements to establish system goals, scope, and architecture.
How deep it goes
Develops use cases into stakeholder questions, service boundaries, APIs, and scenario-specific designs, stopping short of formal notation.
Examples
Uses dataset ingestion and fetching workflows plus progressively complex prediction-service scenarios.
What you can do after
Evaluate/understand which components and capabilities a system needs for concrete users and production scenarios.

Read how Designing Deep Learning Systems: A guide for software engineers explains use case →

Collaborative Software Design: How to facilitate domain modeling decisions

A use case is a description of interactions between an actor and a system that produce an observable outcome.

How it is used
Uses concrete use cases to discover acceptance criteria and constraints at a specific point in a scenario.
How deep it goes
Visualizes use cases through concrete examples, stopping at requirements and constraints rather than implementation.
Examples
Uses movie-seat reservation, adjacent-seat rules, one-ticket-per-seat constraints, and corridor discovery.
What you can do after
Apply it via Example Mapping to surface acceptance criteria and constraints.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains use case →

The Art of AI Product Development

A use case is a defined situation describing how a person or organization applies a system to accomplish a goal.

How it is used
Guides AI opportunity discovery by connecting customer needs, measurable tasks, business impact, and technical feasibility.
How deep it goes
Explains selection and validation criteria but stops short of prescribing a complete implementation design.
Examples
Uses unclear chatbots, measurable AI tasks, evaluation metrics, edge cases, and user feedback as teaching examples.
What you can do after
Evaluate AI opportunities by user need, impact, feasibility, strategic fit, uncertainty, and feedback requirements.

Read how The Art of AI Product Development explains use case →

Lead Developer Career Guide

A description of how an actor interacts with a system to achieve a particular goal.

How it is used
Uses use cases to compare client requests with end-user needs during requirements discovery.
How deep it goes
Develops use cases through interviews and discrepancy review, but stops short of formal notation or implementation detail.
Examples
Uses roles, expected system use, focus-group notes, survey responses, and discrepancies as concrete use-case evidence.
What you can do after
Apply use cases by interviewing users, recording mismatches, and discussing requirement changes with the client and project team.

Read how Lead Developer Career Guide explains use case →

The Well-Grounded Data Analyst

A use case is a specific situation or purpose for which a tool, system, or method is applied.

How it is used
Uses purposes to compare AI-tool demand across users, roles, experience levels, and potential product opportunities.
How deep it goes
Defines use cases through survey comparisons and stakeholder recommendations, then proposes follow-up cross-tabulation without detailing implementation.
Examples
Uses writing code, debugging, codebase discovery, code documentation, testing, collaboration, and project management as contrasting AI purposes.
What you can do after
Evaluate AI product opportunities by identifying popular, underserved, and weakly supported user purposes.

Read how The Well-Grounded Data Analyst explains use case →

Also covered in

What to know first

Related concepts

Questions about use case

What is use case?

A use case is a goal-oriented interaction or application scenario that describes how a system is expected to support an actor or practical objective.

Which Manning books explain use case?

Software Design for Python Programmers, Clean Applications with Hexagonal Architecture, The Design of Web APIs, Second Edition, Designing Deep Learning Systems: A guide for software engineers, Collaborative Software Design: How to facilitate domain modeling decisions, The Art of AI Product Development, Lead Developer Career Guide and The Well-Grounded Data Analyst.

What should I know before learning use case?

Manning books that teach use case usually introduce language model, client, user and SQL first.

What is use case part of?

Use case is part of use case diagram. A use case diagram is a UML behavioral diagram depicting actors, use cases, and their externally visible interactions with a system.

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.