STUDENT ASSIGNMENT FEEDBACK SYSTEM

A PROJECT PROGRESS REPORT

Submitted By
Soumyabrata Choudhury (49/cs/19/26)
Debobrata Chowdhury (49/cs/19/39)
Swarnadeep Dey (49/cs/19/37)
Nayan Das (49/cs/19/36)

Under the Supervision Of

Miss. Parijata Majumdar

Assistant Professor , CSE Department , TCEA , Maheshkhola

Bachelor OF Technology
IN
Computer Science & Engineering

Techno College Of Engineering Agartala, Maheshkhola, 799004

TRIPURA UNIVERSITY: TRIPURA 799022
January 2019

[i]
 DECLARATION

We declare that the work presented in this project proposal titled “Student Assignment Feedback
System” submitted to the Computer Science and Engineering Department, Techno College Of
Engineering Agartala, Maheshkhola, for the award of the Bachelor of Technology degree in
Computer Science & Engineering, represents our ideas in our own words and where others ideas
or words have been included, we have adequately cited and referenced the original sources. We
also declare that we have adhered to all principles of academic honesty and integrity and have
not misrepresented or fabricated or falsified any idea/data/fact/source in our submission. We
understand that any violation of the above will be cause for disciplinary action by the Institute
and can also evoke penal action from the sources which have thus not been properly cited or
from whom proper permission has not been taken when needed.

January, 2018
Maheshkhola, Tripura(W)
Soumyabrata Choudhury

Debobrata Chowdhury

Swarnadeep Dey

Nayan Das

[ii]
 CERTIFICATE

It is certified that the work contained in the dissertation titled “Student Assignment Feedback
System”, by Soumyabrata Choudhury , Debobrata Chowdhury , Swarnadeep Dey & Nayan Das ,
Roll Number (49/cs/19/26) , (49/cs/19/39) , (49/cs/19/37) , (49/cs/19/36) respectively has been
carried out under our supervision and this work has not been submitted elsewhere for a degree.

Miss. Parijata Majumdar

Project Supervisor
Assistant Professor
Computer Science & Engineering Department
Techno College Of Engineering Agartala
Maheshkhola , Tripura (W) ,799004

[iii]
 Abstract

In order to maintain a good recognition at college, the management does every possible aspect in
maintaining the qualities of the faculties. As this is the online-era, where everything is online we
need to develop a system in online which is very useful to maintain feedback reports by the
administrator.

The purpose of this project is to make the process of taking feedback from the students in online
regarding the faculties teaching. With this, the institutes can access the feedback reports in a faster
way and without any loss of data. As of now this task was done manually with the use of papers and
pens. This has many drawbacks and evaluating this handwritten forms is a difficult process.
Student needs to log into the website of online feedback system and giving his/her feedback and
can perform modifications too. But the restriction here is once the student submits the report then
he cannot modify it later. With this the student can successfully submit feedback on faculties
teaching in a very efficient manner without any loss of data. The administrator and the faculty
members can access these feedbacks from the students and take appropriate actions.

Keywords: Feedback system, Submit feedback, Modifying feedback, and Accessing feedback.

[iv]
 Acknowledgement

We would like to take this opportunity to express our deep sense of gratitude to all who helped us
directly or indirectly during this Project work. Firstly, we would like to thank our Project
Supervisor, Miss. Parijata Majumdar (Assistant Prof., CSE Dept. TCEA) for being a great
mentor and the best adviser we could ever have. Her advice, encouragement and critics are
source of innovative ideas, inspiration and causes behind the successful completion of this
project. The confidence shown on us by everyone was the biggest source of inspiration for us.
We are highly obliged to all the faculty members of Computer Sc. & Engineering Dept. for their
support and encouragement. We also would like to thank Mr. Partha Pratim Deb, H.O.D, CSE
Dept. for providing excellent computing and other facilities and without which this work
shouldn’t have achieved its quality goal.

Finally, we are grateful to our loving parents & friends for their support. It was impossible for
us to complete this project work without their love, blessing and encouragement.

Soumyabrata Choudhury
Debobrata Chowdhury
Swarnadeep Dey
Nayan Das

[v]
 List Of Figures

1.1 Use Case Diagram For Admin Module ------------------------------------------ 12

1.2 Use Case Diagram For Faculty Module ----------------------------------------- 13
1.3 Use Case Diagram For Student Module ----------------------------------------- 13
1.4 Level 0 DFD For Student Assignment Feedback System --------------------- 15
1.5 Level 1 DFD For Student Assignment Feedback System ------------------- 15
1.6 Level 2 DFD For Student Assignment Feedback System ------------------- 16
1.7 E-R Diagram For Student Assignment Feedback System ------------------- 18
1.8 Model View Controller(MVC) Diagram --------------------------------------- 23

[vi]
 List Of Tables

2.1 Gantt Chart ------------------------------------------------------------------------- viii

[vii]
 Gantt Chart

An elementary Gantt chart for the development plan is given below. The plan explains the tasks
versus the time(in weeks) they took to complete.

Parameters August September October November December

Requirement
Gathering

Analysis

Design

Coding

Testing

Implementati
on

W W W W W W W W W W W WW W W W W W W W
Weeks 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

[viii]
 TABLE OF CONTENTS

Title Page ----------------------------------------------------------------------------- i

Declaration --------------------------------------------------------------------------- ii
Certificate ---------------------------------------------------------------------------- iii
Abstract ------------------------------------------------------------------------------- iv
Acknowledgement ------------------------------------------------------------------- v
List of Figures ------------------------------------------------------------------------ vi
List of Tables ------------------------------------------------------------------------- vii
Gantt Chart ---------------------------------------------------------------------------- viii

1. Introduction --------------------------------------------------------------------------- 1
1.1 Introduction ------------------------------------------------------------------------ 1
1.2 Problem Definition ---------------------------------------------------------------- 2
1.3 Objective ------------------------------------------------------------------------- 2
1.4 Hardware Specification -------------------------------------------------------- 2
1.4.1 Client Side ---------------------------------------------------------------- 2
1.4.2 Server Side ---------------------------------------------------------------- 2
1.5 Software Specification ---------------------------------------------------------- 3
1.6 Scope ------------------------------------------------------------------------------ 3

2. Literature Survey ------------------------------------------------------------------- 4

2.1 Mobile Virtual Online Feedback System ------------------------------------- 4
2.2 Feedback Management System For Evaluating And Generating Monthly
Report ---------------------------------------------------------------------------- 5
2.3 Existing System ------------------------------------------------------------------ 5
2.4 Proposed System ------------------------------------------------------------------ 6
 2.5 Feasibility Study ------------------------------------------------------------------ 6

3. System Analysis & Design --------------------------------------------------------- 8

3.1 Requirements Specification -------------------------------------------------------- 8
3.2 System Analysis ------------------------------------------------------------------ 9
3.3 Project Modules ----------------------------------------------------------------- 10
3.3.1 Admin Module ----------------------------------------------------------- 10
3.3.2 Faculty Module ---------------------------------------------------------- 10
3.3.3 Student Module --------------------------------------------------------- 11
3.4 UML Diagram ------------------------------------------------------------------- 12
3.5 Data Flow Diagrams ----------------------------------------------------------- 14
3.6 E-R Diagrams ------------------------------------------------------------------ 16
3.7 Design --------------------------------------------------------------------------- 19
3.7.1 Primary Design Phase -------------------------------------------------- 19
3.7.2 Secondary Design Phase ----------------------------------------------- 19
3.7.3 User Interface Design -------------------------------------------------- 19
3.8 Testing --------------------------------------------------------------------------- 20
3.8.1 White Box Testing ------------------------------------------------------- 20
3.8.2 Black Box Testing -------------------------------------------------------- 20
3.8.3 Alpha Testing ------------------------------------------------------------- 20
3.8.4 Beta Testing ----------------------------------------------------------------21
3.8.5 Unit Testing --------------------------------------------------------------- 21
3.8.6 Integration Testing ------------------------------------------------------- 21

4. Implementation ------------------------------------------------------------------- 22
4.1 Model View Controller (MVC) Diagram --------------------------------- 22

5. Outputs ----------------------------------------------------------------------------- 24
6. Percentage Of Project Remains ----------------------------------------------- 38
7. Portion Of the Project Remains ----------------------------------------------- 38
8. Conclusion ---------------------------------------------------------------------------- 39
9. References -------------------------------------------------------------------------- 40
 INTRODUCTION

1. Introduction

The "Student Assignment Feedback System" has been developed to override the problems
prevailing in the practicing manual system. This software is supported to eliminate and in some
cases reduce the hardships faced by this existing system. Moreover this system is designed for the
particular need of the company to carry out operations in a smooth and effective manner.

The application is reduced as much as possible to avoid errors while entering the data. It also
provides error message while entering invalid data. No formal knowledge is needed for the
user to use this system. Thus by this all it proves it is user-friendly. Student Feedback System ,
as described above, can lead to error free, secure, reliable and fast management system. It can
assist the user to concentrate on their other activities rather to concentrate on the record
keeping. Thus it will help organization in better utilization of resources.

Every organization, whether big or small, has challenges to overcome and managing the
information of Feedback, Student, Faculty, Teacher, Subject. Every Student Feedback System has
different Student needs, therefore we design exclusive employee management systems that are
adapted to your managerial requirements. This is designed to assist in strategic planning, and will
help you ensure that your organization is equipped with the right level of information and details
for your future goals. Also, for those busy executive who are always on the go, our systems come
with remote access features, which will allow you to manage your workforce anytime, at all
times. These systems will ultimately allow you to better manage resources.

[1]
1.2 Problem Definition

This work focus on the student feedback system which will be in place at education
Organizations for better teaching & learning process with corrective measures to
bring the quality in education system.

1.3 Objective

The main objective of the Project on Student Feedback System is to manage the details of
Student, Feedback, Feedback Type, Faculty, Subject. It manages all the information about
Student, Teacher, Subject. The project is totally built at administrative end and thus only the
administrator is guaranteed the access. The purpose of the project is to build an application
program to reduce the manual work for managing the Student, Feedback, Teacher, Feedback
Type. It tracks all the details about the Feedback Type, Faculty, Subject.

1.4 Hardware Specification

1.4.1 Client Side

PROCESSOR: Pentium 2.0 or above

RAM : 256 MB
HARD DISK : 10 GB free space

1.4.2 Server Side

PROCESSOR: Pentium 2.0 or above

RAM : 1 GB
HARD DISK : 20 GB free space

[2]
1.5 Software Specification

OPERATING SYSTEM: Windows 7, Windows 8, Windows 10, Linux

FRONT END : HTML, CSS, JS
BACK END : PHP & MYSQL
BROWSER : Google Chrome, Internet Explorer, Firefox etc.
SERVER : XAMPP

1.6 Scope

It may help collecting perfect management in details. In a very short time, the collection
will be obvious, simple and sensible. It will help a person to know the management of
passed year perfectly and vividly. It also helps in current all works relative to Student
Assignment Feedback System. It will be also reduced the cost of collecting the
management & collection procedure will go on smoothly.

Our project aims at Business process automation, i.e. we have tried to computerize
various processes of Student Feedback System.


In computer system the person has to fill the various forms & number of copies of
the forms can be easily generated at a time.


In computer system, it is not necessary to create the manifest but we can directly
print it, which saves our time.


To assist the staff in capturing the effort spent on their respective working areas.


To utilize resources in an efficient manner by increasing their productivity
through automation.

The system generates types of information that can be used for various purposes.

[3]
 
It satisfy the user requirement

Be easy to understand by the user and operator

Be easy to operate

Have a good user interface

Be expandable

Delivered on schedule within the budget

LITERATURE SURVEY

2. Literature Survey

2.1 Mobile Virtual Online Feedback System

We take the inference from this project to create feedback system that collect the
feedback from the student and provides the automatic generation of feedback by
student. This system has security limitation. It is only works on intranet.

In addition to that we also provide the rating system due to which the student will rate
the teacher based on his/her teaching, we also provide the interactive user interface
for student and teacher.

[4]
2.2 Feedback Management System For Evaluating And Generating Monthly Report

We take the inference from this project to create feedback system that collect the
feedback from the student and provides the automatic generation of feedback by
student. This system is not time bound. In case of user interface this system is not user
friendly.
In addition to this we also provide the portal system due to which student will give the
monthly feedback. We are planning to develop the system for not only the college but
also for organization area to develop the user interface.

2.3 Existing System

In the existing system the feedback are given only manually but in proposed
system we have to computerize the exams using this application.

• Lack of security of data.

• More man power.

• Time consuming.

• Consumes large volume of pare work.

• Needs manual calculations.

• No direct role for the higher officials

[5]
 2.4 Proposed System

The aim of proposed system is to develop a system of improved facilities. The

proposed system can overcome all the limitations of the existing system. The system provides
proper security and reduces the manual work.

• Security of data.

• Ensure data accuracies.

• Proper control of the higher officials.

• Minimize manual data entry.

• Minimum time needed for the various processing.

• Greater efficiency.

• Better service.

• User friendliness and interactive.

• Minimum time required.

2.5 Feasibility Study

After doing the project Student Assignment Feedback System, study and analyzing all the
existing or required functionalities of the system, the next task is to do the feasibility study for
the project. All projects are feasible - given unlimited resources and infinite time.

Feasibility study includes consideration of all the possible ways to provide a solution to the
given problem. The proposed solution should satisfy all the user requirements and should be

[6]
flexible enough so that future changes can be easily done based on the future upcoming
requirements.

A. Economical Feasibility

This is a very important aspect to be considered while developing a project. We decided the
technology based on minimum possible cost factor.

• All hardware and software cost has to be borne by the organization.

• Overall we have estimated that the benefits the organization is going to receive from
the proposed system will surely overcome the initial costs and the later on running cost
for system.

B. Technical Feasibility

This included the study of function, performance and constraints that may affect the ability to
achieve an acceptable system. For this feasibility study, we studied complete functionality to
be provided in the system, as described in the Requirement Specification, and checked if
everything was possible using different type of front end and back end platform.

C. Operational Feasibility

No doubt the proposed system is fully GUI based that is very user friendly and all inputs to
be taken all self-explanatory even to a layman. Besides, a proper training has been conducted
to let know the essence of the system to the users so that they feel comfortable with new
system. As far our study is concerned the clients are comfortable and happy as the system has
cut down their loads and doing.

[7]
 SYSTEM ANALYSIS & DESIGN

3. System Analysis & Design

3.1 Requirement Specification

The Software Requirements Specification is produced at the culmination of the

analysis task. The function and performance allocated to software as part of system
engineering are refined by establishing a complete information description, a
detailed functional and behavioral description, an indication of performance
requirements and design constraints, appropriate validation criteria, and other data
pertinent to requirements.

The Proposed System has the following requirements:

• System needs store information about new entry of Student.

• System needs to help the internal staff to keep information of Feedback and find
them as per various queries.

• System need to maintain quantity record.

• System need to keep the record of Feedback Type.

• System need to update and delete the record.

• System also needs a search area.

• It also needs a security system to prevent data.

[8]
3.2 System Analysis

System analysis is a process of gathering and interpreting facts, diagnosing problems and
the information about the Student Feedback System to recommend improvements on the
system. It is a problem solving activity that requires intensive communication between
the system users and system developers. System analysis or study is an important phase
of any system development process. The system is studied to the minutest detail and
analyzed. The system analyst plays the role of the interrogator and dwells deep into the
working of the present system. The system is viewed as a whole and the input to the
system are identified. The outputs from the organizations are traced to the various
processes. System analysis is concerned with becoming aware of the problem,
identifying the relevant and decisional variables, analyzing and synthesizing the various
factors and determining an optimal or at least a satisfactory solution or program of
action. A detailed study of the process must be made by various techniques like
interviews, questionnaires etc. The data collected by these sources must be scrutinized to
arrive to a conclusion. The conclusion is an understanding of how the system functions.
This system is called the existing system. Now the existing system is subjected to close
study and problem areas are identified. The designer now functions as a problem solver
and tries to sort out the difficulties that the enterprise faces. The solutions are given as
proposals. The proposal is then weighed with the existing system analytically and the
best one is selected. The proposal is presented to the user for an endorsement by the user.
The proposal is reviewed on user request and suitable changes are made. This is loop that
ends as soon as the user is satisfied with proposal. Preliminary study is the process of
gathering and interpreting facts, using the information for further studies on the system.
Preliminary study is problem solving activity that requires intensive communication
between the system users and system developers. It does various feasibility studies. In
these studies a rough figure of the system activities can be obtained, from which the
decision about the strategies to be followed for effective system study and analysis can
be taken.

[9]
3.3 Project Modules

3.3.1 Admin Module

Admin has the following features:

Admin Login

Admin can add new faculty

Admin can View faculty list

Admin can Update faculty data

Admin can Delete faculty

Admin can Manage Student

Admin can Check feedback given by student

Admin can check average feedback for faculty

Admin can update the contact details dynamically

Admin can update password

3.3.2 Faculty Module

Faculty can do the following things:

Faculty can login

Faculty can update their profile

[10]
 
Faculty can update Password

Faculty can Check feedback given by students

Faculty can check average feedback given by students

Logout

3.3.3 Student Module

Student can do the following things:

Student can Register

Student can Login

Student can view profile

Student can update profile

Student can update Password

Student can choose faculty and give feedback for every Questions

[11]
3.4 UML Diagram

UML stands for Unified Modeling Language & it is the successor to the wave of
Object Oriented Analysis and Design (OOA&D) methods that appeared in the late
80’s. It most directly unifies the methods of Booch, Rumbaugh (OMT) and Jacobson.
The UML is called a modeling language, not a method. Most methods consist at least
in principle, of both a modeling language and a process. The Modeling language is
that notation that methods used to express design.

Use Case Diagram For Admin Module:

Fig: Use Case Diagram For Admin

[12]
Use Case Diagram For Faculty Module:

Fig: Use Case Diagram For Faculty

Fig: Use Case Diagram For Student Module

[13]
3.5 Data Flow Diagram

A data-flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system. DFDs can also be used for the visualization of data
processing (structured design). A data flow diagram (DFD) is a significant modeling
technique for analyzing and constructing information processes. DFD literally means
an illustration that explains the course or movement of information in a process.
DFD illustrates this flow of information in a process based on the inputs and outputs.
A DFD can be referred to as a Process Model. A DFD has 3 parts:


Level 0: It shows the interaction between the system and external agents,
which act as data sources and data sinks. On the context diagram (also
known as the Level 0 DFD), the system's interactions with the outside world
are modeled purely in terms of data flows across the system boundary. The
context diagram shows the entire system as a single process, and gives no
clues as to its internal organization.


Level 1: The Level 1 DFD shows how the system is divided into sub-systems
(processes), each of which deals with one or more of the data flows to or
from an external agent, and which together provide all of the functionality of
the system as a whole.


Level 2: The level 1 DFD is further spread and split into more descriptive and
detailed description about the project as level 2 DFD . The level 2 DFD can
be a number of data flows which will finally show the entire description of
the software project.

[14]
Level 0 DFD For Student Assignment Feedback System:

Level 1 DFD For Student Assignment Feedback System:

[15]
 Level 2 DFD For Student Assignment Feedback System:

3.6 Entity-Relationship Diagram(E-R Diagram):

E-R Model is a popular high level conceptual data model. This model and its
variations are frequently used for the conceptual design of database application and many
database design tools employ its concept.
A database that confirms to an E-R diagram can be represented by a collecton of tables in the
relational system. The mapping of E-R diagram to the entities are:

[16]
• Attributes
• Relations
o Many-to-many
o Many-to-one o
One-to-many o
One-to-one
• Weak entities
• Sub-type and super-type

The entities and their relationshops between them are shown using the following conventions.
• An entity is shown in rectangle.

• A diamond represent the relationship among number of entities.

• The attributes shown as ovals are connected to the entities or relationship by lines.

• Diamond,oval and relationships are labeled.

• Model is an abstraction process that hides super details while

highlighting details relation to application at end.

• A data model is a mechanism that provides this abstraction for database application.

• Data modeling is used for representing entities and their relationship in the database.

• Entities are the basic units used in modeling database entities can have concrete existence
or constitute ideas or concepts.

• Entity type or entity set is a group of similar objects concern to an organization for which
it maintain data,

• Properties are characteristics of an entity also called as attributes.

• A key is a single attribute or combination of 2 or more attributes of an entity set is used to
identify one or more instances of the set.

[17]
• In relational model we represent the entity by a relation and use tuples to represent
an instance of the entity.

• Relationship is used in data modeling to represent in association between an entity set.

• An association between two attributes indicates that the values of the associated attributes
are independent.

Fig: E-R Diagram For Student Assignment Feedback System

[18]
 3.7 Design

In this phase, a logical system is built which fulfils the given requirements. Design phase of
software development deals with transforming the clients requirements into a logically
working system.

The general tasks involved in the design process are the following:

1. Design various blocks for overall system processes.

2. Design smaller, compact and workable modules in each block.
3. Design various database structures.
4. Specify details of programs to achieve desired functionality.
5. Design the form of inputs, and outputs of the system.
6. Perform documentation of the design.
7. System reviews.

3.7.1 Primary Design Phase

In this phase, the system is designed at block level. The blocks are created on the basis of
analysis done in the problem identification phase. Different blocks are created for different
functions emphasis is put on minimizing the information flow between blocks. Thus, all
activities which require more interaction are kept in one block.

3.7.2 Secondary Design Phase

In the secondary phase the detailed design of every block is performed.

3.7.3 User Interface Design

User Interface Design is concerned with the dialogue between a user and the computer. It is
concerned with everything from starting the system or logging into the system to the
eventually presentation of desired inputs and outputs. The overall flow of screens and
messages is called a dialogue.

[19]
 3.8 Testing

Testing is vital for the success of any software. no system design is ever perfect. Testing is
also carried in two phases. first phase is during the software engineering that is during the
module creation. second phase is after the completion of software. this is system testing
which verifies that the whole set of programs hanged together.

3.8.1 White Box Testing

In this technique, the close examination of the logical parts through the software are tested by
cases that exercise species sets of conditions or loops. all logical parts of the software
checked once. errors that can be corrected using this technique are typographical errors,
logical expressions which should be executed once may be getting executed more than once
and error resulting by using wrong controls and loops. When the box testing tests all the
independent part within a module a logical decisions on their true and the false side are
exercised , all loops and bounds within their operational bounds were exercised and internal
data structure to ensure their validity were exercised once.

3.8.2 Black Box Testing

This method enables the software engineer to device sets of input techniques that fully
exercise all functional requirements for a program. black box testing tests the input, the
output and the external data. it checks whether the input data is correct and whether we are
getting the desired output.

3.8.3 Alpha Testing

Acceptance testing is also sometimes called alpha testing. Be spoke systems are developed
for a single customer. The alpha testing proceeds until the system developer and the customer
agree that the provided system is an acceptable implementation of the system requirements.

[20]
 3.8.4 Beta Testing

On the other hand, when a system is to be marked as a software product, another process
called beta testing is often conducted. During beta testing, a system is delivered among a
number of potential users who agree to use it. The customers then report problems to the
developers. This provides the product for real use and detects errors which may not have been
anticipated by the system developers.

3.8.5 Unit Testing

Each module is considered independently. it focuses on each unit of software as implemented

in the source code. it is white box testing.

3.8.6 Integration Testing

Integration testing aims at constructing the program structure while at the same constructing
tests to uncover errors associated with interfacing the modules. modules are integrated by
using the top down approach.

[21]
 IMPLEMENTATION

4. Implementation

In this project we implemented the system which works on the concept of online feedback from
students which is the replacement of existing paper feedback system which is so complicated
method for finding an average for particular subject feedback which is submitted by students. In
this system we have design main three forms student login form, admin login form, faculty login
form. Student will login in their login form with proper id and password which is provided by
admin at the time of registration. After that if student want any changes in his profile then there is
an option for edit such particular information of his own. After that the subject contains page is
displayed, where the subject is located in it and as per the selection from student students
continued to their feedback after this page the feedback page is displayed. This page contains a
form which includes such questions about the teachers where it contains some simple question
regarding particular subject faculty. After giving the feedback the page appeared which contains a
message like you are feedback is submitted. Then after feedback is submitted there is a log out
button after click on it student will successfully log out from their profile.

4.1 Model View Controller (MVC) Diagram

Model View Controller or MVC as it is popularly called, is a software design pattern for
developing web applications. A Model View Controller pattern is made up of the following
three parts:

[22]
 • Model - The lowest level of the pattern which is responsible for maintaining data.
• View - This is responsible for displaying all or a portion of the data to the user.
• Controller - Software Code that controls the interactions between the Model and View.

MVC is popular as it isolates the application logic from the user interface layer and supports
separation of concerns. Here the Controller receives all requests for the application and then
works with the Model to prepare any data needed by the View. The View then uses the data
prepared by the Controller to generate a final presentable response. The MVC abstraction can
be graphically represented as follows.

[23]
 OUTPUTS

4. Outputs

HOMEPAGE

[24]
ABOUT PAGE

[25]
REGISTRATION PAGE

[26]
CONTACT PAGE

[27]
STUDENT LOGIN PAGE

[28]
FACULTY LOGIN PAGE

[29]
FACULTY DASHBOARD

[30]
UPDATE PASSWORD FACULTY

[31]
UPDATE PROFILE FACULTY

[32]
ADMIN LOGIN PAGE

[33]
ADD FACULTY

[34]
ADMIN DASHBOARD

[35]
MANAGE FACULTY

[36]
MANAGE STUDENT

FEEDBACK AVERAGE

[37]
 PERCENTAGE OF PROJECT REMAINS

6. Percentage Of the Project Remains

The Student Assignment Feedback System comprises of three modules namely Admin
Module, Faculty Module, Student Module so the first two module Admin & Faculty has been
implemented successfully but the student module is not done due to lack of time to be
implemented successfully.

So about 60% work has been completed to the best of our ability & we are committed to
complete the rest of the project in near future.

PORTION OF THE PROJECT REMAINS

7. Portion Of the Project Remains

The front end of the project has been done successfully & two of the three project modules is
also completed. The student module is remaining where student can view the questions &
based on that they will give the appropriate feedback. This portion of the work will be done in
the near future.

[38]
 CONCLUSION

8. Conclusion

This project is design for the purpose to reduce the lecturer’s time and to reduce the burden of
maintaining huge amount of records of students. At the time of feedback generation it apply
formulae for generate a feedback of particular subject. After that it will displayed the whole
record sheet to the faculty, when the staff will login in the system. As the comparison with
manual feedback or existing feedback system the new system is easier way to manage whole
things in a particular manner. As per the existing system it is very easy process to save each
and every record of individual student by the use of database.

[39]
 REFERENCES

9. References

[1] Google for problem solving

[2] https://www.freeprojectz.com/dfd
[3] https://www.ijraset.com/fileserve.php?FID=6568
[4] https://www.slideshare.net/karthikvenkatesh20
[5] https://www.tutorialspoint.com/html/
[6] https://www.w3schools.com/php/
[7] http://www.JSP.net/
[8] http://www.tutorialspoint.com/mysql/

[40]