Académique Documents
Professionnel Documents
Culture Documents
Chapter 1
INTRODUCTION
1.1 Project Description
It is multi user and a user can register once and post any number of issues in their
locality. It will provide a common man to deliver his complaints and problems to municipal
authority provides a complaint module which helps clicking up a picture of any problem that
people are facing and upload its image along with the complaint. In India we don’t have any
direct communication between the government and public in an efficient way for solving the
problems. That is for getting a problem solved in our place we have to bribe the officials and get
them solved in two months which can be solved actually in one month of time. In order to make
the goal of NIC come true we are going to develop a system which will be able to provide the
complete information to the public at any point of time regarding the problems. They are facing
currently and what is the impact of it and then how effectively the funds are utilized for the
development purpose can be known by public which also includes the online discussion forums
and feedback forms which will help them to communicate well with the government.
Chapter 2
In earlier existing systems, one must visit the office and complaints given through written
statement. Based on the priority, the complaint can be submitted in drop box or directly to the
commissioner or the concerned department, which may take physical effort and time consuming
task. In this existing system, one cannot get any acknowledgement that the complaint has been
received. Guarantee for problem solution is given through verbal communication. Hence, it is not
meant for problem.
As we all know, we are facing many problems in our daily life that are not fulfilled by the
government workers on daily time basis. The problems could be like sewage and drainage
problems, power cuts, street lightings, man holes, problems in the road structure or the levelling
of the roads and water supply problem etc. These problems occur in a day to day basic of life in
the Society and the Government workers fail to solve these problems time to time and cause a
delay in the work and that makes delay in serving the people of the Society. These problems are
all occurring because of the lack of communication medium between the Government workers
and the people of the Society. That is because that the people of the Society can contact the
particular Government worker either through letter medium or by visiting them directly in person
in their place.
In order to solve the problems being faced in the Society by the people, we need to make
an easy way to the people of the society such that they can contact the particular Government
officer to help the people to solve their problems. We are making a web based application or an
online portal through which people can post the problems that are being based on the daily basis
in the Society by clicking pictures of them or by making a video recording of the problem or by
just posting a text message through the post to the particular Government worker by making
them notice about the problems that have been occurring in the society without their notice and
that are being faced by the people. The people will now have the time to share the problems and
request for the solution from the particular Government worker without any hassle or time
consuming and making their day go in vain by aborting other personal problems in their life.
After taking considerations about the problems faced in the Society by the people
because of the lack of involvement of the Government workers. We have a made a implemental
project by making a web based application for making people easy to share the problems being
faced in the Society on time to time and reporting them to the Government workers so that they
can help the people of the Society by solving the problems that are being faced by the people of
the Society. Nowadays quite undeniable that the internet has revolutionized the world since its
effect will soon spread into lives of everyone at all levels. Unfortunately, there is no such web
application to raise the everyday social issues we are facing in our locality. The explosive growth
of the internet has given place to creations of these kinds of online portals to resolve user needs.
Ram: 1 GB or More
Bootstrap JavaScript
2.5 Analysis:
Chapter 3
SYSTEM DESIGN
SQL was initially developed at IBM by Donald D. Chamberlin and Raymond F. Boyce in
the early 1970s.[14] This version, initially called SEQUEL (Structured English Query
Language), was designed to manipulate and retrieve data stored in IBM's original quasi-
relational database management system, System R, which a group at IBM San Jose Research
Laboratory had developed during the 1970s.[14]The acronym SEQUEL was later changed to
SQL because "SEQUEL" was a trademark of the UK-based Hawker Siddeley aircraft
company.[15]
In the late 1970s, Relational Software, Inc. (now Oracle Corporation) saw the potential of
the concepts described by Codd, Chamberlin, and Boyce, and developed their own SQL-based
RDBMS with aspirations of selling it to the U.S. Navy, Central Intelligence Agency, and other
U.S. government agencies. In June 1979, Relational Software, Inc. introduced the first
commercially available implementation of SQL, Oracle V2 (Version2) for VAX computers.
The SQL language is subdivided into several language elements, including:
Clauses, which are constituent components of statements and queries. (In some cases, these
are optional.)[17]
Expressions, which can produce either scalar values, or tables consisting of columns and rows
of data
Predicates, which specify conditions that can be evaluated to SQL three-valued logic
(3VL)(true/false/unknown) or Boolean truth values and are used to limit the effects of statements
and queries, or to change program flow.
Queries, which retrieve the data based on specific criteria. This is an important element of
SQL.
Statements, which may have a persistent effect on schemata and data, or may control
transactions, program flow, connections, sessions, or diagnostics.
3.2.2 Normalization:
Definition: Normalization is the process of efficiently organizing data in a
database. There are two goals of the normalization process: eliminating redundant
data (for example, storing the same data in more than one table) and ensuring data
dependencies make sense (only storing related data in a table). Both of these are
worthy goals as they reduce the amount of space a database consumes and ensure
that data is logically stored. There are several benefits for using Normalization in
Database.
Benefits:
Chapter 4
4.1 Algorithms:
Index:
1. Include header.php.
2. Add background Image.
3. Add heading welcome to municipality.
4. Add subheading online complaints.
5. Add the buttons view complaints and post complaints.
6. Include footer.php.
Header:
1. Include dbconnect.php.
2. In the top header bar add face book, twitter, instagram, linkedin Icon and
reference to face book page, twitter page, instagram page.
3. In the bottom header bar.
4. If the session is for user.
5. Add dashboard, post complaints, my complaints, logout and respective
links to them.
6. Else if the session is for admin.
7. Add home, all complaints, logout.
8. Else
9. Add home, signup, login, post complaint and respective links to them.
dbconnect:
1. Store host name, database user name, database user password, database
name in respective variables.
2. Call mysqli_connect with the host name, database user name, database
user password, database name to connect to the database.
3. If connection failed die with mysqli_error.
4. Assign variables for index address, user login, user dashboard, admin
dashboard, admin login, view complaints, complaint lists respectively.
User signup:
1. Start session for user.
2. If time out then redirect to web_user_dashboard.
3. Include header.php.
4. Read user name and assign it to a variable using post method.
5. Read user email address and assign it to a variable using post method.
6. Read user phone number and assign it to a variable using post method.
7. Read user password and assign it to a variable using post method.
8. Check if the email address is already registered.
9. If email address is already registered then,
10.Show that the email address is already registered and please login.
11.Else insert the user name, user email address, phone number, password to
the users table and show successfully registered.
12.Include footer.php.
User login:
1. Start session for user.
2. If time out then redirect to web_user_dashboard.
3. Include header.php.
4. Read the user email address and user password from post method and
assign them to respective variables.
5. Check whether the given email address and password are matching with
the values in the user table.
6. If true successfully login to the user account and open user dashboard.
7. Else show incorrect credentials.
8. Include footer.php.
Admin login:
1. Start session for admin.
2. If time out then redirect to web_admin_dashboard.
3. Include header.php.
4. Read the admin email address and admin password from post method and
assign them to respective variables.
5. Check whether the given email address and password are matching with
the values in the admin table.
6. If true successfully login to the admin account and open admin
dashboard.
7. Else show incorrect credentials.
8. Include footer.php.
Complaint lists:
1. Include header.php.
2. Select all complaints from the posts table.
3. Display the title, area name, department and post status of all the posts
as a table.
4. Hyperlink all the titles with the corresponding view complaints page.
5. Include foote.php.
View complaints:
1. Include header.php.
2. For the selected post title select all the details from the posts table.
3. If the post details are found then
4. Display the post title, post description, post image, department, post
status.
5. Else display no complaints found.
6. Include footer.php.
(i)Replay post:
1. Include header.php.
2. Select all the post from the posts table.
3. Display the title, area name, department, post status and options such
as view and reply.
4. Under view, view the complaints.
5. Under reply, reply from the admin.
6. Include footer.php.
Footer:
4.2 Results:
4.2.1 Snapshots:
Fig.4.2.1.5 My complaint
Future enhancement:
Bibliography:
1.Cho Y., Hiltz R., & Fjermestad J., “An Analysis of Online Customer Complaints:
Implications for Web Complaint Management.” in Proceedings of the 35th Hawaii
International Conference on System Sciences, Hawaii, (2002).
2. C.Chiao-Chen and C. Yang-Chieh, "Comparing consumer complaint responses to
online and offline environment”.Research, vol. 21, pp. 124-137, 2011.
3. K. Coussement and D. Van den Poel, "Improving customer complaint management by
automatic email classification using linguistic style features as predictors," Decision Support
Systems, vol. 44, pp. 870-882, 2008.
4. V. Bosch and F. Enriquez, "TQM and QFD: exploiting a customer complaint
management system," International Journal of Quality and Reliability Management, vol.22, pp.
30-37, 2005.
5. ESRAA ABD EL-AZIZ ABD EL-SADEK AFIFY, “A model for Customer
Complaint Management system using SOA”, Management Information System Department,
Modern Academy for Computer Science & Management Technology, CAIRO, EGYPT.