CHAPTER 1

PROJECT DESCRIPTION
1.1 Introduction

Individual or community water-supply systems, properly designed and constructed, present

difficulties that are almost always beyond the possibilities and resources of individuals to solve by
themselves. In the matter of rural water-supply, therefore, more community or group action is
necessary in order to search for and concentrate technical and financial resources. The central
health administration should be prepared to give assistance in these problems. It can properly
justify the employment of highly paid technical personnel, who will often be called for service by
an increasing number of rural communities. It should also be prepared to give financial help in
terms of grants or loans, as the case may be. In many developed countries, farm credit and home
improvement programmers provide a means for constructing residential water-supplies, while
national loan and assistance programmers are resorted to for the solution of community water-
supply problems. Experience in parts of the world shows that when the health administrations have
organized themselves in such a way as to be able to give technical assistance to local communities
and to promote long-range financial planning, there has been great progress in the construction of
public water-supplies for small rural towns and villages. But whatever the case, the central agency
concerned should organize a technical section entrusted with the definite responsibility of giving
direct consultation and assistance in this field. The vast majority of small rural towns and villages,
to say nothing of individuals, are unable to pay for the technical services required to make proper
preliminary investigations, and to design and construct even small, simple, water-supply systems.
As a matter of fact, even in those rare cases where a town can pay. it is not easy in most countries
to find qualified water-supply engineers interested in the small fees involved. The agency should,
therefore, provide the consulting I service which is indispensable in order to start the series of
events that will 1 lead to the actual construction of proper water-supply systems. If the central
administration or agency is ready to guide and assist local communities, it can often discourage
them from spending money on less important projects and may help them to channel available
resources into the water supply scheme. The agency should be prepared to make preliminary field
investigations to determine the best source of water, to make topographical surveys of the town or
village and its surroundings, and generally to obtain complete information upon which an accurate
design could be based. Thereafter it should undertake to make detailed engineering designs and
financing plans, including the preparation of all documents necessary for letting the construction
by contract, if such a system is possible or desirable. After that, it should provide for the
supervision of the construction work and, if required, for the execution of the work directly under
its own administration. The staff and equipment necessary to carry out such work are discussed in
other sections of this monograph. The water supply management system will help the local
government and the private institutions to manage the water supply system in a better way. It
will also help the billing and invoicing to work in a better way.

1.1 EXISTING SYSTEM

In existing system, urban water is supplied to the home with the help of some man power. The
person in charge will go to the placeand then open the valve to that particular area. Once the
time is over the person will go again to that place and close the valve. This type of operation
needs man power. This is waste of time to go to that place and come back often. Also the
people may take excess water for their personal use with the help of motor or some other
equipment. Due to this many people will not receive sufficient water for their use. Here the
supply of water to different areas is done according to the level of the water in main tank. A
worker is needed to switch ON the supply so that the main tank located in the operator area
gets filled and is ready to distribute water to different regions. Suppose there are two areas say
area „A‟ and area „B‟. if water is to be supplied to area „A‟ then depending on the number of
houses located in area „A‟ the main tank should be filled 100% with water and then for the
duration of one hour the water is supplied to that area, whereas area „B‟ has to wait till the
supply of water is done to the area „A‟. Now again it takes some time for the main tank to be
filled with water in order to supply water to houses residing in area „B‟ and remaining the
same procedure is carried out. This states that the existing system is not capable of providing
water to both the areas simultaneously.
1.1.1 DISADVANTAGES OF EXISTING SYSTEM

Time consuming & involves manual processes in billing & resource scheduling.

Water may be sucked by motor pumps which lead to scarcity on low areas.

Resources are not shared properly

People are not aware of their usage.

Governments are also unaware whether the resources are shared properly or not.

1.2 PROPOSED SYSTEM

Our proposed system involves a Smart Controller system for efficient utilization of resources
and resource management of resources such as water to overcome shortages due to limited
availability of resources and high demand. This new technology is the successor to the
existing systems in place. This system aims at better utilization of resources and aids in
analysis which would be useful for future planning.
1.2.1 ADVANTAGES
•Learn Resource information
•Reduced wastage, increased revenue.

1.3.1 Hardware Specification

 Processor : Dual core processor 2.6.0 GHz

 RAM : 1GB
 Hard disk : 160 GB
 Compact Disk : 650 MB
 Keyboard : Standard keyboard
 Monitor : 15 inch color monitor
1.3.2 Software Specification
 Front End : JSP
 Back End : SQL Server 2008
 Platform : Windows 7
 IDE : Net beans

FRONT END (JSP):

Java Server Page (JSP) is a technology for controlling the content or appearance of Web
pages through the use of servlets, small programs that are specified in the Web page and run on
the Web server to modify the Web page before it is sent to the user who requested it. Sun
Microsystems, the developer of Java, also refers to the JSP technology as the Servlet application
program interface (API). JSP is comparable to Microsoft's Active Server Page (ASP) technology.
Whereas a Java Server Page calls a Java program that is executed by the Web server, an Active
Server Page contains a script that is interpreted by a script interpreter (such as VBScript or JScript)
before the page is sent to the user. Architecturally, JSP may be viewed as a high-level abstraction
of Java servlets. JSPs are translated into servlets at runtime, therefore JSP is a Servlets; each JSP
servlet is cached and re-used until the original JSP is modified.JSP can be used independently or
as the view component of a server-side model–view–controller design, normally with JavaBeans
as the model and Java servlets (or a framework such as Apache Struts) as the controller. This is a
type of Model 2 architecture.
JSP allows Java code and certain pre-defined actions to be interleaved with static web
markup content, such as HTML, with the resulting page being compiled and executed on the server
to deliver a document. The compiled pages, as well as any dependent Java libraries, contain Java
byte code rather than machine code. Like any other Java program, they must be executed within a
Java virtual machine (JVM) that interacts with the server's host operating system to provide an
abstract, platform-neutral environment. JSPs are usually used to deliver HTML and XML
documents, but through the use of Output Stream, they can deliver other types of data as well. The
Web container creates JSP implicit objects like request, response, session, application, config,
page, page Context, out and exception. JSP Engine creates these objects during translation phase.
SYNTAX
JSP pages use several delimiters for scripting functions. The most basic is <% ... %>, which
encloses a JSP scriptlet. A scriptlet is a fragment of Java code that is run when the user requests
the page. Other common delimiters include <%= ... %> for expressions, where the scriptlet and
delimiters are replaced with the result of evaluating the expression, and directives, denoted with
<%@ ... %>.Java code is not required to be complete or self-contained within a single scriptlet
block. It can straddle markup content, provided that the page as a whole is syntactically correct.
For example, any Java if/for/while blocks opened in one scriptlet must be correctly closed in a
later scriptlet for the page to successfully compile. Content which falls inside a split block of Java
code (spanning multiple script lets) is subject to that code. Content inside an if block will only
appear in the output when the if condition evaluates to true. Likewise, content inside a loop
construct may appear multiple times in the output, depending upon how many times the loop body
runs.
COMPILER
A Java Server Pages compiler is a program that parses JSPs, and transforms them into
executable Java Servlets. A program of this type is usually embedded into the application server
and run automatically the first time a JSP is accessed, but pages may also be precompiled for better
performance, or compiled as a part of the build process to test for errors. Some JSP containers
support configuring how often the container checks JSP files timestamps to see whether the page
has changed. Typically, this timestamp would be set to a short interval (perhaps seconds) during
software development, and a longer interval (perhaps minutes, or even never) for a deployed Web
application.
5.2 ABOUT MY-SQL
Introduction
MySQL is the world's most used open source relational database management system
(RDBMS) as of 2008 that run as a server providing multi-user access to a number of databases.
The MySQL development project has made its source code available under the terms of the GNU
General Public License, as well as under a variety of proprietary agreements. MySQL was owned
and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by
Oracle Corporation.
MySQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open source web application software stack—LAMP is an
acronym for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open source projects that
require a full-featured database management system often use MySQL.
For commercial use, several paid editions are available, and offer additional functionality.
Applications which use MySQL databases include: TYPO3, Joomla, Word Press, phpBB, MyBB,
Drupal and other software built on the LAMP software stack. MySQL is also used in many high-
profile, large-scale World Wide Web products, including Wikipedia, Google (though not for
searches), ImagebookTwitter, Flickr, Nokia.com, and YouTube.
Inter Images
MySQL is primarily an RDBMS and ships with no GUI tools to administer MySQL
databases or manage data contained within the databases. Users may use the included command
line tools, or use MySQL "front-ends", desktop software and web applications that create and
manage MySQL databases, build database structures, back up data, inspect status, and work with
data records. The official set of MySQL front-end tools, MySQL Workbench is actively developed
by Oracle, and is freely available for use.
Graphical
The official MySQL Workbench is a free integrated environment developed by MySQL
AB, which enables users to graphically administer MySQL databases and visually design database
structures. MySQL Workbench replaces the previous package of software, MySQL GUI Tools.
Similar to other third-party packages, but still considered the authoritative MySQL frontend,
MySQL Workbench lets users manage database design & modeling, SQL development (replacing
MySQL Query Browser) and Database administration (replacing MySQL Administrator).MySQL
Workbench is available in two editions, the regular free and open source Community Edition
which may be downloaded from the MySQL website, and the proprietary Standard Edition which
extends and improves the feature set of the Community Edition.
Command Line
MySQL ships with some command line tools. Third-parties have also developed tools to
manage a MySQL server, some listed below. Maatkit - a cross-platform toolkit for MySQL,
PostgreSQL and Memcached, developed in Perl Maatkit can be used to prove replication is
working correctly, fix corrupted data, automate repetitive tasks, and speed up servers. Maatkit is
included with several GNU/Linux distributions such as CentOS and Debian and packages are
available for Programming. MySQL works on many different system platforms, including AIX,
BSDi, FreeBSD, HP-UX, eComStation, i5/OS, IRIX, Linux, Mac OS X, Microsoft Windows,
NetBSD, Novell NetWare, OpenBSD, OpenSolaris, OS/2 Warp, QNX, Solaris, Symbian, SunOS,
SCO Open Server, SCO UnixWare, Sanos and Tru64. A port of MySQL to OpenVMS also exists.
MySQL is written in C and C++. Its SQL parser is written in yacc, and a home-brewed
lexical analyzer. Many programming languages with language-specific APIs include libraries for
accessing MySQL databases. These include MySQL Connector/Net for integration with
Microsoft's Visual Studio (languages such as C# and VB are most commonly used) and the JDBC
driver for Java. In addition, an ODBC inter image called MyODBC allows additional programming
languages that support the ODBC inter image to communicate with a MySQL database, such as
ASP or ColdFusion. The HTSQL - URL-based query method also ships with a MySQL adapter,
allowing direct interaction between a MySQL database and any web client via structured URLs.
Features
 As of April 2009, MySQL offered MySQL 5.1 in two different variants: the open source MySQL
Community Server and the commercial Enterprise Server. MySQL 5.5 is offered under the same
licenses. They have a common code base and include the following features:
 A broad subset of ANSI SQL 99, as well as extensions
 Cross-platform support
 Stored procedures
 Triggers
 Cursors
 Updatable Views
 Information schema
 CHAPTER 2
LOGICAL DEVELOPMENT
2.1. DFDs

DFD describes the processes that are involved in a system to transfer data from the input
to the file storage and reports generation.
Data flow diagrams can be divided into logical and physical. The logical data flow diagram
describes flow of data through a system to perform certain functionality of a business. The
physical data flow diagram describes the implementation of the logical data flow.
A data flow diagram (DFD) maps out the flow of information for any process or system. It uses
defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs,
outputs, storage points and the routes between each destination. Data flowcharts can range from
simple, even hand-drawn process overviews, to in-depth, multi-level DFDs that dig progressively
deeper into how the data is handled. They can be used to analyze an existing system or model a
new one. Like all the best diagrams and charts, a DFD can often visually “say” things that would
be hard to explain in words, and they work for both technical and nontechnical audiences, from
developer to CEO. That’s why DFDs remain so popular after all these years. While they work well
for data flow software and systems, they are less applicable nowadays to visualizing interactive,
real-time or database-oriented software or systems.

DFD rules and tips:

 Each process should have at least one input and an output.

 Each data store should have at least one data flow in and one data flow out.
 Data stored in a system must go through a process.
 All processes in a DFD go to another process or a data store.
Data flow Symbols:

Symbol Description

An entity. A source of data or a destination

for data.

A process or task that is performed by the

system.

A data store, a place where data is held

between processes.

A data flow.

LEVEL 0

DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system or process
being analyzed or modeled. It’s designed to be an at-a-glance view, showing the system as a single
high-level process, with its relationship to external entities. It should be easily understood by a
wide audience, including stakeholders, business analysts, data analysts and developers. A context
diagram gives an overview and it is the highest level in a data flow diagram, containing only one
process representing the entire system. It should be split into major processes which give greater
detail and each major process may further split to give more detail.
 Level 0 DFD must balance with the context diagram it describes. Input going into a process
is different from outputs leaving the process. Data stores are first shown at this level.

Admin

LOGIN

VIEW_DETAILS

WATER
PRODUCTS
SUPPLY
INFO
SYSTEM

Fig 2.1.1 level 0-DFD

LEVEL 1

DFD Level 1 provides a more detailed breakout of pieces of the Context Level Diagram.
You will highlight the main functions carried out by the system, as you break down the high-level
process of the Context Diagram into its sub – processes. Level 1 - interaction between 2 different
business applications. This is primarily used to explain the process to business and tech leads, QA
leads. As described previously, context diagrams (level 0 DFDs) are diagrams where the whole
system is represented as a single process. A level 1 DFD notates each of the main sub-processes

that together form the complete system. We can think of a level 1 DFD as an “exploded
view” of the context diagram.

the context diagram.

 1.0
User Registra Database
tion

2.0
Admin
Login

3.0
View water
bottle details

Add card

View my
accounts

VIEW DETAILS

Fig 2.1.2 level 1 DFD

2.2 ARCHITECTURAL DESIGN

A system architecture or systems architecture is the conceptual model that defines the
structure, behavior, and more views of a system. An architecture description is a formal description
and representation of a system, organized in a way that supports reasoning about the structures and
behaviors of the system. System architecture can comprise system components, the externally
visible properties of those components, the relationships (e.g. the behavior) between them. It can
provide a plan from which products can be procured, and systems developed, that will work
together to implement the overall system. There have been efforts to formalize languages to
describe system architecture; collectively these are called architecture description languages
(ADLs).

Various organizations define systems architecture in different ways, including:

 An allocated arrangement of physical elements which provides the design solution for a
consumer product or life-cycle process intended to satisfy the requirements of the
functional architecture and the requirements baseline.
 Architecture comprises the most important, pervasive, top-level, strategic inventions,
decisions, and their associated rationales about the overall structure (i.e., essential elements
and their relationships) and associated characteristics and behavior.
 If documented, it may include information such as a detailed inventory of current hardware,
software and networking capabilities; a description of long-range plans and priorities for
future purchases, and a plan for upgrading and/or replacing dated equipment and software.

An architecture diagram is a graphical representation of a set of concepts that are part of

architecture, including their principles, elements and components. Architecture diagram can help
system designers and developers visualize the high-level, overall structure of their system or
application, in order to ensure the system meets their users' needs. Using architecture diagram, you
can also describe patterns that are used throughout the design. It's somewhat like a blueprint that
you use as a guide, so that you and your colleagues can discuss, improve and follow.
Features are fetched from the database.
 CHAPTER 3

DATABASE DESIGN

3.1. DATA DICTIONARY

3.3 RELATIONSHIP DIAGRAM

Entity Relationship Diagram, also known as ERD, ER Diagram or ER model, is a type

of structural diagram for use in database design. An ERD contains different symbols and
connectors that visualize two important information: The major entities within the system
scope, and the inter-relationships among these entities. And that's why it's called "Entity"
"Relationship" diagram (ERD)!When we talk about entities in ERD, very often we are referring
to business objects such as people/role (e.g. Student), tangible business objects (e.g. Product),
intangible business objects (e.g. Log), etc. "Relationship" is about how these entities relate to
each other within the system.
Fig 3.3.1ER diagram
 CHAPTER 4

PROGRAM DESIGN

4.1 MODULES

 ADMIN
 USER
 SUPPLIER

ADMIN

Login:
Admin should login into the system to monitors news or reports by the users. Admin will view
the news if the comments seems to be illegal about the news then the news will be deleted by the
admin.
View details:
admin can see all detail in brief like total order, total new order, total accept order, total order
deliver, total cancel order, total company and total register user. Admin can also update his profile,
change password and recover password
Water Bottle info:
In this section admin can manage water bottle(Add/Update).
USER
Water Bottle:
In this section user can view which drinking bottle available.
My Accounts:
In this section user can change his/her own password, view and update his/her profile and logout
from accounts.
My Orders: In this section user can view order history after login.
Cart: In this section user can add their drinking bottle which he/her want to order.

CHAPTER 5
 TESTING
5.1 TESTING

Testing is a series of different tests that whose primary purpose is to fully exercise the computer
based system. Although each test has a different purpose, all work should verify that all system
element have been properly integrated and performed allocated function. Testing is the process of
checking whether the developed system works according to the actual requirement and objectives
of the system. The philosophy behind testing is to find the errors. A good test is one that has a high
probability of finding an undiscovered error. A successful test is one that uncovers the
undiscovered error. Test cases are devised with this purpose in mind. A test case is a set of data
that the system will process as an input.

5.1.1 TYPES OF TESTING:

 System testing

After a system has been verified, it needs to be thoroughly tested to ensure that every component
of the system is performing in accordance with the specific requirements and that it is operating as
it should including when the wrong functions are requested or the wrong data is
introduced. Testing measures consist of developing a set of test criteria either for the entire system
or for specific hardware, software and communications components. For an important and
sensitive system such as an electronic voting system, a structured system testing program may be
established to ensure that all aspects of the system are thoroughly tested.

Testing measures that could be followed include:

 Applying functional tests to determine whether the test criteria have been met
 Applying qualitative assessments to determine whether the test criteria have been
met.
 Conducting tests in “laboratory” conditions and conducting tests in a variety of
“real life” conditions.
 Conducting tests over an extended period of time to ensure systems can perform
consistently.
  Conducting “load tests”, simulating as close as possible likely conditions while
using or exceeding the amounts of data that can be expected to be handled in an
actual situation.
Test measures for hardware may include:

 Applying “non-operating” tests to ensure that equipment can stand up to expected levels
of physical handling.
 Testing “hard wired” code in hardware (firmware) to ensure its logical correctness and that
appropriate standards are followed.

Tests for software components also include:

 Testing all programs to ensure its logical correctness and that appropriate design,
development and implementation standards have been followed.
 Conducting “load tests”, simulating as close as possible a variety of “real life” conditions
using or exceeding the amounts of data that could be expected in an actual situation.
 Verifying that integrity of data is maintained throughout its required manipulation.

 Unit testing

The first test in the development process is the unit test. The source code is normally
divided into modules, which in turn are divided into smaller units called units. These units have
specific behavior. The test done on these units of code is called unit test. Unit test depends upon
the language on which the project is developed.

Unit tests ensure that each unique path of the project performs accurately to the documented
specifications and contains clearly defined inputs and expected results. Functional and reliability
testing in an Engineering environment. Producing tests for the behavior of components (nodes and
vertices) of a product to ensure their correct behavior prior to system integration.
  System testing

Several modules constitute a project. If the project is long-term project, several developers
write the modules. Once all the modules are integrated, several errors may arise. The testing done
at this stage is called system test. System testing ensures that the entire integrated software system
meets requirements. It tests a configuration to ensure known and predictable results. System testing
is based on process descriptions and flows, emphasizing pre-driven process links and integration
points. Testing a specific hardware/software installation. This is typically performed on a COTS
(commercial off the shelf) system or any other system comprised of disparate parts where custom
configurations and/or unique installations are the norm.

 Integration testing

Testing is which modules are combined and tested as a group. Modules are typically code
modules, individual applications, source and destination applications on a network, etc. Integration
Testing follows unit testing and precedes system testing. Testing after the product is code
complete. Betas are often widely distributed or even distributed to the public at large in hopes that
they will buy the final product when it is release.
 CHAPTER 6

CONCLUSION
We are trying to develop a environment where we can save the waste of water as conservation of
water it is essential task for humanity and also better scheduling of garbage collector system. The
increasing temperature affecting the resources already and waste of water can cause other major
problems. This system will provide an appropriate solution to the daily problems faced by
municipal corporations and residential in big cities. We believe this system will be one of the most
promising for current and coming generation.
CHAPTER 7

REFERENCES

[1]. C. Vandenberg A. Danilenko, the IBNET Water Supply and Sanitation Performance
Bluebooks, the World Bank, Washington D.C, 2011.

[2]. S. Tsegaye J. Eckart, K. Vairava moorthy, urban water management in cities of the future:
emerging areas in developing countries, on the water front, 2011, pp. 42-48.

[3]. B. Charalambous, the Effects of Intermittent Supply on Water Distribution Networks, Water
Loss2012, Manila, Philippines, 2012.

[4]. C.-K. Woo, managing water supply shortage: Interruptions. Pricing, J.PublicEcon.54
(1994)145–160.

[5].http://www.ifpri.org/sites/default/files/publications/eptdp68

[6.]http://dolr.nic.in/fguidelines.html

[7]. http://dolr.nic.in/fguidelines.html