E-Learning Portal for Course Management, Enrollment and Online Assessment
Challenge
Systems of this kind are frequently outgrown rather than broken. An early portal built as a set of database forms handles a modest cohort adequately, then fails on scale and customisation: rigid course structures, no separation between catalogue and offering, assessment logic hard-wired to a single question type, and reporting that requires direct queries against production tables. Assessment defines the load profile. Traffic is spiky rather than steady, with an entire cohort starting a timed test in the same minute, so the write path for attempts and answers must be sized for that peak and must survive a lost connection without destroying a candidate response. Student records carry regulatory weight around privacy and access, grade data demands auditability, accessibility conformance to WCAG is an obligation for public institutions, and academic-integrity controls such as question randomisation, pooled banks and attempt limits are design decisions rather than plug-ins.
Systems of this kind are frequently outgrown rather than broken. An early portal built as a set of database forms handles a modest cohort adequately, then fails on scale and customisation: rigid course structures, no separation between catalogue and offering, assessment logic hard-wired to a single question type, and reporting that requires direct queries against production tables. Assessment defines the load profile. Traffic is spiky rather than steady, with an entire cohort starting a timed test in the same minute, so the write path for attempts and answers must be sized for that peak and must survive a lost connection without destroying a candidate response. Student records carry regulatory weight around privacy and access, grade data demands auditability, accessibility conformance to WCAG is an obligation for public institutions, and academic-integrity controls such as question randomisation, pooled banks and attempt limits are design decisions rather than plug-ins.
Solution
The domain separates cleanly into course management, scheduling, enrollment, assessment and a records module, with reporting reading from that data rather than owning it. The distinction that prevents most later pain is between a course as a catalogue entity and a course offering as a scheduled instance, so a syllabus can change without rewriting history and the same course can run across several terms and campuses. Identity federates to the institutional directory through SAML or OpenID Connect, the student information system remains authoritative for person records under an explicit synchronisation contract, and payment runs through a gateway with hosted card capture. Packaged content and assessment items follow SCORM, IMS Common Cartridge or QTI, tools embed through LTI, and activity is captured as xAPI where analytics is required. Grades and credits are held as an append-only history with corrections modelled explicitly, course content lives in object storage behind signed access, and test delivery degrades safely with browser-side buffering and idempotent submission.
The domain separates cleanly into course management, scheduling, enrollment, assessment and a records module, with reporting reading from that data rather than owning it. The distinction that prevents most later pain is between a course as a catalogue entity and a course offering as a scheduled instance, so a syllabus can change without rewriting history and the same course can run across several terms and campuses. Identity federates to the institutional directory through SAML or OpenID Connect, the student information system remains authoritative for person records under an explicit synchronisation contract, and payment runs through a gateway with hosted card capture. Packaged content and assessment items follow SCORM, IMS Common Cartridge or QTI, tools embed through LTI, and activity is captured as xAPI where analytics is required. Grades and credits are held as an append-only history with corrections modelled explicitly, course content lives in object storage behind signed access, and test delivery degrades safely with browser-side buffering and idempotent submission.
Results
A portal built this way is sized for the assessment peak rather than the daily average, keeps the catalogue flexible enough to absorb programme changes without a schema migration, and gives administrators reporting they can trust without touching production tables. Autosave, server-authoritative timing and resumable attempts mean a dropped network does not cost a candidate an attempt. Role-based access separates instructor, administrator and registrar capabilities instead of relying on a single privileged account, and the specifications that usually consume the most effort late, such as prerequisite rules, withdrawal handling and retake policy, are settled before implementation.
A portal built this way is sized for the assessment peak rather than the daily average, keeps the catalogue flexible enough to absorb programme changes without a schema migration, and gives administrators reporting they can trust without touching production tables. Autosave, server-authoritative timing and resumable attempts mean a dropped network does not cost a candidate an attempt. Role-based access separates instructor, administrator and registrar capabilities instead of relying on a single privileged account, and the specifications that usually consume the most effort late, such as prerequisite rules, withdrawal handling and retake policy, are settled before implementation.