Scribd
Upload
391 views

Use Case Template

This document provides a template for documenting a use case, including sections for a header with metadata, a description, actors, goals, triggers, preconditions, postconditions, normal flows, alternative flows, exceptions, included use cases, priority, frequency of use, constraints and requirements, assumptions, and notes. The template is to be used to document primary and secondary usage scenarios and ensure all relevant details are captured for analysis and development.

Uploaded by

mkamal101
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
391 views

Use Case Template

This document provides a template for documenting a use case, including sections for a header with metadata, a description, actors, goals, triggers, preconditions, postconditions, normal flows, alternative flows, exceptions, included use cases, priority, frequency of use, constraints and requirements, assumptions, and notes. The template is to be used to document primary and secondary usage scenarios and ensure all relevant details are captured for analysis and development.

Uploaded by

mkamal101
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Page 1

Use Case Template


Note: Please reference the Use Case Template Description for assistance and instructions on filling
out this template

Header: To be completed and maintained by the Initiator.


Use Case ID: <Use Case identifier or Project Tracker number>
Requirement ID: <Requirement identifier or Project Tracker ID number>
Use Case Type: <Feature Use Case or System Use Case>
Created By: <name of the person who Last Updated By: <name of the person who
initially documented Use performed the most recent
Case> updated>
Date Created: <date on which the Use Date Last Updated: <date on which the Use
Case was initially Case was most recently
documented> updated>

Part 1: To be completed by the Initiator.


Description: <a short paragraph describing in simple terms the basic idea of this
Use Case>
Actors: <primary and secondary actors>
Goal: <business goal of the primary actor>
Trigger: <the action that kicks off the Use Case>
Preconditions: <the state of the system before the Use Case starts>
Postconditions: <the state of the system at the conclusion of the Use Case
execution>
Normal Flow: <primary legitimate usage>
Alternative Flows: <alternative legitimate usage>
Exceptions: <anticipated error conditions>
Includes: <list of Use Case ID’s “called” by this Use Case>
Priority: <if a Requirement has multiple Use Cases, set the priority of the
Use Case for this feature – note: this is NOT the relative priority of
the Requirement>
Frequency of Use: <frequency of the execution of this Use Case – example: once per
week, 10 times per day, every day at midnight>
Constraints and Special <dependencies on other functionality, dependencies or architecture
Requirements: changes, business constraints, performance requirements, etc>
Assumptions: <any assumptions that were made during the analysis of this Use
Case>
Notes and Issues: <any additional comments, remaining open issues, TBDs about this
Use Case–as well as due date and who assigned to>

You might also like