The OES is designed to allow students to enrol in their subjects, check academic details, and monitor their enrolment status without having to step foot on campus. In theory, this system should make enrolment easier and less stressful. However, as many students—including myself—have experienced, the reality of using the system during actual enrolment periods can be very different.
As an Information Technology student, using the Online Enrolment System felt like more than just completing a requirement. While trying to enrol like everyone else, I found myself paying attention to how the system responded, especially when things did not go as planned. This blog shares my experience with the OES, highlighting what worked well, what caused frustration, and what could be improved from a student and IT perspective.
First Impressions and General Experience
At first glance, the Online Enrolment System looked clean and fairly easy to navigate. Important information such as enrolled subjects, academic details, and enrolment status was displayed clearly on the dashboard. The process of selecting subjects and requesting advising did not feel overwhelming, especially for students who were already familiar with the system.
However, this smooth experience did not always last. As enrolment days went on and more students accessed the system at the same time, issues started to appear. Pages took longer to load, and some actions required multiple attempts before they went through. At first, I assumed the problem might be my internet connection, but after hearing similar complaints from other students, it became clear that the system was struggling to handle heavy traffic.
What the System Does Well
One of the biggest advantages of the Online Enrolment System is convenience. Being able to enrol from home saves time, effort, and transportation costs. Students no longer need to line up on campus just to submit forms or confirm their schedules, which is a huge improvement compared to the traditional enrolment process.
The system also benefits from automation. It automatically checks prerequisites, computes total units, and updates enrolment records. When these features work properly, they help prevent mistakes that usually happen with manual processing. From an IT standpoint, this shows that the system has a solid foundation in terms of logic and database integration.
Another useful feature is centralized access to academic information. Having grades, subject availability, and enrolment status in one place makes it easier for students to track their progress without constantly asking for updates from different offices.
Frustrations and System Limitations
Despite its strengths, the OES also had several frustrating moments. One common issue was how the system handled errors and schedule conflicts. In some cases, conflicts were only detected at the very end of the enrolment process. After carefully selecting subjects, being told that there was a conflict—without clear guidance on how to fix it—was both confusing and time-consuming.
Another problem was the lack of flexibility when issues occurred. Once an error was detected, enrolment could not proceed at all. There was no option to submit the enrolment as “pending” or have the issue reviewed within the system. This forced students to wait for manual intervention, which defeated the purpose of having an online system in the first place.
From an IT student’s perspective, these issues felt less like user mistakes and more like design limitations. A system that guides users away from errors, instead of stopping them at the end, would create a much better experience.
Performance During Peak Enrolment
System performance became a major concern during peak enrolment hours. When many students logged in at the same time, the system slowed down significantly. Pages took a long time to load, and some processes seemed to freeze altogether.
This experience highlighted how important scalability and performance testing are for systems expected to handle heavy traffic. Enrolment happens within a limited time frame, so the system needs to be prepared for sudden spikes in usage. Without proper optimization and stress testing, even a well-designed system can struggle when it matters most.
What Could Be Improved
Based on my experience, there are several ways the Online Enrolment System could be improved. Clearer and more helpful error messages would make a big difference. Instead of generic alerts, the system should explain what went wrong and what steps students can take next.
The system would also benefit from real-time validation. Detecting conflicts as subjects are selected—rather than at the final step—would save time and reduce frustration. Adding a provisional or pending enrolment status could also help students move forward while issues are being reviewed.
Lastly, improving system performance during peak hours should be a priority. This could involve better server management, optimized database queries, or more thorough load testing before enrolment begins. Regular feedback from students after each enrolment period could also help guide future updates.
Final Thoughts
The Online Enrolment System is a clear step toward modernizing enrolment at the University of Southeastern Philippines. It offers convenience, accessibility, and automation that traditional enrolment methods simply cannot provide.
However, my experience shows that the system still has room to grow. Performance issues, limited flexibility, and unclear error handling affected many students during enrolment. As an IT student, I see these challenges not just as frustrations, but as reminders that technology is always a work in progress. With continuous improvement and user-focused design, the Online Enrolment System has the potential to become a smoother and more reliable platform in the future.
No comments:
Post a Comment