🎯 Objective
The objectives are to streamline administrative processes, reduce manual work, and improve the overall efficiency of managing student attendance load and grouping as following:
Loading attendance to be automated
Grouping of students to be automated
Elective Module selection process to be automated
\uD83D\uDDD2 Requirements List
Change of Grouping: Allow students to choose or change their grouping themselves to avoid manual assignments by admins.
Grouping Criteria: For fresh intake, split alphabetically, and for progression, copy from the previous class code (applies to Pre-U programs with more than one group).
Number of Groups per Student: Implement a view in APSpace Admin showing the number of groups assigned to each student in an intake.
Elective Modules: Allow students to choose or change elective modules themselves, attached to the class code to avoid missing modules.
Load Attendance: Automatically load attendance for late registration students to avoid delays. Notify lecturers when students are auto-loaded.
Attendance Automation: Attendance to be automatically loaded by CTI based on the event list provided by the scheduler.
Bulk Class Setup Changes: Add a new column for intake code and group in bulk class setup.
Script for Student Assignment: Create a script to assign students to each class based on intake.
1. Requirements from CRF
Requirement | User Story | Importance | Jira Issue | Remarks | Meeting Notes | |
---|---|---|---|---|---|---|
1 | Change of grouping - student to be given access to choose/change their own grouping from the system to stop student from asking to exchange grouping for each class of each subject which should be attached to the class code. | Currently the process is done manually and students assigned to each group by admin. If the students, would like to change their grouping, they contact admin currently. | HIGH | https://apiit.atlassian.net/jira/servicedesk/projects/CRF/queues/custom/617/CRF-61 |
Implement number of groups assigned for each student in intake setup to distribute the student in an intake as a view on APSpace Admin (20/02/2024) | |
2 | elective modules - student to choose/change elective module by themselves which should be attached to the class code to avoid any missing modules in the semester. | to reduce the frequency of changing the grouping, elective and load attendance request. |
|
|
| |
3 | load attendance - to avoid delay in loading the attendance for late registration student. auto load is necessary for student not to miss any attendance for classes and not have the necessity to keep informing the lecturer if the new added student in the classes, lecturer to receive auto notification when student is auto load, to also implement the system not to have the lecturer to refresh the system every time new student is auto load. |
|
| |||
4 | Bulk Class Setup Changes:
|
|
2. Flowchart
Current Process
Proposed Process by Admin
\uD83D\uDCCA Success metrics
Goal | Metric |
---|---|
\uD83E\uDD14 Assumptions
Changes in the requirements or team members
Open Questions
Question | Answer | Date Answered |
---|---|---|