Industrial Project of Billing System

WOLAITA SODO UNIVERSITY
COLLEGE: - NATURAL AND COMPUTATIONAL

SCIENCE
DEPARTMENT:-COMPUTER SCIENCE AND
INFORMATION TECNOLOGY
INDUSTRIAL PROJECT II
TITLE:-Billing System in Ethiopian Electric Power Corporation for

Wolaita District Office
Group Member ID No
Bereket Yoseph NSC/R/921/03
Betha Tafere NSC/R/925/03
Frezgi Arefayne NSC/R/943/03
Advisor:-Yibrah (BSc.)
Submitted to Department of Computer Science and Information Technology, College of Natural
and Computational Science, Wolaita Sodo University, in Partial fulfillment for Requirement of
the Degree of Bachelor Science in (Computer science and Information Technology)
Wolaita Sodo, Ethiopia

[Submission Date:-22/09/2006 E.C]
ACKNOWLEDGMENT
We have taken efforts in this project. However, it would not have been possible without the kind
support and help of many individuals. We would like to extend our sincere thanks to all of them.
We are highly indebted to our department teachers especially to our advisor (Yibrah Haile) for
their guidance and constant supervision as well as for providing necessary information regarding
the project.
Members of Group Three students!
I
Table of Contents
ACKNOWLEDGMENT .................................................................................................. I
CHAPTER ONE................................................................................................................ 1
1. Introduction ................................................................................................................... 1
1.1 Background.......................................................................................................... 1
1.2 Statement of the problem ........................................................................................... 2
1.3 Why this particular topic is chosen? .......................................................................... 3
1.4 Objective of the project ............................................................................................. 3
1.4.1 Objectives .......................................................................................................... 3
1.4.1.1 General objective................................................................................................. 3
1.4.1.2 Specific objectives ............................................................................................... 3
1.4.2 Scope of the project ............................................................................................ 4
1.4.3 Alternative Solutions .......................................................................................... 4
1.5 Methodology ............................................................................................................ 4
1.5.1 Development Environment and Programming tool ..................................................... 5
1.6. Feasibility of the project ........................................................................................... 6
1.6.1Economical feasibility ............................................................................................. 6
1.6.2Technical feasibility ................................................................................................ 7
1.6.3 Operational feasibility ............................................................................................ 7
1.7 Budget Outlay .......................................................................................................... 8
1.8 Project schedule ......................................................................................................... 8
CHAPTER TWO ............................................................................................................... 9
2.1 Introduction of Existing system .................................................................................. 9
2.2 Players in the Existing System ................................................................................... 9
2.3 Major Function in Existing system............................................................................ 10
2.4 Business rules ......................................................................................................... 10
2.5 Reports Generated .................................................................................................. 11
2.6 Forms and Other Documents of the Existing System .................................................. 11
2.6.1 Work flow of the Existing System ...................................................................... 15
2.7 Bottlenecks of the Existing system............................................................................ 16
2.7.1 Performance (response time) .............................................................................. 16
II
[EEPCO,WOLAITA DISTRICT OFFICE BILLING SYSTEM AND
January 28, 2014 PREPARATION]
2.7.2 Input and Out put .............................................................................................. 16

2.7.3 Security and control .......................................................................................... 16
2.7.4 Efficiency ........................................................................................................ 16
2.8 Practices to be preserved From the Existing System ................................................... 17
2.9 Proposed solution for the new system that addressed problem of the existing system ..... 17
2.10 Requirements of Proposed system ........................................................................... 17
2.10.1 Functional Requirements ................................................................................. 17
2.10.1.1 Non Functional Requirements ....................................................................... 20
CHAPTER THREE ...................................................................................................... 21
System Analysis ........................................................................................................... 21
3.1 Introduction............................................................................................................ 21
3.2.1 System Development Methodology .................................................................... 21
3.2.2 System Approach ............................................................................................. 22
3.2.3 Process Model .................................................................................................. 24
3.2.4 Requirement Gathering ..................................................................................... 24
3.2 Requirement Structuring ............................................................................................. 26
3.2.1 Use case diagram ................................................................................................. 27
3.2.2 Use case documentation (for each use case identified) .......................................... 28
3.2.3 Sequence diagram ............................................................................................. 31
3.2.4 Activity Diagram ..................................................................................................... 34
3.2.5 Analysis Level Class Diagram (Conceptual Diagram) .................................................. 37
3.2.6 User Interface ...................................................................................................... 38
CHAPTER FOUR ........................................................................................................ 39
System Design................................................................................................................. 39
4.1 Introduction............................................................................................................ 39
4.2 Class Type Architecture .......................................................................................... 39
Business/Domain Layer ................................................................................................ 40
Control/process Layer ................................................................................................... 40
4.3 Design Level Class Modeling .............................................................................. 42
4.4 State chart modeling .............................................................................................. 43
4.5 Collaboration Modeling ......................................................................................... 44
4.6 Component Model .................................................................................................. 47
4.7 Deployment Modeling ............................................................................................. 49
4.8 Persistence modeling ............................................................................................... 50
III
4.9 User Interface Design .............................................................................................. 52

CHAPTER FIVE ............................................................................................................ 58
Implementation and Testing .......................................................................................... 58
5.1 Introduction ...................................................................................................... 58
5.2. Implementation Codes ..................................................................................... 58
5.3. User Manual preparation ........................................................................................ 74
CHAPTER SIX ............................................................................................................... 83
Conclusion .................................................................................................................. 83
6.1. Conclusion .......................................................................................................... 83
Client organization ........................................................................................................... 84
APPENDEX ................................................................................................................ 85
Acronyms ................................................................................................................... 85
Abstract ..................................................................................................................... 86
References ................................................................................................................... 87
IV
V
CHAPTER ONE
1. Introduction
1.1 Background
The Ethiopian Electric Power Corporation is established during Hailselase regime in Wolaita
District. At that time Ethiopian Electric Power Corporation was known as “South Lights”,
Ethiopian Electric power Authority. There are many public and private organizations which has
the goal to support day to day life of the people around them. Telecommunication Corporation,
Hospitals and Electric Power Corporation are the major governmental organizations in Ethiopia.
All of these are aimed at giving services such as communication, electric power and health care
respectively to the community by the help of electric power.
The first customer of Ethiopian Electric Power Corporation in Wolaita District was Wolaita
Sodo town, wolaita’s suburb areas such as Areka, Bodit, Humbo, Bilate Military camp.
The Wolaita district Electric power corporation had been facing many challenges starting from
its establishment still now. These problems include:
 The distribution of power was less
 The delivery of power was limited to a few people who has authority and property
 Unbalanced power usage such as too high or too low power delivery
 Higher cost beyond the customers’ consumption and so on....
Today there is higher modernization; Ethiopian Electric Power Corporation gives many types of
importance to our community. Many governmental and private companies are dependent on the
power which is provided by Ethiopian Electric Power Corporation. “Life without electric power
is impossible.”
EEPCo requires an effective and accurate billing system to be able to assure their revenue and
provide reliable service to its customers. The billing process involves receiving billing records
from various networks, determining the billing rates associated with the billing records,
calculating the cost for each billing record, aggregating these records periodically to generate
invoices, sending invoices to the customer, and collecting payments received from the customer.
1
1.2 Statement of the problem

The Billing preparation has different activities which are held manually. We focus on this area
because we have realized that it is a complicated environment of the system to perform the tasks
manually. Our team understands that most manual system, particularly the Wolaita EPCo, has
many drawbacks. Such as
1. Time wastage: manual system is more time consuming than computer system.
2. Cost: every manual system needs more labor force than computer system
3. Security problem: It is very difficult to control and to give different privileges to
different customers and users in manual system.
4. Data redundancy: it is difficult to control all transactions and registration of record
books & customer’s information without redundancy.
5. Data accessing problem: since all data are processed on paper, it is hard to access the
data particularly when it is necessary.
Detailed problem of Bill preparation system, handled manually, has problems like:-
 Individual records have its own database, so the worker around the Bill preparation must
check these databases in order to achieve their goals.
 They use manual material like pen, pencil, paper, calculator, and ruler and soon to
prepare Bill account which is tedious and can contain Errors.
 They use manual system and sometimes support Microsoft office excel.
 Searching for customer information is too difficult which needs visiting through each
record manually.
 This manual database can be harmed by different factors and they can lose the record.
2
1.3 Why this particular topic is chosen?
In Wolaita District EPCo work manual documentation based file system. Different
arithmetic operations (calculations) are also performed manually. Generally, the project team has
chosen this topic because of the following reasons:
Billing system in manually is very complex starting from network elements that generate usage
to the billing system to usage collection, mediation, rating, and invoice or account. So based on
this problem we can prove that the manual system or tedious data handling way should be
change to computerized system.
1.4 Objective of the project

1.4.1 Objectives
1.4.1.1 General objective
To change the manual system which is reflected in preparing Billing system of the Wolaita
District Electric power corporation office into computerized System.
1.4.1.2 Specific objectives
Going deep into the general objectives of this project we come across the specific
objectives that should be met by the end of this project. These are:
 To have a well standard data to user and to the company for further usage
 To save resources i.e. like time in searching of the customer name from the database,
manual system materials pen,pencil,paper,Adding machine (calculator) and the worker
power
 To ease data modification i.e. adding, updating, editing and deleting of data in
calculation
 To avoid data redundancy and to keep the security of data
 To achieve minimal speed of preparing Bill
 To provide easy search methods and faster data retrieval
 To provide a way of having accurate penalty fee system
 To develop good application for district management system
 To create better working environment for the employees
3
1.4.2 Scope of the project

Scope: Scope of the system identifies the problem to be studied, analyzed, designed,
constructed and ultimately improved.
The project can cover the following activities:-
 This system is computerized in order to store data in well defined pattern
 To easily search and finding record for the customer from the database
 Modifying the data in the data base
 Displaying errors and warning in the time of inserting incorrect data.
 Generating Bill report
 Recording new customer
 Providing fast service for the user
 Calculating the monthly payment for the customer according to power consumption
Our project doesn’t do the following activities:-
 .Doesn’t support Amharic version
1.4.3 Alternative Solutions

There are some alternative solutions to make billing system at a better efficiency than its
current performance. These are:
 Web application
1.5 Methodology
The method in which enable us to capture information about requested system is called is
Methodology. Our team use different methodology to capture the data of Wolaita Sodo
District Electric power Corporation Organization system.
The Methodologies are:-
 Interviewing the Manager
 Asking the required data from Workers in the Bill System
 Observing the Billing system how to calculate the payment in documentation form.
 Referring the database they have and different books
Our Group chooses the above Methodology because of:-
 To have complete and the necessary information to develop the proposed system
In short form of methods to capture the information
4
 System analysis
o Document review
o Observation
o interview
 System design
o Microsoft Visio 2007
o Prototype processing model
o Structured approached
 Implementation
o Coding
o Database Design
1.5.1 Development Environment and Programming tool

This Development environment and programming tool contains hardware and software
which is used to develop the proposed system in proper ways. The hardware and
Software we use are discussed as follows:-
A. Hardware used:
 Desktop computer with
o 80GB Hard disk
o 256 MB RAM
o keyboard and mouse
 processor type and speed
o Intel Pentium 4HT processor
o 3.2 GHZ speed
 Secondary data storage devices
o 8 GB flash disk drive
 Output Devices
o Printer
B. Software used:
1. Windows 7 ® or XP operating system
2. MYSQL Server
5
3. Notepad
4. WAMP
C. Programming Languages
 HTML(Hyper Text Markup Language)
 Scripting languages such as Java
 PHP (Hyper Text processor)
1.6. Feasibility of the project

All projects are feasible given unlimited resources and infinite time. Project has as much as
possible developed within the time constraints. The feasibility factors of the projects are as
follows:
 Economical feasibility
 Technical feasibility
 Operational feasibility
 Schedule feasibility
1.6.1Economical feasibility: is process of identifying the financial benefits and associated

with development of the proposed system (project). This feasibility is the resource saving
ability specially cost-benefit analysis.
Determine project benefits:-All information can provide much importance to organization.
The project that we work on can change the manual system to computerized system, which
can reduce error occurrences, time consumption, intensive labor use and license of flexibility
of the organization.
Benefits that are gained from our project are:-
 Cost effectiveness-resource saving
 Error reduction-providing error checking mechanism
 Increasing flexibility-multiple activity with less power and time
 Increasing speed –in the time of searching records
 Improve management planning
 Giving brain-breaking to the worker
 Provide with the confidence to the manager of the company
6
 Reliability of the customer on the system

1.6.2Technical feasibility: is the process of evaluating the organization ability to construct a
proposed system.
The proposed new system is expected to be technically feasible as:
 The proposed new system is also technically feasible as the required hardware and other
resources are already available in the Wolaita District EPCo.
 The system is easily maintainable
 The proposed system can be easily used by non IT professionals
 The project team members have a good understanding on hardware, software, operating
environments to be used the new system.
1.6.3 Operational feasibility: to gain understanding of the degree to which our proposed
system will likely solve the business problems or the advantage of the opportunity outlined
in the system service request. Wolaita District EPCo bill preparation system solves the
problem around the worker as well as the problem around the customer
Beneficiaries of the project
 Customer:-save their time

o No payment above their usage of consumption
 Employer:-Save time
o Reduce load from worker
o Decrease Error created when calculating the Bill
 They can refer the database if there is mistake in payment
For our Group:-Initiate us to get knowledge how to develop system for the company for
filling our requirement in academic pattern.
7
1.7 Budget Outlay (cost)

Item Quantity Unit price(Birr) Total price(Birr)
Computer 2 17500 35,000
Printer 1 2800 2,800
External Hard disk 1 840 840
Flash disk 8GB 1 300 300
Compact Disc (CD) 6 25 150
Antivirus 500
Others - - 3000
Total 42,590
Table 1.1 Budget Outlay
8
1.8 Project schedule
Table 1.2 Project schedule
8
CHAPTER TWO
2.1 Introduction of Existing system

The EEPCo in wolaita District office has a manager, Different level employees, secretary and
others. However, the staff has no full access of computer facility. The main services of the
EEPCo in Wolaita District office are giving, receive, billing records from various networks,
determining the billing rates associated with the billing records, calculating the cost for each
billing record, aggregating these records periodically to generate invoices, sending invoices to
the customer, and collecting payments received from the customer in manually.
2.2 Players in the Existing System

Player or Actor refers to a person, organization, or external system that plays a role in one or
more interactions with the existing system. The major actors or players that are involved in the
existing system are the following:
 Customer: A person/ an organization that needs services from the EEPCo. The main player that
interact with the system in order to contract for supply of electricity
 Store Man : to put the all documents and other materials for example cables, the general
information of the customer with paper etc
 Advocate: Interacts with the system in processing the demands of customer. The main function
of the advancer is checking and register whether put in form by using contract form fill correctly
or not. Generally advancer is the bridge (an interface) between the customer and the system.
 Casher: Interact with the system in processing the demand of the customer during sale bill and
other deposit. Generally control the all finance.
 Technical: They able to check the materials and can be connect meters and break the electric
supply.
 Manager: An employee who manages and controls the activities of the whole organization.
 Bill collector (seller): sales the bill to the customer and collect the bills.
 Reader: read the bill in each customer in different networks.
9
2.3 Major Function in Existing system

Main function of Billing is collect data without network transactions, determine the appropriate
chargeable amounts, apply applicable discount, format the bill, and send the bill to the customer
form of paper.
 Activation (start): without Interacts with the network to enable new customers, and can’t
modify details for existing customers.
 Collection: Collects and standardizes details of customers ‘without network activity.
 Pricing: Individually prices non-network charges.
 Bill Generation: Periodically collects a customer's charges in the form of paper and prepares a
bill, applying discount based on the customer's collective volume, value or other criteria.
 Bill Distribution: Prepares the raw bill information into customer friendly formats that can be
sent on paper. The billing process involves receiving billing records from various area,
determining the billing rates associated with the billing records, calculating the cost for each
billing record, aggregating these records periodically to generate invoices, return back invoices
to the customer, and collecting payments received from the customer.
2.4 Business rules

Business rule is a rule in which the organization uses it to perform any activities or invoice.
Hence any account is expected to be valid with respect the rule. A rule often focus on access
control issue, may also business calculation, policy of the organization.
EEPCo business rules to put in common way first, the customers pay the first or the previous
month and continue the monthly consumption so, each customers pay for command day.
Otherwise must be penal. Any where the price of the calculation of the consumption within
invoice must be the same because EEPCo is governmental organization and the business rules
has help to the whole EEPCo branches.
Penalty rule of EEPCo billing system in wolaita:-
Before buy the bill report customers divided in to four groups this groups used to pay easily
without time consuming and used to employee easily control the customer so, this schedules
come out in payment month can be list the first group is must be pay in the first week and the
second group must be pay in the second week etc.
10
But in this schedule couldn’t buy the bill should be pay the payment up to 6 days by the same amount
(36.12birr) that means the penalty of one day the same as 6 days. But more than 6 days must be break
the bill and stop the service of electricity. Those problems can be solving the customer pay the
penalty 36.12 birr and buy the bill.
2.5 Reports Generated

These are reports generated for the Manager, this enables the manager to control and
supervise the monthly and annual activities of the EPCo.
Generally report generated done customer report how many members of EEPCo supply getting
monthly (timely) consumption, Technical report and bill report.
2.6 Forms and Other Documents of the Existing System

The following are forms and other documents used in the existing system
Contract for supply of Electricity: Date, Full Name, Address, Woreda, Keble, House No,
Signature, contract no , power approved ,application tariff ,purpose of electricity is to be
Supply, deposit birr, connector birr, total, receipt, customer sign and authority sign.
Fig: customer application paper
11
Fig: Contract form

Receipt voucher Form: received form, contract no, the sum of birr, coequal no cash birr,
purpose, casher’s sign, account title, account no, total birr.
12
Fig Receipt voucher

Meter connection and order:
Record the first month: date, reading id, reading (previous and current), account number,
property number.
Record the next month:-date, reading id, reading (previous and current), account number,
property number.
Fig: meter connection and order
13
fig: Application paper for power supply
14
Fig: Electricity Bill sale.
2.6.1 Work flow of the Existing System

The existing bill preparation system has the following.
15
2.7 Bottlenecks of the Existing system
2.7.1 Performance (response time)

 Time consuming when registered as a customer of the company.
 Time consuming to prepare a bill.
2.7.2 Input and Out put

 Lot of paperwork: Existing system requires lot of paper work and
Even a small transaction requires many papers fill.
 Problem in getting monthly (timely) Report about customer, consumption and bill.
 Gaining incorrect customer bill.
 After register the power supply problem.
 Duplication of data may occur.
2.7.3 Security and control

 Complexity to manage the customer.
 Data Inconsistency may appear.
 Manual operator control: Manual operator control is there and leads to a lot of chaos and errors.
 Loss of even a single paper led to difficult situation because all the papers are interrelated.
2.7.4 Efficiency
 Since the work is performed manually the efficiency of the working system is that much not
good.
 As the number of the customer increase the waiting time of the customer will be increased.
 The resource of the customer and company is being waste. [Time, Money, stationary materials
like Pen, Pencil, Papers etc...].
 Since the data is stored in redundant manner, the information generated also is redundant.
 Inability of sharing the data: Data cannot be shared in the existing system. This means that
no two persons can use the same data in existing system. Also the two groups in an
organization cannot interact with each other without the actual movement of data.
16
2.8 Practices to be preserved From the Existing System

In the existing system there are many practices and activities that help to perform the billing
preparation. All the activities are almost manual, done by human power. Even if we are going to
change the billing system in to computerized, there are many activities preserved in the new
system. Some of these are:
1. Any customer needs to visit the billing system, present the requirements and fill the forms based
on the kind of service he/she needs to be a customer of the EEPCo.
2. There are forms [vouchers] to be filled to get the corresponding services like use EEPCo.
2.9 Proposed solution for the new system that addressed problem of the existing system
When manually preparing the invoice, you have to take care a lot the below mentioned things.
 Your invoice template is attractive and neat.

 It looks professional, and error free.
 Your invoice should have full of description of that what your customer are been charged.
 Accurately keep the record of customer and rates.
 Just maintain the status of being paid or unpaid.
 It manages recurring billing cycles (subscriptions).
 Password protection for company’s files.
 It manages customers as well product database.
 It fully supports multiple users over a network.
2.10 Requirements of Proposed system
2.10.1 Functional Requirements

Functional requirements must be actionable, measurable, testable, related to identified
business needs or opportunities, and defined to a level of detail sufficient for system design.
Our team follows functional requirement analysis because a functional requirement defines a function
of a system or its component. A function is described as a set of inputs, the behavior, and outputs.
Functional requirements may be calculations, technical details, data manipulation and processing and
17
other specific functionality that show how a user case is to be fulfilled and supported.
1. Performance requirement
 Increase number of customer’s response time of the system serving the customers will be
increase.
 The productivity of the organization is effective
Registering the customer
 The system gathers the required information about the customer to be as member of the EEPCo.
2. Process requirement
Taking a reading
 Firstly check whether the customer registered or not.
 Putting data on the database if registered
Preparing bill
 Check whether the reading on the database.
 If ‘Yes’ calculate monthly bill.
3. Input related requirement
Administration and security
A. Administrator
o Control all activity and all user of the system
o Administrator insure that guaranty access to the table user of the system
B. Employee(Reader)
o The system works only to authorized access
o Allows the user to insert the reading preparing bill
4. Output related requirement
A. User (customer)
o Allowed to see only some report
o Searching records without modifying the existing record.
B. Searching
o Should provide searching for records.
o Advanced searching.
C. Report
o Timely report as wanted supported by the system.
18
5. Storage related requirement

o Restore previously information in database.
o The general information of the identity of the customer and the results of the billing system.
o Put the bill preparation on the database.
 Safety and Security issues are considered as well in our system, in such a way that it gives better
security to the data and information contained in it and safe mechanism to perform the tasks. And
is Stable as well.
1. Error handling
Shows error that has problems in inserting to the systems.
2. Easiness of the system
The system is very easy to use as software.
3. Security and access interface
o The system provides limit the access to the customer .Example searching, advanced searching
.Report and helping files granted to customer.
o The system has access control for each function
o Administrator can create Account, Changing password.
Generally, here we tried to analyze what capabilities the new system can:-
 Calculate the penalty.
 Generate the report.
Those are type of reports
 Report is used to display the list of the customers that are registered.
 Display the list of the meter that the customer used.
 Display the list of the paid user for the first month.
 Display the list of unpaid user for the first month.
 Display the next month paid customer list.
 Display the next month unpaid customer list.
 print the reports

 displays the current members and information
19
 add new members and information

 easily update and users information
 restore previously information
 be protected by password and different user privileges
 change the penalty rate
2.10.1.1 Non Functional Requirements

Other features, characteristics and constraints that will be satisfied in addition to the above
system functional requirement.
 Effectiveness (resulting performance in relation to effort): more effective when compared to the
manual approach, resulting in fast accomplishment of task with in some amount of time
[Performance / Response time].
 Efficiency (resource consumption for given load): consumes less resource like time, power
needed to perform the task.
Hardware Requirement
 Network interface card (NIC) for connecting computers
20
CHAPTER THREE
System Analysis
3.1 Introduction
We need to analyze how this system uses hardware, software and the people resources to convert
data resources, such as transaction data, into information products, such as Reports and
displays. Thus we should document how the information system activities of input, processing,
output, storage and control are accomplished.
The new system is able to provide a new user friendly interface and more attractive working
environment to the billing system and users. Generally, the new system used for:
 Recording new customers.
 Calculating daily, monthly and yearly penalty.
 Generating reports.
 High data security, user privileges and reliability.
 Organizing all the EEPCo wolaita distinct tasks in one working environment.
 Providing fast service for the user.
 Easy searching bill reports.
 Easy Updating user’s information.
3.2 system Requirements specification
3.2.1 System Development Methodology

The diagram below shows the phases, with the major activities carried out during each
one. The arrows show how each phase feeds into the next one. The outputs from one phase are
inputs to the next phase.
21
3.2.2 System Approach

The project team used the modern structured approach of system development life cycle (SDLC)
to develop the billing system like structured program.
The structured approached enable us to take in hand all the activities of analysis and design and also it
Ensured that the system is complete and coordinated. Structured programming breaks up a large program
into a hierarchy of modules that makes our billing system development easier to implement and maintain.
Some of the advantages of using a structured approach like this are:
 Concentration on the data in a system – a system built around a flexible data structure will be
easier to change and will have a longer lifetime.
 This approach uses tools such as diagrams and structured English this improves communication
between users and developers, which increases the chance of a system that satisfies user
requirements.
 Structured methods encourage thoroughness and cross-checking – this makes it easier to spot
errors and omissions in the analysis of the system.
 The focus is on business requirements rather than technical issues – technology is used to
support the business requirements, not used for its own sake.
 The approach includes production of documentation – this means that complete, consistent
documentation will have been developed with the system this makes future.
Maintenance/upgrades easier.In the process of developing the new system the team followed
some phases that the system development life cycle would be easier and more efficient.
The following figure shows the information system cycle
22
Defining the
problem
Determining the data

Existing System
requirement procedure
Change
Requirement
Analyzing the requirements s
Requirement
Analysis
Specifying the requirements
Design of physical and Specification
internal schemes for the Project
Implementation of conceptual Design

and external schemes
Integrate codes and test

Implementation
Program functionality (coding and
debugging)
Integration &
Testing
Installation Upgrading, or modifying the Maintenance & upgrade

Program
Development
Maintenance
Retirement
Fig: System Development Life cycle (SDLC)
23
3.2.3 Process Model

Our team chooses prototype process model for the following reasons:
 Prototypes can be easily changed.
 Early visibility of the prototype.
 Gives users an idea of what the final system looks like.
 Encourages active participation among users and producer.
 Cost effective.
 Increases system development speed.
3.2.4 Requirement Gathering

The team has followed coat sampling methodology to investigate the problems of the
current working system, due to the time constraint and other factors.
Our team gathers the requirements from. Our target is employees, staff of the billing system. The
team takes sample of 5 persons from each group.
 Questioning the concerned employees: we have under taken an interview to the employees
there and we have tried to examine the activities of the billing system orally.
General questions
 What is the way of registering customer?
 How to update members and detail in manual system?
 How to calculate daily, monthly and yearly penalty?
 In what way you count monthly read?
 Problem faced while working in manual system?
 Examining written documents and forms: the team has also collected some documents and
forms from the billing office that might be helpful to improve the current system.
 Joint Application Design (JAD): JAD is a technique that is used to speed up the process of
Requirements Analysis. We involve gathering together all the key people and, in one session,
attempting to identify what needs to be done.
 On job observation: we have observed the system functioning for one day.
So far we have used the above mentioned methodologies to study the system and the team will
use this methodology in the future whenever it is necessary.
24
3.2.5 Hardware and Software Requirements and Specification

Our team categorized the specification into two major categories. These are software and
hardware specification
A) Hardware specification
Storage devices like
 CD
 External hard disk 250GB
 Flash disks 8GB
Hardware requirements for the client computer
 1.80 GB of hard disk
 1 GB of RAM
 processors 3.4GHZ
 Printer hp laser jet 420
Hardware requirements for the server computer

 High storage capacity Hard disk
 2 GB of RAM size
 processor 4.0GHZ
 UTP cable cat5e
 RJ-45 connector
Software requirements
 Anti Virus
 MYSQL Server
 Notepad
 WAMP
 Edraw Max
 Operating systems
 For the client computers windows XP,7 operating system
 For the server computer server 2003 OS
25
3.2 Requirement Structuring

Data flow diagram
A data flow diagram is graphical representation that depicts the information flow and the transforms that
applied as data moves from input to output. It can be used to represent software at any level of abstraction.
In fact DFDs may be partitioned in to levels that represent increasing information flow and functional details.
DFDs are defined in levels with every level decreasing the level of abstraction as well as defining a greater
detail of the functional organs of the system.
A zero level DFD also known as context or fundamental system model represents the entire software
elements as a single bubble with input and output data entities.
Which are indicated as incoming and outgoing arrows, Data Flow Diagram help understanding the basic
flow of data from one process to another process. This 0 level DFD represents fundamental overview of the
billing system. We can see process modeling and involved in the requirement word.
Process model
Fig .Context level DFD
26
3.2.1 Use case diagram

Use case, sometimes called a business use case, is a simplified, abstract, generalized use case
that captures the intentions of a user in a technology and implementation independent manner.
An essential use case is a structured narrative, expressed in the language of the application
domain of users, comprising a simplified, generalized, abstract, technology free and
implementation independent description of one task or interaction. An essential use case is
complete, meaningful, and well designed from the point of view of users in some role or roles in
relation to a system and that embodies the purpose or intentions underlying the interaction.
Fig: use case diagram for Existing system
27
Fig: use case Diagram the proposed system
3.2.2 Use case documentation (for each use case identified)

Security login
Name: Login
Description: to enter the system
Actors: Customer, admin, employee
Precondition: must follow the steps
Main Flow
1. click login form
2. insert the correct information
28
3. click ok button can gain the main page

4. use case ends
Post-Condition: logout the form
Name: contract for supply electricity (registering a user)
Description: A new customer need to first register before performing any actions.
Actors: Customer, employee
Precondition: Legal Customer
Main Flow
1. The new customer first bring application paper to employee
2. The employee fills out the required information.
3. The System checks the form is correctly filled.
4. Registered the customer.
5. Use case ends.
Post Condition: A customer can be use the power supply.
Name: bill collection and bill sale
Description: bill collect and bill sale to the customer.
Actors: employee.
Main Flow
1. The sale bill online transaction.
2. The collect the reading.
3. Use case ends
Name: Bill preparation.
Description: Bill prepare by inserting the bill information.
Actor: Employee
Precondition: insert the bill information
Main Flow
1. The Employee Fill The required information of the bill.
2. The system checks that all the required information was correct.
3. The bill will be prepared.
4. Use case ends.
Post Condition: the bill prepare results store in database.
29
5. Name: Bill report.

Description: the last achievement of bill information of the customer.
Actors: employee.
Pre-condition: the employees or the customer must be used logon forms you can see the bill
report.
Main Flow
5. Click login for.
6. Insert the correct information.
7. Click ok button can gain the bill report.
8. Use case ends.
Post-Condition: Logout the form.
Name: Create account.
Description: give the identity (Account No) to each user.
Actors: administrator.
Pre-condition: the users must be use power supply or must register
Main Flow
1. Click sign in.
2. Insert the correct information ordering.
3. Click ok button can gain the account.
4. Use case ends.
Post-Condition: sign out the form
Name: Bill reading
Description: Bill read from different place.
Actors: employee.
Pre-condition: check the previous reading.
Main Flow
1. Go to the customer house.
2. Read the bill the first and the remaining month.
3. Record the bill in paper.
4. Go back the office.
5. Use case ends.
30
Post-Condition: give to bill collector.

Name: Bill sale.
Description: Bill report sells to the customer.
Actors: employee.
Pre-condition: check the amount of invoice within month.
Main Flow
1. Check the previous price.
2. Take the price from the customer.
3. Give the bill report to the customer.
4. Use case ends.
Post-Condition: The whole price collects and submitted to chaser.
3.2.3 Sequence diagram

Sequence diagrams are used to model the logic of usage scenarios. A usage scenario is exactly what its
name indicates the description of a potential way that your system is used. The logic of a usage scenario
may be part of a use case, perhaps an alternate course. It may also be one entire pass through a use case,
such as the logic described by the basic course of action or a portion of the basic course of action plus
one or more alternate scenarios. It may also be a pass through the logic contained in several use cases.
Fig sequence Diagram for login
31
Fig sequence Diagram for register
32
Fig: bill preparation
Fig: manage the system
33
Fig: Create account
3.2.4 Activity Diagram

Activity diagrams are used to document the logic of a single operation/method, a single use case, or the
flow of logic of a business process. It is a diagram that can be used to graphically depict the flow of a
business process, the steps of a use case, or the logic of an object behavior (method). It used to better
understand the use case logic in terms of the flow of steps and their sequencing
34
35
36
3.2.5 Analysis Level Class Diagram (Conceptual Diagram)

Class models are the main step of object-oriented analysis and design, and before the UML most
methodologies called they object models instead of class models.
Class models show the classes of the system, their inter-relationships (including inheritance,
aggregation, and association), and the operations and attributes of the classes.
Fig: class diagram
37
3.2.6 User Interface

Fig: interface prototype
38
CHAPTER FOUR
System Design
4.1 Introduction
Our project team design desktop and web based application system for billing system. We are
going to design our web based application with the help of Microsoft Access 2003 and web application.
The main reason that why we chose these applications are their reliability and best effectiveness for web
based application system.
The main goal of our web based application is to develop simple and easily understandable, flexible
and accessible billing system application for Wolaita district office. In addition to this we designed the
system to avoid and reduce errors that cause the loss of data on the existing system.
Another goal of our design is to develop/implement user friendly billing system with other system and to
make more secure our system has a user-login privilege to access the system.
4.2 Class Type Architecture
Fig: Class Type Architecture
39
Layer Description
Interface This layer wraps access to the logic of our system. For instance in our system the
User interface (UI) provides the customer and employee to access the system
easily. Whereas the system interface (SI) also provide to access to the external
system.
Domain
Business/Domain Layer
The following are the Business/Domain classes
1. Administrator
2. Account
3. Password
4. Customer
5. Employee
Process The process layer implements process logic that involves collaborating with
several domain classes or even other process classes.
For example, login Processes when the customers information is valid .In addition
to this, if the customer information is invalid the system notify the customer that
the result or the information is invalid.
Control/process Layer
The wolaita District office billing system has the following controllers:
1. Logins
2. Add customer information’s.
3. Edit customer information’s.
4. Register customers.
5. Update customer information’s.
6. Delete customer information’s.
7. View customer information’s.
40
Persistence Persistence layers encapsulate the capability to store, retrieve, and delete
objects/data permanently without revealing details of the underlying storage
technology in the system. Often implement between object schema and database
schema and there are various available to us. For instance, Our system uses
My SQL database.
System System classes provide operating-system-specific functionality for our
applications, isolating our software from the operating system by wrapping OS-
specific features, increasing the portability of your application.
This file is compatible with desktop and laptops.
Table: Class type architecture
41
4.3 Design Level Class Modeling

Class diagram are the basis of object oriented analysis and design. A class diagram shows the
classes of the system, their interrelationships (including, inheritance, aggregation and
association) and the operations and attributes of the classes. Class diagrams are used for wide
variety of purposes, including both conceptual/domain modeling and detailed design modeling.
Fig: class modeling
42
4.4 State chart modeling
Fig: state chart for customer registration process
43
Fig: state chart for customer login
4.5 Collaboration Modeling
Fig: collaboration for Login
44
Fig: collaboration for Registration
Fig: collaboration for Manage account
Fig: collaboration for create Account.
45
Fig: collaboration for bill preparation
Fig: collaboration for Bill Application
46
4.6 Component Model
Fig: component model for Administrator.
47
Fig: component model for Employee.
Fig: component Model for customer.
48
4.7 Deployment Modeling
Fig: Deployment model.
49
4.8 Persistence modeling
Fig. Persistence modeling
50
Fig: the relationship taken from Microsoft Access
51
4.9 User Interface Design
User interface design is iterative analysis technique in which user is actively involved in
identifying the user interface of the system. Helps to get the problem of memory or spaces and its
solution of system from the user.
User interface that we get information collected from user are shown below.
Fig: user interface of homepage
52
This interface is displayed when the user select setting from menu of the main form of to create
an account for the user.
The system are used to create an account has create, refresh, edit, delete, exit command buttons.
And also allowed to Administrative user.
Fig: user interface for manager Login
53
This interface displays when we open the program and allows the user to select first name, last
name, date, month, year, contract number, reading id, meter detail and usage type.. Then click on
Register button.
Fig: user interface for customer Registration Form.
54
This interface display when the bill prepares employee selects the ‘Bill’ from main form.
The prepare can insert previous and current reading then calculate then store the amount can be
calculated and the search bill list will display the calculated amount for the bill and purchased list
of bill.
Fig: user interface for bill calculation.
55
Fig: user interface for bill system.
56
This interface display when the bill report employee click view bill button then you can
see the bill amount and you can print on line.
Fig: user interface for bill report paper
57
CHAPTER FIVE
Implementation and Testing
5.1 Introduction
Electric Billing system and preparation refers to a variety of services that target bill preapare and
to save the time to the customer. Since the clients of billing system and preparation (EEPCo)
have to register the customer and store on database.
Wolaita sodo district EPCo is register the customer on line and read in manual bill then after
store the bill calculate the bill amount.
5.2. Implementation Codes
For Index Page
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type"
content="text/html; charset=utf-8"><title>Electric Billing System</title><link rel="stylesheet"
href="styles.css" type="text/css"><script type="text/javascript"
src="js/jquery.js"></script><script type="text/javascript" src="js/slider.js"></script><script
type="text/javascript" src="js/superfish.js"></script><script type="text/javascript"
src="js/custom.js"></script><!--
(www.spyka.net)
</head>
<ul id="menu">
<right>
<script LANGUAGE="JavaScript">
todayDate=new Date();
thisday=todayDate.getDay();
thismonth=todayDate.getMonth();
thisdate=todayDate.getDate();
thisyear=todayDate.getYear();
thisyear = thisyear % 100;
thisyear = ((thisyear < 50) ? (2000 + thisyear) : (1900 + thisyear));
if (((thisyear % 4 == 0)
&& !(thisyear % 100 == 0))
||(thisyear % 400 == 0)) monthdays[1]++;
startspaces=thisdate;
while (startspaces > 7) startspaces-=7;
58
startspaces = thisday - startspaces + 1;

if (startspaces < 0) startspaces+=7;
document.write("<table border=2 bgcolor=ddeeaa ");
document.write("bordercolor=black><font color=black>");
document.write("<tr><td colspan=7><center><strong>"
+ monthnames[thismonth] + " " + thisyear
+ "</strong></center></font></td></tr>");
document.write("<tr>");
document.write("<td align=center>Su</td>");
document.write("<td align=center>M</td>");
document.write("<td align=center>Tu</td>");
document.write("<td align=center>W</td>");
document.write("<td align=center>Th</td>");
document.write("<td align=center>F</td>");
document.write("<td align=center>Sa</td>");
document.write("</tr>");
for (s=0;s<startspaces;s++) {
document.write("<td> </td>");
}
count=1;
while (count <= monthdays[thismonth]) {
for (b = startspaces;b<7;b++) {
linktrue=false;
document.write("<td>");
for (c=0;c<linkdays.length;c++) {
if (linkdays[c] != null) {
if ((linkdays[c][0]==thismonth + 1) && (linkdays[c][1]==count)) {
document.write("<a href=\"" + linkdays[c][2] + "\">");
linktrue=true;
}
}
}
if (count==thisdate) {
document.write("<font color='FF0000'><strong>");
}
if (count <= monthdays[thismonth]) {
document.write(count);
}
else {
document.write(" ");
}
if (count==thisdate) {
document.write("</strong></font>");
}
if (linktrue)
59
document.write("</a>");
document.write("</td>");
count++;
}
document.write("</tr>");
startspaces=0;
}
document.write("</table></p>");
</script>
<script language="JavaScript" type="text/javascript">
// This array holds the "friendly" day names
var day_names = new Array(7)
day_names[0] = "Sunday"
day_names[1] = "Monday"
day_names[2] = "Tuesday"
day_names[3] = "Wednesday"
day_names[4] = "Thursday"
day_names[5] = "Friday"
day_names[6] = "Saturday"
// This array holds the "friendly" month names
var month_names = new Array(12)
month_names[0] = "January"
month_names[1] = "February"
month_names[2] = "March"
month_names[3] = "April"
month_names[4] = "May"
month_names[5] = "June"
month_names[6] = "July"
month_names[7] = "August"
month_names[8] = "September"
month_names[9] = "October"
month_names[10] = "November"
month_names[11] = "December"
// Get the current date
date_now = new Date()
// Figure out the friendly day name
day_value = date_now.getDay()
date_text = day_names[day_value]
// Figure out the friendly month name
month_value = date_now.getMonth()
date_text += " " + month_names[month_value]
// Add the day of the month
date_text += " " + date_now.getDate()
// Add the year
date_text += ", " + date_now.getFullYear()
60
// Get the minutes in the hour

minute_value = date_now.getMinutes()
if (minute_value < 10) {
minute_value = "0" + minute_value
}
// Get the hour value and use it to customize the greeting
hour_value = date_now.getHours()
</script>
</right>
<body>
<form name="where">
<select name="city" size="1" onchange="updateclock(this);">

<option value="" selected>Local time</option>
<option value="0">London GMT</option>
<option value="1">Rome</option>
<option value="7">Bangkok</option>
<option value="8">Hong Kong</option>
<option value="9">Tokyo</option>
<option value="10">Sydney</option>
<option value="-8">San Francisco</option>
<option value="-5">New York</option>
</select>
<script language="JavaScript">
if (document.all||document.getElementById)
document.write('<span id="worldclock" style="font:bold 25px Arial;"></span><br>')
zone=0;
isitlocal=true;
ampm='';
function updateclock(z){
zone=z.options[z.selectedIndex].value;
isitlocal=(z.options[0].selected)?true:false;
}
function WorldClock(){
now=new Date();
ofst=now.getTimezoneOffset()/60;
secs=now.getSeconds();
sec=-1.57+Math.PI*secs/30;
mins=now.getMinutes();
min=-1.57+Math.PI*mins/30;
hr=(isitlocal)?now.getHours():(now.getHours() + parseInt(ofst)) + parseInt(zone);
61
hrs=-1.575+Math.PI*hr/6+Math.PI*parseInt(now.getMinutes())/360;
if (hr < 0) hr+=24;
if (hr > 23) hr-=24;
ampm = (hr > 11)?"PM":"AM";
statusampm = ampm.toLowerCase();
hr2 = hr;
if (hr2 == 0) hr2=12;
(hr2 < 13)?hr2:hr2 %= 12;
if (hr2<10) hr2="0"+hr2
var finaltime=hr2+':'+((mins < 10)?"0"+mins:mins)+':'+((secs < 10)?"0"+secs:secs)+'

'+statusampm;
if (document.all)
worldclock.innerHTML=finaltime
else if (document.getElementById)
document.getElementById("worldclock").innerHTML=finaltime
else if (document.layers){
document.worldclockns.document.worldclockns2.document.write(finaltime)
document.worldclockns.document.worldclockns2.document.close()
}
setTimeout('WorldClock()',1000);
}
window.onload=WorldClock
</script>
</form>
<body>
<div id="container">
<div id="header">
<img src="images/bulb.gif" alt="Slide #1 image" width="120"height="110">

<blink><img src="images/log.jpg" alt="Slide #1 image" width="660"height="110">
<img src="images/flag3.gif" alt="Slide #1 image"height="110">
<div class="clear"></div>
</div>
<div id="nav">
<ul class="sf-menu dropdown"><li class="selected"><a
href="index.html"><i><h3>Home</h3></i></a></li>
<li><a href="About Us.html"><i><h3>About Us</h3></i></a>
<li><a class="has_submenu" href="#"><i><h3>Service</h3></i></a>

<ul><li><a class="has_submenu" href="#">Customer</a>
<ul><li><a href="#">New</a></li>
62
<ul><li><a href="checkup.html">Application</a></li>
<li><a href="register2.html">Registration</a></li></ul></li>
<li><a href="chser.php">Exist</a></li></ul></li>
</ul></li>
<li><a class="has_submenu" href="#"><i><h3>Admin</h3></i></a>
<ul><li><a href="managepass2.php">Create Account</a></li>
<li><a href="managepass2.php">Manage Account</a></li>
</ul></li>
<li><a href="comment.php"><i><h3>contact us</h3></i></a>
<li><a href="helpmenu.pdf"><i><h3>Help</h3></i></a>
<li><a class="has_submenu" href="#"><i><h3>Login</h3></i></a>
<ul><li><a href="billreadpass2.php"> Bill Reader</a></li>
<li><a href="storeinsertpass2.php"> Store Man</a></li>
<li><a href=" billprepar2.php"> Bill prepare</a></li>
</ul></li>
</ul></div>
<div id="slides-container">
<div id="slides">
<div>
<div class="slide-image"><img src="images/d1.jpg" alt="Slide #1 image"></div>
<div class="slide-text">
<h2>Customer Is King</h2>
<p>EEPCo wolaita District Office Respect Its Customers through with in Time, by
Honesty, Trustfullness, Customers the firest.....</p>
</div>
</div>
<div>
<div class="slide-image"><img src="images/d2.jpg" ></div>
<h2>EEPCo in Wolaita District Office</h2>
<p>In EEPCo Wolaita District Office The Organization Gives Contract Number With
its Public or Wireless phone To fullfill their their Application forms to get Electric Meter...</p>
</div>
</div>
63
<div>
<div class="slide-image"><img src="images/nn.jpg" alt="Slide #1 image"></div>
<h2>Have Customer with EEPCo!</h2>
<p>Ethiopian Electric Power Corporation Wolaita District Office Gives ample
Services to Its Customers like Industries,Small Bussiness
Organizations,Telecommunications,Universities,and Different Non Governmental Organizations
and Governmental Organizations,Banks, and Commertial campanies.</p>
</div>
</div>
<div>
<h2>Have fun with EEPCo!</h2>
<p>These slides can contain anything a webpage can! HTML, Javascript, images, flash
or whatever! They're completely easy to edit and add to as well, no need to bother editing or
even going anywhere near some confusing Javascript files.</p>
</div>
</div>
<div>
<p>These slides can contain anything a webpage can! HTML, Javascript, images, flash
or whatever! They're completely easy to edit and add to as well, no need to bother editing or
even going anywhere near some confusing Javascript files.</p>
</div>
</div>
<div>
<p>Ethiopian Electric Power Corporation Wolaita District Office Gives ample
Services to Its Customers like Industries,Small Bussiness
64
Organizations,Telecommunications,Universities,and Different Non Governmental Organizations

and Governmental Organizations,Banks, and Commertial campanies.</p>
</div>
</div>
<div>
<div class="slide-image slide-image-right"><img src="images/d3.jpg" alt="Slide #3
image"></div>
<h2>EEPCo</H2>
<p>Ethiopian Electric power corporation wolaita district office was Established in
late 1930</p>
</div>
</div>
</div>
<div class="controls"><span class="jFlowNext"><span>Next</span></span><span

class="jFlowPrev"><span>Prev</span></span></div>
<div id="myController" class="hidden"><span class="jFlowControl">Slide 1</span><span
class="jFlowControl">Slide 1</span><span class="jFlowControl">Slide 1</span></div>
</div>
<div id="body" class="has-slider">

<div id="content">
<div class="box">
<h4>About EEPCo wolaita District </h4>

<p>The Ethiopian Electric Power Corporation is established during Hailselase regime
in Wolaita District. At that time Ethiopian Electric Power Corporation was known as “South
Lights”, Ethiopian Electric power Authority. There are many public and private organizations
which has the goal to support day to day life of the people around them. Telecommunication
Corporation, Hospitals and Electric Power Corporation are the major governmental organizations
in Ethiopia. All of these are aimed at giving services such as communication, electric power and
health care respectively to the community by the help of electric power.</p>
<h4>Service</h4>
<li> Report is used to display the list of the customers that are registered.</li>
<li> Display the list of the meter that the customer used.</li>
<li>Display the list of the paid user for the first month.</li>
<li>Display the list of unpaid user for the first month.</li>
</div>
65
</div>
<h4><span><i>Business Rules</i></span></h4>
<p style="margin: 0;">Business rule is a rule in which the organization uses it to

perform any activities or invoice.
Hence any account is expected to be valid with respect the rule.
A rule often focus on access control issue, may also business calculation, policy of the
organization.
EEPCo business rules to put in common way first, the customers pay the first or the previous
month and continue the monthly
consumption so, each customers pay for command day. Otherwise must be penal.
</p>
</li>
</ul></li>
</ul></div>
<div id="footer">
<div class="footer-content">
<span class="sitename">www.eepcowolaitadistrict.com</span>
<p class="footer-links">
<a href="index.html">Home</a>
<a href="About Us.html">About Us</a>
<a href="comment.php">Contact Us</a>

<a href="helpmenu.pdf">Help</a>
<a href="#container" class="backtotop">Back to top</a>

</p>
<div class="clear"></div>
</div>
<div class="footer-bottom">
<p><center><font face="arial"><h2 align="center"><blink>Welcome To EEPCo Wolaita
District Site</blink></h2></font></p>
</div>
</div>
</div>
</body></html>
System registers the user and view, update, delete the user
66
<?php session_start();
if(!isset($_SESSION['id'])){
echo '<script>windows: location="index.php"</script>';
?>
<?php
$session=$_SESSION['id'];
include 'db.php';
$result = mysql_query("SELECT * FROM user where id= '$session'");
while($row = mysql_fetch_array($result))
{
$sessionname=$row['name'];
}
?>
<p style="color:#F00; font-size:12px;">Welcome <?php echo $sessionname;?></p>

<?php
if (isset($_POST['add']))
{
include 'db.php';
$id=$_POST['id'] ;
$lname= $_POST['lname'] ;
$fname=$_POST['fname'] ;
$mi=$_POST['mi'] ;
$address=$_POST['address'] ;
$contact=$_POST['contact'] ;
mysql_query("INSERT INTO owners (id,lname,fname,mi,address,contact)

VALUES ('$id','$lname','$fname','$mi','$address','$contact')");
echo '<script>alert("success")</script>';
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<link href="src/facebox.css" media="screen" rel="stylesheet" type="text/css" />
67
<script src="lib/jquery.js" type="text/javascript"></script>

<script src="src/facebox.js" type="text/javascript"></script>
<script type="text/javascript">
jQuery(document).ready(function($) {
$('a[rel*=facebox]').facebox({
loadingImage : 'src/loading.gif',
closeImage : 'src/closelabel.png'
})
})
</script>
<script src="js/application.js" type="text/javascript" charset="utf-8"></script>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Billing System</title>
<style type="text/css">
#wrapper{
width:900px;
margin:0 auto;
border:3px solid rgba(0,0,0,0);
-webkit-border-radius:5px;
-moz-border-radius:5px;
border-radius:5px;
-webkit-box-shadow:0 0 18px rgba(0,0,0,0.4);
-moz-box-shadow:0 0 18px rgba(0,0,0,0.4);
box-shadow:0 0 18px rgba(0,0,0,0.4);
margin-top:2%;
}
#header { width:900px; height:100px;}
table th {background:#999;}
#form {
width:400px;
float:left;
border-radius:5px;
margin-top:5%;
}
#ryt {
float:right;
68
border-radius:5px;
margin-top:5%;
}
#header ul li{
list-style:none;
float:left; margin-top:30px; margin-left:10px;}
</style>
</head>
<body>
<div id="wrapper">
<div id="header">
<ul>
<li><a href="billing.php">Home</a></li>
<li><a href="bill.php">Billing</a></li>
<li><a href="user.php">Users</a></li>
<li><a href="logout.php">logout</a></li>
</ul>
</div>
<h1 align="center">Electric Billing System</h1>

<div id="form">
<p><h1 align="center">Add Customer </h1></p>

<form method="post">
<table width="332" border="0">
<tr>
<td width="99"><input type="hidden" name="id" value="0" /></td>

</tr>
<tr>
<td>First Name:</td>
<td width="223"><input type="text" name="lname" /></td>
</tr>
<tr>
<td>Last Name:</td>
<td><input type="text" name="fname" /></td>
</tr>
<tr>
<td>Sex:</td>
69
<td><input type="text" name="mi" /></td>
</tr>
<tr>
<td>Address:</td>
<td><input type="text" name="address" /></td>
</tr>
<tr>
<td>Contact #:</td>
<td><input type="text" name="contact" /></td>
</tr>
<tr>
<td><input type="submit" name="add" value="ADD" /></td>

<td><input type="reset" value="CANCEL" /></td>
</tr>
</table>
</form>
</div>
<div id="ryt">
<h1 align="center">View</h1>
<?php
include 'db.php';
$result = mysql_query("SELECT * FROM owners");
echo "<table border='1' bgcolor='#fff'>

<tr>
<th>Id</th>
<th>Firstname</th>
<th>Lastname</th>
<th>Sex</th>
<th>Address</th>
<th>Contact</th>
<th>Action</th>
</tr>";
{
echo "<tr>";
echo "<td>" . $row['id'] . "</td>";
echo "<td>" . $row['fname'] . "</td>";
echo "<td>" . $row['lname'] . "</td>";
70
echo "<td>" . $row['mi'] . "</td>";

echo "<td>" . $row['address'] . "</td>";
echo "<td>" . $row['contact'] . "</td>";
echo "<td><a rel='facebox' href='edit.php?id=".$row['id']."'>Edit </a>| ";
echo "<a rel='facebox' href='del.php?id=".$row['id']."'>Del</td>";
echo "</tr>";
}
echo "</table>";
?>
</div>
</div>
</body>
</html>
<script src="js/jquery.js"></script>
<script type="text/javascript">
$(function() {
$(".delbutton").click(function(){
//Save the link in a variable called element

var element = $(this);
//Find the id of the link that was clicked

var del_id = element.attr("id");
//Built a url to send

var info = 'id=' + del_id;
if(confirm("Sure you want to delete this update? There is NO undo!"))
{
$.ajax({
type: "GET",
url: "delete.php",
data: info,
success: function(){
}
});
$(this).parents(".record").animate({ backgroundColor: "#fbc7c7" }, "fast")
.animate({ opacity: "hide" }, "slow");
71
return false;
});
});
</script>
View Payment
<?php session_start();
if(!isset($_SESSION['id'])){
echo '<script>windows: location="index.php"</script>';
}
?>
<?php
include 'db.php';
$id =$_REQUEST['id'];
$result = mysql_query("SELECT * FROM bill where id='$id'");
{
$prev=$row['prev'];
$owners_id=$row['owners_id'];
$pres=$row['pres'];
$price=$row['price'];
$totalcons=$pres - $prev;
$bill=$totalcons * $price;
$date=$row['date'];
}
?>
<?php
include 'db.php';
$result = mysql_query("SELECT * FROM owners WHERE id = '$owners_id'");

$test = mysql_fetch_array($result);
if (!$result)
{
die("Error: Data not found..");
}
$id=$test['id'] ;
$lname= $test['lname'] ;
$fname=$test['fname'] ;
$mi=$test['mi'] ;
$address=$test['address'] ;
72
$contact=$test['contact'] ;
?>
<style type="text/css">
#data { margin: 0 auto; width:600px; }
</style>
<div id="data">
<center>
<h1>Ethiopian Electric Power Corporation</h1>
<p> Electric Billing System in Wolaita District</p>
<p><strong>Soddo City</strong></p>
<p>Phone: 0465512030 </p>
</center>
<div id="context">
<p>Name: <?php echo $lname.' '.$fname.' '.$mi; ?>




             R
eading Id: 000<?php echo $id; ?>
<br /><br />
Address: <?php echo $address; ?>
<br /> <br />
Contact: <?php echo $contact; ?>
</p>
<center>Date: <?php echo $date; ?> </center>
<p>
Previous Reading : <?php echo
$prev;?>




Price: <?php echo $price; ?><br /><br />
Present Reading : <?php echo $pres; ?> <br /><br />
Consuption: <?php echo $totalcons;?>
<h1 align="center">Bill Amount:P <?php echo $bill; ?> </h1><br /><br />
<?php
$session=$_SESSION['id'];
include 'db.php';
$result = mysql_query("SELECT * FROM user where id= '$session'");
{
73
$sessionname=$row['name'];
}
?>
<p>Casher: <?php echo $sessionname;?></p>
</p>
<CENTER><form><input type="button" onclick="window.print()" value="Print page"
/></form><a href="bill.php">Back</a></CENTER>
</div>
</div>
5.3. User Manual Preparation
Ethiopian Electric power Corporation wolaita District Office is a Governmental organization that
gives Different service to give its customers in manual, online services like, billing, customer
reports and others.
To use our sites some Helps to our customers like: Registration, application, reports, contact
information, comment writing, create account, manage account, bill prepare, bill reader and store
man and other Employee services.
For new customers sending application use the following procedures:
Write URl://www.eepcowolaitadistrict.com then click on Help menu to get more information
about the services procedure…
74
75
Click on service New Application then insert full information
76
Then full valid information in available text boxes First Name, Last name, Date,Phone Number
like this format (0916…..) and Write message text boxes “Hello District Office I want Electric
Meter” then click on send Button after finishing all information click on back button.
After sending your information The District Office calls you and gives you Contract Number
in its office Telephone. Then you get Electric meter going to the District .After getting your
Contract Number you also fulfill Registration Forms again its Web site page.
Click on service New Registration then insert all

information
77
After fulfilling your entire information click on record button then click on back to Home button.
After one month you can the bill reader read consumption from customers Meter by using your
contract number and calculating monthly consumption by Bill prepare Employees. Then the data
will store on District Database you see your consumption by inserting your CONTRACT
NUMBER in available text boxes in the sites.
78
Click on Exist
Insert your First Name you see your all information like this First Name=betha then
search Boxes
79
This is for see your personal Information in Ethiopian Electric Power Corporation Wolaita
District system.
80
And see your consumption clicking on VIEW linkage inserting Your CONTRACT NUMBER
then click on view button you see your consumption and click on print page button then take it
to the District you pay money in manual form in District Finance.
81
Enjoy with our service.

www.eepcowolaitadistrict.com
© All Rights are Reserved. Designed By wolaita sodo University Department of Computer
Science and Information Technology Group Three Students. (2006 E.C)
82
CHAPTER SIX
Conclusion
6.1. Conclusion
So far we were intended in analyzing the existing system of the Ethiopian Electric Power
Corporation Wolaita District Office up to proposing our new system that solves the difficulties
related to the existing system. To say something on the existing system: it is running almost
manually, hence it is highly exposed to the manual related problems, like misplacement,
duplication and corruption/lost of files, high storage space requirement, unshared nature of files,
huge time consumption to manipulate and generally it degrades the effectiveness and efficiency
of the system as a whole.
By having this over the existing system our aim was to build a new system that have greater
functionality that enhance effectiveness and efficiency related parameters on the system. By
keeping in mind that the new system will [have greater usage on]/bring the existing system fully
functional.
To achieve our goal [to design new system] the project team has spent all of its time on the
project on performing the tasks individually and in group based on the schedule available. The
tasks to be accomplished by the team were project selection, initiation and planning,
Requirement gathering and requirement analysis and Designing new system. The project
involves a team that has three members: Betha Tafere, Bereket Yoseph, Frezer Arefayne.
The team has faced many challenges starting from the lab due to electric power loss, lack of
resources like PC even in lab, time, and in the organization some of the employees were not
interested to cooperate/to provide as relevant information as we need [i.e. they have threats on us
to provide the information we need with respect to security].
83
Client organization
Company Name: -Ethiopian Electric Power Corporation (EEPCo) in Wolaita Sodo District
Office
Nature of Business: - Billing System
Owner: - Government
Location: - Wolaita Sodo, Ethiopia
Address: -Tel 0465512111
P.o.Box: 126
Contact person details
Name: -Ato Demise Amona
Status:-BA
Position:-Manager
Tell no:-0912232465
E-mail:-demise@yahoo.com
Project Teams
Name:-Bereket Yoseph
Status:-4th year Information Technology student
Position: - System programmer and debugger
E-mail:- bereketWSU@gmail.com
Name: Frezer Arefayne
Status:- 4th year Information Technology student
Position: Project Manager
E-mail:- frezer@gmail.com
Name:-Betha Tafere
Status:-Fourth year Information Technology student
Position: - Project coordinator
E-mail:-maribandt@gmail.com
84
APPENDEX
Acronyms
1. PHP …………………………....Hypertext PreProssecer

2. WAMP………………………….Window Apache Mysql PHP
3. HTML……………………………Hypertext Markup Language
4. CSS……………………………...Cascading Style Sheet
5. EEPCo……………………… Ethiopian Electric Power Corporation
6. G.C……………………….Gregorian calendar
85
Abstract
This project was conducted in Ethiopian Electric Power Corporation Wolaita district Office. The
objective of this study is to automate the manual system of this department and develop system.
In data collection mechanism we use interview to know details about Wolaita District. We search
the problem of Billing System in manually. This project provides some solutions to handle the
problems that employees face because of using manual system. The major finding of this project
is to show the problem of working with manually. That means it is very difficult to work with
manual system.
86
References
http://www.technologyevaluation.com
http://facstaff.gpc.edu/~ebrown/pracguid.html
http://www.captureplanning.com/!hc_how_to_write_a_proposal.cfm
Gary B.Shelly, Harry J.Ronsenblatt _System Analysis and Design, 9th Edition - (Shelly Cash
man) _course Technology (2011) pdf
Kenneth E.Kendall, Julia E.Kendall _ System Analysis and Design, 8th Edition- practice Hall (2010).pdf
87
88

Industrial Project of 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

Industrial Project of Billing System

Uploaded by

Copyright:

Available Formats

WOLAITA SODO UNIVERSITY

COLLEGE: - NATURAL AND COMPUTATIONAL

TITLE:-Billing System in Ethiopian Electric Power Corporation for

Wolaita Sodo, Ethiopia

Members of Group Three students!

2.7.2 Input and Out put .............................................................................................. 16

4.9 User Interface Design .............................................................................................. 52

1.2 Statement of the problem

1.3 Why this particular topic is chosen?

1.4 Objective of the project

1.4.1.1 General objective

1.4.1.2 Specific objectives

1.4.2 Scope of the project

1.4.3 Alternative Solutions

1.5.1 Development Environment and Programming tool

1.6. Feasibility of the project

1.6.1Economical feasibility: is process of identifying the financial benefits and associated

 Reliability of the customer on the system

 Customer:-save their time

1.7 Budget Outlay (cost)

Table 1.1 Budget Outlay

1.8 Project schedule

Table 1.2 Project schedule

2.1 Introduction of Existing system

2.2 Players in the Existing System

2.3 Major Function in Existing system

2.4 Business rules

2.5 Reports Generated

2.6 Forms and Other Documents of the Existing System

Fig: Contract form

Fig Receipt voucher

Fig: meter connection and order

fig: Application paper for power supply

Fig: Electricity Bill sale.

2.6.1 Work flow of the Existing System

2.7 Bottlenecks of the Existing system

2.7.1 Performance (response time)

2.7.2 Input and Out put

2.7.3 Security and control

2.8 Practices to be preserved From the Existing System

 Your invoice template is attractive and neat.

2.10 Requirements of Proposed system

2.10.1 Functional Requirements

5. Storage related requirement

 print the reports

 add new members and information

2.10.1.1 Non Functional Requirements

3.2 system Requirements specification

3.2.1 System Development Methodology

3.2.2 System Approach

Determining the data

Design of physical and Specification

internal schemes for the Project

Implementation of conceptual Design

Integrate codes and test

Installation Upgrading, or modifying the Maintenance & upgrade

Fig: System Development Life cycle (SDLC)

3.2.3 Process Model

3.2.4 Requirement Gathering

3.2.5 Hardware and Software Requirements and Specification

Hardware requirements for the server computer

3.2 Requirement Structuring

Fig .Context level DFD