How do you write a use case description?

How To Write a Use Case

Identify who is going to be using the website.
Pick one of those users.
Define what that user wants to do on the site.
For each use case, decide on the normal course of events when that user is using the site.
Describe the basic course in the description for the use case.

What is description in use case?

A use case description is a text-based narrative of a functionality comprised of detailed, step-by-step interaction between the actor and the system. It describes the outcomes of an action taken to accomplish a specific goal. Also, some formats for use case descriptions include two columns.

Why use case description is important?

A text-based use case description can be used to provide additional information to support the use case definition. This description can contribute significantly to the use case’s value. The description text can be captured in the model as a single or multiple comments.

Why the use case description is necessary for use case diagram?

When using Unified Modeling Language (UML), a use case diagram helps you understand how a user might interact with the system you’ve engineered. And in the end, it should help your team define and organize requirements. Instead, they represent a high-level overview of how use cases, actors, and your system relate.

What is a use case example?

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 high level use case description?

The high level use case is simply a summary description of the task, written as unstructured text a paragraph or two in length. Its purpose is to provide just enough detail to give you a feel for its complexity and to help you group related use cases for development in the Elaboration phase.

What are the four steps in creating use case descriptions?

Creating Use Case Descriptions Use the following four steps to create use case descriptions: Use agile stories, problem definition objectives, user requirements, or a features list as a starting point. Ask about the tasks that must be done to accomplish the transaction.

What is use case with example?

A use case is a description of how a person who actually uses that process or system will accomplish a goal. It’s typically associated with software systems, but can be used in reference to any process. For example, imagine you’re a cook who has a goal of preparing a grilled cheese sandwich.

How is a use case specification typically created?

The use case specification is typically created in analysis and design phase in an iterative manner. At first, only a brief description of the steps needed to carry out the normal flow of the use case (i.e., what functionality is provided by the use case) is written. As analysis progresses, the steps are fleshed out to add more detail.

When to use a text-based use case description?

What should be included in a use case template?

You need to define the flow of the process that starts when a use case is started. The flow needs to detail how the communication will flow, who the information will be displayed to, what they need to do, and where the primary actor will end up. There are 3 things which you need to mention when writing the flow.

What are the different types of use cases?

Use cases can be written at differing levels of data and scope, each serves a purpose: Summary: General descriptions and sweeping overviews of system functionality or business processes. User Level : Task-related descriptions of users and how they interact with the system; descriptions of a specific business process.