Use Case Statement

By Manuel Dennis III

Name

Manage Request Attachment Section

Description

To allow users to attach small files to the Request for storage in the specified file structure

Dependencies

An Request must exist and an attachment file structure must be in place with the proper rights for the ASPNET user

Scope

To save and retrieve attached files for users related to the Request

Primary Actors

· Requester, Approver, Worker, Assigner

Secondary Actors

· Administrator

Pre Conditions

· Request must exist with a valid Request Number

· Requests file structure must be configured

Success End Conditions

· Users can store and retrieve attachments related to an Request

Failure End Conditions

· Users fail to store or retrieve attachments related to an Request

Document Revision #

Action Taken, Notes

When?

By Whom?

0.1

 

 

 

 

 

Use Case

#

Action / Stimulus

Reaction

1

User clicks on an attachment

The attachment should be accessed as if a file were being sent to the users browser. The user can opt to open the attachment, or save it to their local storage.

2

User clicks create a new attachment

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

  

The application should present all attachments for the Request and related request. Because requesters and approvers will likely include attachments at the request level.

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 Request 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 Request 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

§ Attachment.#.FileExtension

§

o Request

· Year

o RequestNumber

§ Attachment.FileExtension

§ Attachment.#.FileExtension

o Solution

· Year

o SolutionNumber

§ Attachment.FileExtension

§ Attachment.#.FileExtension

The # is incase someone attaches multiple versions of a file with the same filename. This is strictly to keep track of different versions and nothing more.

 

Issues: