OSC Report Final
OSC Report Final
report on
Submitted
in partial fulfillment of
the requirements of the degree of
BACHELORS OF TECHNOLOGY
in
COMPUTER ENGINEERING
By
2024-2025
This is to certify that student’s named Kshitij Shah students of B.Tech in Computer
Engineering, has completed the Mini Project Dissertation entitled, "Student Feedback
System” Mini project to our satisfaction.
1 Introduction
2 Deliverables
5 E x e cut io n
6 Outcome screenshots
7 Conclusion
8 Future Scope
Course Review System: Detailed
Project Report
Team: Kshitij(221070060), Pratham(221070061), Vatsal(221070062)
Batch: B
Subject: OSC
1. Introduction
2. Deliverables
1. User Manuals:
Comprehensive guides for administrators and students on how to
navigate the system and use its features effectively.
2. System Design Documents:
Detailed architecture diagrams, database schemas, and workflow
charts outlining the system’s functionality and design.
3. Testing Reports:
Documentation of unit tests, system integration tests, and user
acceptance tests conducted during development to ensure
system reliability.
2.4 Deployment Deliverables
These deliverables ensure that the Course Review System meets its
objectives of providing a robust, scalable, and user-friendly solution
for managing student feedback efficiently.
1. Admin Login
○ Secure login system with authentication credentials.
○ Access to a dedicated dashboard for managing users,
feedback, and reports.
2. Manage Students
○ Add, update, or delete student profiles.
○ Assign unique login credentials to each student for secure
access.
○ View and track feedback submission status for all students.
3. Manage Teachers
○ Add, update, or delete teacher profiles.
○ Assign teachers to specific subjects for streamlined
feedback mapping.
4. Feedback Management
○ Access detailed feedback reports for each teacher,
categorized by subject.
○ Perform real-time analysis of responses to identify teaching
strengths and areas for improvement.
5. Export Feedback Data
○ Generate and export feedback reports in PDF or Excel
format for record-keeping and further analysis.
○ Supports customized reporting based on selected criteria,
such as subjects or specific timeframes.
6. Notifications
○ Send reminders or notifications to students who have not
submitted feedback.
7. Dashboard Insights
○ Visual representation of key feedback metrics using graphs
and charts for better decision-making.
1. Student Login
○ Secure login with unique credentials assigned by the admin.
○ Simplified login process with password recovery options.
2. Select Subject and Teacher
○ View a list of subjects and their respective teachers based
on enrolled courses.
○ Dynamic selection ensures accurate feedback targeting.
3. Feedback Form
○ Provide feedback on predefined questions using a 5-point
Likert scale (e.g., Strongly Disagree to Strongly Agree).
○ Optional text field to add qualitative comments for
detailed insights.
4. Submit Feedback
○ Confirmation prompt to prevent accidental submission.
○ Immediate acknowledgment of successful submission to
ensure completion.
5. View Feedback Status
○ Check submission status to confirm whether feedback for a
particular subject or teacher has been completed.
6. Data Confidentiality
○ Ensures anonymity of responses to promote honest and
constructive feedback.
1. Mobile-Friendly Interface
○ Fully responsive design for seamless access on mobile
devices and tablets.
2. Error Handling
○ User-friendly error messages for invalid login attempts or
incomplete feedback submissions.
3. Real-Time Updates
○ Reflects changes in subjects, teachers, or student data
immediately after admin updates.
4. Customizable Feedback Criteria
○ Admins can modify or add new feedback questions based on
institutional needs.
4. Execution
1. Requirements Gathering
○ Detailed discussions with stakeholders (teachers, students,
and administrators) to understand requirements.
○ Finalization of functional and technical specifications,
including system workflow and feature sets.
○ Documentation of requirements in a Software Requirements
Specification (SRS) document.
2. System Design
○ Created data flow diagrams (DFDs) to illustrate processes
and interactions.
○ Designed the database schema to define relationships
between users, teachers, feedback, and subjects.
○ Mockups for the user interface (UI) were prepared for both
admin and student portals.
3. Environment Setup
○ Configured the WAMP stack for the development
environment.
○ Installed and tested required tools, including phpMyAdmin
for database management and Visual Studio Code for
coding.
4. Backend and Frontend Development
○ Developed secure login systems for both admins and
students using PHP and MySQL.
○ Implemented feedback form functionality with dynamic
subject-teacher mapping.
○ Designed responsive frontend using HTML, CSS, JavaScript,
and Bootstrap for mobile and desktop compatibility.
5. Database Integration
○ Created tables to manage users, teachers, subjects, and
feedback data.
○ Established secure connections between the frontend,
backend, and database for data flow.
6. Testing
○ Unit Testing: Verified individual modules such as login,
feedback form submission, and admin dashboards.
○ Integration Testing: Ensured seamless interaction between
system components (e.g., database and UI).
○ User Acceptance Testing: Collected feedback from a pilot
group of students and admins to identify and address
usability issues.
7. Deployment
○ Hosted the system on an Apache Web Server for
institutional access.
○ Provided admin training to familiarize staff with system
operations.
1. Login Process
○ Admins and students access the system through separate,
secure login pages.
2. Feedback Collection
○ Students select a teacher and subject, fill out the feedback
form, and submit their responses.
○ Submitted feedback is stored in a secure database for
review and analysis.
3. Admin Management
○ Admins manage user data, view feedback reports, and
export results for record-keeping or analysis.
4. Reporting and Analysis
○ Feedback trends and insights are displayed on the admin
dashboard using graphs and tables.
Client-Server Architecture:
The system adopts a client-server model, where:
Key Processes:
1. Login Validation: Verifies credentials against the database for
both admins and students.
2. Feedback Submission: Stores structured responses and
comments in the feedback table.
3. Data Management: Admins can add, update, or delete user and
subject data.
4. Report Generation: Summarizes feedback trends and exports
them in desired formats.
1. Users Table
○ Attributes: UserID, Username, Password (hashed), Role
(Admin/Student)
○ Purpose: Manages authentication and user roles.
2. Teachers Table
○ Attributes: TeacherID, Name, Subject, Email
○ Purpose: Stores details about teachers and their subjects.
3. Subjects Table
○ Attributes: SubjectID, SubjectName, TeacherID
○ Purpose: Links subjects with their respective teachers.
4. Feedback Table
○ Attributes: FeedbackID, StudentID, TeacherID,
Question1-10, Comments, Date
○ Purpose: Stores student feedback responses and qualitative
comments.
Relationships:
The system was developed using the Waterfall Model, ensuring each
phase was completed before moving to the next:
1. Requirement Analysis: Defined functional needs through
stakeholder meetings.
2. System Design: Created mockups, DFDs, and database schema.
3. Implementation: Wrote PHP scripts, SQL queries, and designed
UI components.
4. Testing: Conducted unit, integration, and user acceptance
testing.
5. Deployment: Deployed on an Apache server and prepared
documentation.
6. Outcome Screenshots
7. Conclusion
The Course Review System is a helpful tool for schools and colleges to
collect student feedback about teachers. It makes the process simple
and organized, with students logging in to give their opinions and
administrators getting clear reports to understand the results. The
system is easy to use and secure, making it reliable for both students
and staff. By using technology like WAMP, we ensured it works smoothly
and can be improved in the future. It also helps teachers see their
strengths and areas to improve, which can make learning better for
everyone. Overall, this project was a great way to create something
useful for education while learning about coding and teamwork.
8. Future Scope