Use Case Statement

By Manuel Dennis III

Name

Manage Request Notification Section

Description

To display a list of roles so that any changes will be notify the proper members

Dependencies

An Request must exist
A email subsystem should be in place

Scope

To notify users when a Request information changes, especially status information

Primary Actors

· Requester, Assigner, Approver

Secondary Actors

· Administrator, Worker

Pre Conditions

· Request must exist

· A role must be defined for each Request

Success End Conditions

· Users are notified via email that a change has taken place

Failure End Conditions

· Users go without notification.

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

User makes a status change

System updates the tracked Request status information.

2

User selects who to notify, recommended notifications are displayed

The system constructs a simple email with a link back to the specific Request and the denoted status change.

3

    

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

A1

User adds an Request comment

System updates the Request and will notify anyone selected to be notified.

A2

    

A3

    

 

Alternative / Additional Scenario:

#

Action / Stimulus

Reaction

B1

    

B2

    

B3

    

 

Alternative / Additional Scenario: Cancel

#

Action / Stimulus

Reaction

C1

    
     
     

Notes:

 

 

 

 

Issues: