Use Case descriptions

Case 1: View Submitted Documents

Scenario: Actor is student in McGill university who is enrolled in Co-op and internship. In Co-op-ERATOR program student needs to submit many documentations to the company. They should be able to view any submitted documents.

Steps:

1. Student goes to profile page
2. Student clicks on the document link
3. System find the document in the database
4. System shows the document in PDF/webform

Basic Path:

1. Student finds the document in profile
2. System locate the document in database
3. System represents the document
4. Student can view it

Alternate:

1. Student cannot find the document because he/she hasn’t submitted yet
2. Newly submitted document takes time to store in profile
3. The terminal student is using doesn’t support the format of the document

Case 2: Submit PDFs

Scenario. Actor is a enrolled in McGill university and is using entering a coop program. In the Co-operator application, students will need to submit various forms in the pdf format to progress in their coop term.

Steps:

1. Student should login to their account
2. Student student locates where they should submit their form
3. Student uploads their electronic pdf

Basic path:

1. Student logs on
2. Student locates the designated upload location
3. Student chooses which form to upload
4. Student submits form
5. System receives and stores form

Alternate:

1. Student does not find the upload location
2. Student uploads the wrong form by accident
3. Student uploads a format different from pdf

Case 3: Track progress in Co-Op Program

Scenario: Actor is a student at McGill University currently enrolled in the Co-Op program. Using Co-Op-ERATOR application, they can check their progress so far in the Co-Op program. This progress includes number of days passed in the current internship, as well as a record of the previous finished internships.

Steps:

1. Student logs on to their account
2. Student navigates to the "Progress" page

Basic Path:

1. Student accesses the "Progress" page
2. System finds that student's progress information in the database
3. System uploads and displays that student's progress for viewing

Alternate:

• Branching off 1: Academic holds somehow interfere with student progress
• Branching off 2: Student has not yet made enough progress to have information in the database
• Branching off 3: Student's terminal cannot format and display the progress

Case 4: User authentication

Scenario: Actor is a student at McGill university who is enrolled in Co-op and internship. In order to use the Co-op-ERATOR program, the student needs to be able to authenticate themselves before using the service.

Steps:

1. Student goes to home page
2. Student clicks on the login link
3. Student enters his credentials
4. System logs him into his personal account

Basic Path:

1. Student is logged in and can use the features on the website
2. Student can now logout after he is done with his tasks

Alternate:

1. Student cannot login because their credentials is not yet been created
2. Student cannot login because they use wrong credentials

Case 5: Resubmitting forms

Scenario: Actor is a student at McGill University enrolled in a co-op program. The student has already submitted a form to the CO-OP-ERATOR system, but needs to resubmit it, due to modifications.

Steps:

1. Student logins to their account
2. Student navigates to their documents section
3. Student presses "Resubmit" and resubmits their form

Basic path:

1. Student navigates to "Documents" section
2. Student selects the form to resubmit
3. Student chooses the file to upload
4. Student accepts form submission
5. System receives and saves form

Alternate:

1. Student uploads file in wrong format
2. Student uploads wrong file
3. System fails to receive or save form