Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
E learning app Software requirements specification
Typology: High school final essays
1 / 16
This page cannot be seen from the preview
Don't miss anything!
2 | P a g e
The basic purpose of this document is to present the detailed requirements E learning system. Student and Teacher are the main parts of this system. By building this system we will facilitate the student and the Tutors. Through this system the Student can learn academic courses. Teachers can easily upload the video lectures and can put the price of whole course. Student can also enroll by paying the amount of course and at the end of the Course they will be certified by the system and Approved by the teacher, Teachers can see the number of students of the course they will receive the payment and the system will deduct its fee for the course because it is providing a facility to the teacher and students. Students can pay through various sources. And there is admin also who can manage all the courses that teacher has uploaded and can rank them according to the criteria. Admin can manage the students record and update and delete their data of study.
The purpose of this Requirements Elicitation documents is to provide a clear understanding what is actually Online Learning system and to identify the critical requirements essential for the projects successful completion. These requirements provide an abstract overview of the Online Learning system and provides a general overview of the entire project. This SRS describes the software requirements both functional and non-functional for the System (E-Learning Sytem). This document is intended to be used by the members of the project team that will implement and verify the correct functioning of the system. All requirements specified here are unless stated otherwise. This document will be used in all phases of Software Process.
This document is intended for providing an abstract overview of Online Learning system and general overview of entire project. It will give the access to the student and the Teacher to share their important data and to do all activities between student and Teachers related to study safely. The scope of this document:
4 | P a g e Manage Profile: The user must be able to edit the profile from the setting they should perform various changes to the profile. Search Courses: The Student Should be able to search the course on the Software he must have access to see every course on the system. Manage Courses: The Teacher Must Edit the Courses he should update, Delete, Add the videos to his various courses. Top Rated Courses: The System Should show the top-rated course of all time in the system. Interest Category: The System should show the courses to the use according to his area of interest. Submit Ratings: The Student must be able to rate the according to his experience. And should provide the feedback in detail. Logout: The user must log out from the system when he wants to. 2.2 Non-Functional Requirements Security: The system needs to log client’s information of registration such as IP address and time for security purpose. Password should encrypt and store in the database. Maintainability: The system developing using Struts, all action is detailed in struts-config.xml and web.xml that easy to modify and make update. Portability: The web application is coding in J2EE and Struts, therefore, it should be transferable between different OS and Java container Usability: The system shall allow the users to access the system from the Internet using HTML or its derivative technologies. The system uses a web browser as an interface. Since all users are familiar with the general usage of browsers, no specific training is required. The system is user friendly and self-explanatory. Reliability: The system has to be very reliable due to the importance of data and the damages incorrect or incomplete data can do. Availability: The system is available 100% for the user and is used 24 hours a day and 365 days a year. The system shall be operational 24 hours a day and 7 days a week. Mean Time between Failures (MTBF) The system will be developed in such a way that it may fail once in a year. Mean Time to Repair (MTTR) Even if the system fails, the system will be recovered back up within an hour or less.
5 | P a g e Accuracy The accuracy of the system is limited by the accuracy of the speed at which the Student can use the system without any worry. Access Reliability The system shall provide 100% access reliability
Actors:
7 | P a g e
Object Classes:
8 | P a g e
Log in: Actors: Student, Admin, Lecturer
10 | P a g e Submit Ratings: Actor: Student View Students: Actor: Lecturer
11 | P a g e Get Certification: Actor: Student
13 | P a g e Receive Payments : Actor: Lecturer
14 | P a g e Manage Course: Actors: Admin, Lecturer Manage Lecture: Actors: Admin, Lecturer
16 | P a g e Upload Video Lectures: Actor: Lecturer
