Requirements Model - MatteoNunez22/eventregistration GitHub Wiki
4. Detailed specification of 5 most important use cases
| Use Case ID: | US1 |
|---|---|
| Actors: | Co-op Administrator, Co-op-perator System |
| Description: | Co-op administrator is able to access all files of students and employers, view them and modify any errors or uncertainties |
| Data: | Co-op admin login credentials, searched user’s identity information (name, ID, or email, etc.) |
| Response: | All files corresponding to the searched user |
| Main success scenario: | 1. Co-op Admin logs in 2. System verifies username & password 3. System shows admin its homepage 4. Admin selects student/employ directory 5. Admin searches for wanted student 6. System shows matched results 7. Admin accesses wanted user’s profile 8. Admin views or modifies selected document 9. Admin saves and closes document 10. Modified documents are saved to database |
| Alternative scenarios: | 3a. No results matched keyword entered - 3a.1 Admin enters user’s Id number - 3a.2 Admin enters user’s phone number - 3a.3 Admin enters user’s email address 6a. Admin does not save modified document - 6a.1 System prompts the admin to save file |
| Exceptional scenarios | 1a. Co-op admin cannot log in to the system 3a. Searched user does not exist in the system’s database 7a. Searched user does not have any files in the system’s database 10a. Co-op-perator system cannot communicate with database. |
| Use Case ID: | US2 |
|---|---|
| Actors: | Co-op Administrator, Co-op-perator System |
| Description: | Co-op administrator is able to access all files of students and employers, view them and modify any errors or uncertainties |
| Data: | Co-op admin login credentials |
| Response: | All files corresponding to the searched user |
| Main success scenario: | 1. Co-op Admin logs in 2. System verifies login credentials 3. Admin accesses the statistics page 4. System prompts admin to select one semester 5. System prompts admin to select one semester 6. System shows percentage of incomplete or missing document submissions for chosen semester 7. System shows the rest of useful program statistics like number of successful co-op placements, number of relevant course per co-op, etc |
| Alternative scenarios: | 1a. Admin cannot log in to the system - 1a.1 System lists all student's progress for all semesters 4a. No results matched keyword entered - 4a.1 System lists all student's progress for all semesters |
| Exceptional scenarios | 4b. Co-op-perator system cannot communicate with database. |
| Use Case ID: | US3 |
|---|---|
| Actors: | Co-op Administrator, Co-op-perator System |
| Description: | Co-op administrator is able to track every student's co-op progress in order to detect any problem (missing documents, incomplete forms) and resolve individual cases |
| Data: | Co-op admin login credentials |
| Response: | Co-op progress of all student users in the system |
| Main success scenario: | 1. Co-op Admin logs in 2. System verifies login credentials 3. Admin selects to view student progress for a given semester 4. System lists all student users and their corresponding co-op progress 5. Admin can search for a specific student 6. Admin selects student with problematic progress 7. System shows the student co-op progress (uploaded and missing docs/forms) 8. Admin can choose to contact the student or edit the documents him/herself 9. Modified documents are saved to the database 10. Student's co-op progress is updated |
| Alternative scenarios: | 1a. Admin cannot log in to the system - 1a.1 System can send email to reset forgotten password 5a. No results matched keyword entered - 5a.1 Admin enters user’s Id number - 5a.2 Admin enters user’s phone number - 5a.3 Admin enters user’s email address 8a. Admin does not save modified document - 8a.1 System prompts the admin to save file |
| Exceptional scenarios | 4b. Co-op-perator system cannot communicate with database. |
| Use Case ID: | US4 |
|---|---|
| Actors: | Co-op Administrator, Co-op-perator System |
| Description: | Co-op administrator is able to observe incomplete co-op placements in order to detect late or missing documents submissions |
| Data: | Co-op admin login credentials |
| Response: | Detection of students with incomplete co-op placements (missing documents) |
| Main success scenario: | 1. Co-op Admin logs in 2. System verifies login credentials 3. System notifies admin there are students with incomplete co-op placements 4. Admin accesses list of students with incomplete co-op placements 5. Admin selects a listed student or searches one 6. System shows the student's profile including late or missing document submissions 7. Admin can flag the student as a problematic student or contact him/her |
| Alternative scenarios: | 1a. Admin cannot log in to the system - 1a.1 System can send email to reset forgotten password 5a. No results matched keyword entered - 5a.1 Admin enters user’s Id number - 5a.2 Admin enters user’s phone number - 5a.3 Admin enters user’s email address 7a. Student has no missing document submissions - 7a.1 Admin sets student's status to complete co-op placement |
| Exceptional scenarios | 4b. Co-op-perator system cannot communicate with database. 5b. Searched user is not a problematic student 5c. Searched user does not exist in the system's database |
| Use Case ID: | US5 |
|---|---|
| Actors: | Co-op Administrator, Co-op-perator System, Students |
| Description: | Co-op administrator is able to send reminder to problematic students in order to prevent or notify about late document submissions |
| Data: | Co-op admin login credentials, list of problematic students |
| Response: | Sent reminders and notifications about late submissions |
| Main success scenario: | 1. Co-op Admin logs in 2. System verifies login credentials 3. Admin accesses list of problematic students 4. System lists all students with missing document submissions 5. Admin selects all sutdents that he/she wants to contact 6. Admin chooses to send notification about missing documents or reminder about approaching deadline 7. System sends message to student or notifies by mobile application |
| Alternative scenarios: | 1a. Admin cannot log in to the system - 1a.1 System can send email to reset forgotten password 6a. No results matched keyword entered - 6a.1 Admin enters user’s Id number - 6a.2 Admin enters user’s phone number - 6a.3 Admin enters user’s email address 7a. Admin can access student's profile first and view missing documents first |
| Exceptional scenarios | 2b. Admin entered wrong username/password 3b. System cannot communicate with database and retrieve list of problematic students |
5. Use Case Diagram
