ความคืบหน้างาน ไฟล์ต้นฉบับ

08 — Non-Functional Requirements

Proposal §5.3 has not been written for TNSU yet. Its current content is leftover template text from another project, so ignore it. No numeric targets (availability, performance, retention) exist for TNSU yet.

Stated in the proposal (TNSU sections)

AreaRequirementSource
Access controlRole-based permissions scoped by unit (campus / school), education level and role§1.1, §4.1, §4.9
AuditRecord usage history§3.3 (8), §4.1 TNSU-11
TraceabilityRequests and documents have status tracking and are auditable after the fact§2.1
Finance auditabilityFinancial and scholarship transactions can be checked retroactively§8.1
AI permissionsThe AI Bot answers within the user's permissions§2.1, §3.3
Responsive and accessible UI§4.10
ExtensibilityAdd modules and integrations without disrupting the core§1.1, §8.1
KPI integrityKPIs are computed from system data§8.2

Stated in the use cases (12-use-cases.md)

AreaRequirementUC
Separation of dutiesSoD-01…18 rules; maker ≠ checker ≠ approver for finance, policy, grades and admission overridesW-01, W-02, W-15, W-74, W-122, …
4-eyesPolicy publishing, data fixes, pickup by others, caregiver certification, break-glass reviewW-15, W-137, W-13, W-160, W-14
Privileged accessJIT PAM, break-glass accounts, periodic access recertification, MFA reset with identity proofingW-124, W-125, W-126, W-142
Tamper evidenceSigned hash snapshots of approved grade sets and submissions; WORM before/after for data fixesW-01, W-35, W-137
Health dataSeparate hlt_vault; access only through a care relationship; 2-person approval (lead physician + DPO) otherwise; every read loggedW-14, W-39
Safeguarding casesRestricted to the assigned team; alleged persons and their line managers excluded; every read auditedW-22
PDPAConsent per purpose and version with expiry and revocation; data-subject requests via ThaID; no PII in notification payloads; bulk-export approvalW-128, W-21, W-36, W-138
MinorsGuardian co-sign by DMN age rule; minor mode UI; guardian is called before message for injuries; urgent auto-alert if no answer within 15 minW-03, W-39, M01
Registration loadVirtual waiting room, synchronous transaction with idempotency key, reloadable result page, no double-submitW-49
TimelinessAdmission clearing job every 5 min, waitlist call within 15 min, offers only 07:00–20:00; safeguarding intake within 24 hW-74, W-22
Change controlChange freeze and capacity check around registration; term rollover dry runW-122
Records managementDocument destruction / archive transfer; retention adjusted on status changeW-40, W-133

Domain-specific sensitivities [inferred]

  • Minors (sports-school students, ม.1–ม.6, and university applicants under 20): health, dorm entry/exit, custody and guardian data are highly sensitive (PDPA §26 for health).
  • Financial data: keep card data with the payment provider. Do not store card data.
  • Peak loads: registration windows and admission clearing across ~18k learners and 30 units.

Open

Availability, performance, data-retention periods, backup/DR and hosting are [unknown] and must be agreed with TNSU.