Use Case Statement
By Deb Sands
Use Case
# |
Action / Stimulus |
Reaction |
1 |
The Attachments button is clicked. |
This can toggle the visibility of the attachments section. This can allow someone to print out their request information from the browser with only pertinent information. |
2 |
The Browse button is clicked |
Requester finds the file they wish to attach to the request. The attachment is sent to the application for storing in the attachment file structure under a specific folder related to the request. See notes for further details. |
3 |
Alternative / Additional Scenario:
# |
Action / Stimulus |
Reaction |
A1 |
Remove attachment |
No facility will be included at this time to delete attachments. Attachments will only be visible in the folders file structure and could be deleted by Server administrators |
A2 |
A record is kept in the attachment table of past attachments related to an assignment even if the file no longer exists in the structure. Some sort of indication should exist. |
|
A3 |
Alternative / Additional Scenario:
# |
Action / Stimulus |
Reaction |
B1 |
||
B2 |
||
B3 |
Alternative / Additional Scenario: Cancel
# |
Action / Stimulus |
Reaction |
C1 |
||
Notes:
The assignment file structure is defined as follows. The folder should be accessible from the ASPNET worker process user. The ASPNET user should have read and write access to this folder. The folder structure should resemble the following:
q AttachmentShare
o Request
· Year
o RequestNumber
§ Attachment.FileExtension
Issues: