Chapter-1

Introduction

1.1Overview and issues involved

Change India will be launched because a need for an online system is being felt that
could be beneficial for both citizen as well as visitors in the India. With this site staff
members can register and host various services. Citizens can get various facilities with
those services and also may present their views regarding various topics related to the
India. This site is an attempt to remove the existing flaws in the manual system of
getting the information of the India.

Change India fulfills the requirements of the India. Users do not have to go to any
manual directory to get the correct information or any happening in India. User can
normally access to the various information through online with getting registration
done. Thus the purpose of the site is to provide a system that saves the efforts and time
of citizens as well as visitors.

Many issues for Indian Citizen involving under Government protocols are as follows:-

 Strong online system is not available regarding Garbage that would facilitate the user
in an effective and efficient manner with its services and information.
 Corporate between the offline information not properly available over the online
information so that its access could be done with much more ease and provide garbage
information in stronger pattern.
 Not properly Specify a privilege for citizen to present their views over the topics
related to the development of the India.
 Not provide flexibility of each and every user to register to the site irrespective of his
citizenship of the India.

1
 Problem definition

To implement Change India in such a way that it enhances the

performance of data structure in the form of efficient retrieval of desired information.
The features and concepts applied are data warehouse, and data mining. Now in India
different states have different culture followed but face same types of problems
regarding issues created by government. But recent online website has not facility of
providing the purchasing of Garbage material by using home delivery concept due to
break down problem of dispatched material. Also they are not providing the same
material filtration according to different contractor.

In our website we understand the drawbacks of recent online protocols are as follows:-
 No online Provision of Garbage materials.
 They are not taking the risk of dispatching of Garbage materials during the home
delivery, because of cracking and breaking.
 No tracking is possible about Garbage Dispatching.
 If anybody wants to Complaint then no provision of tracking the false person.
 Strong online system is not available regarding Garbage that would facilitate the user
in an effective and efficient manner with its services and information.
 Corporate between the offline information not properly available over the online
information so that its access could be done with much more ease and provide garbage
information in stronger pattern.
 Not properly Specify a privilege for citizen to present their views over the topics
related to the development of the India.
 Not provide flexibility of each and every user to register to the site irrespective of his
citizenship of the India.
There are certain problems prevailing presently while conducting Change India
which are as follows:
 No Earning by your Garbage: It is difficult for person to earn from garbage and
handover your garbage to your city “Nagar Nigam”
 Take advantages of another’s Garbage: Anyone can not utilize the old material if
one want to sell. One can design Natural/Organic fertilizer by wet garbage
 Selling is tuff Job: We have to search Garbage contractor, this is wasting of time and
money(petrol) and cannot get the good price for our material/garbage
 No Complaint Arises: No one complaint about wastage kept near your location or
any location

2
 No single platform : No single platform for all types of Government billing sites
related to your house or the particular person

1.1 Proposed solution

We will be using various technologies in coherence to execute and deploy the tool
over internet. We shall employ the following strategy. The basic outline of web-page
will include register option for any user and retrieve information. The site will be
helpful for different people with different solution.
For Citizen:
 Getting the information of the Indian Government protocols in efficient manner in
short time.
 Interacting with the various issues or happening in the Indian protocols with other
users in effective way.
For Visitors:
 No need for them to depend on any offline sources for information.
 Easy access and availability of the complete information in crisp, short pattern.

Fig. 1.1 Change India Diagram

A website, “Change India”, is to be designed to provide platform for interaction
among the citizens via online facility. Unlike other online city system, this website
will not require any detailed information of the user; he/she may access the site from
the point of view of getting correct, crisp information for particular usage. This will
help India as:

3
 There might be possibility that the information is not available at the right time so it
will eliminate this problem.
 Saving the time of getting the information from the place manually and then searching
through it.
 Eliminating the issue of getting spurious information manually and then facing some
irrelevant consequences.
 Also this website will increase efficiency and will save much of the time.
 It will also allow neat handling of records/information of the city rather than error
prone records.

Many facilities in our website for Indian Citizen involving under Government
protocols are as follows:-
 Create strong online system that would facilitate the user in an effective and efficient
manner with its services and information
 Corporate between the offline information available over the online information so
that its access could be done with much more ease and provide garbage information in
stronger pattern.
 Specify a privilege for citizen to present their views over the topics related to the
development of the India.
 Provide flexibility of each and every user to register to the site irrespective of his
citizenship of the India.

System Interfaces:
The system will interface with the following two systems:
1. A Government Portal (Admin): The system will access all Governmental
functionalities with secure connection.
2. User (Citizen of India): The system will interact with the Governmental
functionalities using MYSQL SERVER connection.

User Interfaces:
The system will provide the ability for citizen and Government to access the Change
India via the Internet. There will be two different user interfaces that will accompany
this website: one for the Citizen of India and the administrators.
 Citizen will be allowed to search database with having to login, however, they must
login in order to perform any other query to Admin. These other transaction will

4
 include Selling and purchasing Garbage, or viewing and changing their online
account.
 Admin must be required to login at all times in order to perform any transaction. Once
logged in the Admin member will be able to View Citizen Details and Add new
Contractor Detail.

1.1 Report Organization

This report consists of seven chapters and appendix. The brief description of
each chapter is as follows: -
Chapter 1:- Introduction
This chapter gives an introduction to the project. Explain the importance of project,
Problem definition, problem solution, Report Organization.
Chapter 2- Literature Survey
This chapter deals with the literature, tools, and technologies that are being explored
and adopted throughout the project development, technology of project.
Chapter 3:- Analysis
This chapter deals with model used for our website, advantages and disadvantages,
reason for use, Need and Scope of project including software Hardware requirements,
feasibility study, Architectural Specification, Use case diagram with description.
Chapter 4:- Design
This chapter gives information about Database Design, ER Diagram, Class diagram,
Activity diagrams, and Sequence diagrams, Packaging.
Chapter 5:- Implementation and Testing
This chapter gives information about the implementation of the system, Language
used Characteristics, Class Diagram Description, Testing.
Chapter 6:- Conclusion and Discussion
This chapter gives information about short description of our proposed system,
limitations and future scope of the system.
Appendix
Bibliography

5
 Chapter-2
Literature Survey

2.1 Methodology

1. Front End:- (Languages)

Java Server Pages (JSP) is a server-side programming technology that enables the
creation of dynamic, platform-independent method for building Web-based
applications. JSP have access to the entire family of Java APIs, including the JDBC
API to access enterprise databases.
A Java Server Pages component is a type of Java servlet that is designed to
fulfill the role of a user interface for a Java web application. Web developers write
JSPs as text files that combine HTML or XHTML code, XML elements, and
embedded JSP actions and commands.JSP technology is used to create web
application just like Servlet technology. It can be thought of as an extension to servlet
because it provides more functionality than servlet such as expression language, jstl
etc.
1. HTTP:- the Hypertext Transfer Protocol (HTTP) is an application-level protocol
for distributed, collaborative, hypermedia information systems. HTTP is a generic and
stateless protocol which can be used for other purposes as well using extension of its
request methods, error codes and headers.

2. HTML:- HTML stands for Hyper Text Mark-up Language . A web browser can
read HTML files and compose them into visible or audible web pages. The browser
does not display the HTML tags, but uses them to interpret the content of the page.
HTML describes the structure of a website semantically along with cues for
presentation, making it a markup language rather than a programming language.
HTML elements form the building blocks of all websites. HTML allows images and
objects to be embedded and can be used to create interactive forms. It provides a
means to create structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items. It can embed scripts written
in languages such as JavaScript which affect the behavior of HTML web pages.

6
2. Backend:- (Database)
MySQL Server:-
It is a software product whose primary function is to store and retrieve data as
requested by other software applications, be it those on the same computer or those
running on another computer across a network (including the internet).
There are at least a dozen different additions of Microsoft Sql Server aimed at
different audiences and for different workloads.
Sql Server 2005 added some extensions to the T-SQL language to allow embedding
XQuery queries in T-SQL. In addition it also defines a new extension to XQuery
called XML DML that allows query based modifications to XML Data.
SQL Server 2005 also allows a database server to be exposed over web services using
tabular data string (TDS) packets encapsulated within SOAP (protocol) request.

2.2 Technologies and Tools used

1. Java Script
JavaScript is a lightweight, interpreted programming language with object-
oriented capabilities that allows you to build interactivity into otherwise static HTML
pages. The general-purpose core of the language has been embedded in Netscape,
Internet Explorer, and other web browsers.
JavaScript is: 1. JavaScript is a lightweight, interpreted programming language
2. Designed for creating network-centric applications.
3. Complementary to and integrated with Java.
4. Complementary to and integrated with HTML.
5. Open and cross-platform.

2. Apache Tomcat and Glassfish Server

Apache Tomcat is an open source web server and Servlet container developed by
the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and
the Java Server (JSP) specifications from Oracle, and provides a
"pure Java" HTTP web server environment for Java code to run in. In the simplest
configuration Tomcat runs in a single operating system process. The process runs a
Java virtual machine (JVM).

7
Glassfish is an open-source application server project started by Sun
Microsystems for the Java EE platform and now sponsored by Oracle Corporation.
The supported version is called Oracle Glassfish Server. Glassfish is the reference
implementation of Java EE and as such supports Enterprise JavaBeans, JPA, Java
Server Faces, JMS, RMI, Java Server Pages, Servlet , etc. This allows developers to
create enterprise applications that are portable and scalable, and that integrate with
legacy technologies.
4. Type 4: Pure Java Driver
In a Type 4 driver, a pure Java-based driver that communicates directly with vendor's
database through socket connection. This is the highest performance driver available
for the database and is usually provided by the vendor itself.
This kind of driver is extremely flexible; you don't need to install special software on
the client or server. Further, these drivers can be downloaded dynamically.

Fig 2.1 JSP Working

MySQL's Connector/J driver is a Type 4 driver. Because of the proprietary nature of
their network protocols, database vendors usually supply type 4 drivers

8
 Chapter-3
Analysis

3.1 Process Model Adopted

3.1.1 Description

For any website we have to follow the prototype model. For our website we followed
prototype model which is suitable model for website development and quality is we
can handover our website to our client in faster manner with optimal working of our
website.

The Prototyping Model is a systems development method (SDM) in which

a prototype (an early approximation of a final system or product) is built, tested, and
then reworked as necessary until an acceptable prototype is finally achieved from
which the complete system or product can now be developed. This model works best
in scenarios where not all of the project requirements are known in detail ahead of
time. It is an iterative, trial-and-error process that takes place between the developers
and the users.

Fig. 3.1 Prototype Model

There are several steps in the Prototyping Model:

9
1. The new system requirements are defined in as much detail as possible. This usually
involves interviewing a number of users representing all the departments or aspects of
the existing system.
2. A preliminary design is created for the new system.
3. A first prototype of the new system is constructed from the preliminary design. This is
usually a scaled-down system, and represents an approximation of the characteristics
of the final product.
4. The users thoroughly evaluate the first prototype, noting its strengths and weaknesses,
what needs to be added, and what should to be removed. The developer collects and
analyzes the remarks from the users.
5. The first prototype is modified, based on the comments supplied by the users, and a
second prototype of the new system is constructed.
6. The second prototype is evaluated in the same manner as was the first prototype.

3.1.2 Advantages and Disadvantages

The Benefits of Prototyping

 Reduced time and costs: Prototyping improves the quality of the specifications and
requirements provided to customers. With prototyping, customers can anticipate
higher costs, needed changes and potential project hurdles, and most importantly,
potential end result disasters. Strong prototyping can ensure product quality and
savings for years to come.
 Improved and increased user involvement: Most customer want to feel like they are
involved with the intricate details of their project. Prototyping requires user
involvement and enables them to see and interact with a working model of their
project. With prototypes, customers can give their immediate feedback, request project
changes and alter model specifications. Prototyping most importantly helps eliminate
misunderstandings and miscommunications during the development process.
 Reduced time and costs: Nothing makes customers happier than projects that come
in under budget. Prototyping improves the quality of requirements and specifications
provided to customers. Needed changes detected later in development cost
exponentially more to implement. With prototyping, you can determine early what the
end user wants with faster and less expensive software.

10
 The Disadvantages of Prototyping
Alas, no project development model is perfect expect for, perhaps, oxygen plus
hydrogen equals water. The disadvantages of prototyping must be weighed before
deciding to implement them into project development.
 Insufficient analysis: A focus on a limited prototype can distract developers from
properly analyzing the complete project. The potential end result: A potential
overlooking of better solutions, incomplete specifications or the conversion of limited
prototypes into poorly engineered and developed final projects that are hard to
maintain.
 User confusion: The worst-case scenario of any prototype is customers mistaking it
for the finished project. Customers seeing a rough prototype may not understand it
merely needs to be finished or polished. Also, customers can wrongly perceive the
prototype to accurately model the performance of the final system. Customers may
also grow fond of prototype features that are not part of the final system.
 Developer misunderstanding of user objectives: For every project to be successful,
developers and customers must be on the same page and share the same project
objectives. If customers require all proposed features of a prototype be included in the
final product, this can lead to team and mission conflicts.
 Excessive Development Time: Remember, prototypes are by nature designed to be
developed quickly. If a developer spends too much time developing a complex
prototype, the project can run into roadblocks (especially if there are disagreements
over prototype details) and run over both time and cost budgets.

3.1.3 Reasons for Use

Prototype model should be used when the desired system needs to have a lot of
interaction with the end users. Prototyping ensures that the end users constantly work
with the system and provide a feedback which is incorporated in the prototype to
result in a useable system.

We can use prototype model due to following purposes:-

 Prototype model should be used when the desired system needs to have a lot of
interaction with the end users.

11
 Typically, online systems, web interfaces have a very high amount of interaction with
end users, are best suited for Prototype model. It might take a while for a system to be
built that allows ease of use and needs minimal training for the end user.
 Prototyping ensures that the end users constantly work with the system and provide a
feedback which is incorporated in the prototype to result in a useable system. They are
excellent for designing good human computer interface systems.
3.2 Requirement Analysis

Requirements gathering in systems engineering and software engineering

encompasses those task that go into determining the needs or conditions to meet for a
new or altered product taking account of the possibly conflicting requirements of the
various stack holders, such as beneficiaries or users.

Requirements analysis is critical to the success of a development project.

Requirements must be documented, actionable, measurable, testable related to
identified business needs or opportunities and define to a level of detail sufficient for
system design.
The functional requirement defines a function of a software system or its components.
A function is described as a set of inputs, the behavior, and outputs. Functional
requirements may be calculations, technical details, data manipulation and processing
and specific functionality that define what a system is supposed to accomplish.
Behavioral requirements describing all the cases where the system uses the functional
requirements are captured in use cases.
Functional requirement for User:
1. Visit Garbage.
2. Garbage Selling.
3. Register over the site.

Functional requirement for Staff:

1. Login
2. Update information.
3. Add Garbage
4. Register service providers.

12
3.1.2 Software Requirements
Operating System : Windows XP with SP2.

Language (Front End) : JAVA (1.8)

Server : Apache Tomcat 8.0

Databases : MySQL Server

Web Technology : JSP, HTML,JAVA script

Front-end selection:

1. It must have a graphical user interface that assists customer that is not from IT
background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the culture.
6. Must provide excellent reporting features with good printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Event driven programming facility.
10. Front end must support some popular back end like JSP.
According to the above stated features we selected JSP as the front-end for developing
our website.

Back-end Selection:

1. Multiple user support.

2. Efficient data handling.
3. Provide inherent features for security.
4. Efficient data retrieval and maintenance.
5. Stored procedures.
6. Popularity.
7. Operating System compatible.
8. Easy to install.
9. Various drivers must be available

13
 10. Easy to implant with the Front-end.
According to the above stated features we selected MYSQL as the back-end for
developing our website.

Implementation Language

We have used Java as our programming language due to following services provided
by it:

 It provides inbuilt classes such as Java.lang.* and Java.math.* and many more which is
helpful in computing different algorithm and different mathematical function.
 It provides swing GUI components in programs for interactive graphical user interface.
 It is platform independent.
 It is Robust, Secure, Portable, easy to understand and implement

Web-Server
Oracle GlassFish Server is the commercial offering based on GlassFish Server
Open Source Edition. GlassFish Server Open Source Edition is the open source
application server delivered by the GlassFish community, which was originally
launched by Sun in 2005. Since its inception, Oracle GlassFish Server has notched 24
million downloads and 300,000 product registrations in a recent one-year span. The
current version, Oracle GlassFish Server 3, features an architecture that is modular by
default; allows for rapid, iterative Web development; and supports dynamic languages.
It is an excellent platform for deploying rich internet applications backed by Java.
Oracle GlassFish Server 2 is a commercially supported Java Platform, Enterprise
Edition 5 (Java EE 5)–compatible offering.
The commercial version adds an enterprise-quality application server to the
options available to the open source community and builds on the foundation laid by
earlier versions of Oracle GlassFish Server.
Tomcat was started at Apache by a group that included Sun Microsystems
(now part of Oracle Corporation); the initial code drop came from Sun. It became the
reference implementation (RI) for early versions of the Java servlets and JSP
specifications. The RI for the latest specifications is Oracle GlassFish Server. Tomcat
was critical to the early adoption of server-side Java, was available under an open

14
 source license, and contributed to the popularity of open source software within
enterprise organizations.

Communications Interfaces

There are many types of interfaces as such supported by the Change India website
system namely; User Interface, Software Interface and Hardware Interface.
The protocol used shall be HTTP.
The Port number used will be 80.
3.2.2 Hardware Requirements
Processor : Intel 2.0 GHz
Hard Disk : 80 GB
Ram : 1 GB RAM.
 Any processor that supports wins x versions.
 The output devices as display unit, input devices as keyboard, mouse.
 Java is platform independent due to this we can use any hardware with any supporting
Operating system.

3.3 Feasibility Study

3.3.1 Technical Feasibility

We need resources that are easily available:

 1 GB of RAM.
 Android Platform
The technical requirements (resource availability and technology) are available to us.
Thus our project is technically feasible.
3.3.2 Economic Feasibility
The resources that we use for our project are readily available. The help is
freely available. So, our project is economically feasible. The cost of our project is the
total cost of all the peripherals like mobile. Thus, from the economy point of view our
project does not require a lot of monetary inputs.
3.3.3 Operational Feasibility
A development of any infringement, violation or liability that could result from
development of the systems makes it operationally feasible. There is no law or rule,
which will be violated by the development of this software. So, our project is
operationally feasible.

15
3.3 Architectural Specification

The process of design all basic needs of website or project in which all connections
and dependency shows in specified format than it is called architectural diagram.

Fig. 3.2 Architecture Model

16
3.3 Use Case Model

Registratio
n

Authentication

Add Garbage

View
Garbage

Purchase
Garbage

User Complaint
Admin

Generate Bill

Figure 3.3 Use case Diagram

17
 3.3 Use Case Description

Use case diagrams are used to gather the requirements of a system including internal
and external influences. These requirements are mostly design requirements.
The purposes of use case diagrams can be as follows:
 Used to gather the requirements of a system.
 Used to get an outside view of a system.
 Identify external and internal factors influencing the system.
 Show the interacting among the requirements are actors.
In above figure Admin and User are the actors and there are following 7 use cases:
1. Registration.
2. Authentication
3. Add Garbage
4. View Garbage
5. Purchase Garbage
6. Complaint
7. Generate Bill
In above use cases User only interact with the middle of three use cases i.e. View
Garbage, Complaint Garbage and Purchase Garbage. On the other hand Admin can
interact with all the cases.

18
 Chapter-4
Design

4.1 Sequence diagrams

Sequence Diagram

User Login User Account Add Sell Garbage View Purchase

Garbage Garbage Garbage

Login Verified Attached

Not Item
Verified Add Garbage
Store Garbage
Not Verified About item Purchase
Required
Garbage
Store Garbage

Figure 4.1 Sequence Diagram.

19
 Description of Sequence Diagram

A sequence diagram is an interaction diagram that shows how processes operate with
one another and in what order. A sequence diagram shows object interactions arranged
in time sequence.
The following things are identified clearly before drawing the sequence diagram:
 Objects taking part in the interaction.
 Message flows among the objects.
 The sequence in which the messages are flowing.
 Object organization.
In above diagram there are six Objects taking part in the interaction every time. These
are User, User Account, Add Garbage, View Garbage, Database and Purchasing
Garbage. Firstly User will Login and after verified login he will go at user account.
User interacts with database by putting the add Garbage and demand Garbage to the
database.

20
 4.1 Class Diagram

Manage View
Admin
Garbage Guest
Name: String
Id: integer +ViewGarbage()
Password: String
#Name: String +GetRegistered()
#category: String
+ViewGarbage()
#Quantity: integer
+Authenticate()
+DeleteUser()
Buy Contractor

Citizen -id: integer

#Name: String
Id: int #NoofProducts:intger
#Name: String #Product1: String
#Address: String Has #Rate: int
#Phno: integer #Garbage: String
#Price:Float
BuyGarbage() #Total:Float
ViewGarbage ()
Payment
MakePayment()
SellGarbage
#Customerid:()Int
ChangePassword()
+Name: String
-CardType: String
-CardNo: Int

Figure 4.2 Class Diagram.

21
 4.1 Packaging

A web application often consists of nothing more than one page created with the
JavaServer Pages (JSP) technology. Sometimes you will combine three or more such
technologies. No matter how many you end up using, it's good to know what is
available to you and how you can use each one in a web application.
Java Servlet API
The Java Servlet API lets you define HTTP-specific classes. A servlet class extends
the capabilities of servers that host applications that are accessed by way of a request-
response programming model. Although servlets can respond to any type of request,
they are commonly used to extend the applications hosted by web servers. A servlet
runs on the server side -- without an application GUI or HTML user interface (UI) of
its own. Java Servlet extensions make many web applications possible.
Figure 1 shows clients talking to Java Servlet extensions. Clients may range in
complexity from simple HTML forms to sophisticated Java technology-based applets.
The javax.servlet and javax.servlet.http packages provide the classes and interfaces to
define servlets. HTML servlet classes extend
the javax.servlet.http.HttpServlet abstract class, which provides a framework for
handling HTTP protocol.
JavaServer Pages Technology
JavaServer Pages (JSP) technology provides a simplified, fast way to create dynamic
web content. JSP technology enables rapid development of web-based applications
that are server- and platform-independent. JSP technology lets you add snippets of
servlet code directly into a text-based document. Typically, a JSP page is a text-based
document that contains two types of text:
 Static data, which can be expressed in any text-based format, such as HTML, Wireless
Markup Language (WML), or XML
 JSP technology elements, which determine how the page constructs dynamic content
The packages involved in creating JSP pages
are javax.el, javax.servlet.jsp, javax.servlet.jsp.el, andjavax.servlet.jsp.tagext, though
you will rarely have to import these directly. A JSP page can be as simple as a bit of
HTML with one snippet of JSP code and the .jsp extension of the page name.
For instance, you can create a web site of JSP technology pages that use one snippet of
code to include the header.html file, which contains the site navigation. This way,

22
when you change a link to a button in the navigation, you make the change in only one
file, and that file loads into all the pages on the site that have this code snippet:
<%@ include file="header.html" %>
That line of code works very much like a server-side include, if you are familiar with
those. Because this web page is now a JSP page, you could also go on to add more
Java technology code to create dynamic web content, such as polls, forms, ways to
enter or retrieve data from a database, and so forth.
Take a look at two helpful documents about creating JSP pages:
JavaServer Pages Standard Tag Library
The JavaServer Pages Standard Tag Library (JSTL) encapsulates core functionality
common to many JSP technology-based applications. Instead of mixing tags from
numerous vendors in your applications, you employ a single standard set of tags. This
standardization allows you to deploy your applications on any JSP container that
supports JSTL and makes it more likely that the implementation of the tags is
optimized.
JSTL has iterator and conditional tags for handling flow control, tags for manipulating
XML documents, internationalization tags, tags for accessing databases using SQL,
and tags for commonly used functions.
The packages you can access for using JSTL
are javax.servlet.jsp.jstl.core , javax.servlet.jsp.jstl.fmt ,javax.servlet.jsp.jstl.sql ,
and javax.servlet.jsp.jstl.tlv .
JavaServer Faces Technology
JavaServer Faces technology is a UI framework for building web applications. The
main components of JavaServer Faces technology involve a GUI component
framework, a flexible model for rendering components in various markup languages
and technologies, and a standard RenderKit for generating HTML markup.
This functionality is available through standard Java APIs and XML-based
configuration files. In addition, Sun Java Studio Creator IDE leverages JavaServer
Faces technology in its drag-and-drop GUI tools, allowing you to use the technology
without having to write or understand the underlying code. See also " Getting Started
With Sun Java Studio Creator."
Java Message Service API
Messaging is a method of communication between software components or
applications. A messaging system is a peer-to-peer facility. In other words, a

23
messaging client can send messages to and receive messages from any other client.
Each client connects to a messaging agent that provides facilities for creating, sending,
receiving, and reading messages. By combining Java technology with enterprise
messaging, the Java Message Service (JMS) API provides a powerful tool for solving
enterprise computing problems.
Enterprise messaging provides a reliable, flexible service for the exchange of business
data throughout an enterprise. The JMS API adds to this a common API and provider
framework that enables the development of portable message-based applications in the
Java programming language. An example of how JMS might be used is an application
that keeps track of inventory for an auto manufacturer. The inventory component can
send a message to the factory component when the inventory level for a product goes
below a certain level, so the factory can make more cars. The factory component can
send a message to the parts components so that the factory can assemble the parts it
needs. The parts components in turn can send messages to their own inventory and
order components to update their inventories and to order new parts from suppliers
and so forth.

24
 4.4 E-R Diagram

Password
Name ID Password
Cont_no.

Verifie
d Admin
Address Citizen By

Bank_Acc
E-mail id
Add
Garbag
e Item
Garbage_name
Garbage id
Choose
Category
Item

id Pattern
Garbage_name Price

Price
Purchase
Store
Pattern
Category
Quality

Fig 4.4 E-R Diagram

25
4.1 Database Design

The following diagram describes the attributes and the types of data that shall be used
in the operations.

Admin

Challan

Complaint

26
Contractor

Garbage

27
Garbage Sell

User Registration

28
 Chapter – 5
Implementation and Testing

5.1 Language Used Characteristics

JSP technology is used to create dynamic web applications. JSP pages are easier to
maintain then a Servlet. JSP pages are opposite of Servlets as a servlet adds HTML
code inside Java code, while JSP adds Java code inside HTML using JSP tags.
Everything a Servlet can do, a JSP page can also do it.
JSP enables us to write HTML pages containing tags, inside which we can include
powerful Java programs. Using JSP, one can easily separate Presentation and
Business logic as a web designer can design and update JSP pages creating the
presentation layer and java developer can write server side complex computational
code without concerning the web design. And both the layers can easily interact over
HTTP requests.
Why JSP is preferred over servlets?
 JSP provides an easier way to code dynamic web pages.
 JSP does not require additional files like, java class files, web.xml etc
 Any change in the JSP code is handled by Web Container(Application server like
tomcat), and doesn't require re-compilation.
 JSP pages can be directly accessed, and web.xml mapping is not required like in
servlets.
Advantage of JSP
 Easy to maintain and code.
 High Performance and Scalability.
 JSP is built on Java technology, so it is platform independent.

5.2 Class diagram

Class Diagram Explanation:-The class diagram is consisting six classes such as

Admin, Garbage, guest, Citizen, cart, and payment. Each class has some attribute and

methods like admin class has attributes id and name. the methods are

viewgarbage(), addgarbage () and confirmdelivery().

29
 The view garbage method will be used by the admin to maintain the stock, in

order to check availability and demand of any specific garbage. With the help of the

add garbage method the admin will add the garbage. The delete garbage method will

be used to delete the garbage, the confirm delivery method will be used to confirm the

delivery on of the garbage to customer.

The product class has some attributes such as id, name , category from where it

belongs to. guest class has some methods like viewgarbage () and getregistered() by

which the guest can view the garbage available and can register as to be the

customer. customer class has attributes such as id, name, address, and phone-No

etc, and methods such as buygarbage (), viewgarbage (), makepayments(),. the

buygarbage() method will be used to buy the specific garbage and viewgarbage

method will be used to view garbage products available in the stock and make

payment method will be used to ensure the payment for the garbage.

5.3 Testing

Testing is a process of executing a program with the intent 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 phrase. Testing represents an interesting anomaly for
the software. Thus a series of tests 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.
5.3.1Testing Objectives

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

2. A good test case is one that has a probability of finding an as yet undiscovered error

30
3. 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

5.3.1 Testing Methods and Strategies

The primary objective of 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.
1. 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.
2. Black-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 for 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.
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.

Test Plan:
A test plan can be defined as a document describing the scope, approach,
resources, and schedule of intended testing activities. It identifies test items, the
features to be tested, the testing tasks, who will do each task, and any risks requiring

31
 contingency planning. In software testing, a test plan gives detailed testing
information regarding an upcoming testing effort, including
 Scope of testing
 Schedule
 Test Deliverables
 Release Criteria
 Risks and Contingencies
A testing plan is a methodological and systematic approach to testing a system such as
a machine or software. It can be effective in finding errors and flaws in a system. In
order to find relevant results, the plan typically contains experiments with a range of
operations and values, including an understanding of what the eventual workflow will
be. The test plan is a document which includes, introduction, assumptions, list of test
cases, list of features to be tested, approach, deliverables, resources, risks and
scheduling.
Testing is a process of executing a program with the intent of finding errors. A good
test case is one that has a 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.

32
5.3.3 Test Case

A test case is a detailed procedure that fully tests a feature or an aspect of a

feature. Whereas the test plan describes what to test, a test case describes how to
perform a particular test. You need to develop a test case for each test listed in
the test plan.
S E A S
. T x c t
n e p t a
o s e u t
t c a u
t l s
c e
a d R
s e
e R s
e u
s l
u t
l
t
1 L M M P
. o a a a
g i i s
i n n s
n P P
U a a
s g g
e e e
r
n
a
m
e

33
 /
p
a
s
s
w
o
r
d

2 C C P
. h h C a
a a h s
n n a s
g g n
e e g
e
P P
a a p
s s a
s s s
w s
o f
r o f
d r o
m r
m
3 U U P
p U p a
d p d s
a d a s
t a t
e t e
e
P p

34
 r P r
o r o
f o f
i f i
l i l
e l e
e
4 G P S P
a u h a
r r o s
b c w s
a h n
g a
e s
e
P
u t
r h
c e
h
a G
s a
e r
d b
a
g
e
5 V V S P
i i h a
e e o s
w w w s

G t P
a h r
r e o

35
 b d
a G u
g a c
e r t
b s
a
g
e

Table 5.1 Test Case Design

36
 Chapter-6
Conclusion and Discussion

Proposed system is more efficient and more reliable for selling the garbage and earn
money by contractor. With reference the User Account of Citizen one can enter in the
system and Add the garbage then sell to respective contractor from their account.
This website is a new digital version by which we can work more compare
to manual working in garbage selling as well as complaint to government about the
garbage.
The limitations of this website are, it will work without permission of government
due to some part is dummy work.
The future expansion of this project will include several sub categories of Indian
government website.

37
 Bibliography and References

Bibliography

 Software Engineering A Practitioner’s Approach – Roger S Pressman. 5e.

 The Complete Reference JAVA – Patrick Naughton, Herbertschildt.

 Core Java 2 – Cay Horstmann, Gary Cornell

 How to Program Java – Deitel and Deitel

References

 http://java.sun.com/docs/

 http://planetsourcecode.com

 http://programmersheaven.com

 hhttp://www.shilpgravures.com/
 http://www.shilpmantra.com/
 ttp://www.iicd.ac.in/projects/

38
LIST OF FIGURES

S F Figu P
. i re a
N g Nam g
. u e e
r
N
e
o
N
.
o
.
1 F Chan 3
i ge
g India
. Diag
1 ram
.
1
2 F JSP 8
i Work
g ing
2
.
1
3 F Proto 9
i type
g Mod
. el
3
.
1
4 F Arch 1
i itectu 6
g re
. Mod
3 el
.
2
5 F Use 1
i case 7
g Diag
. ram
3
.

39
 3
6 F Sequ 1
i ence 9
g Diag
. ram
4
.
1
7 F Class 2
i Diag 1
g ram
.
4
.
2
8 F E-R 2
i Diag 5
g ram
.
4
.
4

LIST OF TABLES

S T T P
. a ab a
N b le g
. le N e
N a
o m N
. e o
.
Te
1 T st 3
a 1
C
b
le as
5 e
.
D
1
es
ig

40
 n

41