Online Tutorial Management System

Overview
An Online Tutorial Management System (OTMS) is a web-based platform
designed to facilitate the creation, management, and delivery of educational
content and tutorials. This system is tailored to meet the needs of both educators
and learners by providing a centralized platform where tutorials can be accessed
anytime and from anywhere. The system typically includes features such as
course creation tools, student management, assessment modules, and
communication interfaces.

Key Features
1. Course Creation and Management: Tools for instructors to create and
organize tutorials, lessons, and resources.

2. Student Enrollment and Tracking: Mechanisms to enroll students, track

their progress, and manage their performance data.

3. Assessment and Evaluation: Built-in quizzes, assignments, and exams

to evaluate student understanding and provide feedback.

4. Communication Tools: Forums, chat, and messaging systems to

facilitate interaction between students and instructors.

5. Content Delivery: Multimedia support for video, audio, and text-based

tutorials.

6. Analytics and Reporting: Detailed reports on student performance and

course effectiveness.

Objectives

• To provide a flexible and accessible learning environment.

• To streamline the administrative tasks involved in managing tutorials.
• To enhance the learning experience through interactive and engaging
content.

• To offer tools for continuous assessment and feedback.

Feasibility Study
Technical Feasibility
• Technology Stack: The system can be developed using modern web
technologies such as HTML5, CSS3, JavaScript, and frameworks like
React or Angular for the front end. For the back end, Node.js, Django, or
Ruby on Rails can be used. Databases like MySQL or MongoDB can
handle data storage.
• Infrastructure: Cloud services like AWS, Google Cloud, or Azure can
provide scalable hosting solutions.
Operational Feasibility
• Design Phase- 2 UI/UX Designers & 1 Frontend Developer
• Coding Phase- 2 Backend Developers & 1 API Specialist
• Testing Phase- 3 QA Engineers
• Installation Phase- 1 DevOps Engineer & 1 System Administrator
Legal and Ethical Feasibility
• Data Privacy: Compliance with data protection regulations such as
GDPR or CCPA to ensure user data is handled responsibly.
• Copyright: Ensuring that all educational content respects copyright laws
and that appropriate licenses are obtained.
Economic Feasibility
• Development Costs - Initial investment in development includes hiring
skilled developers, designers, and database administrators. The cost also
includes acquiring necessary tools, software licenses, and infrastructure.

• Combined Cost Breakdown

Design Phase = 4.7 Lakhs
Coding Phase = 3.6 Lakhs
Testing Phase = 4.2 Lakhs
 Deployment Phase = 1 Lakhs
Total Cost = 13.5 Lakhs

Legal and Ethical Feasibility

• Data Privacy and Security
• Copyright and Intellectual Property
• Accessibility and Inclusivity

Schedule Feasibility

• Design Phase
Requirements Gathering and Analysis: 1.5 month
System Design: 1 month
SRS Documentation: 1 month
Review and Approval: 0.5 months
Total Design Phase: 3.5 months

• Coding Phase
Setup Development Environment: 0.5 months
Development of Core Features: 2-3 months
Integration with Existing Systems: 1 month
Code Review and Refinement: 0.5 months
Total Coding Phase: 4-5 months

• Testing Phase
Unit Testing: 1 month
Integration Testing: 1 month
System Testing: 1 month
 User Acceptance Testing (UAT): 0.5-1 month
Total Testing Phase: 3.5-4 months

• Deployment Phase
Preparation for Deployment: 0.5 months
Deployment and Configuration: 0.5 months
Initial Training for Users: 0.5 months
Total Installation Phase: 1.5 months

• Maintenance Phase
Ongoing Support and Bug Fixes: Continuous (not usually included in the
initial project timeline, but can be estimated as a continuous process)

• Summary of Project Timeline

Design Phase: 3.5 months
Coding Phase: 4-5 months
Testing Phase: 3.5-4 months
Installation Phase: 1.5 months
Total Estimated Duration: 12.5-14 months
 AGILE MODEL

Choosing the Agile model for your project can offer several benefits:

1. Flexibility and Adaptability: Agile allows for changes and refinements

throughout the project lifecycle, accommodating evolving requirements
and feedback.
2. Customer Collaboration: It emphasizes close collaboration with
customers, ensuring that the final product meets their needs and
expectations.
3. Incremental Delivery: Agile delivers the project in small, manageable
increments, providing early and continuous delivery of valuable features.
4. Improved Quality: Frequent testing and reviews throughout the project
help identify and resolve issues early, improving overall quality.
5. Increased Transparency: Regular updates and reviews keep all
stakeholders informed, fostering trust and better decision-making.
6. Enhanced Team Morale: Agile promotes a collaborative and self-
organizing team environment, which can boost morale and productivity.
 Implementation

1. Project Planning and Setup

• Define Project Vision: Clearly outline the goals and objectives of the
online tutorial management system.
• Assemble the Team: Form a cross-functional team including developers,
testers, product owners, and other stakeholders.
• Set Up Agile Tools: Choose Agile project management tools like Jira,
Trello, or Asana for tracking progress.

2. Requirement Gathering

• User Stories: Work with stakeholders to create user stories that describe
the features and functionalities from the end-user perspective.
• Product Backlog: Compile all user stories into a prioritized product
backlog.

3. Sprint Planning

• Sprint Definition: Decide on the duration of sprints (typically 2-4

weeks).
• Select User Stories: Choose the top-priority user stories from the product
backlog to work on in the upcoming sprint.
• Task Breakdown: Break down user stories into smaller tasks and
estimate the effort required for each task.

4. Sprint Execution

• Daily Stand-ups: Hold daily stand-up meetings to discuss progress,

identify blockers, and plan the day's work.
• Development and Testing: Developers work on coding and testing tasks,
ensuring continuous integration and testing throughout the sprint.
5. Sprint Review

• Demonstrate Features: At the end of the sprint, hold a sprint review

meeting to demonstrate the completed features to stakeholders.
• Gather Feedback: Collect feedback from stakeholders to understand if
any changes or improvements are needed.

6. Sprint Retrospective

• Reflect and Improve: Hold a sprint retrospective meeting to discuss

what went well, what didn't, and how the team can improve in the next
sprint.
• Implement Improvements: Agree on actionable items for process
improvements and implement them in the next sprint.

7. Release Planning

• Incremental Releases: Plan for regular releases of the online tutorial

management system. Each release should include a set of completed user
stories that add value to the system.
• User Feedback: Collect and analyse user feedback from each release to
refine and prioritize the product backlog.

8. Continuous Improvement

• Adapt and Evolve: Continuously adapt the process based on

retrospectives and feedback. The Agile approach encourages ongoing
learning and improvement.

Example Sprint Workflow:

Sprint Planning:
o Choose a set of user stories from the product backlog (e.g., "User

can register and log in", "Admin can create and manage tutorials").
o Break down stories into tasks (e.g., "Design login page UI",
"Implement backend authentication").
Daily Stand-ups:
 o Each team member shares what they did yesterday, what they plan
to do today, and any blockers they face.
Development and Testing:
o Developers code the login functionality while testers create and
run test cases.
o Continuous integration ensures that new code is regularly merged
and tested.
Sprint Review:
o Demonstrate the login feature to stakeholders.

o Gather feedback (e.g., "The login page should have a 'forgot

password' link").
Sprint Retrospective:
o Discuss what went well (e.g., "Good collaboration between devs

and testers").
o Identify improvements (e.g., "Improve communication about daily

blockers").

Agile Tools and Practices:

• Kanban Board: Visualize work in progress and manage flow using a

Kanban board.
 SRS Document

The Online Tutorial Management System provides real-time information

about the available tutorials and user information. The primary purpose of
this project is to automate and streamline the management of online
tutorials, reducing manual work. This software is capable of managing
tutorial assignments, tracking progress, scheduling sessions, and handling
payments. The administrator (Instructor) controls content, manages users,
and tracks performance. Users (students) can log in to access tutorials, track
their progress, and receive notifications regarding upcoming sessions or
overdue tasks.

A. Functional Requirements
Signing in or signing up
Description (Scope) – Users must sign in to their account if they have already
created one. New users will need to sign up.

• Signing In

Input: User ID and Password.

Output: The requested page as per prior selections. Error message if wrong
details are entered.

• Signing up (For Students)

Input: Full Name, Student ID, Email ID, New Password.

Output: Creation of a new account, User ID, and verification email sent to the
user. If any input is incorrect, display ERROR message.

• Signing up (For Instructors)

Input: Full Name, Instructor ID, Email ID, New Password.

Output: Creation of a new account, User ID, and verification email sent to the
user. If any input is incorrect, display ERROR message.
1. Managing Tutorials

Description (Scope) – Users can search for specific tutorials using the tutorial
name, instructor, or subject. The system searches the database and displays
the tutorial details, including availability and content overview. Users can
then enroll in tutorials accordingly.

• Search by Name / Instructor / subject

Input: Tutorial name and/or instructor.

Output: Displays the tutorial, instructor,subject and availability status. Displays

"Not found" message if the tutorial is not present.

2. Enrolling in a Tutorial
Description – Users can choose to either watch a tutorial video (if available) or
attend live sessions.

• Watch Tutorial Video

Input: Select the tutorial and choose the video option.

Output: A new window opens, showing the tutorial video.

• Attend Live Session

Input: Select the tutorial and enter the session time.

Output: The tutorial is enrolled for the user, displaying a confirmation with the
respective details — Tutorial code, UserID, and session schedule. If the user
has any overdue tasks, they are prompted to complete them before enrolling
in new tutorials.

3. Completing and Submitting Assignments

Description (Scope) – Users select which assignments to submit and upload

their work. If any are overdue, the user is notified accordingly.

• Submitting the Assignment

Input: Select the "Submit" button.

Output: Page showing the details including assignment name, code, and date of
submission. If the assignment is overdue, a prompt with a penalty or
feedback message is displayed.

4. Payment for Tutorials

Description (Scope) – Users are displayed the payment amount for enrolled
tutorials and given options for the method of payment — Pay online
through UPI, or Pay online through net banking.

• Pay through UPI/Net banking

Input: Select the payment option

Output: Redirects to the Razorpay payment site

5. Tutorial Management System (Exclusive to Instructors)

Description (Scope) – The instructor uses this feature to check the

availability of tutorials and track the progress of each tutorial. It also
displays which students have overdue assignments. The instructor can also
add new tutorials and their respective details to the database.

• Check Tutorial Status

Input: Tutorial ID.

Output: Count of tutorial sessions available till date.

• Progress Tracking for a Particular Tutorial

Input: Tutorial ID.

Output: The tutorial progress history, displaying which particular session has
been attended by which student.

• Database of Students with Overdue Assignments

Input: Click on the Assignment Button.

Output: The list of students who have overdue assignments along with their
respective penalty or feedback status.

• Add New Tutorials to the Database

Input: Tutorial details, including name, instructor, code, and content overview.

Output: The page displaying the new list of available tutorials.

6. User Support

Description (Scope) – Users can send their feedback, report problems, and
ask questions via email. Users can also learn more about the institution
using the About Us section.

• Choose Option: Feedback/ Raise a Question/ Problems

Input: Select the appropriate option.

Output: Redirect to the respective page.

B. Non-Functional Requirements
1. HARDWARE REQUIREMENTS
a) 4GB RAM
b) 16GB Hard Disk space in terminal machine
c) 2TB Hard Disk space in server machine
d) Core i5 or higher processor

2. Software Requirements
a) Windows 7 or above OS
b) JRE 1.8
c) SQL Server
d) Chrome or Firefox browser

• Correctness Requirement

This software performs accurately as intended and in no other way.

• Usability Requirement
The software has a simple yet efficient user interface, accessible to all types of
users, both technically proficient and those with limited technical knowledge.
Users can navigate its functionalities without complications.

• Portability Requirement

This software provides a web-based interface accessible on any device with the
latest stable browser, provided that JavaScript and Cookies are enabled. Only
the offline tutorials (if any) have a fixed location at the institution.

• Availability Requirement

The software will be available 24/7, with offline tutorials (if any) adhering to the
institution's schedule. The software will be available on the internet, and
institutions must purchase a license to use it on their systems.

• Efficiency Requirement

The software is highly efficient, allowing various tasks in its modules and sub-
modules to be performed simultaneously. It provides an efficient solution to
the complete online tutorial management process. Offline efficiency depends
on staff management within the institution.

• Performance Requirement

The database can accommodate a high number of tutorials and users without
fault. Leveraging the latest technologies, the system is highly responsive,
ensuring quick and efficient user interactions. Offline responses depend on
the institution's management system.

• Reliability Requirement

The system is extremely reliable, with proper measures in place to protect user
data. Robust firewalls and other security measures have been implemented to
prevent data breaches.