Project Bca
Project Bca
Project Bca
, Mamta Awasthi, hereby declare that this project report on "Water Supply Management"
has been prepared at Technical Education And Research Institute by me under the
supervision of Mr.Durgesh Singh.
This project report is my bona fide work and has not been submitted in any from to
any university or institute for award of any degree or diploma prior to the under mentioned
date.
I bear the entire responsibility of submission of this project report.
BCA Sth senmester.I went through several processes and I successfully completed my training
specification.Jt first describes the present working system .Then the problems are identified.
After the complete analysis of present system and the problem related to old system has been
specified new system is proposed, which gives the user a better and efficient way of
managing transaction and updating his knowledge regarding the latest development.
Then we have covered topics of algorithms, mathematical foundation, and flowchart to be
the best etfort may not prove successful without proper guidance. For a good project one
needs proper time, energy, efforts, patience, and knowledge. But without any guidance it
remains unsuccessful. I have done this project with the best of my ability and hope that it will
serve its purpose.
First of all, I would like to acknowledge the guidance given to me by Mr. Ajit Pratap Singh
Head of the department, BCA, also their valuable that they gave me when I approached them.
I am really a great learning experience and I am really thankful to Mr. Durgesh Singh
helped me in the successful completion of this report but also spread his precious and
I also my express my gratitude to all faculty members who support me not only physically
but also morally and this is the result of his great effort towards me.
After the completion of this Project I feel myself as a well aware person about the Research
Procedure and the complexities that can arose during the process. Also I get an insight of the
advertising industry and its effectiveness in promoting sales. Last but not the least; I would
like to thank my parents and my brother for the immense support that they gave me.
Although they were not physically present with me, but there caring words on phone calls
refreshed my mind and gave me a new zeal to move on.
Mamta Awasthi
INDEX
1 Introduction 7-8
Objective 9-10
System analysis 11
3.1 Existing system description 12
3.2 Proposed System 12
3.3 Software Process Model 13-14
3.4 Feasibility study and report 15-16
trealment,
Water supPiyystems gel water from a variety of locations after appropriate
including
groundwa
(aquifers), surface wate (lakes and rivers), and the sea through desalination.
chlorination and
The water treatment steps include, in most cases, purification, disinfection through
s o
netimes Muoridation. Treated water then either flows by gravity or is pumped to reservoirs, Wne
m e t i n
of
can
be elevated such as water towers or on the ground (for indicators related to the efficiency
water distribution see non-revenue water). Once water is used, wastewater is typically
drinking
into a
discharged in a sewer system and treated in a sewage treatment plant before being discharged
ict,
Ver, lake or the sea or reused for landscaping, irrigation or industrial use (see also sanitation).
treatment,
Water supply systems get
water from a variety of locations after appropriate
including groundwater (aquifers), surface water (lakes and rivers), and the sea through desalination.
and
The water
treatment steps include, in most cases, purification, disinfection through chlorination
which
sometimes fluoridation. Treated water then either flows by gravity or is pumped to reservoirs,
to the efficiency of
can be elevated such as water towers or on the ground (for indicators related
drinking water distribution see non-revenue water). Once water is used, wastewater is typically
into
discharged in a sewer system and treated in a sewage treatment plant before being discharged a
river, lake or the sea or reused for landscaping, irrigation or industrial use (see also sanitation).
are thousands
Drinking water quality has a micro-biological and a physico-chemical dimension. There
at a minimum, be
of parameters of water quality. In public water supply systems water should,
disinfectedmost commonly through the use of chlorination or the use of ultra violet light-or it may
need to undergo treatment, especially in the case of surface water. For more details, please see the
Water pressures vary in different locations of a distribution system. Water mains below the street may
pressures, with pressure reducer located at each point where the water enters a
operate at higher a
trickle of water or so high that it leads to damage to plumbing fixtures and waste of water. Pressure in
an urban water system is typically maintained either by a pressurised water tank serving an urban
area, by pumping the water up into a water tower and relying on gravity to maintain a constant
pressure in the system or solely by pumps at the water treatment plant and repeater pumping stations.
The water supply industry is itally important not only to maintain the health of the community, but for
the sustainability of industry, business and agriculture. Without adequate water supplies our present
ver have on
iety would neve evolved, and our lives today would be unrecognizable. Our dependence
to the worst natural
and
eated water is
now
incalculable, and threats to that supply are comparable
-made disasters. The volumes of water consumed each day by agriculture, industry and the public
m a n - m a d e
stand
network of distribution pipes
net
to service each household, but unlike the other utilities these are
and
or regional networks, rather than integrated national supply networks. In England
alone local
alon
Wales there are 26 private water companies that together supplied 52.7 million consumers in 2004/
from surface
with 15 807
million litres (MI d1 ) of water each day. Sixty-eight per cent of this came
2
2.OBJECTIVE
as well as
very early
times man has obtained water from the surface sources such as rivers, lakes, etc.,
Since
SIh
less requirement of
the subsurace or groundwater sources such as springs, wells, etc. Due to relatively
from
from
be
domestic purposes, these sources were deemed to
water in
the earily times, which was mainly. for
Further water was directly
Cufficient to meet the requirements of the persons residing in the nearby
areas.
to the development of
However, growth of population the demand of water also increased which led
with the
water at
cities close to the areas to be supplied water. The service reservoirs, besides supplying
of towns or
upply scheme which would provide potable water free from ary kind of contamination.
Tthis is so because in the course of its movement through the porous sub-strata the water is completely
this water may have to be
relieved of ils suspended impurities. However, before supplying to the public
other method, in
disinfected by chlorination (i.e., by adding chlorine or chlorine compound to water) or any
orderto remove any harmful bacteria responsible for causing diseascs.
be supplied to
The water obtained from any of the surface sources of water needs to be purified before it can
thepublic.
Water is filtration. In the process of filtration
water
The most commonly adopted method of purification of
through beds of sand and gravel whereby minute suspended and
dissolved particles are
is allowed to pass
removed.
System analysis
System analysis and design refers to the process of examining a situation with the intent of improving
i through beter procedure and methods. System design is the process of planning a new system
or one to replace or complement an existing system. But before this planning can be done, we
must thoroughly understand the system and determine how conmputer can best be used to make its
aneration more effective. System analysis is, therefore, the process of gathering and interpreting
facis, diagnosing problems and using the information to recommend improvements to system.
eloped on HTML and MY SQL. It has been developed and implemented for regular use by the
very easy to understand and operate. Hence it is/Will be totally friendly &
I t is user
meractive system.
Proposed Svstem:
Tie present system needs to be computerized because the present manual system has the following
rzwbacks:-
The biggest problem of existing system is that each time when a model changes then
maintenance.
Thus to overcome all these problems the existing manual system is to be computerized on
wtole
C.It will help in manpower planning and will give perfect estimation of buses information.
Online
EWater supply management will help this to maintain better records.
6
3.3
Software Process Model
TheWaterfall model:
development
The de model which is best suited to
my software project is the waterfall model, which is the
nrocess model, which states that
phases are organize in a linear order. In waterta model, the
CnCe of activities pertormed in software
development project is: requirement analysis, project planning
system design and detai design, coding and testing.
nd of each phase. This is usually done by some verification and validation means that will ensure that
aultnult of a phase is consist with its input, and the output of phase is consist with the overall requirement of
the system.
There are two basic assumptions for justifying the linear ordering of phase in the manner proposed by the
waterfall model:
. For a successful project resulting in a successful product, all phase in the waterfall model must be
Detailed Design
Document
Coding Program
Testing and
Integration
verification
Manuals
Installation Installatinn
Operation
And Maintenance
Report
atroduction:
wnen a project is started an initial investigation is carried out. During this phase
f study users need nas recognized and other requirements are determined. Once the problem has
defined a study is carried out to sclect the best system i.e. a feasible system that meets
been
So is worth
erformance requirements, Feasibility is the determination of whether or not a project
ding and the process followed in making this determination is called a Feasibility Study. In order
Conduct the feasibility study we have seven distinct, but inter-related types of feasibility, these are
o
those are:
Technical Feasibility
Economical Feasibility
Operational feasibility
Technicalfeasibility:
the
specifying equipment (hardware) and software that will successfully satisfy
user
Ihis is concerned with
and
co/beneit amalysls I to muke,'This oroeedure is to determine the benefits
ht ato oxpocted Iron propaedd uystem nd compare them with conls. Four Sactw that
0perationalleasibility.:
Do the existing stalf mcmberw have thee wkill» if not, can they be trained.
Feasibility Study:
i.c. the docunentation aller feasibility study report document. It contains the
The end product,
following scclions:
Table of contlents
of the purpose nd seope of the projccl, the reason for undertaking feasibility
3. Narrative explanation
alfected by candidate system
study, and the departmcnt involved or
Detail outline the methods ued in the present system. Effectiveness, efliciency operating costs
4 findings
the candidate system.
deseription of objcctives and general proccdurcs of
cost estimates for the
Economic justification details poinl-to-point cost comparisons and preliminary
Relurn on Investment (ROI) is also given.
development and operation of the candidate system,
10
endation8 und conclusion suggest to management the most beneficial and coSt C
4
Software Requirement Specification
A with the
It includes a set of all the interactions the will have
eveloped.
t ob e d e v e l o p use cases that describe users
addition to use cases, the SRS also contains non-functional (or supplementary) requirements.
re. In
soltware. In.
(Such
as performanceengineering requirements, guality standards, or design constraints).
Requirement documentation is very important activity after the requirements enelad
consistent format. Requirement
T his is the way 10 represent requirements in a
analysis.
and
ment is called Software Requirement Specification (SRS).
JOC
task.
of the analysis
The software requirements specification is produced at the culmination
tor a
to represent requirements in a consistent format. It is a specification
his
h is the way
certain functions in
soltware product, program or a set of programs that performs
nurticular are
environment .The function and allocated to software as part of system engineering
specific
detailed functional and behavioral
establishing a complete information description, a
refined by validation
appropriate
description, an indication of performance requirements and design constraints,
other dala pertinent to requirements
crieria, and
certain functions in a
Soltware product, program or set of programs that perform
regarding SRS: First one, SRS is used to
environment. There are two important cases
specific for different
of the users. The second one, SRS is written
define the needs and expectations
and This produces the
developer.
a contract document between customer
purpose and serve as
1
o produc the SRS, which describe the
cxtenal behavior of the proposed
ompiete
nization of an SRS;
Introduction
Purpose
Scope
Definitions
System Overview
.OverallDescription
Product Perspetive
Product Functions
User Characteristics
Specific Requirements
Extemal interfaces
Functions
Performance requirements
key features
cOnSistent
complete
unambiguous
odifiabile
verifiable
raceable
aiked
12
NEEDFORSRS:
An SRS establishes the basis for agreement between client and developer.
An SRS provides a reference for validation of the final product.
Plattorm:
Windows is very powerful scalable Operating System that provides basie file and prints
aices as well as robust platform for server applications. Main features are as follow
13
4.1 Obiective
Obiective:
nteraction, and the order in which they should be followed by the A requirements document, on the
user.
would sstate that the software must handle error states reasonably and effectively, and provide
hand,
l l e r
can be diagrams or schematics of functional relationships or flow logic, or they can occupy some
they
itdle ground. Software Requirement Specifications can also be in the form of prototypes, mockups, and
middlo
models.
much important product. Every rule
Project specifications are more for determining the quality of the
nd functional relationship provides a test point.
Adisparity between the program and its specification is an error in the program if and only if the software
exists and correct. A program that follows a terrible specification perfectly is
rEQuirement specification is
14
4.2 Scope
Roundaries oI sortware products are defined by a set of Requirements. The software development
implements,
designs, imp fests, and delivers these Requirements to you. A Requirement is an atomic unit of
software
nroduct from the viewpoint of the user. As a rule, Requirements are always correct,
aits,
yntmbuiguous,
verifiable, and traceable. Requirements are numbered and prioritized.
High-level user Requirements are called Features. Up to 10 Features can be defined in any
nroject, regardless of the project size. Features are defined in the Vision document. The Vision is
software
d before the project commences, and is the basis for the ROM Estimate. The Vision is developed right
e a e d
ou submit an informal request. Up to 5 hours are spent for developing the Vision by a system analyst,
atieryo
oRrdless of
the project size.
All Functional Requirements are then listed in a requirements attributes spreadsheet, where all necessary
rbuies for each Requirement are maintained.Changes to the project scope can be made only by issuing
new Specifications through a process called Change Requests. Each Change Request implies that changes
15
4.3Software Requirement
oftware
are Requirement:
Kequiren
(SRS).
Ihe software
requirements specification is produced at the culmination O
functions
Tunctions in a speCitic environment The function and allocated to software as part o
engineering are refined by establishing a complete information description, a detald
T S T C n
specific environment. There are two important cases regarding SRS: First one, SRS is used to
sfine the needs and expectations of the users. The second one, SRS is written for different
pose and serve as a contract document between customer and developer. This produces the
purp
mobability of the customer being disappointment with the final product.
43.1Functional Requirements:
16
erformance Requirements:
a cu.
to maintain an acceptable speed at maximum number of uploads allowed from pare
In order
o ue
number of users can access the system at any time. Also connections
will be any
c U s t o m e rv i l l ,
whole
be working
will be
based o n
based
the criteria of attributes of the user like his location, and s e r v e r will
4 N7 tumes.
Functional Requirements
Non
7 availability.
i). 24 X
1. Security
2. Reliability
3. Maintainability
4. Portability
5. Extensibility
6. Reusability
7. Application Affinity/Compatibility
8. Resource Utilization
17
2SecurityiRequirement
rity
Security requirements are the
particularly significant in defense svstem and many database
sy>o
uirement place
a u n y requiremeni ace restrictions on the use of certain
commands, control access to data, provide
Jiterentkindof cess requirement for different
people, require the use of passwords and cryptography
and maintai
pumngues, and tain a log of activities in system. Given the current security
s needs even of common
they may also require proper assessment of security threats, proper programming techniques, and
sSCms, h e y m a
eoltoe
Isto detect flaws like buffer overflow.
For
thep u r p o s e
rity process I have added the login feature into my project s0 as to keep it safe from
external problem. em. One can only interact with my project by giving itthe suitable i.e. the accurate ID and
pasSHOrd,
18
SOFTWARE REQUIREMENT
Front End HTML, CSs, BOOTSTRAP
19
4.5 Hardware Requirement
Mdare Requirement:
Requirement documentation is
elicitation
E C n t s clic and very important activity after the
analysis. This is the way to represent
ement document is called Software
Requirement requirements in a
cosisistent
The hardware
Requirement Specification (SRS).
ofthe analysis task. This is the
requirements specification is produced at the
way to represent requirements in a consistent format. itis a
tneanon
n for
tor a
particular hardware product,
program or a set of programs that pertorms
ifunctions in a specific work
HRDWARE REQUIREMENT
Phcessor 2.30GHZ
RAM 4.00GB
Hard Disk 16 GB
20
SYSTEM DESIGN
21
5 SYSTEM DESIGN
design provides the understandings and procedural details necessary for implementing the system
in the
syitmendedin system emphasis is on the
translating the requirements into design
performance
r:Calons The design phase is a transition from a user oriented ment (system proposal) to a
ented to the programmers or database personnel.
m e n to r i e n t e d
1. Logical Design
2. Physical Design
dow diagram shows the logical flow of the system. For a system it describes the input (source),
uenis. When analysis prepares the logical system design, they specify the user needs at a level or
rements.
hatvirtually determincs the information flow into and out of the system and the required data
0UTCes.
22
5.1 DESIGNING APPROACH
downdesign:
The WN
TOP DOW
approach starts from the
vet
lower levels. A top down highest level component of the
design hierarchy and proceed
gugh
them into
nto their lower level approach starts by the
eomposing
major com
omponent of the system.
design method
Top down desig component and iterative until the desired
is in some label
of detail is
form of step wise
s h e v e a
pIN In cach
step the design is refine to more refinemer
ment. Starting from an abstract
nent is needed.
concrete level, until we
reach a level were no more
A system consi. nsists of
components, which have
of components. The highest level components of their own, indeed a system is a
component
corresponds to the total system. The top doWn
start from the upper level
component of hierarchy and
g v a c h
23
High Level Design
2A
HIGH LEVEL DESIGN
FLOW DIAGRAM:
diagram (DED) Is a
graphical representation of the information
flow & transformation that are
moves from the input
nle, as data to the output. It is also
known "DATA flow
Graph" or "bubble
as
ho DED may be used to
The represent
increasing information flow & function details. a
Aa "fundamental system model",
level 0 DFD,
represent an entire software element an a
data directed by the
single bubble with the
he output
e
incoming outgoing arrows. Quite general & nit limited to
&
ir software requirement specification
problem
tor
(SRS). DFD are very useful if understanding a & can system
etdvnively
used during analysis.
e
bca
FTow
tlaiw Diagram Diagram are commonly used during problem analysis. Data Flow
Diagram are quite
and are not limited to problem analysis for software requirement
specification.A DFD
dhe flow of data through a system. It views function that transforms the
as a
input into desired
The DFD aims to capture the transformations that take place within
a system to input data so
data is produced
the output
SYMBOLSUSED IN DATA FLOw
DIAGRAM
REPRESENTATION
more process
26
D
OR
1 O R
level DFD
Rogintration
loer login WSM
Home Page
Rogitraition/
L.ogin SueceNsiul
21
1ST LEVEL FOR QUERY PROCESS
1-LEVEL DFD
DATABASE
Water supply
Customer
manament Supply
sign in
NEW
NO
Check
Login information
YES
Contact Us
28
E-R DIAGRAM
Attribute- :An atribute is the property or characteristics of an entity Each entity type has a set of
attributes associated with it. For example, an entity student has attributes name, age, class, roll number, etc.
29
ns of E-R Diagram- :The overall logical structure of a database can be expressed
by ER Dia
Diagram .These are the notations used in ER
pihicalh Diagram
relationship.
the entity
30
ENTITY RELATIONSHIP DIAGRAM
LOGIN ID
Login
PASSWORD
email
password
Water Packed
Supplv bottles
Applied
for
Supplier
FEES
31
LowLevel Design
32
LOW LEVEL DESIGN
LOW Level Desi
Level Design (LLD) is a
component level design process that follows a step by step relinement
sS. This process can be used for
process,
designing data
structures, required software architecture, source code
ultimately, performance algorithms. Overall, the data
organization may be defined during requirement
Ivsis and then refined
Jnalysis
during data design work. Post-build, each
component is specified in detail.
The goal of LLD or a low-level design document (LLDD) is to give the internal logical design of the
-tual program code. Low-level
actua
design is created based on the high-level design. LLD describes the class
diggrams with the methods and
relations between classes and
program specs. It describes the modules so
hat the programmer can
directly code the program from the document.
maintenan
33
TABLE SCHEMA
Database Table of login
NAME TYPE
EMAIL VARCHER
PASSWORD VARCHER
Of Auribute
34
BIBLIOGRAPHY &REFERENCES
we are the following link which assist me each and every step in completing this project.
There.
. www.tutorialspoint.com
2. www.w`school.com
3. www.javapoint.com
4. www.wikipedia.com
35