Raisd CMS

Canonical Raisd product surface: the Student portal demo, logical ERD/DFD for all portals, and the bridge to the existing campus CMS. These are not a copy of the LUCT CMS physical schema — legacy tables stay behind the CAP-53 anti-corruption layer.

Student portal demo Logical / contract model Demo ≠ Live CMS writes

Student portal — capabilities CAP map, demo status, where each feature lives Student portal — screenshots 19 desktop captures of the current demo UI Student portal — use guides Step-by-step paths for registration, fees, forms, and more Student portal — user manual Every screen, rule and limit for students, plus troubleshooting Entity Relationship Diagrams Institution, curriculum, delivery, student journey, finance, integration Data Flow Diagrams Context, ACL, auth, admissions, registration workflow, teaching Architecture SoR ownership, CAP-53 ACL, SDD & ADR catalogue LUCT physical ERD Legacy Cyberjaya tables — discovery only, not the Raisd model

How this relates to LUCT CMS

Surface	Role
Raisd CMS (this section)	Student portal product docs, canonical portal contracts, clean domain ERD/DFD
LUCT CMS	Existing Cyberjaya SoR this phase; physical tables, desks, batches
CAP-53	Anti-corruption / Portal API boundary between the two