Billing

ystem
ARBA MINCH UNIVERSITY

ARBA MINCH INSTITUTE OF TECHNOLOGY
Centralized Billing System For Arbaminch Town

Group Members
1. TemesgenTamrie . RAMIT/1571/05
2. KassahunAlemayehu.RAMIT/1440/05
3. TemesgenAyana
RAMIT/1569/05
4. TigistAbere................. RAMIT/1582/05
5. SeblewongelMezigebu .RAMIT/1534/05
Advisor name: -Prince T.
Examiner name:-Tillie
A Senior Project
Submitted to Department of Computer Science and IT, Institute of Technology, ArbaMinch
University, in Partial fulfillment for the requirement of the Degree of Bachelor Science in
Computer Science.
ArbaMinch, Ethiopia
March 2016
Centralized billing system
Page 1
Abstract
In this project, we propose a new model for central 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 anywhere. Expense reports can also be generated for all bills monthly, which is a very
useful tool for users to know and plan their expenses.
Contents
Abstract......................................................................................................................... ii
Page 2
CHAPTER ONE.............................................................................................................. 1
1.1 Background of the Organization...................................................................................... 1
1.2 Background of the project.......................................................................................... 1
1.3 Team Composition................................................................................................... 2
Table 1 team composition............................................................................................................... 2

1.4 Tasks and Schedule................................................................................................... 2
Table 2 task and schedule...............................................................................................................2

1.5 Statement of the problem........................................................................................... 2
1.6 Objectives of the project............................................................................................ 3
1.6.1 General objectives.................................................................................................................3

1.6.2 Specific objectives.................................................................................................................. 3
1.7 Scope and significance of the project.............................................................................3
1.7.1 Scope of the project................................................................................................................3

1.7.2 Significant of the project....................................................................................................... 3
1.8. Feasibility Analysis.................................................................................................. 4
1.8.1 Technical Feasibility............................................................................................................. 4

1.8.2 Operational Feasibility.........................................................................................................4
1.8.3 Economic Feasibility.............................................................................................................4
Table 3 software cost.......................................................................................................................5
Table 4 hardware cost..................................................................................................................... 5
So the first year total cost can be calculated like this:-.............................................................. 5
Table 5 tangible benefits................................................................................................................. 5
Table 6 net cost benefit................................................................................................................... 5
1.8.4 Political Feasibility................................................................................................................ 5
1.9 Methodologies of the project....................................................................................... 5
1.9.1 Data source............................................................................................................................ 5

1.9.2 Fact-finding and analysis..................................................................................................... 6
1.9.3 Development Tools................................................................................................................6
Table 7 Development Tools............................................................................................................. 6
1.9.4 Testing procedures................................................................................................................. 7
1.10. Limitation of the project.......................................................................................... 7
Chapter Two................................................................................................................... 7
Page 3
Existing System............................................................................................................... 7
2.1 Introduction............................................................................................................ 7
2.2 Players in the existing system...................................................................................... 8
2.3 Major functions/activities in the existing system...............................................................8
2.4 Business rules......................................................................................................... 8
2.5 Report generated in the existing system..........................................................................8
2.6
Forms and other documents of the existing systems......................................................8
Figure 1 telecom service form........................................................................................................9

Figure 2 Water service form......................................................................................................... 10
Figure 3 Electric service form......................................................................................................10
2.7 Bottlenecks of the existing system.............................................................................. 10
2.7.1 Performance.........................................................................................................................11
2.7.2 Input..................................................................................................................................... 11
2.7.3 Security and Controls...........................................................................................................11
2.7.4 Efficiency..............................................................................................................................11
2.8 Practices to be preserved.......................................................................................... 11
2.9 Proposed solution................................................................................................... 11
2.10 Requirements of the Proposed System........................................................................12
2.10.1
Functional requirements.............................................................................................. 12
2.10.2 Nonfunctional requirements............................................................................................. 13

Chapter Three............................................................................................................... 14
System Analysis............................................................................................................ 14
3.1 Introduction.......................................................................................................... 14
3.2 System Requirement Specifications............................................................................14
3.2.1 Actor Identification..............................................................................................................14

3.2.2 Use Case Identification........................................................................................................14
3.2.3 Use Case Diagram............................................................................................................... 14
Page 4
....................................................................................................................................................... 15
Figure 4 use case diagram for centralized billing system........................................................... 15
3.2.4 Use case documentation...................................................................................................... 16
Table 8 login table........................................................................................................................16
Table 9 create account................................................................................................................. 17
Table 10 update account..............................................................................................................18
Table11 delete account.................................................................................................................19
Page 5
Table 12 registration....................................................................................................................20
Table 13 check payment.............................................................................................................. 21
Table 14 generate report............................................................................................................. 22
Table 15 prepare bill....................................................................................................................23
Table 16 pay money..................................................................................................................... 24
Table 17 view report.................................................................................................................... 25
3.2.5 Sequence diagram...............................................................................................................26
Figure 5 sequence diagram for login..........................................................................................26
Figure 6 sequence diagram for create account..........................................................................27
Figure 7 sequence diagram for update account........................................................................ 27
Figure 8 sequence diagram for delete account..........................................................................28
Figure 9 sequence diagram for register customer.....................................................................29
Figure 10 sequence diagram for check payment.......................................................................29
Figure 11 sequence diagram prepare bill...................................................................................30
Figure 12 sequence diagram for generate report......................................................................30
Figure 13 sequence diagram for pay money..............................................................................31
Figure 14 sequence diagram for create own account............................................................... 31
Figure 15 sequence diagram for update own account..............................................................31
Figure 16 sequence diagram for view report.............................................................................32
3.2.5 Activity Diagram.................................................................................................................32
Figure 17 activity diagram for login.......................................................................................... 32
Figure 18 activity diagram for create account.......................................................................... 33
Figure 19 activity diagram for update account.........................................................................33
Figure 20 activity diagram for delete account...........................................................................34
Figure 21 activity diagram for generate report........................................................................ 34
Figure 22 activity diagram register customer........................................................................... 35
Figure 23 activity diagram for prepare bill...............................................................................35
Figure 24 activity diagram for view report............................................................................... 36
Figure 25 activity diagram for view report............................................................................... 36
3.2.6 Analysis level class diagram...............................................................................................37
Figure 26 analysis level of class diagram...................................................................................37
Page 6
3.2.6 User Interface Prototyping................................................................................................ 38

Figure 27 user interface prototype............................................................................................. 38
Chapter Four................................................................................................................ 39
System Design.............................................................................................................. 39
4.1
Introduction.................................................................................................... 39
4.2 Class type architecture............................................................................................. 39
4.2.1 User interface layer.............................................................................................................40

4.2.2 Controller/process layer..................................................................................................... 41
4.2.3 Business/Domain layer....................................................................................................... 41
4.2.4 Persistence layer..................................................................................................................41
4.2.5 System layer........................................................................................................................ 41
4.3 Class modeling...................................................................................................... 42
4.4 State chart modeling............................................................................................... 43
4.5 Collaboration Modeling........................................................................................... 46
4.6 Component Modeling.............................................................................................. 47
4.7 Deployment modeling............................................................................................. 48
4.8 Persistence modeling.............................................................................................. 49
4.9 User Interface design.............................................................................................. 50
Chapter Five................................................................................................................. 53
Implementation and Testing.............................................................................................. 53
Introduction.................................................................................................................. 53
5.1 Finale testing of the system....................................................................................... 53
Short Description: Give information about whether the customer have paid the required money or not..55
5.3 Hardware and Software Acquisitions...........................................................................56
5.4 User Manual Preparation.......................................................................................... 57
5.5 Training............................................................................................................... 57
5.6 Installation Process................................................................................................. 57
5.7 Start-up strategy.................................................................................................... 57
5 .9 Coding............................................................................................................... 57
CHAPTER SIX............................................................................................................. 69
CONCLUSION and RECOMMENDATION.........................................................................69
6.1 Conclusion........................................................................................................... 69
Page 7
6.2 Recommendations.................................................................................................. 70
Reference................................................................................................................. 71
Webliography............................................................................................................ 71
List of Tables
Table 1 team composition
Table 2 task and schedule
Table 3 software cost
Table 4 hardware cost
Table 5 tangible benefits
Table 6 net cost benefit
Table 7 Development Tools
Table 8 login table
Table 9 create account
Table 10 update account
Table11 delete account
Table 12 registration
Table 13 check payment
Table 14 generate report
Table 15 prepare bill
Table 16 pay money
Table 17 view report
List of figures
Figure 1 telecom service form
Figure 2 Water service form
Page 8
Figure 3 Electric service form

Figure 4 use case diagram for centralized billing system
Figure 5 sequence diagram for login
Figure 6 sequence diagram for create account
Figure 7 sequence diagram for update account
Figure 8 sequence diagram for delete account
Figure 9 sequence diagram for register customer
Figure 10 sequence diagram for check payment
Figure 11 sequence diagram prepare bill
Figure 12 sequence diagram for generate report
Figure 13 sequence diagram for pay money
Figure 14 sequence diagram for create own account
Figure 15 sequence diagram for update own account
Figure 16 sequence diagram for view report
Figure 17 activity diagram for login
Figure 18 activity diagram for create account
Figure 19 activity diagram for update account
Figure 20 activity diagram for delete account
Figure 21 activity diagram for generate report
Figure 22 activity diagram register customer
Figure 23 activity diagram for prepare bill
Figure 24 activity diagram for view report
Figure 26 analysis level of class diagram
Figure 27 user interface prototype
Page 9
CHAPTER ONE
1.1Background of the Organization
Arbaminch town is found 505 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
administration structure to organize, control and manage the local communities. In Arbaminch
town there are governmental and nongovernmental organizations which facilitate the
development of the town and provide services to the community. All these organization uses
manual type of billing system. The Ethiotelecom is one of the governmental organizations. It was
established after the town was established, Which located at the back of Nechisar campus .It
provides more services such as voice single billing, voice over internet protocol, internet
broadband connection ,business data service and line share for the community. The organization
has smooth relation with the other organization especially electric corporation in order to get
electrical power .The organization controlled by central administrator of Ethiotelecom. The
second one is electric power corporation which located near sikela having its own manager. The
third one is water service institute which gives water service for the town.
Currently the organization information system process tasks in the form of document
based applications or traditional file systems. The current system of recording of bill system,
financial system, technical system and human resource management information has been
formatted in manual based.
1.2 Background of the project

We are trying to do the system which can solve all the problems in manual billing system.
We have considered all the problems within the system to overcome it. We have realized there is
no centralized billing system to pay all the bills of a customer. The main purposes of this project
are aimed at developing a system which reduces work burden of the customer. Some times in
manual process there is a possibility to get errors such as forget due date of payment. To
overcome these difficulties we are forced to develop web based centralized billing system. This
will minimize labor force and the time required. In this system customers can submit their bills
to the system and made the payment by online. The bills could be various types and various
amounts. The system will pay the bill before the due date and provide the consolidated payment
details to customer with the service tax. Also the system will provide the deadline to the
customer to pay the bill amount to system. An email will be sent to the concerned people to let
them know about the status of the bill.
Page 1
1.3 Team Composition

The team has five each having common as well as individual responsibilities.
Centralized Billing System
S.NO Name
ID
Email
1.
TemesgenAyana
RAMIT/1569/05
2.
3.
4.
5.
KassahunAlemayehu
TemesgenTamrie
TigistAbere
SeblewongelMezigeb
u
RAMIT/1440/05
RAMIT/1571/05
RAMIT/1582/05
RAMIT/1534/0
5
Temesgenayana1234@gmail.co
m
Kassishbest16@gmail.com
Temu1571@gmail.com
Tigistabere21@gmail.com
Sebli23@gmail.com
Responsibilit
y
All Activity
All Activity
All Activity
All Activity
All Activity
Table 1 team composition
1.4 Tasks and Schedule
June05-
Apr 30-
Mar17-
Dec23-
Activities
Nov 14-
Dec 17
Time
Project Proposal
Requirement Analysis
Design
Implementation &Coding
Testing
Project Defense
Table 2 task and schedule
1.5 Statement of the problem

The billing system applies manual way of recording customer information and processing
of tasks. In the current situation the customer record can be easily exposed to theft and
unexpected damage because of poor security to do the task it will also takes much efforts and
time to retrieve
Customer information and file control mechanism is very tedious, Complicated and not
secured.High material resource wastage (written materials) and much cost are expanded for
handling records. Generally the current billing systems have the following problems
It is limited to a single organization.
It is less user-friendly.
It is having lots of manual work (Manual system does not mean that you are working
with pen and paper, it also include working on spread sheets and other simple software's)
It requires more number of employees need to work.
Page 2
It is time consuming process.

The present system is very less secure.
It is unable to generate different kinds of report.
Difficulty in conducting consistent reports.
Unclear in handwriting and duplicating the sequence of bill number.
Manual operator control is there and leads to a lot of errors.
1.6 Objectives of the project

1.6.1 General objectives
The general objective of this project is to develop the centralized billing system for
Arbaminch town people.
1.6.2 Specific objectives
To achieve the general objectives of the project, the proposed system consists of the
following specific objectives:
Analyze the current system
To make the system user friendly
To minimize human errors
To save the time
To minimize number of employee
To improve the security
To generate different report
1.7 Scope and significance of the project

1.7.1 Scope of the project
There are different services in Arbaminch town that requires billing system. These are
water resource bureau/ office, electric power corporation service and telecommunication service.
For those different subsystems, our project will develop a centralized billing system. On the
system the customer will register first and so that they will get the access.
The proposed system is only applicable on:
With less effort and cost, the system is able to maintain and store service information
system.
Accurate way of recording or processing customer information and set records into
organized database system for reference..
To provide security mechanism and different access level in the system.
Produce reports for only information provide records.
To develop easy and understandable user interface that handle billing system.
The proposed system is limited on recording, storing, updating and retrieving for all
service that we have listed above.
1.7.2 Significant of the project
The project has a lot of significant to Arbaminch town society.
1. For each user:-by providing fast access to the billing system by reducing time like waiting
for turn in the queue and going to different offices. The user accesses the system anywhere and
anytime when they need to pay and need to get the billing. It improves the tiredness of user.
Page 3
2. For Organization:-in manual there is loss of materials like paper, pen which is cost and
more man power, the system reduces loss of costly materials and man power.
3. For Developers of the project:-It increases our knowledge and we get mental satisfaction
from the project that we will develop.
1.8. Feasibility Analysis

Preliminary investigation examine project feasibility, the likelihood the system will be
useful to the organization. The main objective of the feasibility study is to test the Technical,
Operational, Political and Economical feasibility for adding new modules and debugging old
running system. All system is feasible if they are unlimited resources and infinite time. There are
aspects in the feasibility study portion of the preliminary investigation:
1.8.1 Technical Feasibility
The technical issue usually raised during the feasibility stage of the investigation includes
the following:
Does the necessary technology exist to do what is suggested?
Does the proposed equipment have the technical capacity to hold the data required to use
the new system?
Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and data security?
1.8.2 Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system.
That will meet the organizations operating requirements. Operational feasibility aspects of the
project are to be taken as an important part of the project implementation. Some of the important
issues raised are to test the operational feasibility of a project includes the following: Is there sufficient support for the management from the users?
Will the system be used and work properly if it is being developed and implemented?
Will there be any resistance from the user that will undermine the possible application
benefits?
Page 4
1.8.3 Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economic feasibility, the development cost in creating the
system is evaluated against the ultimate benefit derived from the new systems. Financial benefits
must equal or exceed the cost.
A. Software cost
Item
Price
Microsoft window 7
MSVisio2010
Microsoft word 2010
SQL Server 2005
Microsoft power point 2007
Macromedia Dreamweaver
Visual basic studio
Total
30
35
30
25
30
30
30
210
Table 3 software cost
B. Hardware costs
Item
PC
Flash disk
Other material
Total
Quantity
1
1
---
Unit price
12000 (free)
120
----
Total
12000
120
300
12,420
Table 4 hardware cost

So the first year total cost can be calculated like this:-
Total cost=hardware cost +software cost

=12420 +210=12,630
Tangible benefits
Benefits
failure reduction
Cost reduction
Service Value
Total benefit
Page 5
Price
4,500
10,000
2,500
17,000
Total benefits
17,000
Table 5 tangible benefits

Net cost benefit
Total cost
12,630
Net benefit
4,370
Table 6 net cost benefit

1.8.4 Political Feasibility
The system that we will develop must not contradict the rule and regulation of the
organization so as to keep the rule we have asked the organization what is accepted and not
accepted. We must have active relationship with the member of the organization
We have to keep the security of the organization
1.9 Methodologies of the project

1.9.1 Data source
During requirement analysis, data needed for the project we will gather from various
sources. During gathering and collecting necessary data and information need for system
analysis, we will use two major fact-finding techniques those are primary source and secondary
source. In primary source we will use empirical approach such as interview and observation. In
secondary source we obtain data from different document.
1.9.2 Fact-finding and analysis
We have used /and will be used/ different methodology to collect data. such as:Interview
The team use interviews to collect information from individuals or from groups. The
respondents are generally current users of the existing system or potential users of the propose
system.
Observation
Through observation, our team can obtain firsthand information about how activities are
carried out. The teams know the way how the current billing system is performed so as to
overcome the problem what we have observed, at that time the team understands how much the
process is tedious and require high human power to accomplish the process.
Document Analysis
For more information about the existing system we refer relevant documents and other
reading materials.
1.9.3 Development Tools
We will different hard ware and software tools to develop the system those are:Software Tools
Tools/programmers
Activities
HTML
Client Side Coding
Java Script
Client Side Scripting
Microsoft SQL Server
Data base Server
Mozilla Firefox, IE, Google Chrome
Browsers
Page 6
CSS
Ms office word 2010
MS office power point 2010
E_Draw, Paint
For style
For Documentation
For presentation
To draw the UML Diagrams and for designs
Microsoft visual Studio 2010

Adobe Photo shop CS4
Development area
To design back ground images
Hard ware Tools

Tools
Desktop/Laptop computer
function
to work our project
Printer
to print the file documentation
Copy Machine
to copy the documentation
CD/DVD and flash disk
to take back up & store file

Table 7 Development Tools
1.9.4 Testing procedures

We will perform different testing for checking functionality of our proposed system.
1.9.4.1. Unit testing:First we will tests each unit at each system. So, if a problem is encountered
it will immediately maintain at which the problem is occurred.
1.9.4.2. Integration Testing: -After we test each unit of the proposed system we will perform an
integration test to check whether the system meets all the functional requirements. When a
number of components are complete; it will test to ensure that they integrate well with each
other, the operating system, and other components.
1.9.4.3. System testing:-After all of the above testing are checked we will test our system by
other peoples and we will conduct some comments how they get our system.
1.10. Limitation of the project

This project is limited to automate Billing system for Arbaminch town organization
specifically what we have listed above and customer.
Page 7
Chapter Two
Existing System
2.1 Introduction
The existing system of the Billing system for Telecom, water and electric is working
manually. Whatever be the process involved in the system is working through documented
(stored files). There are a lot of complexities involved in the system. When any customer takes
new interaction with the system then separate files are maintained. Updating of data is very
tedious job. It is not easy to do several administrative works like managing rates of calls,
addition or modification of metered calls & customer entries. The existing system required
different data about customer name, sex, nationalities, Keble, house Number which are
customers give to the employee. In this system administrators accept the request of the customer
from employee and the administrator sends customer request to the central administrator and the
central administrator provide registration number of customer to the administrator then the
administrator gives the bill number to the customer.
2.2 Players in the existing system

In the existing system there are numbers of players, each having their own
responsibilities
Users/Costumers
Bill staff/employee
Administrator
2.3 Major functions/activities in the existing system

The following section summarizes the function of existing system with their input, process and
output.
Page 8
Input:
Input to the system is in the form, which is fulfilled by each user/costumer with respect to the
service whatever they want. The process of filling information for all bill system (electric,
telecommunication and water bill system) in the existing system is the same.
Process:
The form that is filled by the costumer are collected and signed by the respected office after 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 costumer will start
using the service with respect to their request.
2.4 Business rules

The main business rules or principles of the existing system are:
Anyone who signsthe 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.
If the costumer does not pay the required money they will be punished.
2.5 Report generated in the existing system

Current billing system for telecommunication, water and electric services are manual.
From this system we take some forms as they are. The forms generated in the existing system are
in the forms of forms and files.
Forms:
It contains all information about customer and service filled by the costumer at the time
of requesting service from the organization
Files:
It is collection of registration forms and copy of the bills. This all reports are kept in
offices of the each service provider
2.6
Forms and other documents of the existing systems
Telecom service form
Page 9
Figure 1 telecom service form
Water service form
Page 10
Figure 2 Water service form

Electric service form
Figure 3 Electric service form
2.7 Bottlenecks of the existing system

There are a lot of problems in the existing system as compared to the proposed system.
These problems can be seen from the following perspectives like performance, information,
economic, control, efficiency and services given by the existing system to the users, by using the
PIECES framework as follow:
Page 11
2.7.1 Performance
Since the existing system is manual, it takes long response time. For example when one
costumer need his document for what he have used the document may not be available or it takes
much longer time to search. The acceptable response time for a particular task is large. But in the
proposed system concurrency problems can be solved by the new system at a time.
2.7.2 Input
List of the guest does not contain their full information on the papers.
Receive the incorrect/redundant costumer list.
To fill incorrect name and id.
One costumer may be asked twice per month because of if the data is loosed. As a result
there will be conflict b/n costumer and workers.
2.7.3 Security and Controls
In the existing system security and control is somewhat worried about. It is difficult to
control the system because there is no privilege in data accessing. Here the necessary reports
may not generate at exact time so it may occur security violence. The system shouldnt provide
sufficient protection for access and manipulation of the records associated with the system. So it
is not easily protected and used properly the resource.
2.7.4 Efficiency
In manual operation, most of the activities are prone to wastage of resources like papers,
man power, time etc. to produce the corresponding outputs. This makes the current system
inefficient while utilizing resources. There should be a mechanism that reduce wastage of
resources and that make the system to be efficient. As a result the new system will reduce
wastage of resources and make it efficient. The existing system has less efficiency than the
proposed system. The existing system has concurrency control problems i.e. more number of
users. Data management facilities are limited and the reporting schemes are not according to the
specific needs of the users.
2.8 Practices to be preserved

The system displays all the bill details such as bill no, name and price etc.The existing
system use file and forms that is used to perform the business rules, describe the operations,
definitions and constraints that apply in the maintenance and deployment of system.
Checks the availability of the services.
2.9 Proposed solution

The important thing is to make works easy
It is computerized billing system process
Computerization of the system must fulfill the requirement of giving effective services in
terms of speed, accuracy, response time, efficiency, etc.
The proposed system stores all the information about billing on the database other than
paper file.
Page 12
2.10Requirements of the Proposed System

2.10.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 requirement of our system is must assign customer bill account and make accessible
for a user.
The main requirements are to handle the observable tasks and processes that must be
performed by the system.
Make accessible the interface to customer and user
Assign customer easily, accurately and quickly.
Solve the problems that will be occurring around bill system
2.10.1.1Performance requirements
System capable to increase total throughput speed under an increased load when
resources are added
Enable the administrator to create, modify, or even to delete his/her account if it is
necessary
The system can generate information and forms for user to access Friendly
2.10.1.2 Process requirements
There will be efficient storage and easy accessibility and user must have his/her own
account
Modify his/her by asking the administrator that they wants to cancel membership of the
service.
During registration each costumer should fill the appropriate information in the specified
place.
2.10.1.3 Input related requirements
There will be accurate and flexible input mechanisms.
The input form must include name, date and customer login detail and others
Collecting the information of the costumer that who is going access service for water,
electric and telecom. The administrator must enter the password so that access is given
only to him to view the detail.
2.10.1.4 Output related requirements
Since the input is effective the output is also effective. There will be accurate display of
customer reports in accordance with the query process accessibility is possible for whom who
has an account and no one can view information unless matched successfully.
Page 13
2.10.1.5 Storage related requirements

There will be efficient storage and the entire processed system can stored in the data base.
2.10.2 Nonfunctional requirements
A non-functional requirement specifies how the new system should perform:
A non-functional requirement is a statement of how a system must perform; it is a constraint
upon the systems behavior.Non-functional requirements specify all the remaining requirements
not covered by the functional requirements. They specify criteria that judge the operation of a
system, rather than specific behaviors. Non-functional requirements specify the new systems
quality characteristics or quality attributes. Potentially many different stakeholders have an
interest in getting the non-functional requirements right. This is because for many large systems
the people buying the system are completely different from those who are going to use it
(customers and users).
2.10.2.1 Performance
Performance requirement is defines acceptable response times for system
functionality.Response time of the billingSystem should be faster than the manual system.
Response time refers to the waiting time while the system accesses, queries and retrieves the
information from the databases
Response time of the system will not take long time
The system should support many user at a time
2.10.2.2 User Interface
The window format and the forms prepared for the information are easy to user they can
easily understand.
The system shall be design according to standards and the system shall replace existing
system.
2.10.2.3 Security and Access permissions
Only system administer has the right to change system parameters, such as password
change. The system should be secure and must use encryption to protect the databases.
Users need to be authenticated before having access to any personal data.
2.10.2.4 Backup and Recovery
If the connection between the user and the system is loss the system will automatically
save the filled information and the remaining can enable by the administrator by
contacting the costumer using phone.
To recover a data we will have a copy of the original data in another place
Page 14
Chapter Three
System Analysis
3.1 Introduction
This chapter is related to the object oriented analysis (OOA). This phase helps to identify
the relationship between objects and the interaction between each object. During Object Oriented
Analysis the following major activities are performed.
3.2 System Requirement Specifications

3.2.1 Actor Identification
Customer:
Someone who wants to access the service.
Administrator:
A special user of the system who can setup access rights for other users like customer and
employee.
Bill staff/Employee:
Person who is interacts with the customers.
3.2.2 Use Case Identification
Registration:
If the customer is a new user, he can request to register with the system. TheSystem
displays a registration page. The customer is also required to enter their name and address
and other information's.
Updateinformation:
The administrator can request to update their customer information.
Viewinformation:
The customer requests to view their account and information
Fillinformation:
The customer enter the necessary information
Select service:
The costumer will select the service whatever they want.
Delete account:
The system administrator removes the costumer account if the customer wants to be
out of the system.
Generate report:
The employee will generate report of the costumer it may be per day or per month.
3.2.3 Use Case Diagram
A use case diagram is simple to represent the user's interaction with the system that
shows the relationship between the users. Also it shows the different use cases in which the user
is involved. A use case diagram can identify the different types of users of a system and the
different use cases and will often be accompanied by other types of diagrams as well.
Page 15
Figure 4 use case diagram for centralized billing system
Page 16
3.2.4 Use case documentation

Security Log in
Actors
Administrator ,Employee, customer
Use case name
Login
Use case Id
01
Description
Login to the system
Pre-condition
The user has been registered
Post condition
The user has been authorized.
Basic course of Actor Action

action
Step1: The user wants to login
System Response
Step2: The System display user log in
form.
Step3: The user enter username

and password
Step4:The system validates whether the
username and password submitted is
correct (already in the data base)
Step5: The system display the user

account page
Alternative
curse of action
Step6: The use case ends

01. The user enter wrong username and password
Step 1.1 The system indicates the user information invalid
Step 1.2 The use case continues Step 3 till correct
Table8 login table
Page 17
Create account
Actor
Administrator, employee ,customer
Use case Id
02
Use case name
Create Account
Description
This use case gives information about account creation that means
administrator will create account for employee, employee for customer and
customer for its own.
In case when users want to access service
After registration all users starts using the service what they have requested
Pre-condition
Post condition

action
System Response
Step1: The users want to register

to be member of the staff or to
get service access.
Step3: The user fill all the
necessary information
Step5: Click the "create" option.
Step2: the system displays the

registration form
Step4: The system checks whether the

all the information is filled or not.
Step6: The message creates successfully

is displayed.
Step7:The use case ends
Alternative
02. The create account is invalid
curse of action

Step 2.2 The use case continues Step 3 of the basic course of action
Table 9 create account
Page 18
Update account
Actor
Administrator, Employee, Customer
Use case ID
Use case name
03
Update account
Description
This use case allows To update user account
Pre-condition
Post condition
The users wants to update user information

The users have information that will be updated

action
Step1: User can request to update
the user information and other
information in the database.
System Response
Step2: The system Displays user
information update page
Step4: The system validates whether the

Step3: The user enters the necessary information submitted is correct
new information.
Step5: The system displays Confirmation
page and save the updated information.
Alternative curse 03. The input information invalid

of action
Table 10 update account
Page 19
Delete account
Actors
Administrator, Employee
Use case Id
04
Use case name
Delete account
Description
This use case describe the canceling of existing account
Pre-condition
The users to be out of the system required for what he/she used.
Post condition
The account will be deleted automatically
System Response
action
Step1:The
Step2:The system Displays delete
administrator/employee wants to account page
cancel the created account
Step3: Enters
number
the
Step4: The system validates whether the

account information submitted is correct or exist
Step6: The message "Account has been
deleted successfully" is also displayed.
Step5: Selects the "Process

delete" option.
Alternative
curse of action
04. The input reservation number is invalid

Table11 delete account

Registration
Page 20
Actors
customer
Use case ID
05
Use case name
Register customer
Description
This use case allows customers to register in to the system
Pre-condition
The customer wants to access service and the Customer must be legal, must be
familiar to the town and should have house in the town
Post condition
The customerregister to access the needed service...
System Response
action
Step1: The customer wants to Step2: The system Displays customer
register in to the system.
Registration page
Step3: The customer enters the Step4: The system validates whether all
necessary information in the the required information is fulfilled or
customer registration page.
not.
Step5: The system register and displays
customer registration Confirmation page
and leads to his or her account
Alternative
curse of action
05. The input information invalid

Table 12 registration
Check payment
Page 21
Actor
Employee
Use case Id
06
Use case name
Check payment
Description
This use case gives information about the payment.
Pre-condition
The employee wants to know whether the customer pays or not.
Post condition
The customer gets bill from employee.

action
System Response
Step1: The employee wants to

login to the page.
Step2:The system Displays page
Step3: Theemployee select check

payment link.
Step4: The system displays list of
persons that pay the required money.
Table 13 check payment
Generate report
Page 22
Actor
Employee
Use case Id
07
Use case name
Generate report
Description
This use case gives information about all what is done with respect to the
service.
Pre-condition
In case the employee want to generate report on that day

Or for the week
The necessary report generated and saved to the database.
Post condition

action
System Response

generate report
Step2:The system Displays generate

report page
Step3:employees enters the

generated report
Step4: The system checks whether the
report is correct or not
Step5: Selects the "Process of
report generation" option.
Step6: The message "report successfully
generated" is also displayed.
Alternative
07. The generated report is invalid
curse of action

Table 14 generate report
Prepare bill
Page 23
Actor
Employee
Use case Id
08
Use case name
Prepare bill
Description
This use case gives information about prepare a bill.
Pre-condition
Post condition
The user must ask the bill.

The bill will be given to each individual in the form of message for what
they have used. The users have to search to get the bill information.
System Response
action
prepare bill for the user.
Step2: The system Displays the form.
Step3: The employee will fill all

the information.
Step4: The system will say you have
prepare the bill correctly
Alternative
08. if all the above is invalid
curse of action

Step 8.2 The use case continues Step 3.
Table 15 prepare bill
Pay money
Page 24
Actor
Costumer
Use case Id
09
Use case name
Pay money
Description
This use case gives information about paying money for costumer usage.
Pre-condition
In case the costumer have an access to the service
Post condition
The costumer will pay for what they have used per month.

action
System Response
Step1: The costumer wants to

pay.
Step2: The system Displays thebank

userto loginpage.
Step3: The costumer enter the

user name and password
Step4: The system displays payment

mode
Step5: Selects the net banking.
Step6: System displays the transaction

page
Step7: Enters the transaction

password and press pay button
Step8: displays payment successful
Alternative
09. else the above is invalid
curse of action

Table 16 pay money
View report
Page 25
Actor
Costumer
Use case Id
10
Use case name
View report
Description
Here the use case will help the costumer to display the report.
Pre-condition
In case the employee want to generate report on that day

Or for the week
The necessary report generated and saved to the database.
Post condition

action
System Response
Step1: The costumer wants to

view their own report.
Step2: The system displayview report

page.
Step3: Then the costumer select

view report option
Step4: The system displays the
generated report in the form of table
Table 17 view report
Page 26
3.2.5 Sequence diagram

A Sequence diagram is an interaction diagram that shows how processes operate with
one another and in what order. It is a construct of a Message Sequence Chart. A sequence
diagram shows object interactions arranged in time sequence. It depicts the objects and
classes involved in the scenario and the sequence of messages exchanged between the objects
needed to carry out the functionality of the scenario. Sequence diagrams are typically
associated with use case realizations in the Logical View of the system under development.
Sequence diagrams are sometimes called event diagrams or event scenarios.
Login
Page 27
Figure 5 sequence diagram for login
Create account
Figure 6 sequence diagram for create account

Update account
Page 28
Figure 7 sequence diagram for update account
Delete account
Figure 8 sequence diagram for delete account
Register
Page 29
Figure 9 sequence diagram for register customer

Check payment
Figure 10 sequence diagram for check payment

Prepare bill
Page 30
Figure 11 sequence diagram prepare bill

Generate report
Figure 12 sequence diagram for generate report

Payment
Page 31
Figure 13 sequence diagram for pay money

Create own account (user)
Figure 14 sequence diagram for create own account

Update own account (user)
Page 32
Figure 15 sequence diagram for update own account

View report
Figure 16 sequence diagram for view report

3.2.5 Activity Diagram
Activity Diagrams are used to Document the logic of a single operation /methods, a
single use case, or the flow of logic of a business operation. In many ways, Activity Diagrams
are the object_ oriented Equivalent of flow charts and Data Flow Diagrams (DFD) from
Structure.
Page 33
Login
Employee, customer and
Figure 17 activity diagram for login
Create account
Employee,customer and
Figure 18 activity diagram for create account

Update account
Employee, customer and
Page 34
Figure 19 activity diagram for update account
Delete account
Employee and
Figure 20 activity diagram for delete account
Page 35
Generate report
Figure 21 activity diagram for generate report
Register customer
Figure 22 activity diagram register customer
Page 36
Prepare bill
Figure 23 activity diagram for prepare bill

Pay money
View report
Page 37
3.2.6 Analysis level class diagram

Class diagrams are typically used, although not all at once, to:
Explore domain concepts in the form of a domain model
Analyze requirements in the form of a conceptual/analysis model
Depict the detailed design
.
Page 38
Figure 26 analysis level of class diagram
3.2.6 User Interface Prototyping
Page 39
Figure 27 user interface prototype
Page 40
Chapter Four
System Design
4.1
Introduction
System design is the transformation of the analysis model into a system design model.
During system design, developers define the design goals of the project and decompose the
system into smaller subsystems that can be realized by individual teams. The result of system
design is a model that includes a clear description is a model that includes a clear description
of each of these strategies, subsystem decomposition, and a UML deployment diagram
representing the hardware/software mapping of the system. This chapter mainly concerned
with the design part of all about the billing system. In this section we will see the different
types of class type architectures, such as user interface layer, process control layer,
business /domain layer, persistent layer, and system layer and also different types of system
modeling techniques that are used for the implementation types of the system such as class
modeling, state chart modeling, component modeling, deployment modeling and also some
system design techniques such as user interface designing are also to be covered in this
design chapter.
4.2 Class type architecture

Class type architecture provides a strategy for layering the classes of the system to
distribute the functionality of the software among classes. Furthermore, class type
architectures provide guidance as to what other types of classes a given type of class will
interact with, and how that interaction will occur. This increases the extensibility,
maintainability, and portability of the systems.
Interface: This layer wraps access to the logic of our system. This layer consists of interface
Class: user interface (UI) classes that provide people access to our system.
Domain: This layer implements the concepts pertinent to our business domain, focusing on
the data aspects of the business objects, plus behaviors specific to individual objects.
Process: The process layer implements business logic that involves collaborating with
several domain classes or even other process classes.
Persistence: Persistence layers encapsulate the capability to store, retrieve, and delete
objects/data permanently without revealing details of the underlying storage technology.
System: System classes provide operating-system-specific functionality for your
applications, isolating your software from the operating system (OS) by wrapping
OS-specific features, increasing the portability of your application.
Page 41
Figure 4.1 class type architecture

4.2.1 User interface layer
This layer binds access to the logic of our system. There are two categories of interface.
Class user interface (UI) classes that provide user access to your system and system
interface (SI) classes that provide access to external systems to your system.
Java script, PHP for server side and HTML for graphical user interface (GUI) screens
implemented via the Swing class library are commonly used to implement UI classes within
HTML.
In our system there is one main home page interface that enables people enter (login) to the
system and large number of user inter faces to work (communicate) each other and with
other layers.
We have the following interfaces: Home page
Login
Administrator
Customer
Employee
Page 42
Create users account
Customer registration
View report
About us
Delete users account
Prepare bill
Generate report
Update user account
Change password
Etc
4.2.2 Controller/process layer

The process layer implements business logic that involves collaborating with several Sub
domain classes or even other process classes.
The business logic is the key element that determine the work flow in the system for
example the system should check whether the customer is new or not and also the customer
have paid on his payment accordingly and on the exact day this also cheeked by the process
layers .etc
The process layer works in collaboration with other layers to do it activities.
4.2.3 Business/Domain layer

This layer implements the concepts relevant to the business domain.
4.2.4 Persistence layer
Persistence layer encapsulate the capability to store, retrieve, and delete objects/data
permanently without revealing details of the underlying storage technology. In our Database
system we have used different tables as object and each object is related to each other and
enforced by referential integrity by the use of foreign key and primary key.
This enables as data manipulation activity such as select, search, view delete on the data base
schema.
Page 43
4.2.5 System layer

System classes provide operating-system-specific functionality for your applications,
isolating our software from the operating system (OS) by wrapping OS-specific features,
increasing the portability of our application.
In this project we have used MS WINDOWS XP, plat form on the each client side, PHP and
on the server side.
4.3 Class modeling

The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the constraints
imposed on the system. The classes diagrams are widely used in the modeling of object
oriented systems because they are the only UML diagrams which can be mapped directly
with object oriented languages.
The class diagram shows a collection of classes, interfaces, associations, collaborations and
constraints. It is also known as a structural diagram.
Page 44
Figure 4.2 class modeling diagram
4.4 State chart modeling

State chart diagram is used for modeling the dynamic aspects of systems. It is similar to
activity diagram. Both activity and state chart diagrams are useful in modeling the lifetime
of an object. However, activity diagram shows flow of control from activity to activity;
whereas state chart diagram shows flow of control from state to state. State chart modeling is
a dynamic modeling technique, one that focuses on identifying the behavior within our
system, behavior specified to the instances of a single class. It tries to show different state
that an object passes through its life span. However, it is not necessary to build state chart
for every class in the system; only state charts of complex objects are necessary to be
modeled. State chart diagram enables us to observe the state of complex that simplifies.
State chart diagram for login
Page 45
Figure 4.3 State chart diagrams for login

State chart for update
Figure 4.4 State chart diagrams for update
State chart for Registration
Page 46
Figure 4.5 State chart diagrams for Registration

State chart for Sign up
Figure 4.6 State chart diagrams for signup

State chart for payment
Page 47
Figure 4.7 State chart diagrams for payment
4.5 Collaboration Modeling

Collaboration diagram show the message flow between objects in an OO application, and
also imply the basic associations or relationships between classes. The rectangle represent the
various objects involves that make up the application, and the line between the classes
represents the relationships (association, aggregation, composition, dependencies, or
inheritance).Use a collaboration diagram (collaboration diagram: An interaction diagram
that shows, for one system event described by one use case, how a group of objects
collaborate with one another.) to show relationships among object roles such as the set of
messages exchanged among the objects to achieve an operation or result.
Collaboration diagram for Registration
Page 48
Figure 4.9 collaboration diagrams for registration

Collaboration diagram to view report
Figure 4.10 collaboration diagrams for view report
Collaboration diagram create account to customers

Page 49
Figure 4.11 collaboration diagram for create account for customers
4.6 Component Modeling

The component model illustrates the software components to build the system.
Components are modeled as rectangles with two smaller rectangles jutting out from the left
hand side. Components have dependencies on the interface of other components.
Component diagrams can show how various components are structurally related to one
another in a given system. These charts are capable of showing a high level of complexity
and can be adapted to a variety of uses. The component diagram below shows relationships
for a centralized billing system.
Page 50
Figure 4.12 component modeling diagram
4.7 Deployment modeling

Deployment model depicts static view of the run time configuration of processing nodes and
the components that run on those nodes.
Deployment model also shows the hardware for the system, the Software that is installing on
that hard ware and the middle ware used to connect the disparate machines to one another.
A deployment diagram in the unified modeling language models the physical deployment
of artifact on nodes. The nodes appear as boxes, and the artifacts allocated to each node
appear as rectangles within the boxes. Nodes may have sub nodes, which appear as nested
boxes. A single node in a deployment diagram may conceptually represent multiple physical
nodes, such as a cluster of database servers.
Page 51
Figure 4.13 deployment diagram
4.8 Persistence modeling

Persistence models _also called data model or Entity relationship (ER) models, are used to
communicate the design of a database, usually a relational database, to both users and other
developers.
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.
Page 52
Figure 4.14 Persistence modeling diagram
4.9 User Interface design

User interface design is the overall process of designing how a user will be able to interact with a
system.
The goal of user interface design is to make the user's interaction as simple and efficient as
possible, in terms of accomplishing user goals.
user interface for home page
Page 53
Figure 4.15 user interfaces for home page
user interface for signup
Figure 4.16 user interfaces for sign up
Page 54
user interface for login
Figure 4.17 user interfaces for login
User interface for customer page
Figure 4.18 user interfaces for customer page
Page 55
user interface for adminstretor page
Figure 4.19 user interfaces for admin page
Chapter Five
Implementation and Testing
Introduction
Implementation refers to the coding of the all documents gathered starting from requirement
analysis to Design phase. All documents, business logic, information gathered are designed into
the code so that the system will be implemented for the user to be used for the purpose it
developed. The chapter here describes about the final testing system, hardware and software
acquisitions, and installation process. The functional system from the design phase above is the
key input to the implementation phase. The deliverable of the implementation phase (the project)
is the operational system that will enter the operation and support stage of the systems life cycle.
Here is the sample code for each module.
5.1Finale testing of the system

Test case
Here we have designed a test case for some of our interfaces.
Test case for login
Page 56
Test Case #:1.1

Test case Name: Login
System: Login
Sub system:
Designed by: team
Design Date: 09/04/2016
Executed by: All user
Execution Date: 11/04/2016Short
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 User
Name and Password.
Step
Action
Click the login

button
Enter user name and
password
Expected System
Pass/Fail
Response
The system displays a login
page
The system displays a
message if user name or
password is incorrect asking
the user to re enter
if correct display main page
Comment
Post condition
The user can access the main page.
Test Case for change password
Test Case #:1.2

Test case Name: Change Password
System: Password
Sub system:
Designed: Team
Designed Date: 11/04/2016
Executed by: Admin, Employee and customer
Execution Date: 12/04/2016
Short Description: Test the change current password
Page 57
Pre-conditions
The user has a valid User Name and Password before.
The system displays the main page.
Step
Action
Expected System Response
Click the Change

password button
Enter user name,
current password and
new password with
confirm new
password.
The system displays a change

password page
The systems displays a Message if
user name and current password is
not match and confirm new
password is also not match the
user to re-enter again.
If both is correct display message
successfully change
Pass/Fai
l
Comment
Post-conditions
The New password is store in database.
Test case pay money

Test Case #:1.3
System: payment
Designed by: Team
Executed by: user/customers
Test case Name: pay money

Subsystem:
Short Description: Give information about whether the customer have paid the required money or not.
Page 58
Pre-conditions
The customer has to be registered first.
Step
1.
2.
Action
Expected System
Response
Click the pay menu The system displays a
payment page
Customer will enter id The system will check the
and amount of birr
money and then it will give
a message have no enough
balance if the amount of
birr is greater than what we
have in bank database else
successfully paid will be
displayed.
Pass/Fail
Comment
Post condition: the customer will get payment rest for what they have paid.
Test Case #:1.4

Test case Name: manage account
System: manage employee account
Subsystem:
Designed by: team
Executed by: Administrator
Short Description: only administrator can manage employees account.
Pre-conditions
The customer has to be registered first and admin have a privilege to do this.
Step
Action
Expected System Response
Click the manage

account button
The system displays create, delete

and update account page
Page 59
Pass/Fai
l
Comment
e.g. For create

account
Admin can create
account for the user
by filling all the
employee information
The system displays account is

successfully created if all the
necessary information are filled
else it will say enter the
information again.
Post condition: the employee will have an account and then they will manage customer account.
5.3 Hardware and Software Acquisitions

Hardware acquisition: The system is going to be implemented on the Arbaminch Billing system
for the three services. Since our system is web based for its deployment a web server is needed.
Here the hardware requirements are the minimum so that to be registered and to be a member.
Software acquisition: The client side application is compatible with windows environment.
5.3.1 Hardware &Software Configuration
Production environments
Recommended - 32-bit OS with Intel/AMD 2.0
GHZ+ CPU
RAM
Recommend minimum - 4 GB
Temporary file space for installs and
10 GB free disk space for software and logs
upgrades
For Redundancy
RAID/Mirroring for redundancy
Additional disk space for storage
Temp files space- The store requires 5GB
Operating system
Windows XP, and Windows 7,window 8 etc.
Internet Connection Speed
Higher
5.4 User Manual Preparation

No more manual preparation is needed for users, because the system developed is not software
and it is not installed on a client computer. After the implementation has been completed, it is
directly hosted on Network (server).
5.5 Training
During the development of the system, the project group members will give short time training
for the system administrators and workers explaining how the system works and in what way
they can manage the system developed.
5.6 Installation Process

Since the project is a web based System, there is no need to install it on a particular machine
rather it will be hosted on a web server. Database server will also be configured.
Page 60
5.7 Start-up strategy

Once the system is hosted, it has two parts: One which needs password and username that is for
Manager. To access those parts one has to have password and user name so that he/she can enter
into it and use it. The other part is those which do not need password and username so they can
be view by anybody.
5 .9 Coding
The physical design specification created by the designers is turned in to working computer
code.
Code for home page
<!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>Arbaminch Town Centralized Billing System</title>
<link rel="stylesheet" type="text/css" href="css/style.css" />
</head>
<body>
<div id="main">
<div id="header">

<img width="1200" height="130" src="Img/dr.jpg" alt="image1" width="1201"
height="118"/></div>

<div id="menubar">
<ul id="menu">
<li class="current"><a href="home.php"><font color="white">Home</font></a></li>
<li><a href="cntct.php"><font color="white">Contact Us</font></a></li>
<li><a href="about.php"><font color="white">About Us</font></a></li>
<li><a href="signup.php"><font color="white">sign up</font></a></li>
<li><a href="login.php"><font color="white">Login</font></a></li>




</ul>
</div>
<div id="site_content">
<div class="sidebar_container">
Page 61
<div class="sidebar">
<div class="sidebar_item">
<body bgcolor=#3454FF>

</body>
<img width="215" src="Img/bll.jpg" color="yellow"/>

<font size="5"color="red"
width="200"><b></b></font>
<table bgcolor="red" width="415" align ="center" id="table2">
<img width="300" height="200"src="Img/8.jpg"></a></td></tr>
<img width="300" height="100"src="Img/11.jpg"></a></td></tr>

</table>

</tr>
</table>
</div>

</div>
</div>
<div id="content1">
<div class="content_item">
<center>
<img height="215" width="960" src ="Img/LOGO.gif"/>

<marquee direction="left"width="960"bgcolor="violet"><h1><font
color="green""font-family="sanserif"><bgcolor="orange"><b>Welcome to Arbaminch Town
Centralized Billing System</h1></b></font></marquee>
</center>
<p><h1 class="style9"><center><b> Background of the organization: </h1>
<center><b>    Arbaminch town is found 505 kilometers far
from the capital city of Ethiopia.
Page 62
It is one of the towns in SNNP having different culture and is center of tourism
in the region and has its own administration structure to organize, control and manage the local
communities.
In Arbaminch town there are governmental and nongovernmental organizations
which facilitate the development of the town and provide services to the community.
All these organization uses manual type of billing system. The Ethiotelecom is
one of the governmental organizations.
It was established after the town was established, Which located at the back of
Nechisarcampus .
It provides more services such as voice single billing, voice over internet
protocol, internet broadband connection ,business data service and line share for the community.
The organization has smooth relation with the other organization especially
electric corporation in order to get electrical power .
The organization controlled by central administrator of Ethiotelecom. The
second one is electric power corporation which located near sikela having its own manager.
The third one is water service institute which gives water service for the town.
<center/></b>
</p>
<p><pre><p><font size="5px"bgcolor="orange" font-family="tims-newRoman"></font></pre><p>

</div>
</div>
<ul class="style10" id="menu">
<li class="style9 style14 style13"></li>
</ul>
</div>

</body>
</html>
Code for login

<?php
include('see.php');
session_start();
if(isset($_SESSION['validuser']))
{
$username=$_SESSION['validuser'];
}
Page 63
?>
<head>
<title>ARBAMINCH TOWN CENTRALIZED BILLING SYSTEM</title>
</head>
<body>
<div id="main">
<div id="header">

<img width="1200" height="120" src="Img/bbX.jpg" alt="image1" width="101"

<div id="menubar">
<ul id="menu">
<li><a href="home.php"><font color="white">Home</font></a></li>
<li><a href="cntct.php"><font color="white">Contact Us</font></a></li>
<li class="current"><a href="login.php"><font color="white">Login</font></a></li>
</ul>
<body bgcolor=#9494B8>
<font size="3"color ="green">

<?php
echo "<b>".date('l\, F jS\, Y ')."</b>";
?></font>
<br>
</body>
<img width="215" height="150" src="Img/gg.jpg" color="red"/>
<font size="5"color="red" width="200"><b></b></font>
<table bgcolor="white" width="215" align ="center" id="table2">
<tr><td><img width="200" height="80"src="Img/ad.jpg"></a></td></tr>
Page 64
<tr><td><img width="200"
height="80"src="Img/emp.jpg"></a></td></tr>
<tr><td><img width="200" height="80"src="Img/cu.jpg"></a></td></tr>
</table>

</tr>
</table>
</div>

</div>

<div id="content1">
<center>
<form id="form1" name="login" method="POST" action="login.php" onsubmit='return
formValidation()'>
<form method='POST' action='change.php' onsubmit='returnnformValidation()'
enctype="multipart/form-data">
<form method='POST' action='change.php' onsubmit='returnnformValidation()'
<br><br><br><br><br><br>
<table bgcolor="gray"align="top;" width="500" height="250px">
<tr><td colspan=4 align=right ><p style="margin-top:3%;"><font color=green></td></tr>
<trcolspan="3"><td colspan="3"><img width="500"height="100"src="Img/t.jpg"/></td></tr>
<tr><td><b><font color="black">User Name:</font></b></td><td><input type="text"
name="username"
pattern="\D{3,5}/\d{3}/\d{2}" required x-moz-errormessage="To Login Please Enter User
name"
title="To Login Please Enter User name"></td></tr><br><br>
<tr><td ><font color="red"></font><b><font color="black">
Password:</font></b></td><td><input type="password" name="password" pattern ="[a-zA-Z09]+"id="pass1"
required x-moz-errormessage="To Login Please Enter password" title="To Login Please Enter
password" >
</td></tr><br><br>
<tr><td><font color=red> * </font><b><font color=black>Role: </td></b><td><select
name="role" id="role" required>
<option value=""> enter role of user</option>
<option>Administrator</option>
Page 65
<option>employee</option>
<option>customer </option>
</select></td></tr>

<tr><td> </td><br><td><input type="submit" style="background-color:#808000"
name="submitlogin" " value="login" /></td></fieldset></tr>
</form>
</center>
<?php
if(isset($_POST['submitlogin']))
{
$user =$_POST['username'];
$password=$_POST['password'];
$role=$_POST['role'];
$passdec=base64_encode($password);
$query1 = "SELECT * FROM useraccount WHERE UserName = '$user' AND Password =
'$password'AND Role='$role' ;";
$result=mysql_query($query1);
if(!$result){
die("Login Failed".mysql_error());
}
$rowCheck = mysql_num_rows($result);
$row=mysql_fetch_array($result);
$role=$row['Role'];
//if($row['level']==1){
if($role=='Administrator')
{
$_SESSION['validuser']=$user;
echo "<script>window.location='admin.php';</script>";
}
if ($role=='employee')
{
echo "<script>window.location='employee.php';</script>";
}
if ($role=='customer')
Page 66
{
echo "<script>window.location='customer.php';</script>";
}
else {
echo '<div align="center"><strong><font color="#FF0000"> Incorrect Login
Trial!!! Try Again Latter. !!</font></Strong></div>';
echo'<meta content="2;login.php" http-equiv="refresh"/>';
}
}
mysql_close($conn);
?>
</fieldset>
</table>
</div>
</div>
</div>
<ul class="style10" id="menu">
<li class="style9 style14 style13">
</li>
</ul>
<h2>

</h2>
</div>

</body>
</html>
Code for sign up
Page 67
<! 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>ARBAMINCH BILLING OFFICE</title>
<link rel="icon" type="image/png" href="Img/dbui.png"/>
<meta name="description" content="free website template" />
<meta name="keywords" content="enter your keywords here" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=9" />
<script type="text/javascript" src="js/jquery.min.js"></script>
<script type="text/javascript" src="js/image_slide.js"></script>
<style type="text/css">
</style>
</head>
<body>
<div id="main">
<div id="header">

<img width="1200" height="120" src="Img/bbX.jpg" alt="image1" width="1201"

<div id="menubar">
<ul id="menu">
<li><a href="home.php"><font color="white">HOME</font></a></li>

</ul>
Page 68
<body bgcolor=#9494B8>
<hr><hr>
<font size="3"color ="green">

<?php
echo "<b>".date('1\, F jS\, Y ')."</b>";
?></font>
<br>
<hr><hr></body>
<img width="215" height="200" src="Img/signup.png"/>

<font size="5"color="green"><b></b></font>
<table bgcolor="#4b474"align ="center" id="table2">
<tr><td></td><td><img width="200"
height="50"src="Img/11.jpg"></a></td><td></td><td></td><td></td><td></td><td></td><td>
</td><td></td><td></td><td></td><td></td>
<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>
<td></td><td></td><td></td><td></td><td></td>
</tr>
height="50"src="Img/9.jpg"></a></td><td></td><td></td><td></td><td></td><td></td><td><
/td><td></td><td></td><td></td><td></td>
Page 69
</tr>
height="50"src="Img/wt.jpg"></a></td><td></td><td></td><td></td><td></td><td></td><td>
</td><td></td><td></td><td></td><td></td>
</tr>
</table>
<br><br>
</tr>
</table>
<p> </p>
<p> </p>
</div>
</div>
<div id="content1">
<center>
<div style="width:620px; height:650px; margin:0 auto; position:relative;
border:4px solid rgba(0,0,0,0);
-webkit-border-radius:5px; -moz-border-radius:5px; border-radius:25px; -webkitbox-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:20px; color:#F00000;">
<form method='POST' action='insertsignup.php' on submit='returnn form Validation()'
<div style="background-color:#336699;border-radius:5px;font-family:Arial, Helvetica, sansserif; color:#000000; padding:5px;
height:22px;">
<div style="float:left;" ><img width="30" height="20"
src="Img/signup.png"/>  <strong><font color="white" size="2px">
Page 70
User Signup page</font></strong></div>

<div style="float:right; margin-right:20px; background-color:#cccccc; width:25px; textalign:center; border-radius:10px;
height:12px;">
<a href="home.php" title="Close"><imgsrc="img/close_icon.gif"></a></div>
</div>
<input type="hidden" name="role" id="name" value="<?php echo '4'; ?>" />
<table bgcolor="#A9A9A9"align="center;" width="500" height="350px">
<tr><td colspan=3 align=right ><p style="margin-right:3%;"><font color=green><font
color=red></font></td></tr>
<tr><td><font color=red> * </font><font color=black>UserName :</font></td><td><input
type="text" pattern="\D{3,5}/\d{3}/\d{2}" required x-moz-errormessage="Please Enter Letter
Only Above 2 characters" title="Please Enter Letter Only Above 2 characters "
name="UserName" value="" size='20%' id="txt_fname"
placeholder='Fname'></input></td></tr>

<tr><td><font color=red> * </font><font color=black>Password :</td><td><input
type="password" name="Password" value="" size='20%' id="pass" placeholder='Password'
pattern="[a-zA-Z0-9]+" required x-moz-errormessage="Please Enter Students Login
Password!!! " title="Please Enter Students Login Password!!!"
placeholder='Password'></input></td></tr><br>
<tr><td><font color=red> * </font><font color=black>Role :</td><td><input type="text"
pattern="\D{3,15}" required x-moz-errormessage="Please Enter Role Field!!!" title="Please
Enter Role Field!!! " name="Role" value="" size='20%' id="role" placeholder='Role'
/></td></tr>
<tr><td colspan="2" align="center"><input style="background-color:#808000"type='submit'
class="button example" value='Signup' name='submit Main' Onclick="return
check(this.form);"/>
<input style="background-color:#808000"type='reset' class="button example"
value='clear'/></td></tr>
</form>
</center>
</body>
</html>
Page 71
CHAPTER SIX
CONCLUSION and RECOMMENDATION
6.1 Conclusion
With all the accumulated eort invested, there are reasons to believe that at the end of the project
for Automated Expert System for Ambulance Management in Arba Minch Hospital that
ndsitself in a better way. We summarize the progress with respectto the main objectives of the
project. We the team members can conclude the following perceptional views as we have done
the project throughout this year.
AESAM system supports to manage ambulance andpatient information Inside Arba Minch
hospital. Moreover the system can also be used for send the user request to the ambulance driver,
generate report and perform management activity. The new system will changes the current
manual system of AMHambulance management to computerized manner. It is more flexible and
secure when it compared within the current system. Our project solves the current ambulance
management problem and problem of ambulance service for Arba Minch society.
Page 72
6.2 Recommendations
We strongly recommend that one who under goes through this project can succeed, and they pay
attention for Expert System thatComposing for Ambulance Management. Most of the time has
been taken for understanding the working of existing system, how applications are written in
existing system and how a third party tool can be integrated in this system. But since all these
areas are much clear through this project we recommend adding to sending features from Mobil
to system or Expert system. The final recommendation towards the target group who need to
work on and improving it can even think of different Expert Systementirely developed for every
country.
Page 73
Reference
[1]:- Jaffrey McManus, HomeEncyclopediaDatabases of SQL and Access, 1st edition 1997
[2]:- complete guide of html
[3]:-php five and php four complete guide
[4]:-ER.V.K. JAIN, System analysis and design 1st edition, 2001
[5]:-System analysis and design method, 6th edition
Webliography
www.google.com
www.ethiotelecom.net
www.w3school.com
Page 74

Billing

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Billing

Caricato da

Copyright:

Formati disponibili

ystem

ARBA MINCH UNIVERSITY

Centralized Billing System For Arbaminch Town

Centralized billing system

Table 1 team composition............................................................................................................... 2

Table 2 task and schedule...............................................................................................................2

1.6.1 General objectives.................................................................................................................3

1.7.1 Scope of the project................................................................................................................3

1.8.1 Technical Feasibility............................................................................................................. 4

1.9.1 Data source............................................................................................................................ 5

Forms and other documents of the existing systems......................................................8

Figure 1 telecom service form........................................................................................................9

2.10.2 Nonfunctional requirements............................................................................................. 13

3.2.1 Actor Identification..............................................................................................................14

Centralized billing system

Centralized billing system

3.2.6 User Interface Prototyping................................................................................................ 38

4.2 Class type architecture............................................................................................. 39

4.2.1 User interface layer.............................................................................................................40

Centralized billing system

Figure 3 Electric service form

Centralized billing system

1.2 Background of the project

Centralized billing system

1.3 Team Composition

Table 1 team composition

1.4 Tasks and Schedule

1.5 Statement of the problem

It is time consuming process.

1.6 Objectives of the project

1.7 Scope and significance of the project

1.8. Feasibility Analysis

1.8.2 Operational Feasibility

Centralized billing system

1.8.3 Economic Feasibility

Table 4 hardware cost

Total cost=hardware cost +software cost

Centralized billing system

Table 5 tangible benefits

Table 6 net cost benefit

1.9 Methodologies of the project

Microsoft visual Studio 2010

Hard ware Tools

to print the file documentation

to copy the documentation

CD/DVD and flash disk

to take back up & store file

1.9.4 Testing procedures

1.10. Limitation of the project

Centralized billing system

2.2 Players in the existing system

2.3 Major functions/activities in the existing system

2.4 Business rules

2.5 Report generated in the existing system

Forms and other documents of the existing systems

Telecom service form

Centralized billing system

Figure 1 telecom service form

Water service form

Centralized billing system

Figure 2 Water service form

Figure 3 Electric service form

2.7 Bottlenecks of the existing system