Skip to main content

Curriculab — System Overview

Purpose and Scope

This document describes the scope of Curriculab, a comprehensive university registration and management platform that supports the full lifecycle of student registration, course management, academic records, billing, and institutional reporting.

Curriculab serves students, faculty, academic staff, advisors, registrars, and administrators. It integrates with external systems (financial aid, housing, library) and exposes a REST API for authorized third-party consumers.

All detailed functional requirements are captured as user stories in the documents listed in the Feature Area Index below.


User Roles

RoleDescriptionKey Permissions
StudentEnrolled learnerRegister for courses, view records and grades, pay bills, manage personal preferences
InstructorFaculty member teaching a sectionUpload materials, post announcements, submit grades, view enrollment roster
Academic StaffDepartment staff managing coursesCreate/update/retire courses and catalogue entries, manage schedules and prerequisites
AdvisorAcademic advisorView student records, override enrollment restrictions, approve registration exceptions
RegistrarManages registration windows and deadlinesDefine academic terms, set registration open/close and add/drop dates, manage waitlist rules
AdministratorSystem/registrar admin with full accessAll permissions above plus user management, system configuration, data backup/restore, audit logs

Feature Area Index

#Feature AreaDocumentStory PrefixStories
1User Authentication & Authorizationuser-authentication-requirements.mdAUTHAUTH-001 – AUTH-010
2Course Cataloguecourse-catalogue-requirements.mdCATCAT-001 – CAT-005
3Course Managementcourse-management-requirements.mdCOURSECOURSE-001 – COURSE-009
4Course Capacitycourse-capacity-requirements.mdCAPCAP-001 – CAP-006
5Course Waitlistscourse-waitlists-requirements.mdWAITWAIT-001 – WAIT-008
6Student Registrationstudent-registration-requirements.mdREGREG-001 – REG-006
7Semester & Session Managementsemester-session-requirements.mdSEMSEM-001 – SEM-006
8Academic Recordsacademic-records-requirements.mdRECREC-001 – REC-008
9Payment & Billingpayment-billing-requirements.mdPAYPAY-001 – PAY-006
10Reportingreporting-requirements.mdRPTRPT-001 – RPT-005
11Integrationsintegration-requirements.mdINTINT-001 – INT-005
12Accessibilityaccessibility-requirements.mdACCACC-001 – ACC-005
13Security & Privacysecurity-privacy-requirements.mdSECSEC-001 – SEC-005
14Notificationsnotifications-requirements.mdNOTIFNOTIF-001 – NOTIF-005
15Support & Helpsupport-help-requirements.mdSUPSUP-001 – SUP-005
16Student Profile & Account Managementstudent-profile-requirements.mdPROFPROF-001 – PROF-006
17Degree Programs & Curriculum Managementdegree-programs-requirements.mdDEGDEG-001 – DEG-006
18Room & Facility Managementroom-facility-requirements.mdROOMROOM-001 – ROOM-005
19Administrative User Managementadmin-user-management-requirements.mdUSRUSR-001 – USR-006
20Academic Advisingacademic-advising-requirements.mdADVADV-001 – ADV-006
21Graduation & Commencementgraduation-commencement-requirements.mdGRADGRAD-001 – GRAD-006
22Transfer Credit Evaluationtransfer-credit-requirements.mdXFERXFER-001 – XFER-005
23Document Managementdocument-management-requirements.mdDOCDOC-001 – DOC-005

Cross-Cutting Concerns

The following concerns span multiple feature areas and are each owned by a dedicated requirements document:

  • Security & Privacy — Data encryption, FERPA/GDPR compliance, backups, and retention policy are defined in security-privacy-requirements.md.
  • Accessibility — WCAG 2.1 AA compliance, keyboard navigation, screen reader support, and responsive design are defined in accessibility-requirements.md.
  • Notifications — Email, SMS, and in-system notification rules are defined in notifications-requirements.md. Individual feature documents cross-reference this doc rather than defining notification behavior independently.
  • Deduplication — Waitlist behavior is the single source of truth in course-waitlists-requirements.md. The course capacity and course management docs cross-reference it rather than duplicating waitlist stories.