-
Notifications
You must be signed in to change notification settings - Fork 1
Use Case Specifications for Deliverable 1
Title: Confirm Co-op Start Date
Actors: Employer
Intention: The intention of the employer is to confirm the student’s employment start date to the school.
Precondition: Logged in under an employer account.
Main Scenario:
- Employer receives list of students with potential start dates.
- Student starts employment on a given date.
- Employer receives an employment confirmation request from the school.
- Employer sends the confirmation to the school.
Alternatives Scenarios:
3a. Employer doesn’t receive an employment confirmation request
3a.1. System tries to get the employment confirmation request and notifies the user.
4a. Student does not start employment on listed date.
4a.1. Employer does not send confirmation to the school.
Postcondition (for success case): Employment and start date of student is confirmed to school.
Postcondition (for fail case): Confirmation of employment is not sent to school.
Title: Complete Evaluation Form
Actors: Employer
Intention: The intention of the employer is to fill out the student evaluation form.
Precondition: Logged in under an employer account and student finishes their co-op.
Main Scenario:
- System sends out the evaluation form for this specific student to the employer.
- The employer fills the form and upload to the system.
- The employer clicks send.
- The form is stored into the system database.
Alternative Scenarios:
2a. Employer doesn’t upload the form file.
2a.1. System notifies the employer that no file is uploaded.
2a.2. System waits for a new file and use case continues at step 3.
Postcondition: Confirmation is sent to the co-op administrator.
Title: Download Proof of Co-op placement
Actors: Employer
Intention: The intention of the employer is to download a proof of co-op placement of the newly hired intern.
Precondition: The employer is logged into the system.
Main Scenario:
- The employer selects the student from a list of students.
- The employer selects Proof of Co-op placement as an option
- The employer clicks the download button in the the system.
Alternative Scenarios:
1a. The employer doesn’t select a student
1a.1. The system notifies the user that a student should be selected.
2a. The employer doesn’t select the co-op placement form option.
2a.1. The system notifies the user that a form must be selected.
3a. The system loses connection to internet while downloading.
3a.1. The system cancels the download and prompts the user to retry when connected to internet.
Postcondition (for success case): A pdf file of the proof is downloaded. Postcondition (for fail case): The download is canceled and an error message is displayed.
Title: Access Tax-Credit
Actors: Employer
Intention: The intention of the employer is to download the tax credit form as a pdf file using the system.
Precondition: The employer is logged into the system.
Main Scenario:
- The student finishes his/her co-op.
- The employer selects a student and then tax-credit form.
- The employer clicks the download button.
- The file is saved to the user's computer.
Alternatives Scenarios:
1a. Student does not complete his/her co-op.
1a.1. Use case does not apply, ends in failure.
2a. Employer does not select any student.
2a.1. The system notifies the user that a student has to be selected.
Postcondition (for success case): Tax-credit form is successfully downloaded.
Postcondition (for fail case): Tax-credit form is not downloaded.
Title: Get all Coop Placements
Actors: Employer
Intention: The intention of the employer is to get the non-assigned coop placements in the system.
Precondition: The employer is logged into the system.
Main Scenario:
- System generates a list of the non-assigned coop placements.
- Employer receives the list of empty coop placements.
Alternative Scenarios:
1a. All the coop placements are assigned. 2a. Employer gets notified that all coop placements are assigned.
How to run Frontend?
- Once we push to git, the frontend will be automatically depoloyed using Travis
Frontend link: https://coop-frontend-g8.herokuapp.com/
How deploy run Backend?
- Once we push to git, the backend will be automatically depoloyed using Travis
Trying functionalities:
-
Before we get into the website we can follow these steps to test functionality:
-
Creating coopPositions for Google in Backend:
-
- https://coop-backend-g8.herokuapp.com/CoopPosition/100?PositionName=Hardware Intern&CompanyName=Google&startDate=2020-12-12&endDate=2020-12-15
*Creating Student in Backend:
-
Assigning Student to Coop Position in backend:
-
Using Frontend we can create and employer with Company Google
-
Now we can see the Coop Position created in the Coop Position button. Also once we select the coop position, it will display the ID of the student associated with that coop position.