Mahatma Education Society's

PILLAI COLLEGE OF ARTS COMMERCE &

SCIENCE
(AUTONOMUS),

NEW PANVEL

PROJECT REPORT ON
“DIGITAL-COMPLAINT BOX WESITE”

Submitted to,

“UNIVERSITY OF MUMBAI”
By,

MR.SURAJ RAJENDRA MALAP

UNDER THE GUIDENCE OF,

PROF. – Mrs. Rashmi Ghosalkar

2022-2023

Deparment of Information Technology

 CERTIFICATE

This is to certify that the project entitled “Digital-Comaplaint-Box website” is

successfully completed by Mr. Suraj Rajendra Malap as per the syllabus and in
partial fulfillment for the completion of Bsc. Degree in Information Technology
of University of Mumbai. It is also to certify that this is the original work of the
candidate done during the academic year 2022-2023.
 ACKNOWLEDGEMENT

I Mr. Suraj Malap student of PILLAI COLLEGE OF ARTS ,

COMMERCE & SCIENCE , NEW PANVEL would like to express
my sincere gratitude towards Information Technology Department.
I would like to thank Mrs. Deepika Sharma H.O.D.(I.T.&C.S.)
for granting methe opportunity to build project for the college. Last
but not least I thank Lecturers. (Mrs.Rashmi) for their constant
support during the project. The project would not have been
completed without dedication, creativity and energy which my family
provided.

Yours faithfully,

Suraj Malap

(Final Year Information Technology)

 DECLARATION

I hereby declare that the project entitled, “Suraj Malap” done at

place Pillai College New Panvel, has not been in any case duplicated
to submit to any other university for the award of any degree. To the
best of my knowledge other than me, no one has submitted to any
other university. The project is done in partial fulfillment of the
requirements for the award of degree of BACHELOR OF SCIENCE
(INFORMATIONTECHNOLOGY) to be submitted as final
semester project as par to four curriculum.

Suraj Malap

Signature of the Student

Modules of the proposed system

Gantt chart

Entity Relationship diagram

Use Case
 Sequence diagram
3.6 Class diagram

3.7

3.8

3.9

3.10 Component diagram

3.11 Data Flow diagram

Data table constraints and integrity

 CHAPTER 1

INTRODUCTION

Digital complaint-box is the website that handles complaints, manages complaints, responds
to the complaints, and reports customer grievances. The user can easily register their
complaint and view the complaints that are previously registered. The user can process
through the website and follow the instructions. after the registration, the user will be able to
choose the categories for the complaints, user can select multiple categories like ( breaking
traffic signals, etc.) and can write complaints in brief and can submit them to the government.
Users can also register their complaints via social media, emails, and web forms and also post
images along with the descriptions. A user can also update it later by visiting his/her profile
where the complaints have been saved. When a user submits a complaint, it needs to be
routed to the right department or person or an area police station. While this process can be
done automatically, it increases the risk of delays. While on the other hand Admin can
change the features and update the new features. his system which could enhance the day-to-
day activities of the business with efficiency and correctness. Admin can also view the
complaints that are registered by the user. “Digital Complaint-Box website” helps to
overcome people's problems.

BACKGROUND

The existing Digital Complaint-Box website, In the Existing System users of the
Organization, has to Visit the Organization Whenever they have any Complaints regarding
the Products of the Organization, This wastes a lot Of time Whenever a customer of the bank
requires service from the bank he required moving to the bank and then he required to submit
the complaint to the specified officer. The problem is written on paper and will be submitted
to the bank. Then the manager will look after it and then he will take care of the customer’s
problems. After that the manager will enquire and allocate the problem to the specified
person in that department. The person will enquire about the problem and then rectifies it.
OBJECTIVES

1) Complaints are directly sent to the government without any third-party involvement.
2) User can make their own profile and see for registered complaints.
3) Users will get notifications after the successful registration of complaints.
4) Users can Give Complaints about any region or state anytime.
5) After the Complaint is get resolved, the user can send feedback
6) This Website will Provide High security on the database.
7) Data security is maintained to a relatively high level by implementing it at the Database
level to ensure that only authorized admin have access to confidential complaints about user
information.
8) Users can also Register their Complaints by uploading or clicking pictures.
9) If the Registered complaint is not get resolved, the user can again register the same
complaint again.
10) Admin can have all the authorization to check Registered complaints by the user.
11) To provide company with an effective tool to identify and target problem areas, monitor
complaints handling performance.
12) Controlling redundancy in storing the same data multiple times.
PURPOSE

Digital complaint-box provides an online way of solving the problems faced by the public by
saving time and eradicate corruption , And The ability of providing many of the reports on
the system , and add to Facilitate the process of submitting a complaints .

SCOPE

Digital complaint-boxis used to record resolve and respond to customer complaints, requests
as well as facilitate any other feedback.
 CHAPTER 2

SURVEY OF TECHNIQUES

A Survey of techniques involves Requirements determination studying the existing system

and gathering details to find out what are the requirements, how it works, and where
improvements should be made. It includes analysis of factual data, identification of essential
requirements, and selection of Requirement-fulfillment strategies. It can handle complex
subjects. It is easy to discover the key problems by seeking opinions from different people.
We can reach our customers by fulfilling their requirements by exploring the data that they
have shared.
● Interview customers, for their requirements
1) What is the most important thing that you want to implement in your project?
2) What are all the requirements that you wanted in your project
3) What kind of help, you will get after getting your requirements done?
4) What are all the requirements that you all needed for your promotion?

FACT FINDING

Fact-finding is the process of collection of data and information based on techniques that
contain a sampling of existing documents, research, observation, questionnaires, interviews,
prototyping, and joint requirements planning
In this, we actually collect the actual data from surveys of the project. There are different
types of surveys.
1. Questionnaires.
2. Interviews.
● Questionnaires.
Questionnaires are also one useful fact-finding technique to collect information from a large
number of users. People can fill out the forms and give answers freely to the analyst. This
technique is inexpensive.
● Interviews.
The interview is the most commonly used technique to collect information from face-to-face
interviews.
1) How you will use the gathered information for your project implementation?
2) How you are seeking more information for your project?
3) Is your App or Website effective?
4) Is your App or Website User Friendly?
5) Did all the registered Complaints get Resolved?
6) Is there any involvement of the third-party app?

FEASIBILITY STUDY

Feasibility analysis is used to determine the viability of an idea, such as ensuring a project is
legally and technically feasible as well as economically justified. It tells us whether a project
is worth the investment in some cases, a project may not be doable. There can be many
reasons for this, including requiring too many resources, which not only prevents those
resources from performing other tasks but also may cost more than an organization would
earn back by taking on a project that isn’t profitable.
There are different types of the feasibility study are as follows:
1) Technical feasibility:
It is an evaluation of hardware and software and how it meets the need of the proposed
system.
It is possible to develop the system by using NetBeans IDE using HTML as FrontEnd Tool
and MySql as backend tool it will be helpful for the Computer Institute. Admin, Customers,
and Employees can use it without any specific training.
2) Economical feasibility:
It deals with the analysis of a project’s costs and revenues in an effort to determine whether
or not it is logical and possible to complete. The Website will help in automating the offline
manual processes leading to profits and gains for the Private Business organizations. With
this Website, the machine and manpower utilization are expected to go down. This will save
time. It will benefit the private Business Organization
3) Financial feasibility:
It is an analysis of the marketplace to determine if the is economically practical and desirable
to develop a particular project. The total cost of the project is estimated. It is financially
feasible for a fully-fledged Private Business organization to afford the software.
4) Operational feasibility:
Operational feasibility is the measure of how well the proposed system solves the problems
and takes advantage of the opportunities identified during the scope definition.

STAKEHOLDERS

A stakeholder is anyone with an interest or investment in your project. Project stakeholders,

in general, can be single individuals or entire organizations who are affected by the execution
or outcome of a project. It doesn't matter whether the project affects them negatively or
positively — if they're affected, they're a stakeholder. These are the people and groups whose
objectives must be satisfied, as they have the power to make or break the project.
 CHAPTER 5

MODULES OF THE PROPOSED SYSTEM.

1.User model :
The user model is the model in which the local user and new user can Register and login into
the Website and make their account, they can add the details in the profile and edit it
afterward Users can register any complaints of any type by giving images and doing many
more.

a) Registration: The user can register himself in the system.

b) Login: the user can log in into the system
c) Home Page: the user see all the types of complaint and register as per their need, and
get many more features
d) View complaints: Users can see the complaints they have registered with all the
details they have given.
e) Logout: user can log out of their account

2. Admin model :
the Admin model has all the rights to make the changes in the website, he can see the
feedback and post many more categories on the website, also update the details, and track all
the details of the user’s Complaint.

a) Admin login: Admin can log in into the system.

b) Admin Home : Admin has different Departments
( ADD , VIEW,ALL COMPLAINTS,ALL USERS )
c) View: Admin can see all the details of the user ( complaints , profile,
departments,users)
d) Admin Logout: Admin can log out of the system.
GANTT CHART :

ENTITY RELATIONSHIP DIAGRAM :

USE CASE DIAGRAM :
SEQUENCE DIAGRAM :

Admin Model -

User Model –
CLASS DIAGRAM :

PACKAGE DIAGRAM :
DEPLOYMENT DIAGRAM :

COMPONENT DIAGRAM :
DATA FLOW DIAGRAM :
 CHAPTER 4

USER INTERFACE :

Login :

Registration:
Home Page:

View Comaplaints:
Admin login page:

Admin Home page:

Admin can see Department :

Admin can see Complaints:

Admin can view users :

Admin can add Department:

DATA TABLE CONSTRAINTS AND INTEGRITY :

1.Admin_deatils
Sr.no Field_name Datatype constrain
1 Admin_id Int Primary key
2 Admin_name Varchar(50) Not null
3 Admin_email Varchar(50) Not null
4 Admin_password Varchar(50) Not null
5 Dep_id Varchar(50) Not null

2.complaint_detials
Sr.no Field_name Datatype constrain
1 Complaint_id Int Primary key
2 Complaint_date Varchar(50) Not null
3 User_id Int Not null
4 Dept_code Int Not null
5 Complaint_topic Varchar(50) Not null
6 Complaint_des Varchar(50) Not null
7 Image_path Varchar(50) Not null
8 Complaint_ack Varchar(50) Not null
9 Compalint_status Varchar(50) Not null

3.Department_details
Sr.no Field_name Datatype constrain
1 Dept_id Int Primary key
2 Dept_name Varchar(50) Not null
3 Dept_discription Varchar(50) Not null

4.Image_details
Sr.no Field_name Datatype constrain
1 image_id Int Primary key
2 Complaint_id int Not null
3 Image_path Varchar(50) Not null

5.user_details
Sr.no Field_name Datatype constrain
1 Master_id Int Primary key
2 Master_name Varchar(50) Not null
3 Master_email Varchar(50) Not null
4 Master_password Varchar(50) Not null