0% found this document useful (0 votes)
32 views41 pages

Teacher Evaluation System Final

Uploaded by

bm3573630
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
32 views41 pages

Teacher Evaluation System Final

Uploaded by

bm3573630
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 41

Tribhuvan University

Faculty of Humanities and Social Sciences

TEACHER EVALUATION SYSTEM

A PROJECT REPORT

Submitted to
Department of Computer Application
D.A.V College

In partial fulfillment of the requirements for the Bachelors in Computer Application

Submitted by
Ramesh Kunwar
[TU Reg No: 6-2-469-172-2020]
August, 2023

Under the Supervision of

Er Manil Vaidhya
Tribhuvan University
Faculty of Humanities and Social Sciences
D.A.V College

Supervisor’s Recommendation

I hereby recommend that this project prepared under my supervision by RAMESH


KUNWAR entitled “TEACHER EVALUATION SYSTEM” in partial fulfillment of the
requirements for the degree of Bachelor of Computer Application is recommended for the
final evaluation.

Er. Manil Vaidhya

SUPERVISOR
Lecturer
Department of Bachelors in Computer Application
Jawalakhel, Lalitpur

i
Tribhuvan University
Faculty of Humanities and Social Sciences
D.A.V College

LETTER OF APPROVAL

This is to certify that this project prepared by RAMESH KUNWAR entitled


“TEACHER EVALUATION SYSTEM” in partial fulfillment of the requirements
for the degree of Bachelor in Computer Application has been evaluated. In our opinion
it is satisfactory in the scope and quality as a project for the required degree.

Er. Manil Vaidhya, Lecturer Mr. Sudip Adhikari, H.O.D


Department of Bachelors in Computer Department of Bachelors in Computer
Application Application
Jawalakhel, Lalitpur Jawalakhel, Lalitpur

External Examiner

Er. Kumar Prasun


Internal Examiner
Asst.Professor
Tribhuvan University

ii
Abstract

The website is aimed for facilitating communication between students and teachers,
allowing students to provide feedback on their teachers' performance in various aspects
such as teaching style, communication, and subject matter. The project comprises three
main components: one for administrative management, one for student interaction, and
one for university oversight. These components work in tandem to enhance the
learning experience and ensure the effectiveness of teachers. The project was executed
using the MERN stack, a comprehensive set of tools for web development. MongoDB
was employed to store information pertaining to both teachers and students. The
backend was fortified with Express.js and Node.js to handle data efficiently. The
frontend, responsible for the website's appearance and functionality, was constructed
using React. The development process began with meticulous planning, followed by a
systematic step-by-step implementation. Initially, emphasis was placed on enabling
students to log in, rate their teachers, and share additional insights about their
educational experiences. Concurrently, a dedicated section for administrators was
established, enabling them to manage teacher-related tasks. Furthermore, a segment
was integrated to allow the university to gain insights into the subjects students were
learning. The primary objective of the project is to foster communication between
students and teachers, ultimately contributing to the improvement of education as a
whole.

Keywords: Teacher Evaluation System, MongoDB, Node.JS, ReactJS

iii
ACKNOWLEDGEMENT

I am very grateful to the department of computer application, DAV college for


providing me an opportunity to work on a minor project as part of Project ‘I’. I am
delighted to express my deep sense of gratitude and gratefulness to our academic
sir Er. Manil Vaidhya for his invaluable guidance, encouragement, and even
monitoring to spare time despite his busy schedule for project progress reviews.

Furthermore, I would like to thank Mr. Sudip Adhikari for his guidance and
motivation throughout the project. In addition, I would like to thank my friends,
who have willingly shared their precious time, advice, and encouragement during
planningof this project.

My special thanks go to our college department and everyone who directly and
indirectly extended their hands in making this project successful.

iv
Table of Content

Abstract .......................................................................................................................... iii

ACKNOWLEDGEMENT .............................................................................................. iv

Table of Content .............................................................................................................. v

List of Abbreviation ...................................................................................................... vii

List of Figures .............................................................................................................. viii

List of Tables ................................................................................................................. ix

CHAPTER 1: INTRODUCTION .................................................................................... 1

1.1. Introduction ..................................................................................................... 1

1.2. Problem Statement ........................................................................................... 1

1.3. Objectives ........................................................................................................ 2

1.4. Scopes and Limitation ...................................................................................... 2

1.5. Report Organization ......................................................................................... 2

CHAPTER 2: BACKGROUND STUDY AND LITERATURE REVIEW ...................... 4

2.1. Background Study .......................................................................................... 4

2.2 Literature Review ............................................................................................ 4

CHAPTER 3: SYSTEM ANALYSIS AND DESIGN ...................................................... 5

3.1. System Analysis .................................................................................................... 5

3.1.1 Requirement Analysis ...................................................................................... 5

3.1.2. Feasibility Analysis ........................................................................................ 6

3.1.3 Process Modeling ............................................................................................ 8

3.2.1 Architectural Design ...................................................................................... 10

3.2.2. Database Schema ......................................................................................... 11

3.2.3 Interface Design (UI Interface / Interface Structure Design) ........................... 11

CHAPTER 4: IMPLEMENTATION AND TESTING ................................................... 12

v
4.1 Implementation: ................................................................................................... 12

4.1.1.Tools And Technology .................................................................................. 12

4.1.2. Implementation Details of Modules .............................................................. 12

4.2. Testing ................................................................................................................ 13

4.2.1 Test Case for Unit Testing ............................................................................. 13

4.2.2. Test Case for System Testing ........................................................................ 16

CHAPTER 5: CONCLUSION AND FUTURE RECCOMENDATIONS ...................... 18

5.1. Lesson Learnt/Outcome ...................................................................................... 18

5.2. Conclusion ......................................................................................................... 18

5.3. Future Recommendation ..................................................................................... 18

References ..................................................................................................................... 26

Appendices.................................................................................................................... 19

vi
List of Abbreviation

CRUD Create, Read, Update, Delete


DFD Data Flow Diagram
MERN MongoDB Express.js React.js Node.js
SDLC Software Development Lifecycle
SQL Structured Query Language
UI User Interface
VS Visual Studio code

vii
List of Figures

Figure 1 Waterfall Model .............................................................................................. 5


Figure 2 Use Case Diagram ........................................................................................... 6
Figure 3 Gantt Chart..................................................................................................... 7
Figure 4 Level 0 DFD .................................................................................................... 8
Figure 5 Level 1 DFD .................................................................................................... 9
Figure 6 Architectural Design ..................................................................................... 10
Figure 7 Schema Diagram ........................................................................................... 11
Figure 8 UI Design ....................................................................................................... 11

viii
List of Tables

Table 1 User Login Test .............................................................................................. 14


Table 2 Student Registration Text .............................................................................. 14
Table 3 Adding, Editing, Deleting teacher by admin ................................................. 15
Table 4 Adding, Editing, Deleting semester by university ......................................... 15
Table 5 Student rates teacher and semester table ...................................................... 15
Table 6 Test Cases for System Testing ....................................................................... 16

ix
CHAPTER 1: INTRODUCTION
1.1. Introduction
In the changing world of education, it's really important to create a strong system that listens
to what students think about their teachers and how they teach. The website aims to provide
a platform for students to provide feedback on their learning experience, and to help
teachers improve their teaching skills. The purpose of the feedback system is to gather the
learning experience of students and to improve the overall quality of education by
promoting transparency and accountability in the teaching profession. To give feedback
and ratings to the teacher, first student must login to the system and give rating and
feedback to the teacher. The website will be developed using a user-friendly interface that
allows students to easily rate their teachers on a scale of 1-5. The website will also include
a comments section where students can provide more detailed feedback on their learning
experience. Teachers will have access to their ratings and comments and will be able to use
this feedback to improve their teaching methods. The application consists of three different
modules which are admin module, student module and TU module.
In Admin module, admin can assign teachers or create teachers based on their subject.
Admin can perform additional operations like updating a teacher, deleting a teacher. In TU
module, university staff can register their email and create a post or page where students
can give ratings to effectiveness or ineffectiveness of the semester. Students can give a
rating to university based on the practical knowledge gained after each semester.

1.2. Problem Statement


There are multiple ways of evaluating the progress of a student like taking exams, checking
assignments, and attendance. However, there are no tools to evaluate the performance of
the teacher and the person who has designed the course. A lot has changed over the last two
decades in the field of technology, agriculture, science, health, fashion, culture, etc. Now,
there are efficient ways to do everything. If it took 3months to do a particular task 20years
before, now the same task can be done within 3hours of time. In every sector, we can see
improvements in efficiency and reduction of time for doing the task. However, this is not
true in the case of academic education. Method of teaching is the same, course structure is
the same, even giving assignments and taking exams is the same. Not even a single thing
has improved in the field of educational sector. If not, it’s getting worse. This is because

1
there is a communication gap between the teacher, students and the person who has
designed the course. The teacher may think that he has explained the concept properly. And
the person who has designed the course may think that he has designed the best course in
the world. But students may not find the course useful and practical. If the student has spent
4years of his valuable time in college, then it’s the job of an educational institution to make
him a professional. But if we check the skill of a student who is in his final year, then we
come to the realization that he doesn’t have a clue what he has learned in the past four
years. This reason might be because of the poor teaching skill of the subject teacher or the
person who has designed the course didn’t design the course in a structured manner.
So, to solve this issue “The Feedback Loop” exists. This system evaluates the performance
of teachers and the person who has designed the course. Rating and feedback are given to
the subject teacher on the basis of his teaching skill, communication skills and the quality
of notes provided. The performance of the person who has designed the course is evaluated
on the basis of course structure and actual skills gained by the student.

1.3. Objectives
 To evaluate the performance of teachers and provide them with feedback.

1.4. Scopes and Limitation

Scopes:
 Student can rate and provide feedback to teacher and semester
 All users can view teacher and semester ratings.
 Admin can create or add teachers.

Limitation:
 Student may use vulgar language.

1.5. Report Organization


Chapter 1: This chapter includes brief introduction about the teacher evaluation
system.
Chapter 2: This involves the background study of the current existing system and
research regarding it.
2
Chapter 3: This includes system analysis and design of the teacher evaluation
system which includes all the functional and non-functional requirements,
feasibility analysis etc.
Chapter 4: This chapter is about implementing and testing of the system which
includes system testing, unit testing.
Chapter 5: This involves brief conclusion about the project and outcomes of the
project.

3
CHAPTER 2: BACKGROUND STUDY AND LITERATURE
REVIEW
2.1. Background Study
In the field of education, it's important to evaluate how well teachers and course
designers are doing their jobs. While other industries have made advancements with
new technologies and improved ways of doing things, education hasn't changed
much. The way teachers teach, the structure of courses, and how students are
assessed have stayed the same. This can create a problem because there's often a lack
of communication and understanding between teachers, students, and course
designers. To fix this, we can use a "Feedback Loop." This means that students give
ratings and feedback to their teachers based on how well they teach and how helpful
their materials are. Course designers also get evaluated based on how well they
structure their courses and if students are actually learning useful skills. By using this
Feedback Loop, we can make sure teachers improve their teaching, courses become
more practical, and students get a better education overall. It's all about working
together and constantly improving

2.2 Literature Review

a. ratemyprofessors [1]:
ratemyprofessors.com is an existing rating system through which student
can rate university professors and the university they are studying in.

The website provides students with a platform to share their opinions and
experiences with others. Students can rate their professors on several
parameters such as clarity, helpfulness, and easiness. The website also
allows students to leave comments about their professors and courses. In
addition, the website provides a search feature that allows students to
search for professors and courses based on various criteria such as school,
department, and subject. RateMyProfessors.com also provides a feature
called “Grade Distribution” that allows students to view the distribution of
grades given by a professor. This feature can help students get an idea of
the grading policies of a professor and the difficulty level of the course.

4
CHAPTER 3: SYSTEM ANALYSIS AND DESIGN

3.1. System Analysis


The Requirements for this project are all known and there is very less time for the
development so, waterfall model fits perfectly for developing this project. The project is
divided into the six phases i.e., Requirement Analysis, System Design, Implementation,
Testing, Deployment and Maintenance.

Figure 1 Waterfall Model

3.1.1 Requirement Analysis


I. Functional Requirements
 Add / Edit/ Delete / View Teacher Details
 Add / Edit / Delete / View Semester Details
 Rate Teacher
 Rate Semester
 Give feedback to the teacher
 Give feedback to the semester
 Register and login

5
Figure 2 Use Case Diagram
In this project, there are three types of users i.e., Admin, University and student. The admin
user can, edit and delete teachers from the system. University user can add, edit and delete
semester details from the system. Student user can only rate and add comments to the
teachers and semester details.

II. Non-Functional Requirements:


 Secure Login
 Clean and Attractive UI
 Responsive

3.1.2. Feasibility Analysis


i. Technical
In this project, for user interface side, html, CSS and JavaScript, ReactJS is
used, for backend expressjs and mongodb are used. These technologies are well
known technologies for the development of the web application which are
modern and doesn’t easily fade out. So, this system is technically feasible.

6
ii. Operational
This proposed system is user friendly with modern and attractive UI which can
be any used by anyone. It can be implemented and operated effectively within
an organization’s existing resources

iii. Economic
“The Feedback Loop” requires minimum cost for development. The Feedback
Loop helps to improve the performance of teachers, which is highly beneficial
for the college and students. Since, there is high return on investment. This
software is economically feasible.
iv. Schedule
The project is completed within the given period of time.

Figure 3 Gantt Chart

The Gantt chart of my project is shown in the above figure. The above Gantt chart has the
project plan for 5 months. This project is based on the waterfall model so, the project
follows the steps of the waterfall model. Project starts from the requirement gathering, most
of the time is separated for the coding part.

7
3.1.3 Process Modeling

Figure 4 Level 0 DFD

8
Figure 5 Level 1 DFD

9
3.2.1 Architectural Design

Figure 6 Architectural Design

10
3.2.2. Database Schema

Figure 7 Schema Diagram

3.2.3 Interface Design (UI Interface / Interface Structure Design)

Figure 8 UI Design

11
CHAPTER 4: IMPLEMENTATION AND TESTING

4.1 Implementation:
Implementation means the phase where the system is being built. Firstly, all the information
that we gathered is studied and analyzed and implemented into a system in operation for
users. It is one of the most important phases of any project. Implementation usually consists
of coding, testing, installation, documentation, training, and support. Different tools and
technologies have been used to develop the system which is already discussed in the
previous chapter. It is converting system design specifications into working software.

4.1.1. Tools And Technology


The various system tools that have been used in developing both the front-end and back-
end of the project are discussed in this chapter.

 Figma

 Draw.io

 TeamGantt

 MERN

 Redux Toolkit

 CSS

 Postman

 VS code

4.1.2. Implementation Details of Modules

After the design was built, it was time to start implementing the application. The
major aspects of the implementation, some modules pf the Online Vehicle Rental
system are listed below

a. Student Registration Module:


It is used to register new student to the system. It contains fields
12
like name, email, password. The information entered is further
stored to use on the login page.

b. Login Module
This module requires the. Student or university and admin to meet
the login credentials i.e., email and Password that matches with the
registered data to login to the system.

c. Student Module:
This module is built for student, where student rates teacher and
semester and provide feedback.

d. Admin Module:
This module is built for the admin users, where admin creates, edit,
delete teacher details.

e. University Module:
This module is built for semester users, where semester creates,
edit, delete semester details

4.2. Testing

Testing is done to check the behavior of a complete and fully integrated software
product Based on the software requirement specification document. For the
application to be deployed it has to be tested. Hence test cases will be written to test
this application.

This project will go through two levels of testing i.e., Unit and System Testing:

4.2.1 Test Case for Unit Testing

For unit testing every functional module were tested separately and the result of those
modules were analyzed. Each unit of application is tested to verify that the detailed
design for the unit has been correctly implemented. Unit testing can be done by
following test cases:

For unit texting, we tested every functional module separately and the result of those
modules were analyzed. The unit of the web application is tested to verify that the
detaileddesign for unit testing has been correctly implemented.
13
Unit testing can be done by the following test cases:

Table 1 User Login Test

S.N Test Case Test Data Expected Result Result


1 Admin enters valid Email: Redirect to teacher pass
email and admin@gmail.com page
password Password: *****
2 Admin enters Email: Display “invalid pass
invalid email and admin@gmail.com credentials”
password Password: *****
3 University enters Email: Redirect to teacher pass
valid email and university@gmail.com page
password Password: *****
4 University enters Email: Display “invalid pass
invalid email and university@gmail.com credentials”
password Password: *****
5 Student enters Email: Redirect to teacher pass
valid email and ramesh@gmail.com page
password password: *****
6 Student enters Email: Display “Invalid pass
invalid email and ramesh@gmail.com credentials”
password Password: *****

Table 2 Student Registration Text

S.N Test Case Test Data Expected Result Result


1 Student register with Name: ramesh User registered pass
valid data Email: successfully
ramesh@gmail.com
Password: *****
2 Student register with Email: User already pass
existing email ramesh@gmail.com exists
password: *****
3 Student try to register Name: All fields are pass
with empty field Email: required
ramesh@gmail.com
Password: *****

14
Table 3 Adding, Editing, Deleting teacher by admin

S.N Test Case Test Data Expected Result Result


1 Admin adds teacher Teacher name: Hitesh Teacher added pass
with image Chaudhory successfully
2 Admin adds teacher Teacher name: Ram Don’t allow admin fail
with other file type Shrestha to add teacher
3 Edit teacher Teachr name = Ram Teacher updated pass
Chaudhory successfully
4 Edit teacher with Teacher name: Restrict admin fail
other file type Shyam Shrestha from editing
Image: a.pdf teacher
5 Delete teacher Teacher deleted pass
successfully

Table 4 Adding, Editing, Deleting semester by university

S.N Test Case Test Data Expected Result Result


1 University adds Semester: Semester added pass
semester Semester 1 successfully
2 University edit Semester: Semester updated pass
semester Semester One successfully
3 University delete Semester deleted pass
semester successfully

Table 5 Student rates teacher and semester table

S.N Test Case Test Data Expected Result


Result
1 Student rates Communication Skill: 5 Reviewed pass
teacher Teaching Skill: 4 Successfully
Resource Provided: 3
Feedback: Great teacher
2 Student rates Communication Skill: 7 Rate pass
teacher Teaching Skill: 4 between 1
Feedback: Great Teacher and 5
3 Student rates Rate Semester: 3 Semester pass
semester Feedback: Worth investing reviewed
time successfully

15
4.2.2. Test Case for System Testing

Table 6 Test Cases for System Testing

S. N Test Case Test Data Expected Result Result

1. Admin User Email: admin@gmail.com Redirects to pass


enters valid teacher page
Password: *****
username and
password

2. Admin User Email: nischal@gmail.com Display “Invalid pass


enters invalid credentials”
Password: *****
email and
password

3. Student login Name: ramesh@gmail.com Redirect to pass


teacher page
Password: *****

3. Admin adds Name: Hitesh Chaudhory Creation of new pass


new teacher Description: teach desc teacher with the
Courses Taught: Java, C given credentials
Image: img.jpg

4. Admin edits Name: Hiteshh Chaudhory Name is updated pass


teacher details

5. University User Email: Redirects to pass


enters valid university@gmail.com teacher page
username and
Password: *****
password

16
6. University user enters Email: Display “invalid pass
invalid username and university@gmail.com credentials”
password
Password: *****

7. University adds new Name: First semester Creation of new pass


semester Description: sem1 semester with
Courses Taught: Java, the given
C credentials

8. University edits Name: Sem 1 Semester name pass


semester details is updated

9. Student rates teacher Communication Skill: Reviewed pass


5 Successfully
Teaching Skill: 4
Resources Provided: 4
Feedback: Great

10. Student rates semester Rating: 4 Semester pass


Feedback: Learned reviewed
about OOP successfully

17
CHAPTER 5: CONCLUSION AND FUTURE
RECCOMENDATIONS

5.1. Lesson Learnt/Outcome

After completion of Teacher Evaluation System project, I have learned many things
while building this project as listed below:

• Learned about MERN stack.


• Learned about how to connect all the modules.
• Learned about researching in the current market about the current related systems.
• Learned to solve the problem related to codes.
• Learned to implement a CRUD operation in a system.
• Learned to develop or built full-stack project.

5.2. Conclusion

In conclusion, the project is all about creating a website where students can share
their thoughts about their teachers. This helps make teaching better by letting
students say what they like and what could be improved. The website is easy to use,
and students need to log in to give ratings and more detailed feedback. There are
different parts of the website for managing teachers, students, and the university. By
bringing students and teachers closer and letting them communicate, this project
aims to improve how education works, making it a win-win for everyone involved.

5.3. Future Recommendation

There are lot more features that can be recommended to enhance this system in
future. Some future recommendations may be:

 College recommendation module

 Filter vulgar words, upvote, downvote, reply to feedback by other students

18
Appendices

19
20
21
22
23
24
25
References
[1] Find and rate your professor or school (2022) Rate My Professors. Available at:
https://www.ratemyprofessors.com/ (Accessed: 19 April 2023).

26
Supervisor’s Log Sheet
Project Log Sheet
Teacher Evaluation System

Supervisors name: Er. Manil Vaidhya


Name: Ramesh Kunwar [6-2-469-172-2020]

Logbook Entry Sheet


Meeting No: Date:
Start Time: End Time:
Meeting Topic:

Achievements:

Problems:

Tasks for next meeting:

_________________
Er. Manil Vaidhya
Supervisor
Lecturer, D.A.V. College
Supervisor’s Log Sheet
Project Log Sheet
Teacher Evaluation System

Supervisors name: Er. Manil Vaidhya


Name: Ramesh Kunwar [6-2-469-172-2020]

Logbook Entry Sheet


Meeting No: Date:
Start Time: End Time:
Meeting Topic:

Achievements:

Problems:

Tasks for next meeting:

_________________
Er. Manil Vaidhya
Supervisor
Lecturer, D.A.V. College
Supervisor’s Log Sheet
Project Log Sheet
Teacher Evaluation System

Supervisors name: Er. Manil Vaidhya


Name: Ramesh Kunwar [6-2-469-172-2020]

Logbook Entry Sheet


Meeting No: Date:
Start Time: End Time:
Meeting Topic:

Achievements:

Problems:

Tasks for next meeting:

_________________
Er. Manil Vaidhya
Supervisor
Lecturer, D.A.V. College
Supervisor’s Log Sheet
Project Log Sheet
Teacher Evaluation System

Supervisors name: Er. Manil Vaidhya


Name: Ramesh Kunwar [6-2-469-172-2020]

Logbook Entry Sheet


Meeting No: Date:
Start Time: End Time:
Meeting Topic:

Achievements:

Problems:

Tasks for next meeting:

_________________
Er. Manil Vaidhya
Supervisor
Lecturer, D.A.V. College
Supervisor’s Log Sheet
Project Log Sheet
Teacher Evaluation System

Supervisors name: Er. Manil Vaidhya


Name: Ramesh Kunwar [6-2-469-172-2020]

Logbook Entry Sheet


Meeting No: Date:
Start Time: End Time:
Meeting Topic:

Achievements:

Problems:

Tasks for next meeting:

_________________
Er. Manil Vaidhya
Supervisor
Lecturer, D.A.V. College

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy