School of Computer Sciences and Engineering

Department of Computer Science and Application

SUBMISSION OF PROJECT REPORT ON TOPIC

“Complaint Management System”

Using HTML, CSS, PHP & MySQL

UNDER THE FACULTY OF COMPUTER SCIENCE &APPLICATION

Submitted by

Akshay Kishor Jagtap

Prasad Prakash Hiray
Pranav Ajay ozarkar

Guide
Dr. Vaibhav Sonaje

Dean, School Of Computer Science & Engineering.

Department of Computer Science and Applications
School of Computer Sciences and Engineering
Sandip University, Nashik

Master of Computer Application

May- 2023

3
Trimbak Road, A/p - Mahiravani, Tal. & Dist. – Nashik, Pin – 422 213

School of Computer Sciences and Engineering

Department of Computer Science and Application
website: http://www.sandipuniversity.edu.in

CERTIFICATE
This is to certify that Mr. Akshay Kishor Jagtap PRN No. 210105051195,Mr. Prasad Prakash
Hiray PRN No. 210105051174,Mr. Pranav Ajay Ozarkar PRN No. 210105051175, student(s)
Of MCA Semester-IV has successfully completed the Project work on Titled“Complaint
Management System” under my guidance. This report submitted to Department of Computer
Science and Application, School of Computer Sciences and Engineering, Sandip
University,Nashik in the AY 2022-23 for partial fulfillment and requirement for the End
Semester Examination.
This report has not been submitted for any other examination and does not form
part of any other course undergone by the candidate.

Prof. Dr. Vaibhav Sonaje Dr. Vaibhav Sonaje

PROJECT GUIDEHOD

4
 Trimbak Road, A/p - Mahiravani, Tal. & Dist. – Nashik, Pin – 422 213

School of Computer Sciences and Engineering

Department of Computer Science and Application
website: http://www.sandipuniversity.edu.in

DECLARATION

I/We hereby declare that the miniProject work titled “Complaint Management
System” submitted to Sandip University, Nashik is a record of an original work done by
me/us under the guidance of Prof. Dr. Vaibhav Sonaje,Department of Computer Science
and Application, School of Computer Sciences and Engineering, Sandip University in the
AY 2022-23 for a partial fulfillment of requirement for the Completion of End Semester
Examination.
This report has not been submitted to any other University or Institute for the award of
any degree or diploma.

Name of Student(s):
 Akshay Kishor Jagtap
 Prasad Praksah Hiray
 Pranav Ajay Ozarkar

Date: ___/___/_______

Place: Nashik

6
 Trimbak Road, A/p - Mahiravani, Tal. & Dist. – Nashik, Pin – 422 213

School of Computer Sciences and Engineering

Department of Computer Science and Application
website: http://www.sandipuniversity.edu.in

ACKNOWLEDGEMENT
I/We would like to express my/our special thanks of gratitude’s to our Project guide Dr.
Vaibhav Sonaje Department of Computer Science and Application, School of Computer
Sciences and Engineering, SandipUniversity, Nashik for his/her able guidance and
support in completing this report.

I/We would like to extend my gratitude to Dr. Vaibhav Sonaje,Dean, SOCSE,

HOD,CSA for providing me/us with all the facility that was required to complete this
reportsuccessfully.
I/WealsothankthemanagementofSandipUniversity,Nashikforprovidingme/usinfrastruct
ure and lab facility to completion of this Project.
At last but not the least I/we am/are thankful to all faculty members, staff, and friends
who have been always helping and encouraging me/us throughout the period of this
internship/project.

Name of Student(s):
 Akshay Kishor Jagtap
 Prasad Praksah Hiray
 Pranav Ajay Ozarkar

7
 Abstract

The main purpose of this project is to help the usera platform where he can lodge a complaint and
getting his problems solved in online without going to the officer regularly until the problem issolved.
By this system the user can save his time. Its main purpose is to provide a smart and easy way through
Android or Web Application for Complaint registrationanditsTracking and eradicating system. We
want to develop an application for complaint management system where user can register complaints
for anything.Totrans form the existing manual compliant management system into anautomate
system.For the better managementof complaints to improve efficiency. This system can be used in any
sector like government, private etc. When a user submits a complaint it is visible to admin & admin
can take the action on the complaint and after resolving the issue, the admin can change the status of
the complaint to closed with a remark.

8
 INDEX

Sr. No Contents

1. Problem Defination

2. Rationale

3. Aim /Benefits of Mini-Project:

4. Course Outcomes Achieved (COs)

5. Literature Review

6. Actual Resources Used

7. Outputs of the Mini-Project:

8. Skill Developed / Learning Outcome of this Project:

9. Applications of Project

10. Testing

11. Conclusion
Problem Definition:

A complaint Management System lets user to register a complaint he/she is facing to get it
solved.Many times a user is unable to complain about certain things offline. This system is
very useful where the user can register for an account in the portal, after registration a user can
login to their account and register a complaint according to the category and then the complaint
is reviewed by the admin and they will take the action on that complaint. It saves a lot of time
of the user and a user also tracks their complaint status. The offline system is very time
consuming where user have to visit a certain place to register a complaint.

Rationale:
The Complaint Management System has user registration to create a web-based account or
profile. It has two logins, One for user and one for Admin who will take an action on the
particular complaint. The user have a dashboard after login and a menu with options like
lodging a complaint, checking history of complaint, profile update option, password changing
option and tracking of complaint. An admin has a menu of checking all user lists, checking
pending, in progress and closed complaints etc. Admin also has profile and changing password
option.

Aim /Benefits of Project:

Our project aims to:
To keep the hardware’s in the Lab in such a way that it will neither overstock nor understock.
To implement various concepts of PHP web based programming language.
To provide ease to the users of hardware devices in the lab.
To maximize the efficiency in the work and studies.

Course Outcomes Achieved (COs):

CO602.1: Develop a program using control statement.

CO602.2: Develop Programs by applying various object oriented concepts.
CO602.3: Use form controls with validation to collect user’s input.

Literature Review:

An institution without an information system will have no track record of its performance
history or its presentstatus and will be unable to forecast the future of its business. According to
O’Brien & Markas (2007), thefundamental roles of an information system are to support
business processes, support decision-making by itsemployees and support strategies for
competitive advantage. Laudon & Laudon (2007) point out that the role of information systems
is to help institutions obtain operational excellence to improve the efficiency of their
operationsin order to achieve higher profitability.
Actual Methodology followed:
1.First of all selected the project topic under the guidance of our staff.

2. Checked out the available resources related to the topic.

3. Studied the topic in detail and confirmed it by the staff.

4. Referred various Websites, Videos and Books related to PHP programming language.

5. Also referred the PPT’S and notes provided by the respected staff.

6. Collected the important methods and functions that can be used in our Project.

7. Prepared Proposal and get checked it from respected staff.

8. Prepared report and get checked it from respected staff.

9. Done corrections told by respected staff .

10. Submitted the project along with viva.

Sr No Name Of Resources Specifications Qty Remarks

1 Computer System Asus Vivobook (i3) 01 Available

*GB RAM
2 Editor Visual Studio Code 01 Available

3 Other Resources XAMPP Server 01 Available

(Apache, SQL)

Outputs of the Project:

Skill Developed / Learning outcome of this Mini-Project:

Technical Skills:

• Knowledge of PHP Concepts

• Loops in PHP

• Use of inbuilt Functions in PHP

• Error Solving
Soft Skills:

• Problem Solving

• Communication Skills

• Speaking Confidently

• Professional Attitude

Applications of Project:

• Letting user to register for any kind of complaints online and tracking the status of the
complaint until oit is resolved.

• To ensure there's always enough stock of working hardware devices for users.

• A Complaint Management System generally asks a user to create a username and

password, and possibly answer other security questions as well and then use his account.

TESTING

Testing is a process of executing a program with the indent of finding an error. Testing is a
crucial element of software quality assurance and presents ultimate review of specification,
design and coding.
System Testing is an important phase. Testing represents an interesting anomaly for the
software. Thusa series of testing are performed for the proposed system before the system is
ready for user acceptance testing.
A good test case is one that has a high probability of finding an as undiscovered error. A
successful test is one that uncovers an as undiscovered error.

TESTING OBJECTIVES:

• Testing is a process of executing a program with the intent of finding an error

• A good test case is one that has a probability of finding an as yet undiscovered error
• A successful test is one that uncovers an undiscovered error
TESTING PRINCIPLES

• All tests should be traceable to end user Requirements.

• Tests should be planned long before testing begins
• Testing should begin on a small scale and progress towards testing in large exhaustive
testing is not possible
• To be most effective testing should be conducted by a independent third party
• The primary objective for test case design is to derive a set of tests that has the highest
livelihood for uncovering defects in software. To accomplish this objective two different
categories of test case design techniques are used. They are;
• White box testing.
• Black box testing.

WHITE-BOX TESTING:

White box testing focus on the program control structure. Test cases are derived to ensure that
all statements in the program have been executed at least once during testing and that all logical
conditions have been executed.

BLOCK-BOX TESTING:

Black box testing is designed to validate functional requirements without regard to the internal
workings of a program. Black box testing mainly focuses on the information domain of the
software, deriving test cases by partitioning input and output in a manner that provides through
test coverage. Incorrect and missing functions, interface errors, errors in data structures, error
in functional logic are the errors falling in this category.

TESTING STRATEGIES:

A strategy for software testing must accommodate low-level tests that are necessary to verify
that all small source code segment has been correctly implemented as well as high-level tests
that validate major system functions against customer requirements.

TESTING FUNDAMENTALS:

Testing is a process of executing program with the intent of finding error. A good test case is
one that has high probability of finding an undiscovered error. If testing is conducted
successfully it uncovers the errors in the software. Testing cannot show the absence of defects,
it can only show that software defects present.
TESTING INFORMATION FLOW:

Information flow for testing flows the pattern. Two class of input provided to test the process.
The software configuration includes a software requirements specification, a design
specification and source code.
Test configuration includes test plan and test cases and test tools. Tests are conducted and all
the results are evaluated. That is test results are compared with expected results. When
erroneous data are uncovered, an error is implied and debugging commences.

UNIT TESTING:

Unit testing is essential for the verification of the code produced during the coding phase and
hence the goal is to test the internal logic of the modules. Using the detailed design description
as a guide, important paths are tested to uncover errors with in the boundary of the modules.
These tests were carried out during the programming stage itself. All units of ViennaSQL were
successfully tested.

INTEGRATION TESTING :

Integration testing focuses on unit tested modules and build the program structure that dictated
by the design phase.

SYSTEM TESTING:

System testing tests the integration of each module in the system. It also tests to find
discrepancies between the system and it’s original objective, current specification and system
documentation. The primary concern is the compatibility of individual modules. Entire system
is working properly or not will be tested here, and specified path ODBC connection will correct
or not, and giving output or not are tested here these verifications and validations are done by
giving input values to the system and by comparing with expected output. Top-down testing
implementing here.

ACCEPTANCE TESTING:

This testing is done to verify the readiness of the system for the implementation. Acceptance
testing begins when the system is complete. Its purpose is to provide the end user with the
confidence that the system is ready for use. It involves planning and execution of functional
tests, performance tests and stress tests in order to demonstrate that the implemented system
satisfies its requirements.

Tools to special importance during acceptance testing include:

Test coverage Analyzer: Records the control paths followed for each test case. Timing
Analyzer: Also called as profiler, reports the time spent in various regions of the code are areas
to concentrate on to improve system performance.
Coding standards: static analyzers and standard checkers are used to inspect code for
deviations from standards and guidelines.
TEST CASES:

Test cases are derived to ensure that all statements in the program have been executed at least
once during testing and that all logical conditions have been executed.
Using White-Box testing methods, the software engineer can drive test cases that

• Guarantee that logical decisions on their true and false sides.

• Exercise all logical decisions on their true and false sides.
• Execute all loops at their boundaries and with in their operational bounds.
• Exercise internal data structure to assure their validity.

The test case specification for system testing has to be submitted for review before system
testing commences.

CONCLUSION
The package was designed in such a way that future modifications can be done easily. The
following conclusions can be deduced from the development of the project.
• Automation of the entire system improves the efficiency

• It provides a friendly graphical user interface which proves to be better when

comparedto the existing system.

• It gives appropriate access to the authorized users depending on their permissions.

• It effectively overcomes the delay in communications.

• Updating of information becomes so easier.

• System security, data security and reliability are the striking features.