VISVESVARAYA TECHNOLOGICAL UNIVERSITY

BELAGAVI-590018

A PROJECT REPORT
ON

“CLEANLINESS MANAGEMENT SYSTEM-KLEAN KUDLA”

BY
DEVIKA SHETTY SNEHAL S
4SF20CS032 4SF20CS146

In the partial fulfillment of the requirement for V Sem. B. E. (CSE)

DBMS LABORATORY WITH MINI PROJECT

Under the guidance of

Ms. ASHWINI C S
Assistant Professor, Dept. of CS&E

Department of Computer Science & Engineering

SAHYADRI
COLLEGE OF ENGINEERING & MANAGEMENT
An Autonomous Institution
Adyar, Mangaluru-575007
 An Autonomous Institution
Adyar, Mangaluru – 575007

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

CERTIFICATE

This is to certify that the project entitled “Cleanliness management system” is

submitted in partial fulfillment for the requirement of V sem. B. E. (Computer Science
& Engineering), “DBMS LABORATORY WITH MINI PROJECT”during the year
2022 – 2023 is a result of bonafide work carried out by

DEVIKA SHETTY 4SF20CS032

SNEHAL S 4SF20CS146

………………………… …………………………
Ms. ASHWINI C S Dr. NAGESH H R
Asst. Prof. Dept. of CS&E HOD, Dept. of CS&E
SCEM, Mangaluru SCEM, Mangaluru

Signature of the Examiners

1. ………………………….

2. ………………………….
 ABSTRACT

A Database Management System (DBMS) refers to the technology for creating and managing databases.
DBMS is a collection of inter-related data and a set of programs and a software tool to organize create,
retrieve, update and manage data in a database. The DBMS software additionally comprises the core
facilities to administer the database. The main aim of DBMS is to supply a way to store up and retrieve
database information that is both convenient and efficient.

This project presents a database management system (DBMS) for cleanliness management. The system
allows users to efficiently track and manage the cleanliness of public spaces, such as parks and streets. The
DBMS is designed to provide an interface for users to report cleanliness issues and track the status of
cleaning efforts. The system also provides an administration panel for authorized personnel to manage and
analyze the collected data, such as identifying trends and hotspots of cleanliness issues. The
implementation of the system has demonstrated improved efficiency and transparency in the cleanliness
management process, resulting in a cleaner and more livable public environment.
 ACKNOWLEDGEMENT

It is with great satisfaction and euphoria that we are submitting the Mini Project Report on “Cleanliness
management system”. We have completed it as a part of the V semester DBMS Laboratory with Mini
Project (18CSL58) of Bachelor of Engineering in Computer Science & Engineering of Visvesvaraya
Technological University, Belagavi.

We are profoundly indebted to our guide, Ms. Ashwini C S, Assistant Professor, Department of
Computer Science & Engineering for innumerable acts of timely advice, encouragement and we sincerely
express our gratitude.

We express our sincere gratitude to Dr. Nagesh H R, Head of the Department of Computer Science &
Engineering for his invaluable support and guidance.

We sincerely thankful to our beloved Principal Dr. Rajesha S, Sahyadri College of Engineering &
Management and Dr. D. L. Prabhakara, Director, Sahyadri Educational Institutions, who have always
been a great source of inspiration.

Finally, yet importantly, we express our heartfelt thanks to our family & friends for their wishes and
encouragement throughout the work.

Devika Shetty Snehal S

4SF20CS032 4SF20CS146
V Sem, B.E., CSE V Sem, B.E., CSE
SCEM, Mangaluru SCEM, Mangaluru
 PAGE INDEX

Chapter No. Topic Page No.

1 Introduction 1-2

1.1 Introduction to Database Management System

1.2 Oracle
1.3 My SQL
1.4 JAVA
1.5 Net Beans
2 Requirement specifications 3
3 Design 4-10

3.1 ER Diagram
3.2 Relational schema(ER to relational schema
3.2.1 Mapping of Regular Entity Types
3.2.2 Mapping of Weak Entity Types
3.2.3 Mapping of Binary 1:1 Relationship Types
3.2.4 Mapping of Binary 1:N Relationship Types
3.2.5 Mapping of Binary M:N Relationship Types
3.2.6 Mapping of Multivalued attributes
3.2.7 Mapping of N-ary Relationship

3.3 Schema Diagram

4 Normalization 13-15
5 Implementation 16-26
 5.1 Table Structure

5.1.1 Teamform Relation

5.1.2 Employee Relation
5.1.3 Complaints Relation
5.1.4 Volunteers Relation
5.1.5 Zones Relation

5.2 Functionality
5.2.1 Connecting to Database
5.2.2 Selection
5.2.3 Insertion
5.2.4 Update
5.2.5 Delete
5.2.6 Trigger

6 Result 27-40

Department of Computer Science and Engineering, Mangaluru

 7 Conclusion 41
8 References 42

Department of Computer Science and Engineering, Mangaluru

 Cleanliness management System

CHAPTER 1

INTRODUCTION

1.1. INTRODUCTION TO DATABASE MANAGEMENT SYSTEM

DBMS stands for “Database Management System”. In short, a DBMS is a database program. Technically
speaking it is a software system that uses a standard method of cataloging, retrieving and running queries on
data. The DBMS manages incoming data, organizes it, and provides ways for the data to be modified or
extracted by used or other programs.

A DBMS makes it possible for end users to create, read, update and delete data in a database. The DBMS
essentially serves as an interface between the database and end users or application programs, ensuring that
data is consistently organized and remains easily accessible.

DBMS include change management, performance monitoring/tuning and backup and recovery. Many
database management systems are also responsible for automated rollbacks, restarts and recovery as well as
the logging and auditing of activity. The DBMS can offer both logical and physical data independence. That
means it can protect users and applications from needing to know where data is stored or having to be
concerned about changes to the physical structure of data (storage and hardware).

As long as programs use the application programming interface (API) for the database that is provided by
the DBMS, developers won’t have to modify programs just because changes have been made to the database.
With relational DBMSs (RDBMSs), this API is SQL, a standard programming language.

1.2. ORACLE

Oracle Database (commonly referred to as Oracle RDBMS or simply as Oracle) [3] is a multi-model
database management system produced and marketed by Oracle Corporation. It is a database commonly
used for running online transaction processing (OLTP), data warehousing (DW), etc. Larry Ellison and his
two friends and former co-workers, Bob Miner and Ed Oates started a consultancy called Software
Development and Laboratories (SDL) in1977. SDL developed the original version of oracle.

Department of Computer Science and Engineering, Mangaluru 1

 Cleanliness management System

1.3. MYSQL

MYSQL, the most popular Open-Source SQL database management system, is developed, distributed, and
supported by Oracle Corporation. MySQL is a component of the LAMP web application software stack (and
others), which is an acronym for Linux, Apache, MySQL, Perl/PHP/Python. MySQL is used by many
database-driven web applications, including Drupal, Joomla, php BB and WordPress.

1.4. JAVA

Java is a popular programming language. It is owned by Oracle, and more devices run Java. Java works on
different platforms (Windows, Mac, Linux Raspberry Pi, etc.). It is open-source, secure, fast, free and
powerful. As Java is close to C++ and C#. It makes it easy for programmers to switch to Java. Java was
developed in the mid-1990 by James A. Gosling, a former computer scientist with Sun Microsystems.

1.5. NETBEANS

NetBeans is an integrated development (IDE) for java. NetBeans allows applications to be developed from a
set of modular software components called modules. The NetBeans Platform is a framework for simplifying
the development of Java Swing desktop applications.

The NetBeans IDE bundle for Java SE contains what is needed to start developing NetBeans plugins and
NetBeans Platform based applications. The underlying NetBeans platform supports creation of new
applications and further development of existing applications using modular software components. As an
application running on the NetBeans Platform, the NetBeans IDE itself is extensible and can be extended to
support new language.

Department of Computer Science and Engineering, Mangaluru 2

 Cleanliness management system

CHAPTER 2

REQUIREMENT SPECIFICATION

2.1. HARDWARE REQUIREMENTS

• Processor: Any processor above 500 MHz
• RAM: 4GB
• Hard Disk: 500GB
• Input Device: Standard keyboard and Mouse
• Output Device : Monitor

2.2. SOFTWARE REQUIREMENTS

• Database: Oracle Express 10g
• Programming Language : Java
• IDE :Apache NetBeans 8.0.2

Department of Computer Science and Engineering, Mangaluru 3

 Cleanliness management system

CHAPTER 3

DESIGN

3.1 ER DIAGRAM

An entity–relationship model describes interrelated things of interest in a specific domain of knowledge. The
ER Diagram of our project is shown in the Figure:2.1.1

Symbols in Entity Relationship:

Attribute Relationship

Entity Derived Attribute

Multivalued Attribute Weak Entity

Weak Relationship Key Attribute

KeyAttribute

Figure 3.1.1 ER Notation

Department of Computer Science and Engineering, Mangaluru 4

 Cleanliness management system

ER DIAGRAM

Figure 3.1.2 ER Diagram

Department of Computer Science and Engineering, Mangaluru 5

 Cleanliness management system

3.2 RELATIONAL SCHEMA

3.2.1 Mapping of Regular Entity Types

For every entity in our relationship diagram, we have created a separate relation. These created
relations contain the respected attributes and respected primary key.

TEAMFORM

EID VID ZNAME TID TASK TDATE

EMPLOYEE

EID ENAME EPHONE EMAIL ELOC

COMPLAINTS

ZNAME CID PNAME COMP CDATE PHONE

VOLUNTEERS

VID VNAME VMAIL VPHONE VLOC

ZONES

ZNAME ZID

Figure 3.2.1: Mapping of Regular Entities

Department of Computer Science and Engineering, Mangaluru 6

 Cleanliness management system

3.2.2 Mapping of Weak Entity Types

The ER Diagram contains no weak entities, this step is ignored in this project.

3.2.3 Mapping of Binary 1:1 Relationship Types

The ER diagram contains no 1:1 entity, this step is ignored in the project.

3.2.4 Mapping of Binary 1:N Relationship Types

There are three 1:N relation in schema diagram. There is a foreign key approach and have included the
primary key of one relation as the foreign key in the N-sided relation.

For Teamform and Employee

Adding Primary Key of Teamform in Employee as Foreign key

Department of Computer Science and Engineering, Mangaluru 7

 Cleanliness management system

For Teamform and Complaints(1:N)

Adding Primary Key of Teamform in Complaints as Foreign Key.

Department of Computer Science and Engineering, Mangaluru 8

 Cleanliness management system

For Teamform and Volunteers (1:N)

Adding Primary Key of Teamform in Volunteers as Foreign key

Department of Computer Science and Engineering, Mangaluru 9

 Cleanliness management system

For Complaints and Zones(1:N)

Adding Primary Key of Complaints in Zones as Foreign Key.

3.2.5 Mapping of Binary M:N Relationship Types

The ER Diagram contains no M:N entity, this step is ignored in the project.

Department of Computer Science and Engineering, Mangaluru 10

 Cleanliness management system

3.2.6 Mapping of Multivalued Attributes

The ER Diagram contains no multivalued attributes, this step is ignored for our project.

3.2.7 Mapping of N-ary Relationship Types

Since our ER Diagram contains no relation having N-ary Relationships, this step is ignored for
our project.

Department of Computer Science and Engineering, Mangaluru 11

 Cleanliness management system

3.3 SCHEMA DIAGRAM

Fig 3.3.1 Schema Diagram

Department of Computer Science and Engineering, Mangaluru 12

 Cleanliness management system

CHAPTER 4

NORMALIZATION

TEAMFORM

FD1:{EID,VID,ZNAME} -> {TASK,TDATE,TID}

⚫ The TEAMFORM relation is in 1NF because there are no multivalued attributes in the relation schema.
⚫ It is in 2NF because the relation is in 1NF and all the attributes in the relation schema are fully
functionally dependent on the primary key.
⚫ It is in 3NF because the relation is in 2NF and there are no transitive dependencies.

EMPLOYEE

FD2: {EID} {ENAME, EPHONE, EEMAIL, ELOC}

⚫ The EMPLOYEE relation is in 1NF because there are no multivalued attributes in the relation schema.
⚫ It is in 2NF because the relation is in 1NF and all the attributes in the relation schema are fully
functionally dependent on the primary key.
⚫ It is in 3NF because the relation is in 2NF and there are no transitive dependencies.
Department of Computer Science and Engineering, Mangaluru 13
 Cleanliness management system

COMPLAINTS

FD3: {ZNAME} {CID,PNAME,PHONE,COMP,ZNAME,CDATE}

⚫ The COMPLAINTS relation is in 1NF because there are no multivalued attributes in the relation schema.
⚫ It is in 2NF because the relation is in 1NF and all the attributes in the relation schema are fully
functionally dependent on the primary key.
⚫ It is in 3NF because the relation is in 2NF and there are no transitive dependencies.

VOLUNTEERS

FD4: {VID} {VNAME,VMAIL,VPHONE,VLOC }

⚫ The VOLUNTEERS relation is in 1NF because there are no multivalued attributes in the relation schema.
⚫ It is in 2NF because the relation is in 1NF and all the attributes in the relation schema are fully
functionally dependent on the primary key.
⚫ It is in 3NF because the relation is in 2NF and there are no transitive dependencies.

Department of Computer Science and Engineering, Mangaluru 14

 Cleanliness management system

ZONES

FD5: {ZNAME} {ZID}

⚫ The Transaction relation is in 1NF because there are no multivalued attributes in the relation schema.
⚫ It is in 2NF because the relation is in 1NF and all the attributes in the relation schema are fully
functionally dependent on the primary key.
⚫ It is in 3NF because the relation is in 2NF and there are no transitive dependencies.

Department of Computer Science and Engineering, Mangaluru 15

 Cleanliness management system

CHAPTER 5

IMPLEMENTATION

5.1 TABLE STRUCTURE

5.1.1 TEAMFORM RELATION

CREATE TABLE teamform (

TID VARCHAR(5) NOT NULL,
EID VARCHAR(5) NOT NULL,
VID VARCHAR(5) NOT NULL,
ZNAME VARCHAR(20) NOT NULL,
TASK VARCHAR(20) NOT NULL,
TDATE DATE,
PRIMARY KEY (EID, VID, ZNAME)
);

5.1.1 TEAMFORM RELATION

Department of Computer Science and Engineering, Mangaluru 16

 Cleanliness management system

5.1.2 EMPLOYEE RELATION

CREATE TABLE entity (

EID VARCHAR(5) NOT NULL,
ENAME VARCHAR(20) NOT NULL,
EPHONE NUMBER(10) NOT NULL,
EEMAIL VARCHAR(30) NOT NULL,
ELOC VARCHAR(20) NOT NULL,
PRIMARY KEY (EID)
);

Fig 5.1.2 EMPLOYEE RELATION

5.1.3 COMPLAINTS RELATION

CREATE TABLE complaints (

CID VARCHAR(5) NOT NULL,
PNAME VARCHAR(20) NOT NULL,
PHONE NUMBER(10) NOT NULL,
ZNAME VARCHAR(20) NOT NULL,
CDATE DATE NOT NULL,
COMP VARCHAR(20) NOT NULL,
PRIMARY KEY (CID)
);

Fig 5.1.3 COMPLAINTS RELATION

Department of Computer Science and Engineering, Mangaluru 17

 Cleanliness management system

5.1.4 VOLUNTEERS RELATION

CREATE TABLE volunteers (

VID VARCHAR(5) NOT NULL,
VNAME VARCHAR(20) NOT NULL,
VEMAIL VARCHAR(30) NOT NULL,
VPHONE NUMBER(10) NOT NULL,
VLOC VARCHAR(20) NOT NULL,
PRIMARY KEY (VID)
);

FIGURE 5.1.3 VOLUNTEER RELATION

5.1.5 ZONES RELATION

CREATE TABLE zones (

ZID VARCHAR(4) NOT NULL,
ZNAME VARCHAR(20) NOT NULL,
PRIMARY KEY (ZID)
);

FIGURE 5.1.3 ZONE RELATION

Department of Computer Science and Engineering, Mangaluru 18

 Cleanliness management system

5.2 FUNCTIONALITY

5.2.1 CONNECTING TO DATABASE

DriverManager.registerDriver(new OracleDriver());

con1=DriverManager.getConnection("jdbc:oracle:thin:@//localhost:1521/XE", "snehal", "snehal");

5.2.2 SELECTION

private void table_update()

{
int c;
try {
DriverManager.registerDriver(new OracleDriver());
con1=DriverManager.getConnection("jdbc:oracle:thin:@//localhost:1521/XE", "snehal", "snehal");
insert = con1.prepareStatement("select * from volunteers order by vid");
ResultSet rs=insert.executeQuery();
ResultSetMetaData Rss=rs.getMetaData();
c=Rss.getColumnCount();
DefaultTableModel Df=(DefaultTableModel)jTable1.getModel();
Df.setRowCount(0);
while(rs.next())
{
Vector v2=new Vector();
for(int a=1;a<=c;a++)
{
v2.add(rs.getString("vid"));
v2.add(rs.getString("vname"));
v2.add(rs.getString("vemail"));
v2.add(rs.getString("vphone"));
v2.add(rs.getString("vloc"));
}
Df.addRow(v2);

Department of Computer Science and Engineering, Mangaluru 19

 Cleanliness management system

} catch (SQLException ex) {

ex.printStackTrace();
}

5.2.3 INSERTION

private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {

String name =jTextField1.getText();

try {
DriverManager.registerDriver(new OracleDriver());

con1=DriverManager.getConnection("jdbc:oracle:thin:@//localhost:1521/XE", "snehal", "snehal");

insert = con1.prepareStatement("insert into zones (zname)values(?)");

insert.setString(1,name);

insert.executeUpdate();
JOptionPane.showMessageDialog(this,"Record Added");
table_update();

jTextField1.setText("");

jTextField1.requestFocus();

} catch (SQLException ex) {

JOptionPane.showMessageDialog(this,"Please Enter the Zone name"); }
}

Department of Computer Science and Engineering, Mangaluru 20

 Cleanliness management system

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {

// TODO add your handling code here:

String name =jTextField1.getText();
String vmail =jTextField2.getText();
String vpho =jTextField3.getText();
String vloc =jTextField4.getText();
String task =(String)jComboBox1.getSelectedItem();

try {
DriverManager.registerDriver(new OracleDriver());

con1=DriverManager.getConnection("jdbc:oracle:thin:@//localhost:1521/XE", "snehal",
"snehal");
insert = con1.prepareStatement("call insert_record(?,?,?,?,?)");

insert.setString(1,name);
insert.setString(2,vmail);
insert.setString(3,vpho);
insert.setString(4,vloc);
insert.setString(5,task);
insert.executeUpdate();
JOptionPane.showMessageDialog(this,"Record Added");
table_update();

jTextField1.setText("");
jTextField2.setText("");
jTextField3.setText("");
jTextField4.setText("");
jComboBox1.setSelectedItem("");
jTextField1.requestFocus();

} catch (SQLException ex) {

JOptionPane.showMessageDialog(this,"Please Check the Entered Details");
}
}

Department of Computer Science and Engineering, Mangaluru 21

 Cleanliness management system

5.2.4 UPDATE

private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {

// TODO add your handling code here:

DefaultTableModel Df=(DefaultTableModel)jTable1.getModel();

int selin=jTable1.getSelectedRow();

try

int fid=Integer.parseInt(Df.getValueAt(selin, 0).toString());

int fid1=Integer.parseInt(Df.getValueAt(selin, 1).toString());

int fid2=Integer.parseInt(Df.getValueAt(selin, 2).toString());

String name =jTextField1.getText();

String vmail =jTextField2.getText();

String vpho =jTextField3.getText();

String vloc =jTextField4.getText();

String task =(String)jComboBox1.getSelectedItem();

DriverManager.registerDriver(new OracleDriver());

con1=DriverManager.getConnection("jdbc:oracle:thin:@//localhost:1521/XE", "snehal",
"snehal");

insert = con1.prepareStatement("update teamform set tid=?,eid=?,vid=?,zname=?,task=? where

tid=? and eid=? and vid=?");

insert.setString(1,name);

insert.setString(2,vmail);

insert.setString(3,vpho);

insert.setString(4,vloc);

insert.setString(5,task);

insert.setInt(6, fid);

Department of Computer Science and Engineering, Mangaluru 22

 Cleanliness management system

insert.setInt(7, fid1);

insert.setInt(8, fid2);

insert.executeUpdate();

JOptionPane.showMessageDialog(this,"Record Updated");

table_update();

jButton2.setEnabled(true);

jTextField1.setText("");

jTextField2.setText("");

jTextField3.setText("");

jTextField4.setText("");

jTextField1.requestFocus();

catch(Exception e)

JOptionPane.showMessageDialog(this,"Please select the details to be edited"); }

Department of Computer Science and Engineering, Mangaluru 23

 Cleanliness management system

5.2.5 DELETE

private void jButton4ActionPerformed(java.awt.event.ActionEvent evt) {

DefaultTableModel Df=(DefaultTableModel)jTable1.getModel();
int selin=jTable1.getSelectedRow();
try {
int fid=Integer.parseInt(Df.getValueAt(selin, 0).toString());
int fid1=Integer.parseInt(Df.getValueAt(selin, 1).toString());
int fid2=Integer.parseInt(Df.getValueAt(selin, 2).toString());
int dialogResult=JOptionPane.showConfirmDialog(null,"Do you want to delete the
record?","Warning",JOptionPane.YES_NO_OPTION);
if(dialogResult==JOptionPane.YES_OPTION)
{

DriverManager.registerDriver(new OracleDriver());

con1=DriverManager.getConnection("jdbc:oracle:thin:@//localhost:1521/XE", "snehal",
"snehal");
insert = con1.prepareStatement("delete from teamform where tid=? and eid=? and vid=?");
insert.setInt(1, fid);
insert.setInt(2, fid1);
insert.setInt(3, fid2);
insert.executeUpdate();
JOptionPane.showMessageDialog(this,"Record Deleted");
table_update();
jButton2.setEnabled(true);
jTextField1.setText("");
jTextField2.setText("");
jTextField3.setText("");
jTextField4.setText("");

jTextField1.requestFocus();

}
Department of Computer Science and Engineering, Mangaluru 24
 Cleanliness management system

} catch (Exception ex) {

JOptionPane.showMessageDialog(this,"Please select the details to be deleted"); }
table_update();
}

Department of Computer Science and Engineering, Mangaluru 25

 Cleanliness management system

5.2.6 TRIGGERS

create table volunteers(

vid varchar(5) primary key,
vname varchar(20) not null,
vemail varchar(30) not null,
vphone number(10) not null,
vloc varchar(20) not null);

create sequence vidauto;

create or replace trigger vidtri

before insert on volunteers
for each row
begin
select vidauto.nextval into :new.vid from dual;
end;
/

create table employee(

eid varchar(5) primary key,
ename varchar(20) not null,
ephone number(10) not null,
eemail varchar(30) not null,
eloc varchar(20) not null);

create sequence eidauto;

create or replace trigger eidtri

before insert on employee
for each row
begin
select eidauto.nextval into :new.eid from dual;
end;
/

Department of Computer Science and Engineering, Mangaluru 26

 Cleanliness management system

CHAPTER 6

RESULT

6.1 EXPLORE PAGE

FIGURE 6.1.1 Explore page

FIGURE 6.1 This is the first page that pops up. The user can click on the explore button to see the further
pages.

Department of Computer Science and Engineering, Mangaluru 27

 Cleanliness management system

6.2 HOME PAGE

FIGURE 6.2 home page

FIG 6.2 will give the user an option to choose what kind of user they are.

Department of Computer Science and Engineering, Mangaluru 28

 Cleanliness management system

6.2.1 ABOUT US

Fig 6.2.1 About us page

6.2.2 CONTACT US

Fig 6.2.2. Contact us

Department of Computer Science and Engineering, Mangaluru 29
 Cleanliness management system

6.3 PUBLIC BUTTON PAGE

Fig 6.3 Public Page

FIG 6.3 When you press the public button you get a range of options. The user may click any on
these depending on what he/she is interested in.

6.4. PUBLIC COMPLAINTS PAGE

FIGURE 6.4 Complaint page

Department of Computer Science and Engineering, Mangaluru 30

 Cleanliness management system
6.4.1 PUBLIC COMPLAINT SUCCESSFULLY

FIGURE 6.4.1 Complaint page

6.4.2 ERROR WHILE ENTERING THE DETAILS

FIGURE 6.4.2 Error message displayed

Department of Computer Science and Engineering, Mangaluru 31

 Cleanliness management system

6.5 PUBLIC CHECK PAGE

FIGURE 6.5 Page to check your zone

6.5.1 ROADS OPTION IN THE CHECK YOUR ZONE PAGE

FIGURE 6.5.1 Zone and last cleaned details of Roads

FIG 6.5.1 As we have seen when we click on the roads button, we can view the details of the zone and when

was it last cleaned. Similarly we can view the same details if we click the other buttons on the check page
i.e. sidewalks, bustands, drainage, waterbodies

Department of Computer Science and Engineering, Mangaluru 32

 Cleanliness management system

6.6 APPLY FOR VOLUNTEERING PAGE

FIGURE 6.6 Application for Volunteers

6.6.1 RECORD SUCCESSFULLY ADDED

FIGURE 6.6.1 Application for Volunteers

Department of Computer Science and Engineering, Mangaluru 33

 Cleanliness management system

6.6.2 RECORD DETAILS ERROR

FIGURE 6.6.2 Error

6.7 ADMIN SIDE OF THE SITE

FIGURE 6.7 Admin login

FIGURE 6.7 In order to access the admin side of the page, he/she must enter the password

Department of Computer Science and Engineering, Mangaluru 34

 Cleanliness management system

6.7.1 ERROR WHILE ENTERING THE PASSWORD

FIGURE 6.7.1 Invalid password Entered

6.7.2 PASSWORD SUCCESSFULLY ENTERED

FIGURE 6.7.2 Password Matched

Department of Computer Science and Engineering, Mangaluru 35

 Cleanliness management system

6.8 ADMIN HOME PAGE

FIGURE 6.8 Home page of the admin

6.9 TO VIEW THE ZONE ID

FIGURE 6.9 View the zone id of the zones that they offer to clean

Department of Computer Science and Engineering, Mangaluru 36

 Cleanliness management system

6.10 TO VIEW THE PROCESSED COMPLAINTS

FIGURE 6.10 Check the processed complaints

6.11 REFER TEAM INFO

FIGURE 6.11 Shows the types of people involved.

Department of Computer Science and Engineering, Mangaluru 37

 Cleanliness management system

6.11.1 EDIT THE RECORDS

FIGURE 6.11.1 Add, Edit or Delete the details.

FIG 6.11.1 This is a common page if we click on any of the buttons in the view team info. In this
page we can add records of an employee, volunteer or team info. We can add new details, edit the
details if there is any mistake and then even delete the record if the record is no longer relevant.

Department of Computer Science and Engineering, Mangaluru 38

 Cleanliness management system

6.12 VIEW CLEANED ZONES

FIGURE 6.12 View status of the zones that are cleaned

6.13 SHOWS LAST CLEANED AND ZONE NAME

FIGURE 6.13 View status of the roads that are cleaned

Department of Computer Science and Engineering, Mangaluru 39

 Cleanliness management system

FIG 6.13 Shows The status of the place cleaned. When we are in the view status page we can choose from five options that ]

are roads,sidewalk,drainage,bus stops and water bodies. When we click on any of them we can access the sone names and

it waill be stated when it was last cleaned.

Department of Computer Science and Engineering, Mangaluru 40

 Cleanliness management system

CHAPTER 7

CONCLUSION
It has been a matter of immense pleasure, honour, and challenge to have this opportunity to take up this

project and complete it successfully. In conclusion, the cleanliness management system is a valuable tool for

the showroom owner to effectively manage their inventory and customer information. The use of a GUI

allows for easy navigation and data entry, making it simple for the admin to access and update the database.

Overall, this project is a great solution for streamlining the operations of a cleaning company and improving

the overall efficiency of the business. One of the key advantages of this system is the ability to easily track

inventory and sales. The admin can quickly access information on the zones available, as well as their

respective tasks.

On the other hand the public can also interact with the company by applying for volunteering to clean

places. People can also lodge complaints of the pending cleanliness tasks in the respective zones. This

makes the cleaning activity easier. The people can also view the last cleaned information of the zones. This

project focuses on keeping our city clean and tidy and thereby supports The Clean India campaign.

Department of Computer Science and Engineering, Mangaluru 41

 Cleanliness management system

REFERENCES

[1] “SQL”, “Fundamentals of Database Systems”, Elmasri Navathe, 3rd Edition,

Pearson Edition, 2000.

[2] “MYSQL”, https://en.wikipedia.org/wiki/MySQL

[3] “JAVA”, https://www.w3schools.com/java

[4] “NETBEANS”, https://en.wikipedia.org/wiki/Neteans

Department of Computer Science and Engineering, Mangaluru 42

 Cleanliness management system

Department of Computer Science and Engineering, Mangaluru 43