SRS Document
SRS Document
Version 1.0
4. Usage Scenarios
5. Adopted Methodology
Scope of Project:
Functional Requirements:
Admin Panel:
Admin can login/logout.
Admin can add another admin.
Admin can add information into the course. Information can
be Course title, course instructor details, course content,
course videos, reading materials and outline, Quizzes (MCQ’s).
For each information, there will be a separate interface/page.
Admin can offer the course free or can mention some amount
to be paid.
Admin can offer coupons for the paid courses.
Admin can send coupons through Email.
Admin will accept / reject the users registration requests
Admin can view how many students are registered for the
course.
Admin can reply a query.
User Panel:
User can view all of the available courses on the home page
without logging in. However, to enroll a course, the user must
have to register on the website.
User can register, login and logout on the website.
User can view the details (Course title, course instructor
details, course content and outline) of each of the courses.
User can ask queries in the comment section.
User can enrol for a course and can complete the course. Each
video in the course needs to be watched about 80% to
complete that section.
User can attempt the quizzes and see the result of the quiz.
Use can also re-take a quiz, if secured less than 75% marks.
User can use different filters to search the courses (free, paid
and other filters).
User can get coupons through Email and can apply coupons to
the paid courses.
User can view the attempted courses like attempt history.
User can download the course certificate after completion by
confirming its name.
Non Functional Requirements:
Performance:
The system should be able to handle multiple concurrent users without
significant performance degradation.
Course materials, including videos and reading materials, should load quickly and
smoothly.
Quizzes and assessments should be processed efficiently, providing timely feedback to
users.
Usability:
The website should be compatible with popular web browsers such as Chrome,
Firefox, and Safari.
It should support multiple operating systems and devices, including desktops, laptops,
tablets, and mobile phones.
Maintainability:
The system should support multiple languages to cater to users from different
regions. Localization features should allow for the customization of date formats,
currency symbols, and other region-specific requirements
Adopted Methodology
Waterfall Model:
This is a sequential model of software development that has multiple
phases. It can be used when your requirements are not changing
very frequently. The project you are working on is not complex. You
have clear requirements while the environment is stable. As per the
resources these are trained and there is stable technology under use.
As mentioned earlier that every SDLC has its own cost and benefits,
spiral model combines out of iterative model and waterfall model.
Basically it is used when the project is large, when change may come
at any time, frequent releases are published, when cost and risk
analysis are important, fast deployment helps a lot. Using this cycle,
you have control over development. There is down side too, Spiral
may go indefinitely and using it in smaller project don’t not goes well
also cost will go up in small projects.
VU Process Model: