Smart Water Billing System

Smart Water Billing Page I
Declaration
We are honestly declared that, this is our work and that all sources of materials used in this
project have been strongly acknowledged.
This project paper is summated in partial fulfillment of the requirement for min project for
Electrical and computer Engineering at Ambo University Institute of technology.
This is to certify that above declaration made by our effort is correct to the best of our
knowledge. In doing so, we assure that we agree with all written above approved by our
signatures
Name Id no. Sign.
1) Biniam Kidane___________________brt/0005/09 ------------

2) Efnera Bekele____________________tbrt /3003/11 ------------
3) GudinaLemessa__________________brt/1084/09 ------------
4) Kalkidanshbiru___________________brt/1225/09 ------------
5) Reshido Abdu____________________brt/1557/09 ------------
Smart Water Billing Page I

Acknowledgement
First of all heartfelt gratitude goes to our School of Informatics and Electrical Engineering for
giving such a chance to work. Next, we would like to thank our advisor Daraje Merga for is
unreserved guidance, suggestion, and advices. We are grateful to is motivation for the timely
completion of the project, and is dynamic suggestion for solution to any challenges during total
work of this project.
Smart Water Billing Page II

Abstract
In the face of advancement in technology organizations use Smart water billing service. Many
organizations use the manual Customer service management system. On the other hand, many
government and private organizations are automating their day-to-day operations. Out of many
applications of computers the group will develop a Smart water billing service that solves the
challenges of Water supply enterprise Customer service management.
It replaces the situation which requires a number of workers and lots of time in the manual
system of customer service management system. The system handles customers’ bill processing,
maintenance processing, customer registration and many other functions. The enterprise can
receive customer maintenance request through internet, the customers make to insert their
application form to get new water supply line, and the enterprise can give payment information
for customers and also the enterprise release news for the customers. For the success of this
project the group uses many methods. The methods used for system analysis and design is
object-oriented System analysis and design. Finally, this project is successfully implemented for
the test on LAN of the organization for testing how the capability of this system is functional.
Smart Water Billing Page III

Table of Contents
Declaration.......................................................................................................................................I
Acknowledgement..........................................................................................................................II
Abstract..........................................................................................................................................III
List of Figures..............................................................................................................................VII
List of Tables..............................................................................................................................VIII
Acronyms......................................................................................................................................IX
Chapter One.....................................................................................................................................1
1.1. Introduction.........................................................................................................................1
1.2. Background of the Project...................................................................................................2
1.3. Problem Statement..............................................................................................................2
1.5. Objective of the Project.......................................................................................................3
1.5.1. General Objective..........................................................................................................3
1.5.2. Specific Objective.........................................................................................................3
1.6. Cost Benefit Analysis............................................................................................................3

1.7. Feasibility Analysis................................................................................................................4
1.7.1 Technical Feasibility.......................................................................................................4
1.7.2 Economic Feasibility.......................................................................................................4
1.8. Scope of the Project.............................................................................................................4

1.9. Limitation of the Project......................................................................................................5
1.10. Significance of the Project..................................................................................................5
1.11. Target Beneficiaries of the System....................................................................................6
1.12. Methodology for the Project.............................................................................................6
1.12.1. Fact Finding Techniques..............................................................................................6
1.13. Systems Analysis and Design Approach.............................................................................6

1.14. Development Tools............................................................................................................7
1.14.1. Software Requirement..................................................................................................7
1.14.2. Hardware Requirement.................................................................................................8
1.15. Risks & Contingencies........................................................................................................8

Smart Water Billing Page IV
1.15.1. Project Development Problems...................................................................................8
Chapter Two....................................................................................................................................9
Description of the Existing System.................................................................................................9
2.1. Introduction of Existing System...........................................................................................9
2.2. Major functions/Activities in the Existing System...............................................................9
2.3. Players in the Existing System.............................................................................................10
2.4 Business Rules......................................................................................................................10
2.5. Practice to be Preserved....................................................................................................11
2.6. Requirements of the Proposed System.............................................................................11
2.6.1. Functional Requirements.............................................................................................11
2.6.2. Non- Functional Requirements...................................................................................12
Chapter Three................................................................................................................................13
System Analysis.............................................................................................................................13
3.1. System Models...................................................................................................................13
3.1.1. Actors and Use Case Identification.............................................................................13
3.1.2. Use Case Diagram.......................................................................................................14
3.1.3. Object Model...............................................................................................................15
3.2. Activity Diagrams...............................................................................................................17

3.3. User Interface.....................................................................................................................18
Chapter Four..................................................................................................................................23
System Design...............................................................................................................................23
4.1. Introduction.......................................................................................................................23
4.1.1. Purpose and Goals of the System Design....................................................................23
4.2. Persistent Data Management............................................................................................24

4.3. Access Control and Security...............................................................................................25
4.4. Boundary Conditions..........................................................................................................26
Chapter Five...................................................................................................................................27
Object Design................................................................................................................................27
5.1. Introduction.......................................................................................................................27
5.2. Object Design Trade-offs.....................................................................................................27
Smart Water Billing Page V

5.2.1. Understandability versus Cost.....................................................................................27
5.2.2. Interface Documentation Guidelines...........................................................................27
5.3. Class Interfaces...................................................................................................................28

5.3.1. Meter Reader Class.....................................................................................................28
5.3.2. Bill Officer Class.........................................................................................................28
5.3.3. Technician Class..........................................................................................................28
5.3.4. Customer Class............................................................................................................28
Chapter Six....................................................................................................................................29
Implementation and Testing..........................................................................................................29
6.1. Final Testing of the System................................................................................................29
6.1.1. Unit Testing.................................................................................................................29
6.1.2. Integration Testing......................................................................................................29
6.1.3. System Testing............................................................................................................29
Chapter Seven................................................................................................................................30
Conclusions and Recommendation................................................................................................30
7.1. Conclusions........................................................................................................................30
7.2. Recommendations.............................................................................................................31
References......................................................................................................................................32
Appendix........................................................................................................................................33
Code Sample..............................................................................................................................33
Smart Water Billing Page VI

List of Figures
Figure 1. System Use case.............................................................................................................13

Figure 2. Class diagram.................................................................................................................16
Figure 3 Activity Diagram for Login.............................................................................................17
Figure 4. UI-homepage..................................................................................................................18
Figure 5. UI-Customers homepage................................................................................................18
Figure 6 .Bill officer homepage.....................................................................................................19
Figure 7. UI-Accountant homepage..............................................................................................20
Figure 8. UI-Meter Reader-Homepage..........................................................................................20
Figure 9. UI-Technicians -Homepage...........................................................................................21
Figure 10. Persistence data management.......................................................................................23
Smart Water Billing Page VII

List of Tables
Table 1 Team composition..............................................................................................................2

Table 2. actor and Use case Identification.....................................................................................12
Table 3. Data dictionary for Employee table.................................................................................14
Table 4. Data dictionary for Bill table...........................................................................................14
Table 5. Data dictionary for Customer table.................................................................................15
Table 6. Access control and security.............................................................................................24
Smart Water Billing Page VIII

Acronyms
 DBMS: Database Management System

 MYSQL: My Structured Query Language
 PC: Personal Computer
 PHPMYADMIN: Hypertext Pre Processor
 CMS: Customer Management System
 HTML: Hyper Text Markup Language
 CSS: Cascading Style Sheet
 UML: Unified Modeling Language
 UC: Use Case
 OO: Object Oriented
 UI: User Interface
 DB: Database
 MYSQL: Structured Query Language
 URL: Uniform Resource Locator
Smart Water Billing Page IX

Chapter One
1.1. Introduction
Technological revolution brought great changes to mankind, access to information becomes

anytime and anywhere.
This Local Government Unit already have a billing system in a form of spreadsheet application.
As result of thorough interview - it is very difficult to provide up-to-date reporting using their
existing system. Finding and encoding customer's data specifically the meter readings of
customer's water consumption was very tedious to the user. Another problem is the report
generation; they could not provide it because it is hard for them to scan individual tables of
customers.
The proposed system will then change the way the current system goes and may have impact on
its current manpower, thus may result to acceptability or not by the end-users. In the long run, as
they may see that process change is inevitable then the proponent is quite sure that the proposed
system will be considered by its end-users.
The proposed system, Web-Based Billing and Collection System for a Municipal Water and
Services Unit comprised the billing, collection, storing the records in a database and report
generation.
1) The system generates billing statement that indicates the water consumed and its
corresponding cost.
2) Collection covers the recording of consumers' payments and necessary for the report
generation as required by treasurers' department of the said unit.
3) Transactions records are stored in the system's database.
4) Report generation as needed by the unit for decision making purposes and in monitoring the
periodic transactions as required and or needed by the decision-making body of the local
government.
Smart Water Billing Page 1

1.2. Background of the Project
Water supply service enterprises need an effective and accurate customer service management
system to be able to assure their revenue. In today’s world of emerging technologies, companies
are moving their faces towards the Web based customer service management technologies.
People are rushing towards the Web based applications for their day-today needs, which in turn
are making the Internet very popular. Web based customer service management has given both
an opportunity and a challenge to traditional customer service. In the fast-growing world,
Services have to be fast and reliable, which saves much of our time processing services
manually.
In manual way paying bills by paper, recording customer’s information on record folders, are all
time-consuming tasks. Web based customer service automates many of these Processes, saving
time and money.
For all governmental and non-governmental companies, web-based customer service is a

powerful tool to Gain new customers while it helps to eliminates costly paper handling and
manual billing
1.3. Problem Statement
Many organizations currently use a semi-automated system. As it is semi-automated, it has its

own problems. Like:
 The data will loss and it takes time to manage.
 During requesting maintenance, the customers may spend unnecessarily expense and
waste their time.
 The customers may not get the chance to request service of the organization at anytime
and anywhere.
 Documents are easily damaged.
 It may be difficult for customers to get the phone number or the location of the
organization.
It takes time and it may not be easy to manage and analyses the monthly work due to massive
collection of data and the generated report may not be accurate
1.5. Objective of the Project
1.5.1. General Objective
Developing Smart water billing service management system.
1.5.2. Specific Objective
Here are some specific objectives that would together help us achieve the overall the project as
follows:
 Identify the problem of the existing system.
 Design a new proposed system to solve the existing problem.
 Design the proposed System using Uml diagram.
 Design a user Interface for the proposed system.
 Implementing the proposed system.
 Testing the proposed system using different testing mechanisms
1.6. Cost Benefit Analysis
Tangible Benefit: - It is project benefit that can convert into monetary values. For this project,
we have identified the following tangible benefits.
 Decrease in labor cost
 Reduced Stationary Cost
 Cost reduction of stationary
 Failure reduction
Intangible Benefits: - It is our project benefit that cannot convert into monetary values.
 Enhance reliability
 Knowledge gain by project developer.

 Increasing the competitiveness of the individual
 Improved productivity
 Improving the morale of our team.
 Faster decision making on the team member.
Intangible Cost: - is a cost that is not seen but its effects are perceived later in future.
 Need of skilled employee
1.7. Feasibility Analysis
Feasibility analysis begins once the goals are defined. It starts by generating broad possible
solutions, which are possible to give an indication of what the new system should look like. This
is where creativity and imagination are used. Analysts must think up new ways of doing things-
generate new ideas.
1.7.1 Technical Feasibility

To implement the system and the company is willing to deploy the system and the staffs in the
organization have some computer knowledge to understand the system easily.
1.7.2 Economic Feasibility

The exact costs are practically not possible to estimate at phases of the project because the end
users’ requirements and alternative technical solutions have not yet been identified fully, but
after estimating the range of costs it is believed by the organization that the cost incurred is
reasonable.
1.8. Scope of the Project
The scope of this project is Developing Smart water billing service management system for
organization which its system boundary includes the functions;
 registering employees,
 request maintenance order

 create user account
 receive meter value from meter readers
 calculate billing process
 Generate different reports (registration, payment, maintenance).
 . The system also allows managers to post different messages and news.
1.9. Limitation of the Project
The organization has its own human resource management, but we do not include in our
project, because Human resource management has wide area and it need large project by
itself and it is beyond our scope. And also, our project doesn’t perform online bill payment
and online customer registration.
1.10. Significance of the Project
The main benefits of this system as it is computerized web-based system:

 It saves the customers’ time when they want to access service from the organization.
 The Customers uses the system safely and gives comfort for them.
 It attracts other customer to join and register under the system.
 Introduces the office to technology and also facilitates technology throughout the
coverage area, as it is web-based system.
 It motivates many customers to join the system, as it is easily accessible.
 It makes the office efficient and more profitable in a short period of time, as it follows
fully automated system and has many customers.
 It increases performance of the organization.
 Generates more secured information for each customer. (use)
 It makes smooth relation between the office and their customer.
 Generates and improves socio economic change to the society.

Generally, the project aims at improving the customer service management of the Water supply
service organization. It helps the organization to improve its activities by making the work flow
smooth and less complicated.
1.11. Target Beneficiaries of the System
There are three beneficiaries in our system. These are:

 The first beneficiaries of this project are to the member of students who works this
project to fulfill their bachelor degree in electrical and computer engineering.
 The second beneficiaries are the customers who have knowledge on how to access
information from the internet and those of employee of Organization
 And the other user of this system the organization by its own, everybody can join
their organization simply and can understand how they work, and understand what
things they done. So, within a short time it becomes more profitable and famous.
1.12. Methodology for the Project
1.12.1. Fact Finding Techniques
Practical Observation
This method used to get the right information about the organization and also to understand how
the existing system works.
Document Analysis: - Forms and documents which the existing system currently uses, revised
to know rules, regulations and constraints in the existing system.
1.13. Systems Analysis and Design Approach
To develop a function-able and good quality system, the software development approach that
chosen must be suitable for developing the certain system, it must also provide all the features
that needed for developing the system. In this project, which is to develop a customer service

management system for water supply office of organization, the object-oriented approach is
chosen.
The object-oriented approach has the ability of encapsulation, inheritance and polymorphism that
provide the facilities of the data hiding and reusability of the code. The objects created in the
program can be reused and the internal structure of the objects it hides using encapsulation to
protect them from corruption. So, it made the system maintenance easier and shortens the
development time. Object-oriented approaches also reduce the complexity of the system
development. This is the reason why object-oriented approach is used in developing this project.
1.14. Development Tools
1.14.1. Software Requirement
Have much software to do this project, but the most important are the following:
 MySQL- to create and design the database which used to store the information of the
customers & the employee of the organization.
 Edraw Maxand visual paradigm: to designs the system analysis part of the project.
 PHP scripting language and its own XAMP server: to implement the system and
provide the user of the system with an interface.
 HTML sand CSS: using for static part of the website and for the style of the website
 Notepad ++: to write the client-side code.
 Windows Operating system: will be used for the system since it is readily available in
laboratories.
 Browsers: -since our system is web based, it is very necessary requirement.
 Microsoft office Word: -for documenting the corresponding deliverables associated with
the project

1.14.2. Hardware Requirement
Different hardware used to develop our project
 Computer: -computer is a machine capable of doing many things. We use it to type on it

and install all software and programming language.
 Flash Disk and CD Hardware: - used for the movement of data from one machine to
another. We use both of them when we move our data from one machine to another.
 Network cable: since our system is web based, it is very necessary requirement. It is also
help us to extract relevant information about our project from internet.
1.15. Risks & Contingencies
1.15.1. Project Development Problems
During the development of the project there may be different problems that we may face.
 Unfortunate failure of system: To handle this problem the teams have some method to
resist not completely but partially by using back up mechanisms using flash disks
 Power problem: we tried to use laptops to cover the gap happened to our project during
power failure.
 Time management problem: this problem by working cooperatively, divide our time by
schedule for each phase of the project and we try to use the schedule effectively.

Chapter Two
Description of the Existing System
2.1. Introduction of Existing System
This section describes how the existing system of the organization actually works with related to
the area on which the project tried to address. It describes the customer service system problems
associated with the existing system and also to suggest the possible ways of solving the
problems. It also includes the user functional and nonfunctional requirements for the new
system.
2.2. Major functions/Activities in the Existing System
Customer Registration: - It is done by customer service by collecting the necessary data from
the user manually.
Bill Calculation: - Customer’s data store and bill calculating was using computer software
which have MySQL database.
 Backup data was stored in manually by using hard disk device.
 Customer must inform the office if his/her reading value was not done in timely manner
by being physically available at the office.
 The billing system was done from the hierarchy of meter reading to bill officer, then bill
officer to accountant and from accountant to bill collector and vice versa manually.
Report Generation
 The organization makes a general report about the billing system once at the end of the
month and generates the report by the system but the result may not be always correct.
Maintenance Reporting
 Customers inform physically to their technical supervisor when service maintenance was
needed.

2.3. Players in the Existing System
In the existing system, there are different actors that are concerned with the issue of giving and
distributing the water supply and billing system to the customers. These actors are: -
1. Customer Relation officer
2. Maintenance officer
3. Billing officer
4. Meter Reader
2.4 Business Rules
The existing business rule of water supply and sewerage enterprise office has its own set of rules
and regulations to supply water to individual’s houses. This rule and regulation must be fulfilled
by customer to get and sustain the water supply in his/her house. The rules are: -
BR1:-The customer data encoder has the responsible to filter applicant based on the queue.
BR2:- The maintenance office is responsible to hear customer problem, if water tube has been
broken to maintain.
BR3:- The customer must pay monthly bill.
BR4:- The customer must pay monthly fees within the five days of month or within specified
time
BR5:-The customer agrees to pay penalty, if he/she does not pay on given time

2.5. Practice to be Preserved
Practices to be preserved are functionalities which we take it from the existing system without
any change and we use these functionalities in our proposed system. These functionalities are:-
Bill Calculation: - Customer’s data store and bill calculating was using computer software
which have MySQL database.
Report Generation: - The organization makes a general report about the billing system once at
the end of the month and generates the report by the system but the result may not be always
correct. The only we make is that make it accurate and web based to be accessed at anywhere at
any time.
Meter Reading Procedure: - this is made by going to the customer read the meter value and
record on the database.
2.6. Requirements of the Proposed System
2.6.1. Functional Requirements
Functional requirement describes the interaction between the system and its environment
 Add Customer: - The system registers applicant’s First name, Last name, Kebele,
Woreda, House number, Telephone number and then save to the database.
 Add Employee: - The system registers employee’s First name, Last name,
position, telephone number and then saves to the database.
 Customer Maintenance Orders: - customers can order services online by filling his/her
id and description about the service to be ordered.
 Display Customer’s Payment Information: - The system displays customers’ bill detail
when they enter their Id number.
 Display News About the Organization: - The system can provide different information
to customers and post notices like vacancy announcement.
 Receive Maintenance Order: - The system receives maintenance order from customers.

 Receive Meter Reader Information: - The system receives monthly customers’ water
consumption and calculate the bill.
 Setting Privilege for Employee: - the system gives different privilege for each actor
 Generate Report: -the system generates different reports. Like payment report,
maintenance report.
2.6.2. Non- Functional Requirements
Nonfunctional (supplementary) requirements pertain to other information needed to produce the

correct system and are detailed separately. Constraints on the services or functions offered by
the system such as timing constraints, constraints on the development process, standards, etc.
 Usability
 Reliability
 Performance
 Supportability
 Usability
 Legal
 Security and Access permissions
 Storage capability

Chapter Three
System Analysis
3.1. System Models
3.1.1. Actors and Use Case Identification
Table 1. actor and Use case Identification
Use Case Name Use Case Identifier Actor of the scenario
Login UC1 Bill-officer, Technician, Customer,

Meter Reader, Accountant
Update customer information UC2 Bill Officer.
Delete customer. UC3 Bill Officer.
Order maintenance UC4 Customer
Receive maintenance Order UC5 Technician
Update maintenance order UC-6 Technician
Meter read UC7 Meter reader
Generate report UC8 Bill officer
Register customer UC19 Customer

3.1.2. Use Case Diagram
Use case diagram is a diagram we used to show the functionality of the system. And also, we
show the external actors who interact with the system to perform their tasks.
Use cases are described in the system boundary and actors are described outside the system
boundary.
Figure 1. System Use case

3.1.3. Object Model
3.1.3.1. Data Dictionary
Table 2. Data dictionary for Employee table
Field Name Data type Description
First name Varchar (30) Holds the First name of the employee.
Last name Varchar(30) Holds the Last name of the employee.
Employee ID Varchar(30) Holds the identifier of the employee.
Position Varchar(30) Holds in which position the employee work.
Tele No Int(10) Describe the phone number of employee.
Table 3. Data Dictionary for Bill table
Bill No Int(10) Holds the identifier of the bill.
Current Read Float(10) Describe the bill value currently consumed.
Previous Read Float(10) Describe the bill value consumed before now.
Consumption Int(10) Describe amount of water consumed by customer.
Category Varchar(30) Describe the type of meter.
Total Float(10) Describe total amount of consumption.

Table 4. Data Dictionary for Customer Table
First name Varchar(30) Holds the First name of the customer.
Last name Varchar(30) Holds the Last name of the customer.
Bank Name Varchar(30) Describe the name of the bank in which customer
account is found.
Branch Name Varchar(30) Describe from which branch customer transfer money.
User Name Varchar (30) Describe the user name used when customer login to
the bank.
Password Varchar(30) Describe the Id used when customer login to the bank
when he/she perform some action.
3.1.3.2. Class Diagram
Class diagrams show the static structure of the model, in particular, the things that exist (such as
classes and types), their internal structure, and their relationships to other things. This project
used class diagram to design the structures that will be included in the system and the things that
will be exist in the system. Our class diagram includes different tables. Such as customer,
employee, maintenance, report, massage, registration. And bill officer, meter reader, accountant,
technician and data encoder are inherited classes from employee

Figure 2. Class Diagram
3.2. Activity Diagrams
Activity diagrams model is a high-level business or processes or transitions between states of a

class. In this activity diagram tries to document the flow of logic for the major business
processes.

Figure 3 Activity Diagram for Login
3.3. User Interface
User interface design or user interface engineering is the design of websites, applications with
the focus on the user's experience and interaction. The system uses user interface design to make

the user's interaction as simple and efficient as possible, in terms of accomplishing user goals—
what is often called user-centered design.
Figure 4. UI-Homepage
Figure 5. UI-Customers Homepage

Figure 6. Bill Officer Homepage
Employee Registration: - This link provided to the bill officer a page to register new
employees.
New User Account: - link provide user account creation page for new employees of the
organization.
View: - This link provides for the bill officer different reports of the offices activities those are,
report from bill collection, maintenance fee collection, penalty fee collection, total customer
registration reports and many other reporting aspects.
Logout: - this link used to sign off from the system.
Change Password: -this link provides the bill officer to change its own password.
Post Home Message: - this link provides a page for the bill officer to post in the homepage of
the system

Figure 7. UI-Accountant homepage
Figure 13
Figure 8. UI-Meter Reader-Homepage

Figure 9. UI-Technicians -Homepage

Chapter Four
System Design
4.1. Introduction
Design is process of describing, organizing, and structuring system components at architectural
design level and detailed design level. Design converts functional models from analysis into
models that represent the solution. Design may use structured or OO approaches.
4.1.1. Purpose and Goals of the System Design
Design goals are qualities that one system should focus on and are from nonfunctional
requirements or from the application domain.
 Performance
 Availability
 Security
 Reliability
 Usability
 Portability
 End user
The project is purposeful on meeting those design goals. For example:
 Speeding up the response time when a customer comes with request to get service.
 Minimizing the storage space and time to find for files.
 Decreasing the expenses customer faces while coming to the office to have a service.

4.2. Persistent Data Management
Web based CMS for organization water supply and sewerage office will largely depend on a
relational database to perform day-to-day operations and storing log data. Data will be stored in a
MySQL DBMS and manipulated through the Database Subsystem, which will ensure data
integrity and consistency. Database Subsystem will contain all necessary SQL queries that will
be accessible by the rest of the Subsystems.
The data stored in the database will include: -
Figure 10. Persistence Data Management

4.3. Access Control and Security
In the system, different actors have access to different information and data. Access control and
security specifies what the user can access or what cannot perform by some users. This access
control is verified by username and password. We use login subsystem to check username and
password. The following table shows access control of our system.
Table 5. Access Control and Security
Actor Confirmation and Control Account

Maintenance officer Update Maintenance ()
Maintenance Record () Login()
Receive Maintenance Change password()
order()
Perform Maintenance ()
View Maintenance report()
Billing officer Update customer() confirm password()
calculate Bill() change password()
Generate Report() Create user Account()
Register Employee() Manage Account()
Register customer()
Post Massage()
Meter reader Read meter() Login()
Record meter value() Change password()
Customer Order maintenance() Login()
View massage() Change password()
Perform payment()

4.4. Boundary Conditions
The boundary condition includes the processes from the deployment of the system to exit
condition.
 Deploy web-based CMS for OWSSO: this is the first action to be taken to make the
application accessible by authorized user.
 Startup: go to system URL and login and perform the action that the user wants.
 Error/Failure Conditions: occur when user input is invalid.
 Shut Down: click log out and close browser

Chapter Five
Object Design
5.1. Introduction
OWSSO consists of subsystems which work separately but concurrently. Subsystems interact
with each other and each subsystem works when it is called by another subsystem.
During the object design, characteristic of each system must be considered its own and the whole
system must be considered.
5.2. Object Design Trade-offs
Deployment diagram is a UML diagram that used for describing how the hardware components
are deployed. We used to visualize the topology of the physical components of our system where
the mentioned software component diagrams are deployed. In the object design phase, some
trade-off decisions may need to be made:
5.2.1. Understandability versus Cost
Understandability of the code is too important especially during the testing phase. Each class and
method must be readable, so number of methods increase in the system and functions must be
implemented in a clear way. Writing comments into the source code increases the
understandability of the code.
5.2.2. Interface Documentation Guidelines
Interface documentation guidelines and coding conventions are the most important factors that
can improve communications between developers during object design.

5.3. Class Interfaces
Class interfaces can be described by the class diagram. It shows the interactions between
different classes of the system or the way how classes are interacted each other to accomplish
their task.
Class interface diagram shows the methods with their own return type which can be implemented
in each class and it doesn’t show any multiplicity.
5.3.1. Meter Reader Class
This is a class with a method read (). This is responsible to read customer meter value and record
to the system.
5.3.2. Bill Officer Class
This is a class with public methods generate report (), update customer (). And it is responsible
generate different reports and update customer information.
5.3.3. Technician Class
This is a class with methods receive Main Order (), perform Maintenance (). And it is
responsible for receiving and performing customer maintenance order.
5.3.4. Customer Class
This is a class with three methods. These are order Maintenance (), view Message () and read
Bill (). And it is responsible for ordering Maintenance and read their own meter value.
This is described using the following class diagram:

Chapter Six
Implementation and Testing
6.1. Final Testing of the System
Testing is a trial experience in which the deliverables of the project are checked with acceptable
Standards in the project. We used unit testing, and system testing to test the correctness of each
Module and the compiled program.
6.1.1. Unit Testing
In this type of testing, components are tested individually. In case of our system, all components
have been tested to maximum satisfaction. The components that has been tested are
 Register customer
 Insert customers’ water consumption
 Calculate customer’s monthly fee
 Display customers’ consumption fee
 Generate bill
 Maintenance order processing
 Releasing News and Updates
6.1.2. Integration Testing
When a number of components are complete; it will test to ensure that they integrate well with
each other, the operating system, and other components.
6.1.3. System Testing
For verifying as the whole system is functioning in integrated manner and helping in striving
planned goal. System testing is comparing Function of the system developed in relation with
expected function of the system.

Chapter Seven
Conclusions and Recommendation
7.1. Conclusions
Now a day the application of Information communication technology in the world is increasing
in a greater rate and the world is going to be considered a small village. However, the application
of internet or more generally speaking the World Wide Web applications like web-based
customer service. As a result, many organizations activities are not computerized. This will cause
loss of cost, time, etc. actually this will reduce accuracy and performance further more enhance
the time, memory, labor, cost, etc. Taking this in mind, this web-based customer service
management system will facilitate customers’ registration process, inserting customers’
consumption (meter read) process, calculating monthly fee process, displaying customers’
payment, and customer maintenance order. This project is designed to fulfill the changing
requirements of the organization Water supply Service customer service management. This
project will be helpful to find out the problems existed in organization water supply customer
service management and to design web-based customer service management system. Different
methodologies of data collection (i.e., observation) and object-oriented analysis and design is
used to develop this system. This system will be capable of protecting from unauthorized users.
Searching, updating and deleting can be performed by the authorized users. Data validity is also
the capabilities of this system. The important feature of this system will be registering customer,
registering customer maintenance order, inserting customers’ water consumption, calculating
customer’s monthly fee, displaying customers’ consumption fee and generating bill. The system,
that is developing will at least removes the problems occurring and further assists procedures
which were used to be handled manually.

7.2. Recommendations
The important feature of this system will be registering customer, maintenance order, inserting
customers’ water consumption, calculating customer’s monthly fee, displaying customers’
consumption fee and generating bill. And due to shortage of time, resources and it is not
applicable now a day we didn’t complete functionalities like online payment and online
registration.
Since in the future Technology is growing fast and even each day new technology born like
humans, we recommend the next researcher/project developer to fulfill the limitation of our
project.
This system is design and implemented but may face some difficulties in some future. So to
overcome this problem from happening the organization has to give trainings for its staffs and
should keep maintaining this system eventually. And they should install and patch new updates,
replace new technological advancement when new updates and patch’s available.
The group recommends the organization to fulfill the following to fully work with the system
without any problem in the process of customer service.
 The organization should have good and fast LAN and Internet with high bandwidth
 Computer systems must have high processing speed and capable of running all necessary
patch’s and updates
 The Operating system the group recommends for running is Linux family (i.e., Ubuntu
web server, Fedora web server and etc.). For the security reason Linux family is very
good.
 The group also recommends straining its staffs as much as possible.

References
[1]Mercer, E. (2014). Tips on Web-Based Customer Service. Mprints Publishing. 2014,

Inc. P.O. Box 1912, McKinney, TX 75070-1912 Retrieved January 11, 2015,
from http://smallbusiness.chron.com/tips-webbased-customer-service-
29689.Html
[2]Efraim Turban (2002), Electronic Commerce 2002: A Managerial Perspective
(2nd Edition). .). Boston, MA: McGraw-Hill/Irwin.
[3]Solomon Negash, Terry Ryan and Magid Igbaria (March 2002) Quality and effectiveness
in Web-based customer support systems. School of Information Science,

Claremont Graduate University, 130 E. Ninth Street, Claremont, CA 91711-6190,
USA
[4]Murphy, B. (2012). Top Customer Service Software Products. Platinum Paw Productions
c/o Zephery Hughes, 1337 Garrison, St. Loius, MO 63106 Retrieved December
26, 2014, from http://www.capterra.com/customer-service-software/

Appendix
Code Sample
LOGIN
<?php
session start ();
$host="localhost"; // Host name
$username="root"; // Mysql username
$password=""; // Mysql password
$db_name="dbwss"; // Database name
$tbl_name="employee"; // Table1 name
$tbl_name2="customer"; // Table2 name
// Connect to server and select databse.
$connect=mysql_connect("$host", "$username", "$password")or die("unable to connect
".mysql_error());
mysql_select_db("$db_name")or die("unable to find database ".mysql_error());
if(isset($_POST['send']))
{
// username and password sent from form
$username=$_POST['username'];
$password=$_POST['password']; //
******************************************************************************
********* md5
// To protect MySQL injection (more detail about MySQL injection)
$username = stripslashes($username);
$password = stripslashes($password);
$username = mysql_real_escape_string($username);
$password = mysql_real_escape_string($password);

$sql = "SELECT * FROM $tbl_name WHERE User_Name='$username' and
Password='$password' LIMIT 1";
$sql2 = "SELECT * FROM $tbl_name2 WHERE User_Name='$username' and
Password='$password' LIMIT 1";
$result = mysql_query($sql);
$result2 = mysql_query($sql2);
if(!$result && !$result2)
{
die("unable to process query ".mysql_error());
}
// Mysql_num_row is counting table row
$count = mysql_num_rows($result);
$count2 = mysql_num_rows($result2);
if($count == 1){
// Register $username, $password and redirect to file "workspace_success.php"
$_SESSION['username'] = $username;
$query=mysql_query("select * from employee where User_Name='$username'");
$row=mysql_fetch_assoc($query);
$id=$row['Employee_ID'];
$_SESSION['EmployeeID'] = $id;
$_SESSION['password'] = $password;
$result = mysql_fetch_array($result);
$Position = trim($result['Position']);
$_SESSION['Position'] = $Position;
if ($Position == '')
{
echo "No usertype value was set!";
}
else {
if($Position=='Bill Officer')
{

$_SESSION['User_Name']=$username;
$_SESSION['validuser']=$username;
echo'<script type="text/javascript">location.href="/customer/Admin/index.php";</script>';
exit;
}
else if($Position=='Accountant1')
{
//$_SESSION['buyerid']=$id;
echo'<script type="text/javascript">location.href="/customer/Admin/kebele1_8.php";</
script>';
exit;
}
else if($Position=='Technician')
{
echo'<script type="text/javascript">location.href="/customer/Admin/Technician.php";</
script>';
exit;
}
else if($Position=='Technician Mainten')
{
echo'<script
type="text/javascript">location.href="/customer/Admin/TechnicianMaintain.php";</script>';
exit;

}
else if($Position=='Meter Reader')
{
echo'<script
type="text/javascript">location.href="/customer/Admin/EmplMeterRead.php";</script>';
exit;
}
}
}
else if($count2==1)
{
$_SESSION['username'] = $username;
$query=mysql_query("select * from customer where User_Name='$username'");
$row=mysql_fetch_assoc($query);
$id=$row['Customer_ID'];
$_SESSION['CustomerID'] = $id;
$_SESSION['password'] = $password;
echo'<script type="text/javascript">location.href=" /customer/home.php";</script>';
exit;
}
else{
echo'<script type="text/javascript"> alert("Incorrect Username or Password!");

location.href="/customer/index.php"; </script>';
//header('Location: ' . 'index.php');
}
}

mysql_close($connect);
?>
Generate bill Report
<?php
include_once("dbwssoreportgenerate.php");
$prg = new phpReportGenerator();
$prg->width = "90%";
$prg->cellpad = "0";
$prg->cellspace = "0";
$prg->border = "1";
$prg->header color = "#465584";
$prg->header_textcolor="#FFFFFF";
$prg->body_alignment = "left";
$prg->body_color = "#D1DCEB";
$prg->body_textcolor = "#000000";
$prg->surrounded = '1';
mysql_connect("localhost","root","");
mysql_select_db("jcwss");
$res = mysql_query("select * from bills");
$prg->mysql_resource = $res;
$prg->generateReport();
?>
calculate bill value
<?php
if(isset($_POST['send'])){
$approve= $_POST['approve'] ;
$MeterEmplID= $_POST['MeterEmplID'] ;
$Employee_ID=$_SESSION['EmployeeID'];
$MeterCustID= $_POST['MeterCustID'] ;
$date= $_POST['readingDate'] ;
$Customer_Type=$_POST['Customer_Type'];

$Meter_Size=$_POST['Meter_Size'];
$Meter_Number=$_POST['Meter_Number'];
$previousRead=$_POST['previousRead'];
$MeterCurrentRead=$_POST['MeterCurrentRead'];
$consum=$MeterCurrentRead-$previousRead;
if($Customer_Type=='Commercial'){
$fixedcharge=3.0;
if($consum<=5)
{
$usage = $consum*5.0;
}
else if($consum >5 && $consum<=10)
{
$usage=(5*5.0) + (5.5*($consum-5));
}
else if($consum>10 && $consum<=15)
{
$usage=(5*5)+ (5.5 *5)+(6.0*($consum-10));
}
else if ($consum >15 && $consum<=25 )
{
$usage=(5*5.0) + (5 *5)+(6.0*5)+(6.5 *($consum-15));
}
}
else if($Customer_Type=='Govermental') {
$fixedcharge=3.0;
if($consum<=5)
{
}

{
$usage=(5*4) + (4.5*($consum-5));
}
{
$usage=(5*4)+ (4.5 *5)+(5.0*($consum-10));
}
{
$usage=(5*4) + (4.5 *5)+(5.0*5)+(5.5 *($consum-15));
}
}
else{
$fixedcharge=3.0;
if($consum<=5)
{
}
{
$usage=(5*3.75) + (4.0*($consum-5));
}
{
$usage=(5*3.75)+ (4.0 *5)+(4.50*($consum-10));
}
{
$usage=(5*3.75) + (4.0 *5)+(4.50*5)+(5.0 *($consum-15));
}
}

$Tax=3.0+$usage;
$total=$usage+$Tax;
require_once('database.php');
$sql="insertintoemployee_meter_reading_data
values('$MeterEmplID','$Employee_ID','$MeterCustID','$date','$Customer_Type','$Meter_Size','
$Meter_Number','$previousRead','$MeterCurrentRead','$consum','$fixedcharge','$usage','$Tax','
$total','$approve')";
$result=mysql_query($sql);
?>
<?php } ?>
Customer registration
<?php
if(isset($_POST['regist'])){
$customerid= $_POST['customerid'] ;
$firstname=$_POST['firstname'];
$lastname=$_POST['lastname'];
$gender=$_POST['select'];
$age=$_POST['age'];
$kebele=$_POST['kebele'];
$phonenumber=$_POST['phonenumber'];
$housenumber=$_POST['housenumber'];
$file=$_FILES['image']['tmp_name'];
$image= addslashes(file_get_contents($_FILES['image']['tmp_name']));
$image_name= addslashes($_FILES['image']['name']);
move_uploaded_file($_FILES["image"]["tmp_name"],"Admin/uploads/" .
$_FILES["image"]["name"]);
$location="uploads/" . $_FILES["image"]["name"];
$sql="insert into customer_request
values('$customerid','$firstname','$lastname','$gender','$age','$kebele','$phonenumber','$housenu
mber','$location')";

if(!$result)
die("unable to insert values".mysql_error());
echo "<h1>Successfully Regestered!!</h1>";
}
else {
?>
Maintenance Order
<?php
if(isset($_POST['Save'])){
$customerid= $_POST['mainCustID'] ;
$mainNumber=$_POST['mainNumber'];
$maintananceDate=$_POST['maintananceDate'];
$MaintenaceType=$_POST['MaintenaceType'];
$date = date('Y-m-d');
$sql="insert into maintenance
values('$mainNumber','$customerid','$maintananceDate','$MaintenaceType')";
if(!$result)
mysql_close($con);
}
else {
?>
Meter Read
<?php
if(isset($_POST['Save'])){
$MeterCustID= $_POST['MeterCustID'] ;
$MeterCurrentRead=$_POST['MeterCurrentRead'];
$readingID=$_POST['readingID'];

$metersize=$_POST['metersize'];
$meterNumber=$_POST['meterNumber'];
$con=mysql_connect("localhost","root","");
if(!$con)
die("unable to connect".mysql_error());
mysql_select_db("dbwss",$con);
$sql="insertinto customer_meter_Read
values('$readingID','$MeterCustID','$MeterCurrentRead','$metersize','$meterNumber')";
if(!$result)
mysql_close($con);
}
else {
echo"successfully inserted";
?>
connect to database
<?php
$con = mysql_connect("localhost","root","");
if (!$con)
{
die('Could not connect: ' . mysql_error());
}
mysql_select_db("dbwss",$con);
?>

Smart Water Billing System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Smart Water Billing System

Uploaded by

Copyright:

Available Formats

Smart Water Billing Page I

Name Id no. Sign.

1) Biniam Kidane___________________brt/0005/09 ------------

Smart Water Billing Page I

Smart Water Billing Page II

Smart Water Billing Page III

1.5.2. Specific Objective.........................................................................................................3

1.6. Cost Benefit Analysis............................................................................................................3

1.7.2 Economic Feasibility.......................................................................................................4

1.8. Scope of the Project.............................................................................................................4

1.13. Systems Analysis and Design Approach.............................................................................6

1.14.2. Hardware Requirement.................................................................................................8

1.15. Risks & Contingencies........................................................................................................8

2.6.2. Non- Functional Requirements...................................................................................12

3.1.2. Use Case Diagram.......................................................................................................14

3.1.3. Object Model...............................................................................................................15

3.2. Activity Diagrams...............................................................................................................17

4.2. Persistent Data Management............................................................................................24

Smart Water Billing Page V

5.2.2. Interface Documentation Guidelines...........................................................................27

5.3. Class Interfaces...................................................................................................................28

5.3.2. Bill Officer Class.........................................................................................................28

5.3.3. Technician Class..........................................................................................................28

5.3.4. Customer Class............................................................................................................28

6.1.2. Integration Testing......................................................................................................29

6.1.3. System Testing............................................................................................................29

Smart Water Billing Page VI

Figure 1. System Use case.............................................................................................................13

Smart Water Billing Page VII

Table 1 Team composition..............................................................................................................2

Smart Water Billing Page VIII

 DBMS: Database Management System

Smart Water Billing Page IX

Technological revolution brought great changes to mankind, access to information becomes

Smart Water Billing Page 1

For all governmental and non-governmental companies, web-based customer service is a

1.3. Problem Statement

Many organizations currently use a semi-automated system. As it is semi-automated, it has its

1.5.1. General Objective

Developing Smart water billing service management system.

1.5.2. Specific Objective

 Identify the problem of the existing system.

 Design a new proposed system to solve the existing problem.

 Design the proposed System using Uml diagram.

 Design a user Interface for the proposed system.

 Implementing the proposed system.

 Testing the proposed system using different testing mechanisms

1.6. Cost Benefit Analysis

 Reduced Stationary Cost

 Cost reduction of stationary

 Knowledge gain by project developer.

 Faster decision making on the team member.

1.7. Feasibility Analysis

1.7.1 Technical Feasibility

1.7.2 Economic Feasibility

1.8. Scope of the Project

 request maintenance order

Smart Water Billing Page 4

 receive meter value from meter readers

 calculate billing process

 Generate different reports (registration, payment, maintenance).

1.9. Limitation of the Project

1.10. Significance of the Project