Use Cases

Intended audience:
Solution Store:

Anyone creating use cases
Click here to access the templates


In software and systems engineering, a use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system to achieve a goal. The actor can be a human or other external system.

Use cases contain the following elements:

Name A one line summary of the use case, often following a set pattern.
Description A description of the use case in simple language.
Key Scenario The most important or frequently discussed scenarios
Actors Who can participate in the use case. Use generic names rather than job titles.
Preconditions What is true at the start of the use case.
Flow of Events

Includes the basic flow:

What steps must the actor take to accomplish the goal of the use case. What does the system do in response?

As well as the alternate flow:

Are there any other ways to achieve the same outcome?

Exception Flows What could happen to prevent the use case from executing correctly?
Special Requirements Describe all the requirements associated with the use case that are not covered by the flow of events
Post Conditions What is true at the end of the use case.


Key Benefits

Here are the key benefits of the RequirementONE Use Case Solution.

Manage Use Cases

Capture use cases that define the people and process to achieve a specific goal. Full traceability of any changes to these requirements.

Streamline the Process

Enable all relevant team members and experts to work in parallel on the same data set to de-duplicate, cleanse, process, prioritize and decide on the use cases to be developed. Use the same system to capture business, functional and non-functional requirements and manage the development process using your chosen methodology - for example Agile.

Reduce Costs

Each step of the process from requirements management, to product development, to testing and issue management will have significantly quicker turnaround time and lower cost by reducing requirement gathering, development, testing and implementation time.

Easy to Use

Simple, browser based interface. Rapid deployment (think minutes not days). Easily customizable. Easy to integrate with existing systems. 

A Single Point of Truth

A central online repository stores each requirement as a record. Updates, comments and meta-data are controlled and tracked individually, allowing definitive product specifications.

A Collaborative Platform

The multi-user environment allows administrators control over which users have access to which project components. Data is accessible to global stakeholders with no version control issues, promoting teamwork.


Parent, Child or sibling links show critical relationships between market requirements, product requirements, the backlog, feedback and issues.


Full visibility into the development process through documentation and reporting of all requirements, agreements, stakeholder feedback and progress. In-line analytics highlight gaps in coverage, management of changes and status of development efforts.

Typical Use Cases

Here is a typical, but not exhaustive, list of roles and associated use cases that would interact with this solution.

Role Use Case
End users
  • Submit stakeholder requirements
  • Submit change requests
  • Submit issues
Project team
  • Gather stakeholder requirements
  • Convert ideas/suggestions to use cases
  • Sign-off requirements with end users
  • Manage change requests
  • Manage issues
  • Manage requirements
  • Verify implementation



These apps and templates are used for the solution.

App Template
Use Cases A specification containing a Use Case Template, which can be used to create and manage use cases.


1) For each use case record:
  • Populate all of the fields with the use case data
  • Add a User custom field if you want to assign the use cases to members of your team
  • If you need a diagram or wireframe, add it as an Attachment or External Link

2) Link related use cases to one another as well as the original requirements.

3) Use filters and reporting to identify gaps.


Getting started

  1. Select an existing, or create a new project
  2. Click on the Solution Store, and select the Use Cases Template
  3. Once you have the template, add your custom data.

Additional notes

This is a generic Use Case template. This can be refined to greater detail based on industry and methodology to meet your current needs. Combine it with other templates to give you an end-to-end solution.

Related links

Questions or Comments?

Respond to this post if you want to comment on the template or ask the author a question.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk