Use-cases capture and specify requirements of a system and stakeholder expectations with a view to the objectives of its users. Do not use this tag for for questions about suitability of the use of techniques/features to solve implementation issues.
Purpose
Use-cases capture and specify requirements of a system and stakeholder expectations with a view to the objectives of its users and the added value.
Tag usage
Use this tag for questions relating to the problems that a system is supposed to solve, and to use-case analysis and design:
- Identifying and scoping use-cases in narratives and requirements
- Analyzing the actors and their interactions with a system
- Abstracting use-cases from specific scenario and user-interfaces
- Documenting use-cases in textual or tabular form
- Modeling use-cases in UML. In this case add uml.
You may also use this tag for questions related to the implementation of use-cases (e.g. with clean-architecture)
Do not use this tag for for questions about:
- suitability of programming techniques or features to solve implementation issues. The remaining tags should be sufficient for people to find your question.
- exclusively UML use-case diagramming syntax. Prefer the tag combination umluse-case-diagram in this case.
Additional information:
- Use case on Wikipedia
- Use case 2.0 free ebook by Ivar Jacobson et al, the inventor of use-cases.
- Tips for writing use cases
- Use Cases for Example ATM System
