Waterfall SDLC Documentation for a University Course Registration & Scheduling Web Portal
Document progressPage 4 of 12
View full document4. Acceptance Criteria and Requirements Traceability
Acceptance Criteria
- AC-01 for FR-03: given an active academic term, when a student searches by subject and availability, only matching sections are displayed with essential section details.
- AC-02 for FR-06: given two sections with overlapping meeting periods, when the student attempts to register for both without an approved override, the second registration is rejected with a conflict explanation.
- AC-03 for FR-07: given a course requiring a prerequisite the student has not satisfied, registration is rejected unless an authorized prerequisite override is present.
- AC-04 for FR-08: given a section with zero available seats, normal registration is rejected and seat availability is not reduced below zero.
- AC-05 for FR-09: given a student outside the permitted registration period, add/drop actions are unavailable or rejected by the server.
- AC-06 for FR-10: after successful registration, the enrollment record exists, section availability is updated, the student's schedule includes the section, and an audit event is recorded.
- AC-07 for FR-11: after an eligible drop, the enrollment is removed or transitioned according to the approved data model, capacity is updated, and an audit event is recorded.
- AC-08 for FR-13: only authorized registrar users can create an override, and the action records actor, reason, student, section, type, and timestamp.
- AC-09 for NFR-08: critical registration workflows can be completed with a keyboard and all actionable controls expose understandable labels.
- AC-10 for NFR-10: if registration persistence fails, no partial enrollment or seat-count update remains committed.
Requirements Traceability Matrix
| ID | Design Component | Test Case | Acceptance |
|---|---|---|---|
| FR-03 | Search API + Search UI | TC-03 | AC-01 |
| FR-06 | Registration Rules Service | TC-06 | AC-02 |
| FR-07 | Prerequisite Validator | TC-07 | AC-03 |
| FR-08 | Enrollment Transaction | TC-08 | AC-04 |
| FR-09 | Registration Window Guard | TC-09 | AC-05 |
| FR-10 | Enrollment Service | TC-10 | AC-06 |
| FR-11 | Drop Service | TC-11 | AC-07 |
| FR-13 | Registrar Override Module | TC-13 | AC-08 |
| NFR-08 | Accessible UI Components | TC-21 | AC-09 |
| NFR-10 | Transaction Boundary | TC-22 | AC-10 |
Traceability Rules
- Every approved functional requirement must map to at least one design component.
- Every requirement that can be verified must map to one or more test cases.
- Every change request must identify affected requirement IDs, designs, implementation components, tests, documentation, and schedule impact.
- No mandatory requirement may be marked complete until its linked tests pass and required acceptance evidence exists.
Requirements Approval Record
The requirements baseline is assigned version SRS-1.0. Any modification after sign-off requires an approved change request rather than an undocumented edit.