diff --git a/Requirements Table - Student Scheduler System.html b/Requirements Table - Student Scheduler System.html new file mode 100644 index 0000000..a6b673b --- /dev/null +++ b/Requirements Table - Student Scheduler System.html @@ -0,0 +1,398 @@ + + +
+ + +| Ref | +Category | +Function | +Requirement | +Definition / Measure | +Priority | +
|---|---|---|---|---|---|
| 4.1 STUDENT RECORD MANAGEMENT | +|||||
| 4.1.1 | +Student Management | +Create Student | +Enable teachers to create new student records with mandatory fields | +System must capture: Student ID, Full Name, Date of Birth, Grade Level, Emergency Contact | +Mandatory | +
| 4.1.2 | +Student Management | +Read/Search Student | +Enable teachers to search and view student records by multiple criteria | +Search by: Name, Student ID, Grade, Class. Results must display within 3 seconds for up to 1000 records | +Mandatory | +
| 4.1.3 | +Student Management | +Update Student | +Enable teachers to modify existing student information | +All editable fields clearly marked. System must save previous version for audit trail | +Mandatory | +
| 4.1.4 | +Student Management | +Delete/Archive Student | +Enable authorized users to remove or archive student records | +Soft delete implementation. Records marked inactive rather than physically deleted. Confirmation required | +Mandatory | +
| 4.1.5 | +Student Management | +Bulk Student Import | +Enable bulk creation/update of student records via CSV upload | +System must validate CSV format, report errors, and provide summary of imported records | +Highly Desirable | +
| 4.1.6 | +Student Management | +Student Photo Management | +Enable teachers to upload and manage student photos | +Support JPG/PNG up to 5MB. Automatic resizing for display. Optional feature for attendance verification | +Desirable | +
| 4.1.7 | +Student Management | +Medical Information Tracking | +Enable recording of basic medical information for emergency purposes | +Allergies, medications, emergency contacts. Access restricted to authorized personnel only | +Desirable | +
| 4.2 CLASS SCHEDULE MANAGEMENT | +|||||
| 4.2.1 | +Schedule Management | +Create Class Schedule | +Enable teachers to create new class schedules with time slots | +Must include: Subject, Room, Time, Days, Maximum Students, Teacher assignment | +Mandatory | +
| 4.2.2 | +Schedule Management | +View Schedule Conflicts | +System must detect and highlight scheduling conflicts | +Real-time validation of: Teacher double-booking, Room double-booking, Student schedule conflicts | +Highly Desirable | +
| 4.2.3 | +Schedule Management | +Update Schedule | +Enable modification of existing schedules | +Changes must notify affected students/teachers. Historical changes logged | +Mandatory | +
| 4.2.4 | +Schedule Management | +Delete Schedule | +Enable removal of class schedules | +Cascade delete of student enrollments with proper notifications and confirmation | +Mandatory | +
| 4.2.5 | +Schedule Management | +Recurring Schedule Patterns | +Enable creation of repeating schedule patterns (weekly, bi-weekly) | +Create once, apply pattern. Easy modification of individual instances in series | +Desirable | +
| 4.2.6 | +Schedule Management | +Room Resource Management | +Enable tracking of classroom resources and equipment | +Link specific equipment to rooms. Check availability for special classes (science labs, computer rooms) | +Desirable | +
| 4.3 USER AND ACCESS MANAGEMENT | +|||||
| 4.3.1 | +Security | +User Authentication | +Require secure login for all system access | +Username/password with minimum complexity requirements. Session timeout after 30 minutes inactivity | +Mandatory | +
| 4.3.2 | +Security | +Role-Based Access Control | +Implement different permission levels for different user types | +Roles: Teacher (CRUD on assigned classes), Admin (full CRUD), View-Only (read-only) | +Highly Desirable | +
| 4.3.3 | +Security | +Audit Trail | +Log all CRUD operations with user and timestamp | +Each record modification must store: Who, What, When, Previous Value, New Value | +Highly Desirable | +
| 4.3.4 | +Security | +Two-Factor Authentication | +Optional 2FA for administrative accounts | +SMS or authenticator app verification for sensitive operations | +Desirable | +
| 4.4 REPORTING AND ANALYTICS | +|||||
| 4.4.1 | +Reporting | +Class Attendance Reports | +Generate attendance reports for classes and individual students | +Weekly/monthly summaries. Export to PDF/Excel. Filter by date range and teacher | +Highly Desirable | +
| 4.4.2 | +Reporting | +Student Performance Tracking | +Track and report student grades and attendance patterns | +Visual charts showing trends. Early warning for at-risk students based on attendance | +Desirable | +
| 4.4.3 | +Reporting | +Teacher Workload Analysis | +Analyze and report teacher schedule load and distribution | +Hours per week, class distribution, identify overloaded teachers | +Desirable | +
| 5.0 NON-FUNCTIONAL REQUIREMENTS | +|||||
| 5.1 | +Performance | +Response Time | +All CRUD operations must complete within 2 seconds for up to 100 concurrent users | ++ | |
| 5.2 | +Performance | +Availability | +System must be available 99% during school hours (8:00-18:00 Monday-Friday) | ++ | |
| 5.3 | +Usability | +User Interface | +Interface must be intuitive for non-technical teaching staff. Maximum 2 clicks to common functions | ++ | |
| 5.4 | +Data Integrity | +Data Validation | +All data inputs must be validated before processing. Invalid data rejected with clear error messages | ++ | |
| 5.5 | +Security | +Data Protection | +Student personal data must be encrypted at rest. Access logs maintained for 1 year | ++ | |
| 5.6 | +Compatibility | +Multi-language Support | +System interface available in Russian and English | +Teachers can switch between languages. Student data stored in original language | +|