Use cases
Overview
A use case describes an interaction between an actor and the system that yields an “observable result of value” to the actor.
Use cases are defined in order to specify all the different ways the system can be used. A complete set of use cases defines all behavior required of the system, effectively bounding the scope of the system without defining any of the system internals. Generally, use case steps are written using a structured narrative that is easy to understand. Use cases should be easy to follow and engaging for users, in order to ease the validation of each use case.
One of the benefits of creating use cases in Blueprint is the ability to simulate them. Use cases can be simulated using UI mockups to promote a clear understanding of the requirements and enhance the feedback provided by stakeholders.
Blueprint's use case editor provides you with the ability to easily create and edit use case artifacts. The use case editor looks like this:
Use Case Artifact Properties
By default,
-
Name: Indicates the name of the use case.
-
Id: Provides a unique identifier for the use case. The Id cannot be modified.
-
Type: Indicates the type of artifact.
-
Use Case Level: Indicates the level of detail of the use case, measured from 1 (high level) to 10 (low level). Use cases can be automatically excluded from simulation or test case generation based on the Use Case Level.
-
Description: Provides a description of the use case.
Your instance administrator can
Tasks
About saving artifacts as images
