System Requirements Document for E-learning and Student Records Management

 Contents 

1. Introduction 3 

2. Functional Requirements 3 

3. Non-Functional Requirements 4 

4. Use Cases 5 

 

 

1. Page BreakIntroduction 

This document will present the requirements for the eLearning and Student Records Management solution for ABC University.  

The university has over 1000 students in various disciplines, courses and programs, supported by over 300 staff including Professors, Administration, Management, and other personnel. This solution in point is being built with the purpose of serving as a one stop shop for all students’ academic needs and providing the university management a system to keep track of and manage the student records. Another objective is to improve the university management productivity through automation and make it easier to effectively utilize the resources. 

This should be an intuitive, easy to operate system using which the students can enroll in courses, update their details, request for marksheets, access e-Learning content, the professors can keep track of students’ progress and the management can maintain student records effectively.  

2. Functional Requirements 

The functional requirements for the e-Learning and Student Records Management system are as follows: 

#	Requirement	Ranking
1	The system should enable the University Administration to create accounts for new users and update details of existing users	High
2	The system should enable Administration to create and manage e-Learning content in the system	Medium
3	The system should enable Administration to add/update/delete Student records to/from the system	High
4	The system should enable Professors to edit and add e-Learning content for the courses they teach	Low
5	The system should enable Professors to update students’ progress for the courses they teach	Low
6	The system should enable students to access e-Learning content for the courses/programs they have enrolled in	Medium
7	The system should enable students to keep track of their progress in the courses they have enrolled into	Medium
8	The system should enable Professors, Students and other personnel to update/change their password in case they forget it or want to change their password	Low
9	The professors should be able to add/remove courses and add/update related content for courses that they offer in the university	Medium
10	The student should be able to access the details of and enroll in the different courses available for enrollment in the university	Medium

 

3. Non-Functional Requirements  

The non-functional requirements for the e-Learning and Student Records Management system are as follows: 

#	Non-Functional Requirement	Priority
1	The response time SLA for the system should be 1 second	High
2	The system should implement NIST web server security	High
3	The system should meet 99% Availability SLA	Medium
4	The system should comply with web component accessibility guidelines	Medium
5	The system should implement scalability to support future growth prospects, and should be capable enough to offer at least 20% over the peak load	Low

 

4. Use Cases 

 

Enroll into a Course | Use Case ID: UC#11 | Priority: High
Actor	Student
Description	This use case describes student can lookup a course he wants to enroll to and complete online application for the said course
Trigger	Student decides to apply for the desired course
Type	External
Pre-Conditions	The system is up  The student is registered and logged in   The course has vacant seats
Normal Course	Student searches for the desired course using the Search ption on the Top right of the Homepage   Student clicks on the desired course from the list of matching courses displayed in response to the Search query   Student is presented with the online application form   Student completes the application form for the desired course by entering his information  Student submits the application form  An email is triggered to the professor and copy to the Admin office about the new application for the course
Post-Conditions	The course application is submitted  The Professor and the admin receive the application through email and they take the necessary action depending on whether there is a vacancy in the course at the moment of receival of the application

 

Change Password | Use Case ID: UC-17 | Priority: Low
Actor	All users
Description	This use case talks about how the eLearning system user can reset their password
Trigger	Customer wants to change his password
Type	External
Pre-Conditions	The system is up  The user has an email ID r a phone number stored in the system
Normal Course	User enters his login ID on the Homepage  User clicks on the Change Password link on the Login Page  The system send an OTP to his email and/or phones number   The user enters the OTP in the field and clicks Submit   The system asks the user to enter the new password and re-enter in the comparison field  The user gets confirmation  The User is redirected to the Login page
Post-Conditions	User’s password is updated