What are the common formats for use cases?
Robert Guerrero
Updated on March 13, 2026
- Use-case model overview: A format for understanding the “big-picture”
- Use-case brief descriptions: A format for writing summary use cases.
- Step-by-step outlines: A format for writing less formal, low-ceremony use cases.
- Fully detailed: A format for writing more formal, high-ceremony use cases.
Correspondingly, which is the best use case format?
The basic flow is the best case scenario of what should happen in the use case if all the conditions are met. So in our example, the basic flow is as follows: The customer visits the support website.
Also, what are the three main parts of a use case scenario? The three main parts of a use case scenario are the use case identifiers and initiators; the steps performed; and the conditions, assumptions, and questions.
Similarly, what is an example of a use case?
A use case is a description of how a person who actually uses that process or system will accomplish a goal. For example, imagine you're a cook who has a goal of preparing a grilled cheese sandwich. The use case would describe through a series of written steps how the cook would go about preparing that sandwich.
What is included in a use case?
Characteristics of use case
Use cases describe the functional requirements of a system from the end user's perspective, creating a goal-focused sequence of events that is easy for users and developers to follow. A complete use case will include one main or basic flow and various alternate flows.
Related Question Answers
What is use case scenario example?
For example a system use case might be "return book when overdue" and would describe the interactions of the various actors (borrower, librarian) with the system in carrying out the end-to-end process.What is use case diagram?
A use case diagram is a graphical depiction of a user's possible interactions with a system. A use case diagram shows various use cases and different types of users the system has and will often be accompanied by other types of diagrams as well.What's another word for use case?
»application testing exp. »applications testing exp. »cases involving the use exp. »cases of abuse exp.How do you create a use case diagram?
How to Draw a Use Case Diagram?- Identify the Actors (role of users) of the system.
- For each category of users, identify all roles played by the users relevant to the system.
- Identify what are the users required the system to be performed to achieve these goals.
- Create use cases for every goal.
- Structure the use cases.
How do I get use cases?
Five Tips for Writing Use Cases- Make each step show an action. A use case is a story.
- Keep it between six and ten steps. When a use case is 6-10 steps long, your reader can absorb and understand it in a minute or two.
- Avoid if statements.
- Forget the UI (for now)
- Put formulas and rules elsewhere.
What is the difference between a user story and a use case?
A user story — some people call it a scenario — expresses one very specific need that a user has. It's usually written out as a couple of sentences. A use case is similar to a user story, because it also describes one specific interaction between the user and the software.What is a fully developed use case description?
The “fully developed use case descriptions” are used to document the context, purpose, description, conditions, and workflow of each use case. SSDs are used to document the inputs and outputs that are passed between the user and the system during a use case.What is trigger in use case?
A trigger is the initiator of a use case. It is what causes the use case to start. There isn't a promise that this event happens – only an indication that this event triggers the start of a use case.What is use case in simple words?
A use case is a written description of how users will perform tasks on your website. It outlines, from a user's point of view, a system's behavior as it responds to a request. Each use case is represented as a sequence of simple steps, beginning with a user's goal and ending when that goal is fulfilled.Who write use cases?
Typically a business analyst writes the use cases for a software project.Can a use case use another use case?
When a use case is depicted as using functionality of another functionality of another use case, this relationship between the use cases is named as an include or uses relationship. A use case includes the functionality described in another use case as a part of its business process flow.What is a primary use case?
Primary vs Supporting ActorsThe primary actor of a use case is the stakeholder that calls on the system to deliver one of its services. It has a goal with respect to the system – one that can be satisfied by its operation. The primary actor is often, but not always, the actor who triggers the use case.
How do you write test cases in use cases?
Deriving Test Cases from Use Cases: A Four-Step Process- Identify the use-case scenarios.
- For each scenario, identify one or more test cases.
- For each test case, identify the conditions that will cause it to execute.
- Complete the test case by adding data values.
How do you show generalization in a use case diagram?
In the context of use case modeling the use case generalization refers to the relationship which can exist between two use cases and which shows that one use case (child) inherits the structure, behavior, and relationships of another actor (parent).What are the types of use cases?
There are basically two types of use cases analysts can draw from: Business Use Cases and System Use Cases. Business Use Cases are more about what a user expects from a system while System Use Cases are more about what the system does. Both use case types can be represented by diagrams or text.What are the two main components of a use case diagram?
Use case diagram components- Actors: The users that interact with a system. An actor can be a person, an organization, or an outside system that interacts with your application or system.
- System: A specific sequence of actions and interactions between actors and the system.
- Goals: The end result of most use cases.