Designed by: [YOUR NAME]
Company: [YOUR COMPANY NAME]
Email: [YOUR EMAIL]
Use this section to provide a unique identifier and a concise title for the use case.
Identifier: [USE CASE ID]
Title: [USE CASE TITLE]
Maintain a log of all revisions made to the use case document.
Date | Author | Revision Description |
---|---|---|
[DATE] | [AUTHOR'S NAME] | [[DESCRIPTION OF CHANGES]] |
List all individuals who have a stake in the success of this use case.
Name: [STAKEHOLDER'S NAME]
Role: [STAKEHOLDER'S ROLE]
Interest: [IINTEREST IN USE CASE]
Define the boundaries of the use case, including the system limits and the interaction with related systems.
System: [SYSTEM NAME]
Subsystems: [SUBSYSTEMS INVOLVED]
Specify the business goals that the use case intends to fulfil.
Main Goal: [MAIN GOAL]
Objectives:
[Objective 1]
[Objective 2]
More objectives as necessary
Provide a detailed description of the use case steps from trigger to goal delivery.
Trigger Event: [TRIGGER EVENT]
Step 1: [DESCRIPTION OF STEP 1]
Step 2: [DESCRIPTION OF STEP 2]
Continue describing steps as needed
Ending Condition: [ENDING CONDITION]
Specify what must be true before and after the use case runs.
Preconditions: [PRECONDITIONS]
Postconditions: [POSTCONDITIONS]
List the requirements that define the quality attributes of the use case. These may include performance, reliability, etc.
Requirement 1: [REQUIREMENT DESCRIPTION]
Requirement 2: [REQUIREMENT DESCRIPTION]
More requirements as necessary
Document assumptions and constraints that affect the design, implementation, and usage of the use case.
Assumption: [ASSUMPTION DETAIL]
Constraint: [CONSTRAINT DETAIL]
More assumptions and constraints as needed
List any alternative flows or extensions to the primary scenario.
Extension 1: [DESCRIPTION OF EXTENSION]
Extension 2: [DESCRIPTION OF EXTENSION]
More extensions as necessary
Templates
Templates