INTEGRATED BILLING SYSTEM 2019

WACHEMO UNEVERSITY

COLLEGE OF ENGINEERING AND TECHNOLOGY

SCHOOL OF COMPUTING AND INFORMATICS

DEPARTMENT OF INFORMATION TECHNOLGY

INDUSTRIAL PROJECT ON:

INTEGRATED BILLING SYSTEM FOR HOSSANA TOWN

JUNE, 2019
WCU HOSANNA, ETHIOPIA
 INTEGRATED BILLING SYSTEM 2019

Advisor Name Mrs. Hadra S. Examiner Name Mrs.Sada A.

Signature ……………….. Signature ………………..

Project Title: Integrated Billing System for Hosanna Town

A Senior Project Report

Submitted to the department of information technology, College of Engineering and Technology,

Wachemo University in partial fulfillment for the requirement of the Degree of bachelor Science
in Information Technology.

Group member name Id Sign

1. Dawit Dake R/ET-1024/08 ………………………

2. Dawit Robel R/ET-1026/08 ……………………….
3. Fikadu Elias R/ET-1062/08 ……………………….
4. Yishak Asfaw R/ET-1347/08 ……………………….
5. Mihret Paulos R/ET-5137/07 ……………………….

Submission Date: 21/10/2011E.C

JUNE, 2019
WCU HOSANNA, ETHIOPIA
 INTEGRATED BILLING SYSTEM 2019

Acknowledgement
First of all, praise God, the almighty, merciful and passionate, for providing this oppor-
tunity granting the capability to proceed successfully. Next to that we would like to thank our
advisor Mrs. Hadra S. The success and final outcome of this project required a lot of guidance
and assistance from many people and the team extremely fortunate to have got this all along the
completion of the project. Whatever the team has done is only due to such guidance and assis-
tance and would not forget to thank them.

i
 INTEGRATED BILLING SYSTEM 2019
CONTENTS
PAGES
List of figures ................................................................................................................................ vi
Abstract ......................................................................................................................................... vii
Acronyms ..................................................................................................................................... viii
CHAPTER ONE ........................................................................................................................... 1
1. Introduction ........................................................................................................................... 1
1.1. Background ......................................................................................................................... 1
1.2. Statement of the Problem .................................................................................................. 2
1.3. Objective of the Project ..................................................................................................... 3
1.3.1 General Objective ....................................................................................................... 3
1.3.2 Specific Objectives ........................................................................................................ 3
1. 4. Methodology ..................................................................................................................... 3
1.4.1. Fact-finding Techniques.............................................................................................. 3
1.4.2. System Analysis and Design Techniques ................................................................... 4
1.4.3. Tools .............................................................................................................................. 4
1.5. Feasibility Analyses ............................................................................................................ 5
1.5.1. Technical Feasibility .................................................................................................... 5
1.5.2. Economic Feasibility.................................................................................................... 6
1.5.3. Schedule Feasibility ..................................................................................................... 6
1.6. Scope of the Project ............................................................................................................ 6
1.7. Significance of the Project ................................................................................................. 7
1.8. Target beneficiaries of the system..................................................................................... 7
1.9. Time Schedule ..................................................................................................................... 8
1.10. Work breakdown structure ........................................................................................... 10
1.11. Cost Breakdown ............................................................................................................. 11
CHAPTER TWO ........................................................................................................................ 12
2. Requirement Specification and Analysis ............................................................................. 12
2.1 Current System.................................................................................................................. 12
2.1.1 Overview of the Current System ............................................................................... 12
2.1.2 Major activities in the existing system ...................................................................... 13
ii
 INTEGRATED BILLING SYSTEM 2019
2.1.3 Players in the Current System ................................................................................... 14
2.1.4 Business Rule............................................................................................................... 14
2.1.5 Alternative Solutions .................................................................................................. 14
2.2 Proposed System ................................................................................................................ 15
2.2.1 Overview of Proposed System ................................................................................... 15
2.2.2 Requirement Analysis ................................................................................................ 15
2.10 Hardware and Software Requirements......................................................................... 19
2.10.1 Hardware Requirements .......................................................................................... 19
2.10.2 Software Requirements ............................................................................................ 19
CHAPTER THREE .................................................................................................................... 20
3. System Modeling .................................................................................................................... 20
3.1. Use case diagram .............................................................................................................. 20
3.1.1 Use case selection for the proposed system .............................................................. 20
3.2 Class diagram .................................................................................................................... 33
3.3 Sequence diagram ............................................................................................................. 34
3.4 Activity Diagram ............................................................................................................... 44
CHAPTER FOUR ....................................................................................................................... 52
4. System design ....................................................................................................................... 52
4.1. Detail Design goals ....................................................................................................... 52
4.3. New System Interface Design ...................................................................................... 53
4.4. Architecture Design...................................................................................................... 54
4.5. Database Design............................................................................................................ 54
4.5.1. ER diagram ................................................................................................................ 54
4.5.2. Normalization............................................................................................................. 56
4.5.3. Persistence modeling ................................................................................................. 59
4.6. State chart Modeling .................................................................................................... 60
4.7. Component Modeling................................................................................................... 62
4.8. Deployment Diagram ................................................................................................... 63
4.9 Access control and security .............................................................................................. 63
CHAPTER FIVE ........................................................................................................................ 65

iii
 INTEGRATED BILLING SYSTEM 2019
5. System Implementation and Testing.................................................................................. 65
5.1 Implementation.................................................................................................................. 65
5.2 Sample code and their screen image ................................................................................ 65
5.2.1 Home Page ................................................................................................................... 65
5.3 Test Approach ................................................................................................................... 68
5.3.1 Integration Testing ..................................................................................................... 69
5.3.2 Unity Testing ............................................................................................................... 69
CHAPTER SIX ........................................................................................................................... 71
6. Conclusion ............................................................................................................................ 71
6.2 Recommendation ............................................................................................................... 71
Reference .................................................................................................................................... 72

iv
 INTEGRATED BILLING SYSTEM 2019

List of Tables

Table no table name page no

TABLE 1: TIME SCHEDULE FOR PROJECT ............................................................................ 9
TABLE 2: WORK BREAK DOWN STRUCTURE .................................................................... 10
TABLE 3: COST ESTIMATION FOR HARDWARE ................................................................ 11
TABLE 4: COST ESTIMATION FOR SOFTWARE.................................................................. 11
TABLE 5: LOGIN USE CASE DESCRIPTION ......................................................................... 22
TABLE 6: CHANGE PASSWORD USE CASE DESCRIPTION .............................................. 23
TABLE 7: PREPARE BILL USE CASE DESCRIPTION .......................................................... 24
TABLE 8: PREPARE BILL USE CASE DESCRIPTION .......................................................... 25
TABLE 9: VIEW USAGE BILL USE CASE DESCRIPTION ................................................... 26
TABLE 10: GIVE FEEDBACK USE CASE DESCRIPTION .................................................... 27
TABLE 11: REQUEST BILL MAINTENANCE USE CASE DESCRIPTION.......................... 28
TABLE 12: VIEW BILL MAINTENANCE REQUEST USE CASE DESCRIPTION .............. 29
TABLE 13: PAY BILL USE CASE DESCRIPTION .................................................................. 30
TABLE 14: USE CASE DESCRIPTION FOR CUSTOMER SIGNUP ...................................... 31
TABLE 15: LOGOUT USE CASE DESCRIPTION ................................................................... 32
TABLE 16: USER ACCOUNT TABLE ...................................................................................... 55
TABLE 17: REPORT TABLE ..................................................................................................... 56
TABLE 18: BILL TABLE ............................................................................................................ 56
TABLE 19: 2NF FOR REPORT TABLE .................................................................................... 57
TABLE 20: 2NF FOR BILL TABLE ........................................................................................... 58
TABLE 21: ACCESS CONTROL AND SECURITY ................................................................. 63
TABLE 22: TEST CASE FOR LOGIN ....................................................................................... 69
TABLE 23: TEST CASE FOR CHANGE PASSWORD ............................................................ 70

v
 INTEGRATED BILLING SYSTEM 2019
List of figures
FIGURE 1: USE CASE DIAGRAM ............................................................................................ 21
FIGURE 2: CLASS DIAGRAM FOR THE PROPOSED SYSTEM........................................... 33
FIGURE 3: SEQUENCE DIAGRAM FOR LOGIN ................................................................... 34
FIGURE 4: SEQUENCE DIAGRAM FOR CHANGE PASSWORD ......................................... 35
FIGURE 5: SEQUENCE DIAGRAM FOR PREPARE BILL ..................................................... 36
FIGURE 6: SEQUENCE DIAGRAM FOR SET PENALTY ...................................................... 37
FIGURE 7: SEQUENCE DIAGRAM FOR GENERATE REPORT ........................................... 38
FIGURE 8: SEQUENCE DIAGRAM FOR VIEW USAGE BILL.............................................. 39
FIGURE 9: SEQUENCE DIAGRAM FOR GIVE FEEDBACK................................................. 40
FIGURE 10: SEQUENCE DIAGRAM FOR REQUEST BILL MAINTENANCE .................... 41
FIGURE 11: SEQUENCE DIAGRAM FOR VIEW BILL MAINTENANCE REQUESTS ...... 41
FIGURE 12: SEQUENCE DIAGRAM FOR PAY BILL USE CASE ........................................ 42
FIGURE 13: SEQUENCE DIAGRAM FOR SIGNUP USE CASE ............................................ 43
FIGURE 14: LOGIN ACTIVITY DIAGRAM............................................................................. 44
FIGURE 15: ACTIVITY DIAGRAM FOR PREPARE BILL ..................................................... 45
FIGURE 16: ACTIVITY DIAGRAM FOR SET PENALTY ...................................................... 46
FIGURE 17: ACTIVITY DIAGRAM FOR GENERATE REPORT ........................................... 47
FIGURE 18: ACTIVITY DIAGRAM FOR VIEW USAGE BILL.............................................. 48
FIGURE 19: ACTIVITY DIAGRAM FOR GIVE FEEDBACK................................................. 49
FIGURE 20: ACTIVITY DIAGRAM FOR REQUEST BILL MAINTENANCE ...................... 50
FIGURE 21: ACTIVITY DIAGRAM FOR CUSTOMER SIGNUP ........................................... 51
FIGURE 22: USER INTERFACE DESIGN ................................................................................ 53
FIGURE 23: PROPOSED SYSTEM ARCHITECTURE DESIGN............................................. 54
FIGURE 24: ER DIAGRAM ........................................................................................................ 55
FIGURE 25: PERSISTENCE DIAGRAM ................................................................................... 59
FIGURE 26: STATE CHART DIAGRAMS FOR LOGIN ......................................................... 60
FIGURE 27: STATE CHART DIAGRAMS FOR SIGNUP ....................................................... 61
FIGURE 28: COMPONENT DIAGRAM .................................................................................... 62
FIGURE 29: DEPLOYMENT DIAGRAM .................................................................................. 63
FIGURE 30: USER INTERFACE FOR WBIBS ......................................................................... 65

vi
 INTEGRATED BILLING SYSTEM 2019

Abstract
In this project, we propose a new model for integrated billing system for personal bills
such as water bills, telecom bills and electric bills. The proposed system consolidates all
bills for one user so the user will not need to track and pay the bills individually. Personal
users can save a lot of time and effort on paying bills every month and will less likely forget to
pay for the bills thus avoiding paying late payment fines. Billing organizations such as utility
companies, telecom companies and banks can benefit from this system by getting payments from
users in time and sending out less physical mails for bills, which can save a lot of costs as well
as save the resources. The proposed system can also provide functionalities for the users
to track and view their expenses back in time and in different aspects online from any-
where. Expense reports can also be generated for all bills monthly, which is a very useful tool
for users to know and plan their expenses.

vii
 INTEGRATED BILLING SYSTEM 2019

Acronyms

The project team did each activity with specified date Acronym
1. CD: Compact Disc
2. CPU: Central Processing Unit
3. CSS: Cascading Style Sheet
4. DB: Database
5. DVD: Digital Versatile Disc
6. GB: Giga Byte
7. HTML: Hypertext Markup Language
8. ID: Identification
9. SQL: Structural Query Language
10. OOSAD: Object Oriented System Analysis and Design
11. PHP: Hyper Text Preprocessor
12. RAM: Random Access Memory
13. PC: Personal Computer
14. UC: Use Case
15. XML: Extensible markup Language
16. BR: Business Rule
17. IE: Internet Explorer
18. DBMS: Database Management System

viii
 INTEGRATED BILLING SYSTEM 2019

CHAPTER ONE

1. Introduction
It is critical for any service provider organization to collect utility payments on time, control the
expenses of the billing management system and tracking the utility payments for the customers.
Integrated Billing System is a system for the payment of multiple service bills through one chan-
nel. This enables customers to get faster and more efficient services. Today’s competitive work
environment also requires organizations to serve customer with the best handling possible.

1.1. Background
Hosanna town is found 230 kilometers far from the capital city of Ethiopia. It is one of the towns
in SNNP having different culture and is center of tourism in the region and has its own admin-
istration structure to organize, control and manage the local communities. In hosanna town there
are governmental and nongovernmental organizations which facilitate the development of the
town and provide services to the community. The basic services of water, electric power and tel-
ecommunication are provided as utility by governmental organizations known respectively as
Hosanna town water supply and sewerage service office, Ethiopian electric utility Hosanna
branch and Ethiotelecom Hosanna branch. These utility providing organization’s offices are lo-
cated in different parts of the city and maintain their own separate business rules and billing sys-
tems.
The project team proposed an on-line/web-based Centralized Billing System which integrates
(centralizes) the three billing systems in to a single system that enables customers to view service
bills through a single channel. It will also serve as a reminder for making on-line payments obli-
gations and in case of delays, and to warn them about it, instantly, to make bill maintenance ser-
vice request or complains online. In generally, the integrated billing system is a governmental
organization that provides billing system service for Ethiotelecom, Electric Corporation and wa-
ter service institute. The organization is located at center of the Hosanna town. The organization
has smooth relation with the three organizations Ethiotelecom, Electric Corporation and water
service institute. The organization controlled by central administrator and managed by its own
manager. Currently the three organization information system process tasks in the form of docu-
ment based applications or traditional file systems.

1
 INTEGRATED BILLING SYSTEM 2019

1.2. Statement of the Problem

In recent time, Hosanna city utility billing systems for water, electricity and telecom is not cen-
tralized. As a result, customers must go to the three offices in order to make utility payments.

Main problems identified in the existing system are:

 Customers need to spend considerable effort and time as well as cover transportation cost
in order to make utility payments at each of the three offices.

 Absence of reminding customers for making payments obligations and in case of delays,
and to warn them the possible fines, and other payment inconveniences such as fixed
days and office hours. (i.e. Lack of online customer notification to application enquiry
such as billing schedule notification)

 The offices of the above service providers are located far apart from each other. Besides,
their monthly payment schedule differs one from another. This causes customers to suffer
from wastage of time and incur additional costs.

 Some customers do not pay bills on time. As a result more and more customers are being
fined; get their services interrupted temporarily, or even permanently (i.e. It is less user-
friendly).

 The manual billing systems entails that these organizations have to maintain records
manually, prepare bill report in a hard copy for each customer in the town which requires
a lot of money spent on paper.
 Problem of updating immediately when changes occurred on items.
 Customers also have to wait a long time before they can make payments, particularly, for
electricity and telecom bills. Bill payments won’t be possible until such utility usages are
sent from the organizations.
 The current system requires much man power.
 The existing system is very less secure.
 Difficulty in conducting consistent reports.
 Absence of designed data base for the system.

2
 INTEGRATED BILLING SYSTEM 2019

1.3. Objective of the Project

1.3.1 General Objective
The general purpose of this project is to develop Web based Integrated Billing System for Ho-
sanna town.

1.3.2 Specific Objectives

To achieve the above stated general objective, the following specific objectives are formulated.

 To collect relevant data and analyzing the collected data.

 To examine the existing processing system.
 To identify the major problems of the system.
 To Provide alternative solutions
 To select the best solution among the provided alternative solutions.
 To Develop and to implement the new billing system for Hosanna town.

1. 4. Methodology
In order to achieve the general objective and specific objective the following method will be
used:

1.4.1. Fact-finding Techniques

We gather information by:

Interview:

We interviewed some of the employees about their existing system functionality, their problems
and background.

 To develop a deeper understanding of the data resources used by the system.

 To know what the current level of system usage by the office.

Observation:

It is observed that present manual system has lot of functionalities which can overcome by pro-
posed system such as time, manpower, readiness of customer details etc.

3
 INTEGRATED BILLING SYSTEM 2019

Questionnaires:

The questionnaires contain predefined questions that helped us to gather important information
and give us some perspective from different angle. It distributed to customers, stakeholders and
Bill staff members and managers. This helped us to know more information about how much
they want the system and in which way did they want the system to be designed.

1.4.2. System Analysis and Design Techniques

In generally, Object-Oriented System Analysis and Design (OOSAD) approach used throughout
the project. We used OOSAD approach because of the following important features:

 Increase reusability
 Increased extensibility
 Improved quality
 Financial benefits
 Reduced maintenance cost

The model that we will use in our system development life cycle is the Iterative model. Because
we aimed to do the project with it .Whenever we want to add or expand the scope we can expand
as well if we cannot implement all the proposed scope by different reasons like shortage of time
we can minimize the scope.
The project team chooses this iterative data model because:

 Building and improving the product is step by step.

 Can get the reliable user feedback.
 Less time is spent on documenting and more time is given for designing.
 Can only create a high-level design of the application before we actually begin to build.

1.4.3. Tools
This can be divided into two phases system development tools (programming tools) and system
design and analysis tools (documentation tools)

1.4.3.1. System Design and Analysis Tools

We tried to make clear, consistent and easily understandable design as much as possible. The
designed application should fulfill the functional and non- functional requirement. This is done
by frequently testing the system during design stage. We tried to use all fundamental tools of

4
 INTEGRATED BILLING SYSTEM 2019
software design and development. The tools which we are used during development of this pro-
ject are listed as follows:

 Use case diagram

 Activity diagram
 Sequence diagram
 Class diagram

1.4.3.2. System Development Tools

In order to develop the new system, our team identifies programing languages, database man-
agement software, editors as tools to be used in the development process as well as software and
hardware tools.

This project used the following hardware tools:

Personal Computer: - used to develop the system.

Flash Disk: - used to store and secure data as backup.
CD/DVD: - used to store and secure data as backup.

This project used the following software tools:

 HTML/XML/CSS: -Client side coding- Used to create the client side interface.
 WAMP: - used to write HTML and PHP code
 IE 5.5/6.0/7.0, Mozilla Firefox 3.0.:- Browsers used to run code.
 Note Pad and Note pad++:-for editing and as reserve code to write this project.
 EDRAW Max: - used to design the diagram of the system or project.

1.5. Feasibility Analyses

To bring the successful completion of this project goals and objectives the feasibility issues listed
below has determined the project viability or the discipline of planning, organizing, and manag-
ing resources.

1.5.1. Technical Feasibility

The goal of technical feasibility is to understand the organization ability to construct the pro-
posed system. Our system is technically feasible. Because, integrated billing system of Hosanna

5
 INTEGRATED BILLING SYSTEM 2019
Town has its own computer printer and software such as SQL-server and PHP Designer that are
needed for the new system. Therefore based on the above different considerations the project is
feasible to be conducted using the new system and Billing System office of Hosanna town is
benefitted if the new system is adopted fully.

1.5.2. Economic Feasibility

Economic analysis is evaluating the effectiveness or success of proposed system determines ben-
efits and savings which are expected from proposed system and organization and compare them
with cost. If the benefits are more than the cost, then decision is made to design and implement
the system.
 Saving cost
 Saving time
Tangible benefits:-
 Reduce the amount of resource required in office.

 Reduce data redundancy storing in the database.

 Improve office efficiency, speed and flexibility.

Intangible benefit:-
 To get well organized information in short period of time

 To make quick decisions based on the organized information retrieved

 Better service to Customer

1.5.3. Schedule Feasibility

It implies effective time management for the system, and the project should finished within dead-
line. So the team decides to implement and configure the new system on time without any delay.

1.6. Scope of the Project

The area bound of our project focuses mainly on functional aspects of water billing, electric bill-
ing and telecom billing system for the office from adding customer to the system to collecting
revenue and particularly focuses on:

 Create new user Account

6
 INTEGRATED BILLING SYSTEM 2019
 Updating customer information

 View comment of customer

 Search customer information

 Delete user account

 Manage Bill information for each utility (water, electricity and telecom).

 Bill calculation
 Penalty calculation
 Generate reports of bill
 Pay money for bill
 Bill maintenance (for water and electricity)
 Check payment of customer

 Search Bill

1.7. Significance of the Project

After completion of this project, the system will give the following benefits for the hosanna
town:

 Reduce costs of paper or other resources for the bill preparation.

 Store data in reliable way.
 The data consistency is applicable.
 Reduce the amount of resources that are wasted.
 Keep users information safely.
 Easy to search and retrieve of the required users data or information i.e. it saves time.
 Give work satisfaction for employees and especially for customers using the utility ser-
vices.
 Increases accuracy and availability.

1.8. Target beneficiaries of the system

Successful implementation of the proposed system can benefit the following target:

7
 INTEGRATED BILLING SYSTEM 2019
Customers:

• Pay all the three utilities in a single channel which lets the customers not to waste of their
time while visiting the three different organizations

• Bill payment becomes easy, fast and efficient as well as anywhere and within the due
date.

• Reduces transportation costs by not traveling to the service providing offices.

The three utility organizations:

• Earn more money by providing a satisfying and sufficient service.

• Since the transactions will be undergone in a computerized manner, decreases the high
demand of man power.

Employee:

• Reduced effort and errors as they are more or less relieved from the tedious manual
works.
• Could let them to service customers within couple of minutes.

Developers of the project:

• In addition to being an academic exercise to fulfill the requirements of the program, this
project could increase our knowledge and real-world problem solving skills of problem
identification, analyze, design and develop solutions such as developing a website. This
project can also be a stepping stone in our future professional carriers.

1.9. Time Schedule

To accomplish our project over all activity in effectively , efficiently and within specific
time we use Gantt chart scheduling mechanism b/c Gantt chart are a visual view of task dis-
played against time. They represent critical information such as what task is assigned to what
duration of time and overlapping activity in a project .All in all Gantt chart are the perfect allies
for planning, scheduling, managing, coordinating and tracking specific task in a project.

8
 INTEGRATED BILLING SYSTEM 2019
Table 1: Time Schedule for project

Schedule
N Task Description
Nov Dec Jan Feb Mar Apr May Jun
o

1 Proposal Select area of study and know the sys-

tem well.
2 Requirements Gathering information and define the
Elicitation project plan and system requirement.
3 Object Oriented Represent the internal structure&
Analysis functionality of data flow and user
interface.

4 Object Oriented Identify, analyse and compare candi-

Design date solution.

5 Implementation The physical implementation for spe-

cific technical solution of the system

6 Testing It constructs the system according to

the system designer’s specification

7 Installation and The installation and delivery of the

Maintenance entire system into production

9
 INTEGRATED BILLING SYSTEM 2019
1.10. Work breakdown structure
It is a tool which helps to easily communicate the work and processes involved to execute the
project. The project team uses the work breakdown structure to develop the project schedule, re-
source requirements and costs.

Table 2: work break down structure

Web based integrated billing system for Hosanna town

Work Breakdown Structure

No. Task Member Duration

1 1.Data Collection All members Nov,2018

1.1 Understand project domain

1.2 methods and tools to be used

2 2.1.Requirement Analysis Dawit Robel Dec 1,2018-

and Fikadu Dec 30,2018
2.1.1functional requirements
Elias
2.1.2 non-functional requirements

3 System Design Dawit Dake Dec 1,2018-

Juan 17,2019

4 Implementation Dawit dake & Feb 1,2019-

Dawit Robel May 30,2019

5 Testing All member June 1,2019-

June 10,2019

10
 INTEGRATED BILLING SYSTEM 2019

1.11. Cost Breakdown

Costs we need during the development of this project includes are shown on the tables.

Table 3: cost estimation for hardware

Name Quantity Unit price in birr Total

No
1 price of flash disk (4GB) 1 150.00 150.00 birr

2 price of stationary paper 1.5 packet 100.00 150.00birr

3 Pen 2 5.00 10.00birr
5 Printing 150 papers 1.25 187.50birr

6 Mobile card 5 25 125birr

7 personal computers 1 12000 12000birr

Total estimate cost - - 1822.50birr

Table 4: cost estimation for software

Name Quantity Unit price in birr Total

No
1 Windows - Free Free

2 EDRAW Max - Free Free

3 WAMP - Free Free
4 Note pad++ - Free Free
5 Mozilla Firefox 3.0 - Free Free

6 PHP - Free Free

11
 INTEGRATED BILLING SYSTEM 2019

CHAPTER TWO

2. Requirement Specification and Analysis

2.1 Current System
2.1.1 Overview of the Current System
Based on our data gathering there is no integrated billing system for Hosanna city. Currently the
three utilities that are water, electricity and telephone billings are not integrated in one central-
ized place. And even there are no local billing system for electricity and telephone. Whenever
the bills are prepared and are ready, schedules of payment day is reveled and customers are left
to purchase the bills that they been recorded with.

Before the bills of the three utilities are passes though different paths.

Electricity billing

Ethiopian Electric Utility Hosanna branch has an overall manual system. The main task in this
office is to sell a bill that has been prepared at bill office. The work flow in this office is that,
first the meter readers read the meters and send the data using flash disks to bill officer in order
to be calculates and printed bills and then finally the printed bills are send to the organization and
customers are left to purchase their bills with in the specified payment day intervals. As a result
of this the current system is not satisfying for all participants of the system.

In the current electric billing system, whenever a customer pays a usage or energy bill in full:
the bill will be given as a receipt and the cashier will keep the stub. The bill contains total bal-
ance of electric usage and is given to the customer to accept the payment. If the customer identi-
fies an unusual amount on the bill, a form is filled from the offline center and sent to the district
office for investigation. After investigation, the corrected reading with the corrected bill amount
is sent to the centers in the form currently referred as ‘CORRECTION MADE ON BILLS
PRINTED WITH ERRORS’ after being corrected. The Miscellaneous cashier at the offline cen-
ter collects the new bill amount on the different receipt and a paid stamp is stamped on the re-
ceipt. The offline centers then fill the form currently referred as ‘RETURNED BILLS DUE TO
CORRECTION MADE ON BILLS PRINTED WITH ERRORS’ for confirmation, which is then
sent to the distinct office.

12
 INTEGRATED BILLING SYSTEM 2019
Water billing

Hosanna city water supply and sewerage service is currently using a semi-automated customer
management system. There is a client server system designed to generate the customer billing
system and meter reading is done with mobile phones. The system has employees like meter
reader, accountant, bill collector, bill Officer and technical supervisor to give service for their
customers. And all the tasks are carried out in a computerized manner but still they demanded a
technological advancement in order to show progression with the services they are providing and
sustain the customer satisfaction.

Telecom billing

Ethiotelecom Hosanna branch is a well-organized office. There are a lot of transactions under
gone. Even if the office afford an advanced technology based services there is no online billing
system designed and also customers are paying for their bills in person visiting the offices. As
the project team has observed the existing billing system of the three organizations, the team
concluded that it is essential to bring their services in one integrated system.

2.1.2 Major activities in the existing system

 Input: Input to the system is the form which is fulfilled by each user/costumer with re-
spect to the service whatever they want and distributed to the office that belongs to the
service they want. The process of filling information for all bill system (electric, tele-
communication and water bill system) in the existing system is the same. In generally,
this is information needed for a system.
 Process : The form that is filled by the costumer are collected and signed by the re-
spected office after creaking that all the necessary information is filled or not.
 Output: The output of the form is that after all the above process is completed each cos-
tumer will start using the service with respect to their request.

13
 INTEGRATED BILLING SYSTEM 2019
2.1.3 Players in the Current System
In the existing system there are numbers of actors each having their own responsibility:-

 Customers: are users of the system that has been registered and those that are consuming
either of water, electricity and telecom utility.
 Bill Staff/Employee: is a person who is responsible for things that are related to the bills.
He/she prepares bills, calculates penalty and manage the bills and generate bill reports.
 Manager: a special user of the system who can setup access right for other users.

2.1.4 Business Rule

. The main business rules or principles for existing systems are:

 Anyone who signs the bill form must be the member of the service.
 Each service provider (electric service, water service and telecommunication service) will
give service with their need.
 Costumers will pay money for what they use per month. And no payment difference for
the same service.
 Costumer should get the bill for what they are paying.
 Some gap is given for a costumer to pay within a given day. If they didn´t pay within a
given day they punished.
 They ask the previous month bill to pay for the next month.

2.1.5 Alternative Solutions

➢ The important thing is to make works easy.
➢ The proposed system processes all those services at one center place.
➢ Integrated billing system of the system must fulfill the requirement of giving effective
services in terms of speed, accuracy, response time, efficiency; reduce man power and
time, etc.
➢ The proposed system stores all the information about billing at one center place for all on
the database other than store separately.

14
 INTEGRATED BILLING SYSTEM 2019
2.2 Proposed System
2.2.1 Overview of Proposed System
During our observation and data gathering of the existing system the project team was able to see
that there are a lot of problems running in the current system. As a result of this the project team
members have discovered solutions in order to create a better working environment. The pro-
posed system will minimize the problems and weakness of existing system by providing inte-
grated billing system integrates the water, electricity and telecom billings through one channel.
Customers will be able to see and pay their utility usage bills online. This system let the three
organizations to perform their billing systems online. Customers won’t be inline rather it lets
them to accomplish their demanded tasks where ever they are and within the due date. With this
new system the organizations give efficient & time observance service for their customer.

2.2.2 Requirement Analysis

The project team has identified the functional and non-functional requirements as mentioned be-
low:

2.2.2.1 Functional Requirements

A functional requirement specifies what the proposed system should do. A requirement specifies
a function that a new system or component must be able to perform. For example, functional re-
quirement of our system is must assign customer bill account and make accessible for a user.

The main requirement that used to handle are observable tasks or processes that must be per-
formed by the system:

 The system must have a dynamic website that provides successful registration of custom-
ers which are under the business rule of the office
 Collecting the information of the costumer who is going access service for water, electric
and telecom. The user must enter the password so that access is given only to him to view
the detail.
 Customers will be able to see and pay their utility usage bills online.
 The system must calculate electric, water and telecom billing (bill calculation).
 The system should display customer usage bill for the customer whenever it is requested.
 Customers should be able to give feedbacks.

15
 INTEGRATED BILLING SYSTEM 2019
 Whenever bill maintenance requests are raised by customers, the system should allow bill
officers to maintain the bills if request is appropriate.
 The system should have a customer notification.
 The system should generate bill reports.

2.2.2.2 Non- Functional Requirements

This is the requirements that are not directly concerned with the specific services delivered by
our system to its users. It specifies how the new system should perform.

Some of the non-functional requirement of this project is listed below.

 Usability: by designing user friendly interface and training users to become familiar with
the system, it shall be highly usable.
 Availability: The system will be available most of the hours, within a day.
 Reusability: The data and record that are saved to the database and shall be reused if
needed.
 Security consideration: The system allows its user to perform their task only after login
process. The user should be accompanied with the legible account and password
otherwise they won’t be allowed. The authority to login to the system is only by the
correct ID and password.
 Good performance: The system will be capable of carrying huge amount of data with
one database.
 Fast response time: The system responses user request quickly to satisfy the user need.
 System Modification & Maintainability: The system can be maintained and modified
for future use because the scope can be enlarged.

 User interface and human factor

The new system will use windows type graphical user interface. This type of interface is easy to
use for very little additional training and common to most computer users. The system will ena-
ble the users to use the system. Generally it will include the necessary features for each user with
a user friendly and attractive interface

16
 INTEGRATED BILLING SYSTEM 2019
 Documentation
At the end of the project, every activity in the development process will be documented for fu-
ture reference. And to some extent these documentations are essential in order to made modifica-
tion to the system and add new features. There will also be a documentation of implementation
language for maintenance during system failure.

 Hardware considerations
The Software product to be developed won’t be technology and hardware specific it should run
on existing standard computers. The system will be portable that can be run on any type of com-
puter and it supports any type of browsers.

 Performance characteristics
Since the system is going to be accessed by different users with different needs, it should be ca-
pable of handling and processing their queries quickly. Besides the software, Hardware will also
be a great factor in the systems’ performance. Generally, the system should be able to handle
many users and it will be responsive.

 Error handling and extreme conditions

The system is expected to handle errors encountered during run time. Errors could rise from us-
ers and from the system. Errors that occurred from the wrong doing of users will be handled by
appropriate exception handling mechanisms. Generally, if an error occurs, the system will identi-
fy the error and notify the user so that he/she can take the appropriate corrections rather than
terminating the system.

 Quality issues
The system calculates the customer’s bill, so it should give accurate result; so should be reliable.

 System modifications
The System modification can be achieve easily because the system is going to be designed using
an object oriented approach. Whenever there is an additional feature or feature to be eliminated,
it can be modified based on change criteria by the developers or any trained person that knows
the code behind the system. For instance, the system is for only one specified customer category,
so whenever it is demanded to broaden and involve other customer categories, the bill calcula-

17
 INTEGRATED BILLING SYSTEM 2019
tions and tariffs also change. So, the system must be modified and add the required feature by the
appropriate officers or individual.

 Physical environment
The server must be put on a place that has high security room. And the client must put in the lo-
cal area it must connect with server.

 Security issues
Since everything in the office is financial, the system should be highly secured and every users
of the system should have their own privilege which in turn maximize the system security. The
system has login page it allow only the user who have privilege to access the system. Therefore
the system can’t be accessed by unauthorized user. Each system users can access the system
based on their access right. In order to strengthen the security of the system, base64 encryption
and decryption algorithms are used for confidential information.

 Resource issues
Server

The minimum hardware requirement for MySQL is-

 CPU: 32 bit or 64 bit

 Cores: AMD Dual-core processor C70
 Display resolution 1366x768(or lower is recommended)

Client

 There is no browser specification

18
 INTEGRATED BILLING SYSTEM 2019
2.10 Hardware and Software Requirements
2.10.1 Hardware Requirements

For the new system to be efficient there is a requirement for specific hardware and software.
 Memory: Recommendation: 256mb RAM and more
 Processing power:64 bit operating system and Intel(R) core™i3 CPU 550@3.20GHz
 Hard disk capacity: 38GB and more that keep the permanent data.
 Physical cables:-to transport files from our mobile phones to our PC.
 Printer: to have a hard copy for the data.
2.10.2 Software Requirements

The system needs to fulfill the following software:

 Operating system: Windows 8 operating system will be used for the system.

 Zapya: To transfer file from one pc to another.

 Database management software (DBMS): To implement the database easily, (MySQL)

 PHP myadmin: choose PHP scripting language which aims at providing the user with an
interface that is easy to learn and attractive.

19
 INTEGRATED BILLING SYSTEM 2019

CHAPTER THREE

3. System Modeling
3.1. Use case diagram
Use case model describes the interactions between the users and the system, and the required be-
havior of the system in satisfying these goals. A use-case model consists of a number of model
elements. The most important model elements are: use cases, actors and the connector between
them.

The actors of proposed system:

 Customers: are users of the system that has been registered and those that are consuming
either of water, electricity and telecom utility.
 Bill officer: is a person who is responsible for things that are related to the bills. He/she
prepares bills, calculates penalty and manage the bills and generate bill reports.
 System admin: is the administrator for the systems and its main function is to manage
the data base and manage accounts of users.

3.1.1 Use case selection for the proposed system

The following are the use cases that will include in web based integrated billing system.

 Login
 Manage account
 Feed Values
 prepare usage bill
 set penalty
 Generate report
 Manage bill
 View usage bill
 Request bill maintenance
 View bill maintenance request
 Give feed back
 View feed back
 Pay bill

20
 INTEGRATED BILLING SYSTEM 2019
 Log out
 Signup

Figure 1: use case diagram

21
 INTEGRATED BILLING SYSTEM 2019
3.1.3 Essential use case description for the proposed system

Table 5: Login use case description

Use case ID UC1

Use case Login

Participating actors Customers, administrator, bill officer.
Description This is a use case to let authenticated users to
access the system functionality.
Pre-condition The user must be already registered or the
user must have user name, password (user
account)
Basic course of action 1. The user selects the login menu
2. The system display the login page
3. The user enters his/her user name and
password
4. The user click on login button
5. The system cheeks the username or ID and
password entered.
6. The system forwards the user to his/her
page.
7. End of use case

Alternative actions Step 5.1, If the identification is not correct

the system display incorrect user type, user
name and password try again message and
the system display the login page. The sys-
tem give chance to try again.
Post condition The user is authorized to perform an action.
Or logged in to the system.

22
 INTEGRATED BILLING SYSTEM 2019
Table 6: Change password use case description

Use case ID UC4

Use case Change Password

Participating actor All system users

description This use case helps the user when it is necessary to change log-
in password.

Entry condition user login to the system

Flow of event 1. User selects change password menu.

2. The system display change password form.

3. User fills all the required information and hit the change but-
ton.

4. The system change the password and save the new password

5. The system acknowledges that password is changed success-

fully

6. end of use case

Alternative Flow of event Step 3.1 If user enters wrong the system display message in
order to correct wrong information.

Exit condition New password is saved

23
 INTEGRATED BILLING SYSTEM 2019
Table 7: Prepare bill use case description

Use case ID UC8

Use case Prepare usage bill

Participating actor Bill officer

description This is a use case for calculating the usage bill in order to let
customers pay their monthly utility usage bill.

pre-condition The bill officer should login to the system And should retrieve
the utilization value inserted.

Basic course of action 1. Bill Officer chooses the prepare bill menu

2. Selects the type of bill he is going to prepare.

3. Bill Officer search for customer and usage month.

4. The system display information of the customer and monthly

usage record.

5. Bill Officer fills other required additional information for the

bill.

6. click the calculate button

7. System calculates the monthly usage bill of the identified

customer.

8. The system displays a message “monthly usage bill for cus-

tomer is ready ”

9.End use case

Alternative course of ac- Step 4.1 If the customer whom the bill is preparing for is not

24
 INTEGRATED BILLING SYSTEM 2019
tion available in the database the system displays “customer account
not found” information.

Post condition Customer usage bill is prepared

Table 8: Prepare bill use case description

Use case ID UC9

Use case Set customer bill penalty

Participating actor Bill officer

description This is a use case for calculating the customer penalty because
of delay of customer bill payment.

pre-condition If customer does not pay for his/her monthly usage bill within
the specified payment day intervals. in order to calculate the
penalty, bill officer must be logged in to the system

Basic course of action 1. User selects the set penalty menu

2. Selects the type of the bill.

3. Extract for the bill that has not been paid.

4. The system displays information of the monthly usage bill

that has expired or not been paid.

5. System displays the monthly usage bill of the identified cus-

tomer and its additional calculated penalty.

6. The system displays a message “penalty has been set”

7. End use case

25
 INTEGRATED BILLING SYSTEM 2019

Alternative course of ac- Step 3.1 if there is no unpaid bill system displays “such file
tion does not exit”

Post condition Penalty is set to the customer usage bill

Table 9: View usage bill use case description

Use case ID UC11

Use case View usage bill

Participating actor Customer

description This is a use case for customers to view or see their monthly
utility usage bill

pre-condition Customer should log in to the system

Basic course of action 1. User selects monthly utility usage bill from the menu bar.

2. The system displays a drop down menu of bill types.

3. User selects the bill type.

4. User clicks view my monthly usage bill button.

5. The system displays the customer usage bill.

6. End of use case

Alternative course of ac- Step 5.1 If there is no bill prepared with that customer infor-
tion mation. The system displays a message “no bill for this cus-
tomer”

26
 INTEGRATED BILLING SYSTEM 2019
Post condition Customer utility usage bill is displayed

Table 10: Give feedback use case description

Use case ID UC12

Use case Give feed back

Participating actor Customer

description This is a use case for customers to give feedback about the
overall system

pre-condition Customer login to the system

Basic course of action 1. User selects the feedback menu.

2. The system display customer feedback form.

3. The user fills the feedback form.

4. User clicks the submit button.

5. The system saves and displays an acknowledgement success-

fully submitting comment.

6.End use case

Alternative course of ac- Step 5.1 .if the information filled on step 3 is not valid system
tion displays a massage” comment not successfully submitted”

Post condition Customer comment is submitted.

27
 INTEGRATED BILLING SYSTEM 2019
Table 11: Request Bill Maintenance Use case description

Use case ID UC13

Use case Request Bill maintenance

Participating actor Customer

description This is a use case for customers to request Bill maintenance

whenever there is un certainty and the customers have more or
less meter read values from his/her usage on bill.

pre-condition Customer login to the system.

Basic course of action 1. User selects the request maintenance menu.

2. The system display maintenance request form.

3. The user fills the form.

4. User clicks the submit button.

5. The system saves the maintenance requests

6. System displays a successful message.

7.End use case

Alternative course of ac- Step 6.1 If the information filled on step3 is not valid system
tion displays a massage” Maintenance request not successfully sent”

Post condition The bill maintenance request is sent.

28
 INTEGRATED BILLING SYSTEM 2019
Table 12: View Bill Maintenance Request Use case description

Use case ID UC14

Use case View Bill maintenance Request

Participating actor Bill Officer

description This is a use case for bill officer to view Bill maintenance re-
quests that has been sent by customers.

pre-condition Bill Officer login to the system.

Basic course of action 1. User selects the bill menu.

2. User selects the view maintenance request button.

3. The system displays the requests from the data base.

4. The user views the requests.

5.End use case

Alternative course of ac- Step 3.1 If there is no request the system displays a massage
tion “there is no Maintenance request”

Post condition Bill officer sends the bill maintenance request.

29
 INTEGRATED BILLING SYSTEM 2019
Table 13: Pay Bill use case description

Use case ID UC15

Use case Pay Bill

Participating actor Bill Officer

description This use case gives information about paying money for cus-
tomer usage.

pre-condition Customer must have account and also there must have enough
balance on his/her account to do payment.

Basic course of action 1. The customer select pay bill menu

2. The system displays the user to bank account page.
3. The customer will fill required information
4. The system checks whether the information filled
are correct or not
5. System displays the payment form that filled with
the required informations.
6. Customer selects pay button
7. System takes payment and reduces that much
amount from account.
8. The message “pay successfully” is also displayed.
9. End use case.
Alternative course of ac- Step5.1 If information is invalid System displays bank page.
tion

Post condition Customer pays money

30
 INTEGRATED BILLING SYSTEM 2019
Table 14: use case description for customer signup

Use case ID UC16

Use case Signup

Participating actor Customer

description This use case leads customer to register their own information
in order to get either three services.

pre-condition Customer must have either of three services to do register.

Basic course of action 1. The customer opens the system.

2. Customer select signup button.
3. The system displays the registration form to the
customer.
4. The customer fills required information on the form.
5. Customer hit the register button.
6. Customer information stored on database.
7. The message “register successfully” is also
displayed.
8. End use case.
Alternative course of ac- -
tion

Post condition Customer make register

31
 INTEGRATED BILLING SYSTEM 2019
Table 15: Logout use case description

Use case ID UC16

Use case Logout

Participating actor All system users

description After finishing their task each user must be logout of the system

pre-condition User login to the system

Basic course of action 1. User wants to logout.

2. User click logout button.
3. System logout the user.
4. End use case.
Alternative course of ac- -
tion

Post condition User Logged out

32
 INTEGRATED BILLING SYSTEM 2019
3.2 Class diagram
The class diagram describes the attributes and operations of a class and also the constraints im-
posed on the system. It represents the properties of entities, their operations and relationships.
Generally the project is including the following class in the class diagram the over view of the
class diagram is:-

Figure 2: Class Diagram for the proposed system

33
 INTEGRATED BILLING SYSTEM 2019
3.3 Sequence diagram
Sequence diagrams show the interaction between participating objects in a given use case.

In this diagram the project team has shown the interactions between objects in the sequential or-
der and defined event sequences that result in some desired outcome.

1. Sequence Diagram for Login Use case

Figure 3: Sequence Diagram for Login

All the system users open the system and the system display the login page. Then the system user
fill the login form fields and the system validate the users input, the user click the login button,
the login form creates the login form controller which allow to execute the users input from the
database, the systems database validate the users Identification and return the result to the login
controller. Login controller validates the result and displays their page to the user. Then the sys-
tem user work on their own page whatever they want to do.

34
 INTEGRATED BILLING SYSTEM 2019
2. Sequence diagram for change password

Figure 4: Sequence Diagram for Change Password

35
 INTEGRATED BILLING SYSTEM 2019
3. Sequence diagram for prepare bill

Figure 5: Sequence Diagram for Prepare Bill

This sequence diagram shows the steps how the bill officers follow to prepare customers month-
ly utility usage bills. To prepare bills the bill officers must login. The bill officer open the system
and fill the login form field , click login button, then the system display bill officers home page.
When the officer wants to prepare bill, the bill preparation page is activated and bill officer fills
the required information on their bill preparation form and click the submit button. The bill of-
ficer lets the system to save the bill. Finally bill for customers will be successfully prepared.

36
 INTEGRATED BILLING SYSTEM 2019
4. Sequence Diagram for set penalty

Figure 6: Sequence Diagram for Set Penalty

37
 INTEGRATED BILLING SYSTEM 2019
5. Sequence diagram for generate report

Figure 7: Sequence Diagram for Generate Report

38
 INTEGRATED BILLING SYSTEM 2019
6. Sequence diagram for view usage bill

Figure 8: Sequence Diagram for View usage Bill

39
 INTEGRATED BILLING SYSTEM 2019
7. Sequence diagram give feedback

Figure 9: Sequence diagram for Give Feedback

40
 INTEGRATED BILLING SYSTEM 2019
8. Sequence diagram for request bill maintenance

Figure 10: Sequence diagram for request bill maintenance

9. Sequence diagram for view bill maintenance request

Figure 11: Sequence diagram for View Bill maintenance requests

41
 INTEGRATED BILLING SYSTEM 2019
10. Sequence diagram for pay bill

Figure 12: sequence diagram for pay bill use case

42
 INTEGRATED BILLING SYSTEM 2019
11. Sequence diagram for signup use case

Figure 13: Sequence diagram for signup use case

43
 INTEGRATED BILLING SYSTEM 2019
3.4 Activity Diagram
Activity diagram is another important diagram in UML to describe dynamic aspects of the sys-
tem. Activity diagram is basically a flow chart to represent the flow from one activity to another
activity. The team member has tried to describe operations of the system using the following Ac-
tivity Diagrams.

1. Activity diagram for Users(System admin, Bill Officer, Customer ) login

Figure 14: Login Activity Diagram

44
 INTEGRATED BILLING SYSTEM 2019
2. Activity diagram for Bill Officer prepare bill

Figure 15: Activity diagram for Prepare Bill

45
 INTEGRATED BILLING SYSTEM 2019
3. Activity diagram for Bill officer to Set penalty

Figure 16: Activity diagram for set penalty

46
 INTEGRATED BILLING SYSTEM 2019
4. Activity diagram for Bill officer to Generate report

Figure 17: Activity diagram for Generate Report

47
 INTEGRATED BILLING SYSTEM 2019
5. Activity diagram for Customer to View usage bill

Figure 18: Activity diagram for View Usage bill

48
 INTEGRATED BILLING SYSTEM 2019
6. Activity diagram for Customer to Give feedback

Figure 19: Activity diagram for Give Feedback

49
 INTEGRATED BILLING SYSTEM 2019
7. Activity diagram for Customer to Request bill maintenance

Figure 20: Activity Diagram for Request Bill Maintenance

50
 INTEGRATED BILLING SYSTEM 2019
8. Activity diagram for Customer to Signup

Figure 21: Activity diagram for customer signup

51
 INTEGRATED BILLING SYSTEM 2019

CHAPTER FOUR

4. System design
It is a process of planning a new business system or replacing an existing system by defining
its components or modules to satisfy the specific requirements.

In this part of the project, all about application design is represented in an object oriented model
and technique diagrammatically. Such as user interface design, proposed system architecture,
component diagram and finally deployment diagram. This all diagram represent the requirement
and on what way to solve the requirement of the proposed system in detail.
System design results in the following products:
 List of design goals, describing the qualities of the system that developers should opti-
mize.

4.1. Detail Design goals

Design goals describe the qualities of the system that developers should optimize. The following
are the qualities that our system should focus on.

 Performance: The web based integrated billing system should respond fast with high
throughput, i.e. it should perform the tasks of system quickly.

 Error Handling and Extreme conditions: The system should be strong enough to handle
error conditions and continue with normal operations. If an error occurs, the system should
identify the error and alert to the user.

 Availability – The web based integrated billing system should be accessible from any com-
puter if the computer is connected with a server computer.

 Security: The web based integrated billing system should be secured, i.e., only allow au-
thorized users to access the system.

 Cost: The system should be developed with minimum cost possible

 Modifiability: The web based integrated billing system should be modifiable for further
modification and enhancement of the application.

52
 INTEGRATED BILLING SYSTEM 2019
4.3. New System Interface Design

Figure 22: User interface design

53
 INTEGRATED BILLING SYSTEM 2019

4.4. Architecture Design

The proposed system will be implemented in Client/Server architecture. The proposed system
will have three tier client-server software architectures.

Figure 23: Proposed system Architecture Design

4.5. Database Design

Database design is the process of producing a detailed data model of a database. The term da-
tabase design can be used to describe many different parts of the design of an overall database
system. Principally, and most correctly, it can be thought of as the logical design of the base data
structures used to store the data.

4.5.1. ER diagram
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is a component of data. In other words, ER diagrams illustrate the logi-
cal structure of databases.

54
 INTEGRATED BILLING SYSTEM 2019

Figure 24: ER diagram

With the help of the above entity relation diagram we construct the following table:-

Table 16: User account table

No Table name Attributes Data type Primary key

1. Useraccount Userid Int
First Name Varchar (20)
Last Name Varchar (20)
username Varchar (20) User Id
Password Varchar (20)
Phone Number Varchar (20
E-mail Varchar (20)

55
 INTEGRATED BILLING SYSTEM 2019
Table 17: report table

No Table name Attributes Data type Primary key Foreign key

1. report Repoid Int repoid
type Varchar (20)
date Date/time
Userid Int
fname Varchar(20) Userid
lname Varchar(20)

Table 18: bill table

No Table name Attributes Data type Primary key Foreign key

1. bill Billno Int Billno
consumption Int
date Date/time
totalbirr Int
Userid Int Userid
fname Varchar(20)
lname Varchar(20)

4.5.2. Normalization
Data normalization is a process in which data attributes within a data model are organized to
increase the cohesion of tables and to reduce the coupling between tables. The fundamental goal
is to ensure that data are stored in one and only one place. This is an important consideration for
application developers because it is incredibly difficult to store objects in a relational database if
a data attribute is stored in several places.

56
 INTEGRATED BILLING SYSTEM 2019

First Normal form (1)

First normal form (1NF): An entity type is in 1NF when it contains no repeating groups of data.

User id Fname Lastname Password username Phoneno Email

1024 Dawit Dake 123 dawit.dake 0987655654 dawitzada@gmal.com

A table listed the above is fulfill the rule of first normalization.

Second Normal form (2NF)

Second normal form (2NF): An entity type is in 2NF when it is in 1NF and when all of its non-
key attributes are fully dependent on its primary key.

Report
Report Type Date User id fname lname
id

Table 19: 2NF for report table

Report table Foreign key

Report Type Date User id
id

User table
User id fname lname

Bill table
Billno consumption Date totalbirr User id fname Lname

57
 INTEGRATED BILLING SYSTEM 2019
Table 20: 2NF for bill table

Bill table Foreign

key
Billno consumption date Totalbirr User id

User table
User id fname lname

58
 INTEGRATED BILLING SYSTEM 2019
4.5.3. Persistence modeling
Persistence models _also called data model or Entity relationship (ER) models, are used to com-
municate the design of a database, usually a relational database, to both users and other develop-
ers. Persistence are used the schema of database. The strength of persistence models is that data
entities are conceptually the same as the table of relation data base and that attributes are the
same as table columns.

Figure 25: persistence diagram

59
 INTEGRATED BILLING SYSTEM 2019

4.6. State chart Modeling

The group members used the state diagram to specify the sequencing / timing behavior of objects
in a class States, Events and Transitions.

Figure 26: State chart diagrams for login

60
 INTEGRATED BILLING SYSTEM 2019

State chart for Signup

Figure 27: State chart diagrams for signup

61
 INTEGRATED BILLING SYSTEM 2019

4.7. Component Modeling

In this part the project team members try to identify components of the system and design the
association between the specified components.

Figure 28: Component Diagram

62
 INTEGRATED BILLING SYSTEM 2019

4.8. Deployment Diagram

This diagram represents the deployment view of a system. So, the system component diagrams
and physical hardware’s used to deploy the application represented on this diagram.

Figure 29: Deployment diagram

4.9 Access control and security

The access control shows who can access which class in the system and we describe it by using
access control matrix.

Table 21: Access Control and Security

63
 INTEGRATED BILLING SYSTEM 2019

Class System Bill Officer Customer

admin
Login Login() Login() Login()
Create Ac- Create User - Create New
count Account() User Account
Update Ac- Update Ac- - -
count count()
Delete Ac- Delete Ac- - -
count count()
Change Change Change Change Pass-
Password Password() Password() word()
Feed value - Feed value -
Functionality

View feed- View feed- - -

back back()
Prepare Bill - Prepare Bill() -
Set penalty - Set Penalty() -
View Bill - View Bill -
Maintenance maintenance
request request()
Add news- Add news- - -
feed feed()
Pay bill - - Pay bill()

View Usage - - View Usage

bill Bill()
Request Bill - - Request Bill
Maintenance Maintenance()
Give Feed- - - Give Feed-
back back()
Signup - - Signup()

64
 INTEGRATED BILLING SYSTEM 2019

CHAPTER FIVE

5. System Implementation and Testing

5.1 Implementation
Implementation refers to the Coding of the all documents gathered starting from requirement
analysis to Design phase. So now the team is in a position of converting all documents gathered
and designed into the code so that the system will be implemented for the user to be used for the
purpose it developed. To implement it the user must have a server on which the system will be
hosted because this system can run on intranet site with connection available or on internet con-
nection.

5.2 Sample code and their screen image

5.2.1 Home Page
Home page:-This pace is found on the main of Hosanna billing system it contains some links
about us, contact us, signup and login page. The user view the page and he/she get login page
and can select it from the menu.

Figure 30: user interface for WBIBS

65
 INTEGRATED BILLING SYSTEM 2019
Steps to follow to use the interface:

1. Type Home Page URL in address bar of web browser

2. The page will be displayed because it is default page.

Code for home

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"

"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">

<head>

<title>Centralized billing system</title>

<meta name="description" content="unified utility billing system" />

<meta name="keywords" content="why we be inline when we can be online " />

<meta http-equiv="content-type" content="text/html; charset=utf-8" />

<div id="logo"style="width: 900px; height: 115px;">

<img height="115" src="images/billpay.png" width="100"/>

<img height="115" src="images/h22.PNG" width="790"/>

<div id="navigation">

<div align="left"><a href="index.php">HOME</a></div>

<div align="left"><a href="aboutus.php">ABOUT US</a></div>

<div align="left"><a href="contactus.php">CONTACT US</a></div>

<div align="left"><a href="signup.php">SIGNUP</a></div>

<div align="left"><a href="index1.php">LOGIN</a></div>

</div><!--close menubar-->

66
 INTEGRATED BILLING SYSTEM 2019
<div class="ws_images"style="width:890px;height:550px;"><ul>

<div class="show">

<li><img width="880" height="400" src="images/all.PNG" /></li>

</div><!--close main-->

<div id="footer">Copyright &copy; 2019 | www.IBS.com</div>

</body>

</html>

Login Page

This page found on the link of home page. The user must have user account or username and
password to login to the system.

67
 INTEGRATED BILLING SYSTEM 2019
Steps to follow to use the interface of login:

1. Click login page

2. Enter username and password.
3. Select the type of services provided by billing system.
4. Click login button to login to the system.
Signup Page
This page found on the link of home page. The user must click on link and user have going to
register his/her detail required informations to login to the system after successful registration.
Steps to follow for use the interface signup new users:

1. The customer select signup link.

2. Fill appropriate information of customer.
3. Click on the register user button.

5.3 Test Approach

The team members develop testing plan to describe how the unified utility billing system will be
tested to check whether this project satisfies the intended functionality without any bugs or errors

68
 INTEGRATED BILLING SYSTEM 2019
by using both black box and white box testing method. The hosanna integrated billing system
will be tested manually by the developers and users.

5.3.1 Integration Testing

In this level of testing we have examined how the different procedures work together to achieve
the goal of the sub system. The type of integration testing that we have followed is bottom up.
Since unified utility billing system is a web based application each and every access is depend on
hypertext transfer protocol (HTTP). So we integrate each component from single functionality
(individual interface) to the main function incrementally step by step through link tag by using
test driver.

 Patterned the interaction between separate functionality which performs the exact tasks.
 Estimate the functionality of subsystem after combination all separate functionality.
 Identify the independency of each subsystem with other subsystem.
5.3.2 Unity Testing
Verification (A set of operations that the software correctly implemented a particular function)
on the smallest element of the program i.e. the modules are tested alone in order to discover any
error in the code.

Test case
Here we have designed a test case for some of our interfaces.

Test case for login

Table 22: test case for login

Test Case #:1.1

Test case Name: Login
System: Login
Designed by: all members
Executed by: All user
Short Description: Test the login Accessibility or check Authorized person
Pre-conditions
The user has a valid User Name and Password. The user has accessed the page by entering the
correct User Name and Password.
Post condition
The user can access the main page.

69
 INTEGRATED BILLING SYSTEM 2019
Test Case for change password

Table 23: test case for change password

Test Case #:1.2

Test case Name: Change Password
System: Password
Designed: all members
Executed by: Admin, Employee
Short Description: Test the change current password

Pre-conditions
The user has a valid User Name and Password before.
The system displays the main page.
Post-conditions
The New password is store in database.

70
 INTEGRATED BILLING SYSTEM 2019

CHAPTER SIX
6. Conclusion
The system that we have developed has three phases; the first phase deals with the analysis phase
of the life cycle with the organization, and the next phase addresses the design phase and third
phase deals about the implementation. As the end of the first phase, we need to review what we
have planned at the beginning. We began our work by identifying the significance of the new
system for Hosanna town and customers. This concerned defining the system development
methodology, identifying process and resource, and setting the deliverable and scheduled for the
project. The flow of analysis helps the team to understand the major functional areas and pro-
cesses of the proposed system. Through this flow, we identified the weakness and strength of the
existing system by developing the proposed system. After that, we discovered system require-
ments. Through this phase, we identify functional and non-functional requirements of the new
system. Then we have undertaken a major phase in system development process: object oriented
Analysis. Here, we tried to model the new system we proposed using UML diagrams: Use case,
sequence, and activity and class diagrams. Also, we designed the new system user interface pro-
totype. As a result, the project team proposed the new system to solve the problem of existing
system such as time management, security and good customer services. And also the project
team developed their capacity during working this new system so that the existing system is en-
hanced by technology.

6.2 Recommendation
The system that the project team has develop is limited on only single category of customers
Therefore, we recommend the following features need to be included in any further revision and
extension attempt.

- Online queue management.

- For those visually impaired customers, voice recognizing features.

71
 INTEGRATED BILLING SYSTEM 2019

Reference
[1] 1.5. (n.d.). Retrieved 03, 20, 2018, from www.tutorialspoints.com

[2] administrator, w. (2004, 6 09). wachemo University, 1.4. (wachemo university) Retrieved 03
20, 2018, from wachemo University web site: wcu.edu.et

[3] Pree, W. (n.d.). Object oriented development.

[4] pressman, R. (n.d.). Software engneering (Vol. v).

[5] Web Finance, Inc.( Retrieved November 16, 2018). Feasibility study.[online].Available:
http://www.businessdictionary.com/definition/feasibility-study.html.

[6] http://cybarlab.com/ooad .Advantage of ooad [Online Available],[December 20, 2018].

[7]ActivityDiagram.[Online].Available:https://www.tutorialspoint.com/uml/pdf/uml_activity_dia
gram.pdf.

[8] Yaybe ICT solutions PLC ,”Consultancy Service For computerized Information systems de-
velopment ,water billing and customers management system for Hosanna water Supply and
Sewerage Services”., 9/1/2011.

72