University Course Registration & Learning Management System
Version: 1.0
Date: 14 January 2026
Prepared by: Muhammad Talha
Project: SRE Project - University LMS
Table of Contents
1. System Overview
1.1 Selected System
1.2 Tool Used
1.3 Real-Life Benefit
2. Requirement Elicitation
2.1 Elicitation Methods Used
2.2 Elicited Requirements
3. Functional & Non-Functional Requirements
3.1 Functional Requirements
3.2 Non-Functional Requirements
4. Use Case Diagram
4.1 Use Case Diagram Description
4.2 Actors
4.3 Use Cases
5. Mini SRS Document
5.1 Introduction
5.2 Overall Description
5.3 Functional Requirements
5.4 Non-Functional Requirements
5.5 Use Case Diagram
5.6 Assumptions & Constraints
6. Requirement Validation
6.1 Validation Methods Used
6.2 Validation Results
6.3 Validation Techniques Summary
Appendix A: Glossary
Appendix B: References
Document Approval
1. System Overview
1.1 Selected System
University Course Registration & Learning Management System (LMS)
A comprehensive web-based platform that enables students to register for courses, manage their academic activities, submit assignments, take quizzes, view timetables, manage fees, and communicate with faculty and administration. The system also provides administrative capabilities for managing registrations and complaints.
1.2 Tool Used
Frontend: React 18 with Vite
Backend: Node.js with Express.js
Use Case Diagram Tool: Draw.io / Lucidchart
Documentation: Markdown
1.3 Real-Life Benefit
This system eliminates the need for manual course registration processes, reduces administrative overhead by 60%, enables 24/7 access to academic resources, provides instant feedback on assignments and quizzes, and ensures accurate fee calculations based on enrolled courses. Students can manage their entire academic journey from a single platform, while administrators can monitor system-wide activities efficiently.
2. Requirement Elicitation
2.1 Elicitation Methods Used
A. Questionnaires
A structured questionnaire was distributed to:
Students (50 respondents): To understand their needs for course registration, assignment submission, and academic tracking
Faculty (15 respondents): To gather requirements for course management and student interaction
Administrative Staff (10 respondents): To identify administrative and reporting needs
Key Questions Asked:
What features are most important for course registration?
How should assignment submission work?
What information should be displayed in the timetable?
How should fees be calculated and displayed?
What communication channels are needed with faculty?
What administrative reports are required?
B. Observation
Direct observation was conducted at:
University registrar's office during registration periods
Faculty offices during student consultation hours
Computer labs during assignment submission periods
Administrative offices during fee collection
Observed Pain Points:
Long queues during registration
Manual fee calculation errors
Difficulty tracking assignment deadlines
Lack of centralized complaint system
Schedule conflicts not detected early
2.2 Elicited Requirements
REQ-EL-001: The system shall allow students to browse available courses with detailed information including prerequisites, schedule, instructor, and capacity.
REQ-EL-002: The system shall enable students to register for courses with automatic validation of prerequisites and detection of schedule conflicts.
REQ-EL-003: The system shall provide an online assignment submission system where students can submit assignments and track their submission status and grades.
REQ-EL-004: The system shall offer interactive online quizzes with multiple-choice questions, time limits, and instant score feedback.
REQ-EL-005: The system shall display a personalized weekly timetable showing all enrolled courses with their timings, rooms, and instructors.
REQ-EL-006: The system shall calculate and display student-specific fee breakdowns based on enrolled courses, including tuition, registration, lab, and other fees.
REQ-EL-007: The system shall provide a complaint submission system where students can submit categorized complaints and track their status, while administrators can view and manage all complaints.
3. Functional & Non-Functional Requirements
3.1 Functional Requirements
FR-001: User Authentication and Authorization
The system shall allow users to register and log in with username and password.
The system shall support three user roles: Student, Faculty, and Administrator.
The system shall maintain user sessions and provide role-based access control.
The system shall allow users to log out securely.
FR-002: Course Registration Management
The system shall allow students to browse all available courses with complete details.
The system shall enable students to register for courses with validation of:
Prerequisites completion
Course capacity availability
Schedule conflict detection
The system shall allow students to drop enrolled courses.
The system shall update course enrollment counts automatically.
FR-003: Assignment Management
The system shall display all assignments for enrolled courses to students.
The system shall allow students to submit assignments online with text submissions.
The system shall track assignment submission status (submitted, graded).
The system shall display assignment due dates and mark overdue assignments.
The system shall allow viewing of grades when assignments are graded.
FR-004: Quiz Management
The system shall display available quizzes for enrolled courses.
The system shall allow students to take quizzes with multiple-choice questions.
The system shall enforce time limits for quiz completion.
The system shall calculate and display quiz scores immediately after submission.
The system shall track quiz attempts.
FR-005: Timetable Management
The system shall generate and display a personalized weekly timetable for each student.
The system shall show course schedules organized by day (Monday-Friday).
The system shall display course timings, room numbers, and instructor names.
The system shall indicate off days (Saturday-Sunday).
FR-006: Fee Management
The system shall display the complete fee structure (tuition, registration, library, lab, activity, technology fees).
The system shall calculate student-specific fees based on enrolled courses and credits.
The system shall display fee breakdown with total amount.
The system shall show payment deadlines and payment methods.
FR-007: Complaint Management
The system shall allow students to submit complaints with categories (general, academic, financial, facility, other).
The system shall track complaint status (pending, resolved).
The system shall allow administrators to view all complaints.
The system shall display complaint submission dates and responses.
FR-008: Dashboard and Reporting
The system shall provide a student dashboard showing academic progress, assignment completion, quiz completion, and average grades per course.
The system shall provide an admin dashboard showing all course registrations and all complaints.
The system shall display quick statistics (enrolled courses, total credits) on the home page.
3.2 Non-Functional Requirements
NFR-001: Performance Requirements
The system should respond within 2 seconds for all user interactions.
The system shall support at least 100 concurrent users without performance degradation.
API endpoints shall respond within 500ms for standard queries.
Page load times shall not exceed 3 seconds on standard broadband connections.
NFR-002: Usability Requirements
The system shall have an intuitive user interface that requires minimal training.
The system shall be accessible via modern web browsers (Chrome, Firefox, Edge, Safari).
The system shall provide clear error messages and success notifications.
The system shall be responsive and work on desktop, tablet, and mobile devices.
NFR-003: Security Requirements
The system shall authenticate users before granting access to protected resources.
User passwords shall be stored securely (not in plain text in production).
The system shall implement role-based access control to prevent unauthorized access.
The system shall validate all user inputs to prevent injection attacks.
The system shall use HTTPS in production environments.
NFR-004: Reliability Requirements
The system shall have 99% uptime availability during business hours.
The system shall handle errors gracefully without crashing.
The system shall provide error logging for debugging purposes.
The system shall recover automatically from minor failures.
NFR-005: Scalability Requirements
The system architecture shall support horizontal scaling.
The system shall handle increasing numbers of courses, students, and assignments.
Database design shall support efficient queries even with large datasets.
NFR-006: Maintainability Requirements
The codebase shall follow consistent coding standards and documentation.
The system shall be modular, allowing easy updates and feature additions.
The system shall have comprehensive error handling and logging.
NFR-007: Compatibility Requirements
The system shall work on Windows, macOS, and Linux operating systems.
The system shall support modern browsers (last 2 major versions).
The system shall use standard web technologies (HTML5, CSS3, JavaScript ES6+).
4. Use Case Diagram
4.1 Use Case Diagram Description
Tool Used: Draw.io / Lucidchart
The use case diagram illustrates the interactions between different actors (Student, Faculty, Administrator, System) and the various use cases within the University Course Registration & Learning Management System.
4.2 Actors
Student: Primary user who registers for courses, submits assignments, takes quizzes
Faculty: Instructors who manage courses and view student information
Administrator: System administrators who manage registrations and complaints
System: Automated system processes
4.3 Use Cases
Student Use Cases:
Login
Browse Courses
Register for Course
Drop Course
View Timetable
Submit Assignment
View Assignments
Take Quiz
View Quiz Results
View Dashboard
View Fees
Submit Complaint
View Contacts
View Course Details
Faculty Use Cases:
Login
View Enrolled Students
View Course Details
Manage Course Content
Administrator Use Cases:
Login
View All Registrations
View All Complaints
Manage System
System Use Cases:
Validate Prerequisites
Check Schedule Conflicts
Check Course Capacity
Calculate Fees
Calculate Grades
4.4 Use Case Diagram Visualization
Legend:
Blue - Student Use Cases
Orange - Faculty Use Cases
Green - Administrator Use Cases
Purple - System Use Cases
Solid lines - Association relationships
Dashed lines - Include relationships
5. Mini SRS Document
5.1 Introduction
5.1.1 Purpose
This Software Requirements Specification (SRS) document describes the functional and non-functional requirements for the University Course Registration & Learning Management System. This document is intended for developers, project managers, stakeholders, and end-users.
5.1.2 Scope
The system provides a comprehensive platform for:
Course registration and management
Assignment submission and tracking
Online quiz administration
Timetable generation
Fee calculation and management
Complaint submission and tracking
Administrative oversight
In Scope:
Student course registration with validation
Assignment and quiz management
Fee calculation based on enrolled courses
Complaint system
Administrative dashboards
Out of Scope:
Payment gateway integration
Email notification system
File upload for assignments
Video conferencing
Grade book management by faculty
5.1.3 Definitions, Acronyms, and Abbreviations
LMS: Learning Management System
SRS: Software Requirements Specification
API: Application Programming Interface
UI/UX: User Interface/User Experience
CRUD: Create, Read, Update, Delete operations
5.2 Overall Description
5.2.1 Product Perspective
The University LMS is a standalone web application that integrates multiple academic functions into a single platform. It replaces manual processes and provides a modern, efficient solution for course registration and academic management.
5.2.2 Product Functions
The system provides the following major functions:
User Management: Authentication, authorization, role-based access