Use cases describe which operations should be possible within an Application and by which Actor they should be possible. Each use case is built around a Feature previously specified in ReqBuilder and aims to detail its operation in a detailed way in the form of scenarios.

For example, the feature F01 – Authentication is the convergence point for all use cases related to user authentication: the use cases Log in, Log out, Request a password reset, Reset password, and Validate account all relate to it.

A use case relates to an Actor and a Feature specified elsewhere in ReqBuilder.

It is possible to indicate preconditions (tests that must prove true before the use case is allowed to be executed) as well as postconditions (which must be verified before exiting this use case). These conditions can refer to requirements defined in ReqBuilder, which then appear in a particular format: Pages, Forms, Tables, Functional Requirements, or Non-functional Requirements.

The detail of a Use case is described in the form of a nominal scenario (most frequent or « normal » sequence of actions to satisfy the objective of the use case) and possibly exception scenarios (sequence of interactions caused by an exceptional event that results in the failure of the objective) or alternative scenarios (other possible sequence of actions that also satisfy the objective)

Each step involves an Actor (as below in blue, « User ») or the system (example « Litigation BackOffice »).

It is possible to modify the ordering of steps by a drag-and-drop action.

When a reference is made to a requirement defined in ReqBuilder, it appears in a particular format. This is particularly the case for Glossary terms, Functional or Non-functional requirements, Tables, Forms, and Pages. In the example below, the mention Login Form refers to a form, the details of which can be displayed by simply clicking on the corresponding mention.

Tip: all texts displayed in blue or with a particular formatting are links: to access the preview of the Actor or Feature to which the use case is attached, simply click on the corresponding text.

Note: you can view the UML use case diagram by displaying the details of a Feature.