Industrial Project I Final-Signed

PROJECT ON
CUSTOMER MANAGEMENT SYSTEM FOR BAHIR DAR CITY WATER

SUPPLY SERVICE
(SHUMABOO BRANCH)
SUBMITTED
IN PARTIAL FULLFILMENT OF THE REQUIRMENTS FOR THE DEGREE OF
BACHELOR OF SCIENCE
IN
INFORMATION TECHNOLOGY
BY
[Dejen Agaziu……………………....ENG(R) /222/2002]
[Ermiyas Birhanu…………….……ENG(R) /279/2002]
[Habtamu Wubalem………….…....ENG(R) /381/2002]
BAHIR DAR, ETHIOPIA
Advisor ………………………………………………………Getasew T.
Jun-2013 GC
Declaration
The Project is our own and has not been presented for a degree in any other university and all
the sources of material used for the project/thesis have been duly acknowledged.
Dejen Agaziu…………………………ENG(R)/222/2002…………………………………..
Ermiyas Birhanu……………………..ENG(R)/279/2002……………………..……………..
Habetamu Wubalem…………………ENG(R)/381/2002……………………………………
Name ID Signature
School: School of Computing and Electrical Engineering
Program: Information Technology
Project subject: Customer Management Service for Bahir Dar City Water Supply Service
(Shumaboo Branch)
I certify that this project satisfies all the requirements as a project for the degree of Bachelor of
Science.
Worku Kelemework
------------------------------------- ---------------------------------------------
Name of program coordinator Signature
This is to certify that I have read this project and that in my opinion it is fully adequate, in
scope and quality, as a thesis for the degree of Bachelor of Science.
------------------------------------- ---------------------------------------------
Name of Advisor …Getasew T…………….Signature ……………………………..
Examining committee members signature Date
1. Chairman _____________________ ________________ ____________________

2. Examiner 1 _____________________ ________________ ____________________
3. Examiner 2 _____________________ ________________ ____________________
It is approved that this project has been written in compliance with the formatting rules laid
down by the school of the university.
CMS for Bahir Dar City Water supply Service (Shumaboo Branch) 2013
Acknowledgment
We would like to acknowledge the support of the Bahir Dar City Water Supply Service
Shumaboo branch stuff members. They have given the required all documents
essential for the study. Particularly Teshome Mulalem manager of the office, Getnet
Adiss Information Technology professional who allowed our group for interview at
any time. We also would like to express the deepest appreciation to our advisor
Getasew T. who has supported us in the past 3 months by his valuable comments and
corrections. He encouraged us to pursue on this topic and spent extra time by helping
our group to accomplish our study.
Finally, we also appreciate the help and support from all persons who were
directly or indirectly involved in our project.
~ ii ~
Contents
Acknowledgment ...................................................................................................................... ii
List of Figures .......................................................................................................................... iv
Abbreviation ............................................................................................................................ vi
Abstract ................................................................................................................................... vii
Chapter one: INTRODUCTION .............................................................................................. 1
Background ........................................................................................................................................ 2
Existing System Study ........................................................................................................................ 3
Statement of the problem .................................................................................................................... 4
Proposed System ................................................................................................................................. 4
Objectives of the Project ..................................................................................................................... 5
General Objective ............................................................................................................... 5
Specific Objective ............................................................................................................... 5
Scope of the project ............................................................................................................................ 5
Methodology....................................................................................................................................... 5
Data / requirement collection method .................................................................................. 5
System analysis & design methodology .............................................................................. 6
Software tools to be used .................................................................................................... 6
Benefit and Beneficiary of the project ................................................................................................. 6
Benefit of the project........................................................................................................... 6
Beneficiary of the project .................................................................................................... 7
Organization of the Project .................................................................................................................. 7
Chapter Two: SYSTEM FEATURES...................................................................................... 8
Hardware and Software Requirements ................................................................................................. 8
Hardware Requirements ...................................................................................................... 8
Software Requirements ....................................................................................................... 8
User Requirements .............................................................................................................................. 9
Functional Requirements ..................................................................................................................... 9
Non Functional Requirements ........................................................................................................... 10
Analysis Models ............................................................................................................................... 10
Actor Definition ................................................................................................................ 10
Use case Diagram ............................................................................................................. 12
Use Case List and Descriptions ......................................................................................... 13
Sequence Diagram ............................................................................................................ 20
Activity Diagram .............................................................................................................. 33
Chapter Three: SYSTEM DESIGN ....................................................................................... 46
Deployment Diagram ........................................................................................................................ 46
Architectural Design ......................................................................................................................... 48
Class Diagram................................................................................................................................... 48
User Interface Design ........................................................................................................................ 49
Data Structure Design ....................................................................................................................... 57
Entity Relationship Diagram (ERD) .................................................................................. 57
Table for ER-Diagram ...................................................................................................... 59
Normalization Table ......................................................................................................... 60
Schema Relationship Diagram .......................................................................................... 61
Algorithm Design ............................................................................................................................. 62
Bibliography ........................................................................................................................... 67
Appendix A ............................................................................................................................. 68
Questions asked during requirement gathering using interview .......................................................... 68
~ iii ~
List of Figures
Figure 1: Use case diagram ................................................................................................................................12
Figure 2: Sequence Diagram-Login ...................................................................................................................20
Figure 3: Sequence Diagram-Apply registration.................................................................................................21
Figure 4: Sequence Diagram-Audit and Analysis ...............................................................................................22
Figure 5: Sequence Diagram-Bill collects ..........................................................................................................23
Figure 6: Sequence Diagram-View Message ......................................................................................................24
Figure 7: Sequence Diagram-Update Customer Information ..............................................................................25
Figure 8: Sequence Diagram-Delete Customer Information ...............................................................................26
Figure 9: Sequence Diagram-Order Maintenance ...............................................................................................27
Figure 10: Sequence Diagram-Receive Maintenance Order................................................................................28
Figure 11: Sequence Diagram-Update Maintenance Order .................................................................................29
Figure 12: Sequence Diagram-Enter Meter Read Value .....................................................................................30
Figure 13: Sequence Diagram-Generate Report .................................................................................................31
Figure 14: Sequence Diagram-View Report .......................................................................................................32
Figure 15: Activity Diagram - Login ..................................................................................................................33
Figure 16: Activity Diagram – Apply Registration .............................................................................................34
Figure 17: Activity Diagram – Audit and Analysis.............................................................................................35
Figure 18: Activity Diagram – Bill Collect ........................................................................................................36
Figure 19: Activity Diagram – Update Customer Information ............................................................................37
Figure 20: Activity Diagram – Delete Customer Registration.............................................................................38
Figure 21: Activity Diagram – View Message....................................................................................................39
Figure 22: Activity Diagram – Order Maintenance ............................................................................................40
Figure 23: Activity Diagram – Receive Maintenance .........................................................................................41
Figure 24: Activity Diagram – Update Maintenance Order ................................................................................42
Figure 25: Activity Diagram – Enter Meter Read Value .....................................................................................43
Figure 26: Activity Diagram – Generate Report .................................................................................................44
Figure 27: Activity Diagram – View Report.......................................................................................................45
Figure 28: Deployment Diagram ........................................................................................................................47
Figure 29: Class Diagram ..................................................................................................................................48
Figure 30: UI – Login Page................................................................................................................................51
Figure 31: UI – Customer Registration...............................................................................................................52
Figure 32: UI – Customer Maintenance Order....................................................................................................53
Figure 33: UI – Update Maintenance Order ......................................................... Error! Bookmark not defined.
Figure 34: UI – Meter Read Input ......................................................................................................................53
Figure 35: UI – Update Customer ......................................................................................................................54
Figure 36: UI – Delete Customer ......................................................................... Error! Bookmark not defined.
Figure 37: UI – Bill Interface .............................................................................................................................55
Figure 38: Printable Bill Format .......................................................................... Error! Bookmark not defined.
~ iv ~
Figure 39: Report On Customer Debt .................................................................................................................56
Figure 40: Entity Relationship Diagram (ERD) ..................................................................................................57
Figure 41: Table for ER Diagram .......................................................................................................................59
Figure 42: Normalization for the table ...............................................................................................................60
Figure 43: Schema Relationship Diagram ..........................................................................................................61
~v~
Abbreviation
 BDWSSO: Bahir Dar city Water Supply Service Office
 CD: Compact Disk
 DBMS: Database Management System
 ER diagram: Entity Relationship diagram
 GB: Giga Byte
 I/O: Input Output
 MYSQL: My Statement Query Language
 PC: Personal Computer
 PHPMYADMIN: Hypertext Pre Processor
 RAM: Random Access Memory
 SQL: Statement Query language
~ vi ~
Abstract
The principal objective of this paper is to demonstrate and automate the capability in BDWSSO to conduct
effective, automated, accurately, and inexpensively.
The need for electronically controlled service, in the absence of customer to ensure constant and effective
service distribution is a serious demand. We therefore intend to provide a solution by constructing an electronic
system that has the capability of monitoring the service of the organization to the customers and at the same time
supply Registration and other related service to the customer when they need to access.
The project involves methods like data/requirement collection, system analysis and design(object
oriented approach).It also includes the use of hardware and software’s like operating system, DBMS
,application software, PhpMyAdmin and the likes. DBMS for the purpose of database implementation,
Application software’s to develop user and administrative interface, PhpMyAdmin to providing the user with an
interface. From this project, we hope to build automatically effective and efficient system for BDWSSO.
~ vii ~
Chapter one: INTRODUCTION
Bahir Dar water supply service office (BDWSS) has many activities; Such as, Customer registration, bill
calculating, maintenance etc. The system has employees like meter reader, bill officer, accountant, bill
collector, Bill Officerand technical supervisor to give service for their customers. The office use software
which is desktop application to generate the customers billing system and also they use manual system to
store back up files like file cabinets and suspension card. In general the office uses semi-automated system.
So, the project try to reduce this problem and enable the office system to have very fast service to their
customer and to become fully automated system by designing web based service management system for
BDWSS.
~1~
Background
Bahir Dar city water supply service office (BDWSSO) is a water supply organization which is in Bahir
Dar city. The organization is established in 1951 E.C as part of the city administration, with the name
called “Water section”. At that time, the office had only five employees’ water chemist, motor operator,
meter reading expert and two security bodies. BDWSS follows semi automated system to give service for
their customer. Until 1971 E.C the office had only 200 customers, which register to apply the service.
But, in 1970 this “Water section” builds its own office by 60,000 birr and become independent
organizational office by the name called BDWSSO, within 25 employees under the workplace. Currently,
the organization has many customers and employees.
~2~
Existing System Study

The basic existing system functions of the organization are:
Customer registration
 It is done by customer service by collecting the necessary data from the user.
Bill calculation
 Customer’s data store and bill calculating was using computer software which have SQL 2008
server.
 Backup data was stored in manually by using cabinet and suspension card and also CD, hard disk
device
 Customer must inform the office if his/her reading value was not done in timely manner by being
physically available at the office.
 The billing system was done from the hierarchy of meter reading to bill officer, then bill officer to
accountant and from accountant to bill collector and vice versa.
Report generation
 The organization makes a general report about the billing system once at the end of the month
and generates the report.
Maintenance reporting
 Customers inform physically to their technical supervisor when service maintenance was needed.
 Employees get feedback from their customers using suggestion box.
The following table shows current tariff of water consumption
Number Consumption Tariff/Birr
1 From 0 - 5 m3 2.90
3
2 From 5.1 - 10m 4.40
3 From 10.1 - 25m3 6.10
4 From 25.1m3 and above 8.20
~3~
The following table shows current water meter rent

Number Meter size Rental tariff
1 1/2” 2.00
2 ¾” 2.50
3 1” & above 3.00
Statement of the problem

BDWSSO is currently uses a semi automated system. As it is semi-automated, it has its own problems. Like;
 Since the billing information was circulated, the data will loss, and it takes time to manage it.
 Since customer registration is taking place in physically; it leads to wasting time.
 During requesting maintenance, the customers may spend unnecessarily expense and waste their time.
 The customers may not get the chance to request service of the organization 24/7(twenty four hours a
day and seven days a week).
 During the backup system of the office, it was not efficient if the documents were damaged.
 It may be difficult for customers to get the phone number or the location of the organization.
 During generating monthly report, it takes time and it may not be easy to manage and analyses the
monthly work due to massive collection of data and the generated report may not be accurate.
Proposed System
The proposed solution for BDWSSO is changing the semi-automated system into web based system by
creating dynamic web page for the organization. Unlike the existing system, which operates by registering
one customer at a time the online web based system can register many customers concurrently. The new
system can also help to found any files of the customers with in a fraction of seconds. With this new system
the organization gives efficient & time observance service for their customer.
~4~
Objectives of the Project

General Objective
The general objective of the project is to automate the services of Bahir Dar water supply service office
(BDWSSO).
Specific Objective
Here are some specific objectives that would together help us achieve the overall the project as follows:
 Study the existing system and find out the problem.

 Find the solution for the problem found in existing system.
 Design and build a particular model of this proposed system.
 Deploy the system and test it till it fits to the needs of the organization.
Scope of the project

The scope of this project is developing web based system for BDWSS organization.
This project is focused on the following points:
 Some activities related to customers. Like: customer registration, Customer Maintenance order
processing, meter reading, billing system processing, audit and analysis, bill report(weekly, and
monthly ), setting privilege for employee
 Automating the processes that have been done in the billing system.
Methodology
Data / requirement collection method

There are different methods to collect information. From those the project uses the following tools and
methods to collect data from the organization.
 Observation (Documentation & material): use this method to get the right information about the
organization and also to understand how the existing system works.
 Interview: This methodology encapsulates two types of methods. These methods are closed and open
interview. So the team has selected an open interview for interviewing the manager and employees
for recognizing the existing working procedure of the organization. So the team was able be to gather
more information about the organization and requirements (see appendix A).
~5~
System analysis & design methodology

For the system analysis and design part there are two models. These, structured and object oriented
approach. From those this project uses object oriented approach because it is efficient to show how the
data is organized, it also shows clearly the definition of the data of the system. In general, the project uses
the object oriented paradigm to develop the system.
As the whole for the methodology requirement we use spiral model for perfect movement and
finishing our project very well.
Software tools to be used

Have much software to do this project, but the most important are the following:
 MySQL- to create and design the database which used to store the information of the customers &
the employee of the organization.
 MS-Visio-to design the system analysis part of the project.
 MS-word- to prepare the documentation part of the project
 PHP scripting language and its own WAMP server: to implement the system and provide the user
of the system with an interface.
Benefit and Beneficiary of the project

Benefit of the project
The main benefits of this system as it is computerized web based system:
 It save the customers time when they want to access service from the organization.
 The Customers uses the system safely and gives comfort for them.
 It initiates and increases employee moral to do their task properly.
 It attracts other customer to join and register under the system.
 Introduces the office to technology and also facilitates technology throughout the coverage area,
as it is web based system.
 It motivates many customers to join the system, as it is easily accessible.
 It makes the office efficient and more profitable in a short period of time, as it follows fully
automated system and has many customers.
 It increases performance of the organization.
 Generates more secured information for each customer. (use)
 It makes smooth relation between the office and their customer.
 Generates and improves socio economic change to the society.
~6~
Beneficiary of the project

The first beneficiaries of this proposed system is the customers who have knowledge on how to access
information from the internet and those of employee of BDWSSO. And the other user of this system the
organization by its own, everybody can join their organization simply and can understand how they
work, and understand what things they done. So, within a short time it becomes more profitable and
famous.
Organization of the Project

The project document is organized in 4-chapters. The first chapter contains introduction about the
organization and detail about what type of system, will be done in the project. It also contains the
schedule part of the project
The second chapter of the project document contains the system features (the requirement analysis)
part of the system, which shows the activities that will be done in the system diagrammatically using use
case diagram, Activity diagram, Sequence diagram, it also shows the relationship among them.
The third chapter is about the system design part which contains the Deployment diagram,
Architectural design (class diagram), User interface Design.
The last chapter of the project document is about the system implementation & coding part of the
project. It clearly shows the interfaces, implementation, testing part of the project.
~7~
Chapter Two: SYSTEM FEATURES

In the requirement analysis (system features), divide the requirements into hardware & software, functional
and non-functional requirements.
Hardware and Software Requirements

Hardware Requirements
For the new system to be efficient there is a requirement for specific hardware and software.
o Memory:
 Rocmendation:3GB RAM.
o Core i5
o Hard disk: to keep the permanent data.
o Flash Disk: 2GB to store & transfer data from one PC to another PC.
o Printer: to have a hard copy for the data.
Software Requirements
The client PC running the system may use any of the following operating system:
 Window server 2003, 2008:
 The client PC may use one of the following browsers:
 Internet Explorer  Mozilla Firefox
 Commit Bird  Google chrome……..etc
But the system needs to fulfill the following software:

 Operating system: MS-window 2003, 2008 server will be used for the system.
 Database management software (DBMS): is the mandatory one for the new system. To implement
the database easily, (MySQL) is recommended.
 Application software: to develop user and administrative interface it also used for connecting to the
database, Most MS-Office applications are appropriate.
 PhpMyAdmin: choose PHP scripting language which aims at providing the user with an interface
that is easy to learn and attractive.
 Macromedia Dreamweaver and notepad++: to edit the PHP code.
~8~
User Requirements
User requirements are statements, in a natural language plus diagrams, of what services the system is
expected to provide to system users and the constraints under which it must operate. That describes user
goals or tasks that the users must be able to perform with the system. User requirements therefore describe
what the user will be able to do with the system. (Sawyer S.)
 The user interface shall be menu driven, it shall provide dialog boxes; help screens, drop down lists,
radio buttons, check boxes and text boxes for user input.
 The navigation from one screen to the other must be easy.
 The bill officer wants to get real report according to the report type.
 Customers will send service maintenance order to the target place.
 Buttons and labels would be indicating exact function that it represented known, example submit
represent save, add but not retrieve from database.
 All the system function will be compatible with the user.
Functional Requirements
Functional requirements These are statements of services the system should provide, how the system
should react to particular inputs, and how the system should behave in particular situations. It specifies
the software functionality that the developers must build into the product to enable users to accomplish
their tasks. (Sawyer I. a.)
 The system must have a dynamic website that provides successfully registration of customers
which are under the business rule of the office and generate report to interact with various users.
 The system should allow staff to login to the system using their username and password.
 The system should provide to modify record that is deleting, editing and inserting as well as
retrieving the required information.
 The system should display message when employees of the BDWSS and customers do their task
successfully or not when they insert invalid username and password.
 The system should display full information for the customer from the database to the interface of
the web page.
 The system should have well organized information storage and accessing mechanism.
 The system should allow generating report for the organization.
 The system must easy to enter meter read value to the database.
 The system must presents information of the customer and their monthly costs, and requests
service maintenance in secured manner.
 It is expected to solve the difficulty of managing overloaded customer registration, maintenance
order, bill calculating and other task successfully.
~9~
Non Functional Requirements

Non-functional requirements, as the name suggests, are requirements that are not directly concerned with
the specific services delivered by the system to its users. They may relate to emergent system properties
such as reliability, response time, and store occupancy. Alternatively, they may define constraints on the
system implementation such as the capabilities of I/O devices or the data representations used in
interfaces with other systems. Non-functional requirements, such as performance, security, or
availability, usually specify or constrain characteristics of the system as a whole.
 Since everything in the office is financial, the system of DBMS should be highly secured and
every users of the system should have their own privilege which in turn maximize the system
security.
 The system calculates the customer’s bill rent, so it should give accurate result; so should be
reliable.
 The system should have an easily understandable design in order for users to use it; this means the
system should be user friendly.
 The system provides quick and easy information analysis which in turn maximizes the overall
work efficiency.
 The system should be able to manage all the information incoming from the database and the
catalogue; Capacity Requirements.
Analysis Models
Actor Definition
Actors are portrayed in a use case diagram as a stick figure and represent external factors that will provide
interaction with the system.
Customer: A person who is using a web browser to access BDWSSO web based.
Bill Officer: an employee, who works on customer service office, which have the following
responsibilities.
 Approve new customer application.
 She/he makes a decision when a customer is deleted or updated.
Bill reader: an employee in the Billing system, who is responsible to check the monthly or ant time
when the organization want to check reading data,
Bill officer: An employee who works on the billing system office, she/he coordinates the system and he
takes the customer’s monthly reading value from the bill reader calculate the value of each customer
using the system and transfer each result to the accountant and bill collector and also She/he responsible
to generate the report that reads by the bill collector using the system.
~ 10 ~
Accountant: A professional person who performs accounting functions such as audits or financial
statement analysis, which responsible to takes the final value from the Bill officer and she/he asks the
customer to pay their fee depend on the calculated value. After the payment the Accountant must be
transfer the overall deposit of the customer to the Bill collector.
Bill collector: The Bill collector takes the deposit from the Accountant and check if exception was
happened, if not he/she approve the customers. This employee also has a privilege to read the generated
report that is done by the Bill officer.
Technical supervisor: An employee who works on the maintenance service of customers, they have the
following activities.
 It receives the maintenance order of the customers.
 It updates the order as much as possible.
~ 11 ~
Use case Diagram
CMSBDWSS
Receive
Maintanance Order
Audit and Analysis
Update Maintanance
Accountant Logout Technician
*
order
«uses»
Generate Report «uses»
*
«extends» «uses»
«uses» Assign Technician
Delete Customer* «uses» «uses»
«uses»
Bill officer Login
Update Customer
«uses»
Bill Collect
«uses» Apply Registration
«uses»
Bill Collector
Maintanance Order
Customer
View Report
View Message
Meter Reader
Meter Reading
*Note: Deleting customer is not mean that totaly delete customers from the database, actualy mean temporarly
remove the data.
Figure 1: Use case diagram
~ 12 ~
Use Case List and Descriptions
Use case name: Apply Registration

Identifier: UC1
Actor: Customer
Description: A customer requests service by using online application for BDWSSO web page.
Precondition: The customer should fullfil the business rule of BDWSSO.
Basic course of action: The customer:
 Open the home page.
 Click sign up form
 Enter the correct & all necessary information.
 Click submit button.
Post condition: The customer will join the organization and access online service from the office.
Use case name: Login

Identifier: UC2
Actor: Bill officer, Accountant, Bill collector, Customer service, Technician, Customer.
Description: A member login to BDWSS uses their appropriate user name and pasword.
Precondition: Must have valid username and password.
Basic course of action: The employee:
 Open home page
 Click sign in from the right top of the screen
 Enter Username and password.
 System validates the address.
 User login to the system.
 If not try again
 End use case.
Post condition: The employees enter to the System.
~ 13 ~
Use case name: Audit and analysis

Identifier: UC3
Actor: Accountant
Description: The Accountant would receive the total cost from the customer that has been being used.
Precondition: The bill officer transfer the final calculated value to the Accountant
Basic course of action: The accountant:
 Open the homepage.
 Sign in
 Enter username and password.
 Click the customer payment page link.
 He/she receive payment from the customer’s according to the data; if the customers
had debit, add the penalty value (10 birr per month).
 After the payment process was finished, transfer the general data to the bill collector.
 Log out.
 End use case.
Post condition: The accountant take the payment from customers according to the calculated bill value,
audit and transfer to the bill collector.
Use case name: Bill collect

Identifier: UC4
Actor: Bill collector
Description: The Bill collector accumulates the overall financial value from the accountant and takes the
data of the customers from the bill officer to approve it.
Precondition: The Accountant must be finished the payment value and the bill officer must also be
transfer the original data of the customers to this employee.
Basic course of action: The Bill collector:
 Sign in
 Enter username and password.
 Click the customer payment page link.
 Check
 The payment and the calculated data.
 Identifies the customers who have debit value.
 Approve.
 After the approving process was finished, transfer the data to the accountant and bill
officer.
 Log out. End use case.
Post condition: The accountant takes the payment from customers according to the calculated bill value,
audit and transfer to the bill collector.
~ 14 ~
Use case name: View Message

Identifier: UC5
Actor: Customers
Description: The Customers of the system views their monthly bill value online and other announcement
information.
Precondition: UC2.
Basic course of action: The customer:
 If there is, see the announcement and advertisement.
 else
o Sign in
o Enter username and password.
o System validates the address.
o Click information button.
o See the monthly cost value
o Log out.
 End use case.
Post condition: The customer know monthly bill read value.
Use case name: Update customer information

Identifier: UC6
Actor: Bill Officer.
Description: Allow to update previously recorded customer data.
Precondition: UC1, UC2.
Basic course of action: The Bill Officer:
 Open the home page.
 Sign in
 Enter login address on the homepage.
 The system check is the correct address or not.
 Bill Officer enter customer ID of the intended customer.
 The system validates the customer ID.
 The system searches and display customer detail.
 Bill Officer enters new modification.
 System updates the information and displays it.
 Logout
 End use case.
Post condition: updated customer data.
~ 15 ~
Use case name: Delete customer.

Identifier: UC7
Actor: Bill Officer.
Description: Used to block customer from BDWSSO system service.
Precondition: UC2.
Basic course of action: The Bill Officer:
 Login to the Bill Officer page.
 Sing in
 Enter user name and password
 Search the customer information in their database by entering their appropriate ID.
 Block the customer.
 End use case.
Post condition: The customer will be blocked.
Use case name: Order maintenance

Identifier: UC8
Actor: Customer
Description: Allow customer to order maintenance for the office.
Precondition: UC1.
Basic course of action: The Customer:
 Open the homepage
 Sign in
 Customer selects maintenance order form from the home page.
 The customer enters their ID.
 The customer enters maintenance detail in the form.
 The system responses whether message is transferred or not (fault tolerance).
 logout
 End use case.
Post condition: Maintenance order will be recorded to the system.
~ 16 ~
Use case name: Receive maintenance Order

Identifier: UC9
Actor: Technician
Description: Receive, assign technician and approve customer maintenance order.
Precondition: UC9.
Basic course of action: The Technician:
 Sign in
 Enter user name and password.
 Checks and see the problem and identify the customers who send the order.
 Take the order from the customer.
 logout
 End use case.
Post condition: Assign technician for the service being transferred.
Use case name: Update maintenance order

Identifier: UC10
Actor: Technician
Description: update the service order that would maintain.
Precondition: UC10
Basic course of action: The Technician:
 Sign in
 Check the weather the required service is maintained or not
 If it was maintained
o Record the maintained service
o Calculate how much it cost to maintain
o Transfer the calculated cost to the accountant
o Update the received data to permanently
 Else try again to maintain the service
 logout
 End use case.
Post condition: Update the maintained service and reassign the technician to the unsolved service.
~ 17 ~
Use case name: Meter read

Identifier: UC11
Actor: Meter reader and Customer
Description: Read the meter reader how much it count and enter the value to the system.
Precondition: know previous reading value
Basic course of action: The customer or meter reader:
 Read the value of the meter reader
 Take the data to the system
 Sign in
 Option 1:
o If the reader were customer;
 Click send information link
 Click meter value button
 Enter the value that he/she read
 Click send button
 Option 2:
o If the reader were meter reader
 Click meter read value link
 Enter the value that he/she read
 Click send button
 logout
 End use case.
Post condition: Transfer the reading value to the system.
Use case name: Generate report

Identifier: UC12
Actor: Bill officer
Description: Generate report that was done monthly in the form of printable data.
Precondition: UC1, UC3, UC11.
Basic course of action: The Bill officer:
 Sign in
 Click report link
 Select report type that wants to generate then click preview.
 Click print button, logout, End use case.
Post condition: Generate report.
~ 18 ~
Use case name: View Report

Identifier: UC13
Actor: Bill collector
Description: view report that was done monthly.
Precondition: UC1, UC3, UC11.
Basic course of action: The Bill collector:
 Sign in
 Click report link
 Select report type that wants to view.
 logout
 End use case.
Post condition: Generate report.
~ 19 ~
Sequence Diagram
A sequence diagram shows an interaction arranged in time sequence. In particular, it shows the instances
participating in the interaction by their “lifelines” and the stimuli that they arranged in time sequence. It
does not show the associations among the objects. (Sawyer I. a.)
User Home Page User Login Login

<<actor>> <<UI>>, Login <<controler>> <<UI>> Database
Login: Basic course of action
for the the login
Wishes to open
click the login tab

Send()
1. Open home page of the system
2. click login tab <<creates>>
2. Enter username
and password Enter user name and password
Login()
3. The system check the eligibility of
user name and password from check
the database
Invalid
4. Redirect to the page

Redirect to the required page
Figure 2: Sequence Diagram-Login
~ 20 ~
Customer
aCustomer Home page Registration Application form
<<actor>> <<UI>> Regestration: <<controller>> <<UI>> Database
Apply Registration:: Basic

course of action
for the system.
Wish to registration
Click registration link
send()
1. Customer wishes to register.
<<create>>
fill the required information

2. Customer input their personal
information using form screen
on the home page
apply
.
3. Customer apply. submit()
cann't accept
4. The reply is send back to customer. Successfully registerd
Figure 3: Sequence Diagram-Apply registration
~ 21 ~
audit and analyze:
anAccountant auditAnalysis Login Customer payment

theHomePage Login:login Database
<<actor>> <<controler>> <<UI>> <<UI>>
Wish to audit and analyse
click login
send()
<<create>>
Enter userName and Password
Check()
invalide()
open()
add the payment and debit value of the customer
send()
check()
invalide()
Successfull Inserted
logout()
Figure 4: Sequence Diagram-Audit and Analysis
~ 22 ~
Bill Collect:
aBillCollector billCollector Login Monthly payment

theHomePage Login:login Database
<<actor>> <<controler>> <<UI>> <<UI>>
Wish to check the audit
click login
send()
<<create>>
Check()
invalide()
open()
check the monthly payment and identify who has debit
approve()
check duplicate files
invalide()
Successfull Inserted
logout()
Figure 5: Sequence Diagram-Bill collects
~ 23 ~
View Message::
aCustomer Message Login Information

theHomePage Login:login
<<actor>> <<controler>> <<UI>> <<UI>> Datbase
View anouncement and advertizment
click login link
send()
<<create>>
Check()
invalide()
open()
click(view)
retrive data from the database
No
Display()
logout()
Figure 6: Sequence Diagram-View Message
~ 24 ~
Update Customer information:
aCustomerService customerUpdate Login Customer update

theHomePage Login: Database
<<actor>> <<controller>> <<UI>> <<UI>>
Wish to update customer
click login
send()
<<create>>
check()
invalide()
open()
Insert the customer identification number
check(id)
invalide()
Enter the data to update
update()
successfully updated
logout()
Figure 7: Sequence Diagram-Update Customer Information
~ 25 ~
Customer Detail Login View Details

aCustmerService theThomePage Search
Login Information <<UI>> <<UI>> Database
<<actor>> <<UI>>
<<controller>>
wish to delete customer
Click login link

send()
Delete customer
information
<<create>>
Login (user name, password)
validation()
invalide()
<<create>>
Enter customer identification number
search()
Here deleting customer means
hide the customer data noResult()
temporarly from the database
click delete button
delete()
display()
logout
Figure 8: Sequence Diagram-Delete Customer Information
~ 26 ~
Order Maintanance:
aCustomer Maintanace Login orderMaintanance

theHomPage Login Database
Wish to order service maintanance
Click login link
send()
<<create>>
check()
open() invalide()
Insert the all the information to order
click send
send()
successfully inserted
logout
Figure 9: Sequence Diagram-Order Maintenance
~ 27 ~
Receive Maintanance order:
aTechnician Mantanice Login viewOrder

theHomPage Login Database
Click login link
send()
<<create>>
check()
invalide()
open()
view order
assign technician
send()
successfully inserted
logout
Figure 10: Sequence Diagram-Receive Maintenance Order
~ 28 ~
Update Maintanance order:
aTechnician Maintenance Login

theHomePage login Service
<<actor>> <<controller>> <<UI>> Database
<<UI>>
Click login link
send()
<<create>>
check()
invalide()
open()
check the service maintained or not
if maintained update the service
Enter the cost value
value()
if not, assign technician again
send()
successfully done
logout
Figure 11: Sequence Diagram-Update Maintenance Order
~ 29 ~
Meter read:
aCustomer,
aMeterREader Login MeterRead Login meterReadValue
theHomePage Database
Click login link
send()
<<create>>
check()
open() invalide()
Enter meter read value
click send
send()
successfully done
logout
Figure 12: Sequence Diagram-Enter Meter Read Value
~ 30 ~
Generate report:
aBillOfficer generateReport Login

theHomePage login Report Type
<<actor>> <<controller>> <<UI>> Databse Printer
<<UI>>
Click login link
send()
<<create>>
check()
open()
invalide()
click report
select report type to generate
click print
print()
logout successfully done
Figure 13: Sequence Diagram-Generate Report
~ 31 ~
View report:
aBillCollector generateRerport Login

theHomePage login Report Type
<<actor>> <<controller>> <<UI>> Database
<<UI>>
Click login link
send()
<<create>>
check()
open() invalide()
click report
select report type to generate
click preview
display()
report displayed
logout
Figure 14: Sequence Diagram-View Report
~ 32 ~
Activity Diagram
Activity diagrams model is a high level business or processes or transitions between states of a class. In
this activity diagram tried to document the flow of logic for the major business processes.
Login:
Open home page
Login
Enter username and password
Click login button

[ invalid
]
valid
Redirect to the page
Figure 15: Activity Diagram - Login
~ 33 ~
apply registration:
Open home page
Registration
Click customer registration button
Fill the registration filled
applay
Figure 16: Activity Diagram – Apply Registration
~ 34 ~
auditing and analysis:

Open home page
Login
Enter user name and password
Click login
[ invalid
]
valid
Take the payment and debit value
Check the payment and debit

invalid
valid
Successfully inserted
logout
Figure 17: Activity Diagram – Audit and Analysis
~ 35 ~
bill collector:
Open home page
Login
Click login
[ invalid
]
[Valid
]
check the monthly payment and debit
check Duplicate files
[Invalid]
[Approv
e]
succesfully inserted
logout
Figure 18: Activity Diagram – Bill Collect
~ 36 ~
update customer information:
Open home page
[ invalid]
Login
valid
Insert customer identification number
[ incorrect ID]
[ correct ID]
Enter the data to update
Successfully update
logout
Figure 19: Activity Diagram – Update Customer Information
~ 37 ~
delete customer information:
Open home page
Login
[ Incorrect
Enter user name and password ]
[ Correct]
Enter the customer identification number
[ Incorrect ID
]
[ Correct ID]
[ no result
Search ]
Click to delete button
Successfully deleted
logout
Figure 20: Activity Diagram – Delete Customer Registration
~ 38 ~
View Message
Customer open home page
Login
Enter Username and password
[ Incorrect Address]
[ Correct address]
Click View link
Logout
Figure 21: Activity Diagram – View Message
~ 39 ~
Customers Open the Homeoage
Order Maintenance
Signin
Enter usernmae and password

[ CorrectAdd]
[ IncorrectAddress]
Customer selects maintenance order form from the home page
The customer enters ID
[ Incorrect ID
]
[ Correct ID]
The customer enters maintenance detail in the form
System respond success message to the customer
Figure 22: Activity Diagram – Order Maintenance
~ 40 ~
Receive Maintenace
Technician open the homepage
Signin

[ Incorrect address
]
[ Correct address]
Check the problem and identify the customer
Take the order from the customer
Figure 23: Activity Diagram – Receive Maintenance
~ 41 ~
Technician open the homepage
Signin Update maintenance Order

[ Incorrect address
]
[ Correct address]
Check weather the ordered service is done or not
[ It's Maintained]
[ Not maintained]
Record the maintained service
Calculate cost for the service
Transfer value to the Accountant
Update the recevied data permanently
Figure 24: Activity Diagram – Update Maintenance Order
~ 42 ~
Enter Meter Read Value
Meter reader open the homepage
Signin

[ Incorrect address
]
[ Correct address]
Click Meter read value link
Enter the value that has
Transfer value to the Accountant
Figure 25: Activity Diagram – Enter Meter Read Value
~ 43 ~
Generate Report
Signin
The Bill officer open the homepage
[ Correct address]
Click report link
Select report type that want to generate
Click print button
Figure 26: Activity Diagram – Generate Report
~ 44 ~
View Report
Signin
The Bill collector open the homepage
[ Correct address]
Click report link
Select report type that want to view
Click view button
Figure 27: Activity Diagram – View Report
~ 45 ~
Chapter Three: SYSTEM DESIGN

This chapter of the project document which provides a system design of this project. This chapter
contains and describes about deployment diagram, architectural design, user interface design and data
structure design.
Deployment Diagram
Deployment diagrams show:
 The configuration of run-time processing elements and the software components,
processes, and objects that live on them. Software component instances represent run-time
manifestations of code units.
 The physical communication links between hardware items (machines and other sources,
such as printers).
 The relationship between physical machine and processes-what runs where?
~ 46 ~
Web server: Appache

Client
<<executable>>
Customer register
<<HTML>>
<<executable>>
Bill calculator
<<executable>>
Report generator
PHP Printer
Database: MySQL
Fax
Scanner
CMSBDWSS
Database
Figure 28: Deployment Diagram
~ 47 ~
Architectural Design
A software system is a set of communicating entities that collaborates to perform task. The architectural
Design is a top level design which shows these entities, their relationships. Class diagrams or structure
charts may be used to represent architecture of a system.
Class Diagram
Class diagrams show the static structure of the model, in particular, the things that exist (such as classes
and types), their internal structure, and their relationships to other things
Reads
Employee
+First Name : char
+Last Name : char
+Employee ID : char Meter reader
+Position : char
+Tell No : int +Reads()
Message
1
Reads
+Message type : char Accountant
Bill officer 1
-Message No : int
+Message date : int +Audit and Analysis() 1..*
+View Message() +Generate()
1 Water Meter
0...* 1 -Meter type : int
1 Audits 1
Views 1 -Meter size : int
Technician +Meter No : int
- Checks +Read meter()
0...* +Receive main order()
Customer +Update main order()
-Cust ID : int
-Sex : char 1
-First Name : char
-Last Name : char 0..* 1...* 1...*
-City : char Prepares
-Kebele : int Bill
-House No : int Orders -Bill No : int Generates
-Tel No : int Receives -Current read : int
-Previous read : int
+Apply Register() -Consumption : int
+Order Maintenance() -Catagory : char
0..* +Total : int
0..* +Calculate bill()
Applys Maintenance 0..*
0..* -Maintenance No : int 0..*
+Main order date : int
Registration +Maintenance Type : char Report
+Register No : int +Recevie() -Report type : char
-Report date : int 1...*
-Register Date : int +Update()
-Register Time : float +Report No : int
-Register Place : char +View()
+Apply()
Figure 29: Class Diagram
~ 48 ~
Database Design
~ 49 ~
User Interface Design

Home interface of the office
~ 50 ~
User interface is the external part of the system which is used to access and interact with the system
easily.
(A) UI- Login Page
Figure 30: UI – Login Page
~ 51 ~
(B) UI- Customer Registration
Figure 31: UI – Customer Registration
(C) UI- Customer Maintenance order
~ 52 ~
Figure 32: UI – Customer Maintenance Order

(E) UI- Meter Read Input
Figure 33: UI – Meter Read Input

(F) UI- Update Customer
~ 53 ~
Figure 34: UI – Update Customer
~ 54 ~
(H) UI- Bill Interface
Figure 35: UI – Bill Interface
~ 55 ~
(J) UI- Report on Customer Who Has Debit
Figure 36: Report On Customer Debt
~ 56 ~
Data Structure Design

Data structure design describes about data modeling and in this part Entity Relational Diagram, relational
mapping, and the likes are described. So, E-R diagram is appropriate to show this.
Entity Relationship Diagram (ERD)

The entity relationship diagram describes the relationship between entities, cardinality and their
attributes.
Figure 37: Entity Relationship Diagram (ERD)
~ 57 ~
ER Description
 Entity’s:- Bill officer, technician, message, bill, bill collector, report, registration, Bill Officer, meter
reader, water meter, accountant and customer
 Attribute: - First Name, Father Name, Sex, Cust_ID,Tel_No, Empl_ID, position, type, Date, kebele,
Report Date, Report Number, Report type, Current Read, meter size, Previous read, House_No,
Meter_No, Category, Consumption and Mainten_No.
 Relationship: Apply, view, order, update, delete, get value, receive, read, generate and collect
Entity Description
 Bill officer:
 Technician: The technician receives, update and assign the received maintenance order from
customer.
 Customer: The customers are the users of the system have their own privilege and a relationship with
Bill Officer, technician to gate service and submit monthly water meter value.
 Message: Information that post to all user of the system.
 Bill Collector: The employee that check the balance and debt value received by the accountant.
Manage.
 Bill Officer: An employee that updates and delete customer.
 Meter reader: An employee who read water meter.
 Accountant: An employee who make audit and analysis the bill value of the customer.
Relationship Description
 Apply- This relationship shows that new customers apply registration to the system
 View- This relationship shows that the bill collector view the generated report by bill officer.
 Order- This relationship shows that the customer order maintenance service to the technician.
 Delete- This relationship shows that the Bill Officer delete the illegal customer from the database
 Generate- This relationship shows that the bill officer generate monthly report to the office.
 Receive- This relationship shows that the employee take the request service or report customer’s
problems.
 Read: This relationship shows that the customer or meter reader read the value of the water meter.
~ 58 ~
Table for ER-Diagram

Customer
Cust_ID Name Sex House_No Tell_No Kebele
Maintenance
Maintain_ID Type
Message
Msg_No Msg_Type Date
Bill Officer
Empl_ID Name Sex Position Tell_No
Water Meter
Meter_No MeterType MeterSize
Meter Reader
Bill Officer
Empl_ID Name Position Position Tell_No
Bill Collector
Technician
Bill
Bill_Number Previouse read Current read Consumption Category Total
Report
Report_No ReportType ReportDate
Figure 38: Table for ER Diagram
~ 59 ~
Normalization Table
Normalization is a process that aims at achieving better designed relational database schemas through the user of
semantic information given by Functional dependencies and Primary keys, Normalization process takes a
relational schema through a series of tests to certify whether it satisfies conditions. The schemas that satisfy
certain condition are said to be in a given “NORMAL FORM’ and unsatisfied schema are decomposed by
breaking up their attributes into smaller relations that posses desirable properties. Normalization allows us to
organize data that it allows fast access and reduced space. (Elmasri; fundamentals of database systems, 2003).
Customer
Cust_ID Name Sex House_No Tell_No Kebele
First normal form (remove multi valued attributes)
Cust_ID First Name Father Name Sex House_No Kebele
Cust_ID House tell number Mobile Number
Employee
First normal form (remove multi valued attributes)
Empl_ID First Name Father Name Position
Empl_ID Office tell number Mobile Number
Maintenance
Maintain_ID Type
Message
Msg_No Msg_Type Date
Water Meter
Meter_No MeterType MeterSize
Bill
Bill_Number Previouse read Current read Consumption Category Total
Report
Report_No ReportType ReportDate
Figure 39: Normalization for the table
~ 60 ~
Schema Relationship Diagram
Customer
Cust_ID First Name Father Name Sex House_No Kebele House_Tell_No Mobile_No
Cust_Maintenance
CID MID Order _Date
Maintenance
Maintain_ID Type
Main_Technician
Empl_ID MID
Service_ID Type SCust_ID
Cust_Message
Msg_No Msg_Type CID
Cust_Cus Relation
Empl_ID CID
Cust_Water Meter
Meter_No MeterType MeterSize CID

Water Meter_Meter Reader
Empl_ID MNo
Registration
Reg_No Date Time
Regist_WaterMeter_BillOfficer
Empl_ID RNo MNo

BillOfficer_Report
Report_No ReportType ReportDate EID
Report_BillCollector
Empl_ID RPNo
BillCollector_Bill
Bill_Number EID
Figure 40: Schema Relationship Diagram
~ 61 ~
Algorithm Design
In this part we describe the algorithm of the operations or methods which found in class diagram using Pseudo code.
Pseudo code is one type of algorithm representation method by using English language.
Pseoudocode Customer for registration

Steps/procedure
Method name=apply
Begin
Variable - FirstName
-FatherName
-Cust_ID
-Sex
-Kebele
-HouseNumber
-HomePhoneNumber
- Mobilenumber
If (*inputs are valid*)
Then
Add to table Customer (FirstName, FatherName, Cust_ID, Sex, Kebele, HouseNumber, HomePhoneNumber, and
Mobilenumber )
Otherwise
Display “inputs are not valid try again!”
End if
End
Pseudo code Maintenance order

Steps/procedure
Method name= maintenance Order
Begin
Variables-maintain_No
-type
If (*variables are valid*)
Then
Add to table Maintenance (MaintenanceNumber, Type)
Otherwise
Display “inputs are invalid”
End if
End
~ 62 ~
Pseudo code for login

Steps/procedure
Method name=login
Begin
Variables:-username
-password
(*select the previous username and password from database and compare with entered*)
If username = entered username and
Password = entered password
(*go to login page*)
Otherwise
Display “login error!”
Endif
Otherwise
Display “inputs are invalid try again!”
Endif
End
Pseudo code employee for registration

Steps/procedure
Method name=employee registration
Begin
Variable – Empl_ID
-First_Name
-Father_Name
-OfficePhoneNumber
-MobileNumber
-Position
Then
Add to table employee (Empl_ID, First_Name, Father_Name, OfficePhoneNumber, MobileNumber, and
Position)
Otherwise
End if
End
~ 63 ~
Pseudo code for Update Customer

Steps/procedure
Method name=updateCustomer
Begin
Variable - FirstName
-FatherName
-Cust_ID
-Sex
-Kebele
-HouseNumber
-HomePhoneNumber
- Mobilenumber
Search (*Cust_ID*)
Then
Update table Customer set (FirstName, FatherName, Cust_ID, Sex, Kebele, HouseNumber,
HomePhoneNumber, and Mobilenumber)
Otherwise
End if
End
Pseudo code for Delete Customer

Steps/procedure
Method name=deleteCustomer
Begin
Variable -Cust_ID
Search (*Cust_ID*)
Then
Delete from table Customer (Cust_ID )
Otherwise
End if
End
~ 64 ~
Pseudo code Update for Maintenance order

Steps/procedure
Method name=updateMainOrder
Begin
Variable - Mainten_No
- Type
Search (*Mainten_No*)
Then
Update table Maintenance set (Mainten_No, Type, and Order_Date)
Otherwise
End if
End
Pseudo code for Audit and Analyze

Steps/procedure
Method name=audit||analyze
Begin
Variable - Cust_ID
-First Name
-FatherName
-Bill_No
-PreviousRead
-CurrentRead
-Category
- Total
Search (*Cust_ID*)
Then
Update table Customer_Bill set (Cust_ID, FirstName, FatherName, Bill_No, PreviousRead, CurrentRead,
Category, and Total)
Otherwise
End if
End
~ 65 ~
Pseudo code Register for meter value

Steps/procedure
Method name=audit||analyze
Begin
Variable -Cust_ID
-CurrentRead
-Date
-Category
- Total
Then
Add to table Bill value (Cust_ID, CurrentRead, Date, Category, and Total)
Otherwise
End if
End
~ 66 ~
Bibliography
Sawyer, I. a. Requirement Engineering a good Practice.
Elmasri, R.
FUNDAMENTALS OF DATABASE SYSTEMS. (2003).
~ 67 ~
Appendix A
Questions asked during requirement gathering using interview
Q1. What are the objectives of your organization?

Q2. What is the mission of your organization?
Q3. How many employees do you have?
Q4. How does your current system work?
A. Is it manual?
B. is it computerized?
C. is it semi automated?
Q5. If your answer for question number 4 is choice “b” or “c” what computer applications do you use?
Q6. How you make relationship with the customer?
Q7.What is the procedures or steps when customers get service of the organization?
Q8.What qualifications are expected from a customer who wants to register to the system?
Q9.How does you store customers and other information’s?
Q10.What are the problem that you get when the organization use the existed system?
Q11.How you prepare monthly or annually report?
Q12. What are the employees that included from the system?
Q13. How the bill calculating system was done?
Q14. If there is, what are the hierarchies that the bill system was going on?
Q15. How employees are make relationship with each other to do their task?
~ 68 ~

Industrial Project I Final-Signed

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 I Final-Signed

Uploaded by

Copyright:

Available Formats

PROJECT ON

CUSTOMER MANAGEMENT SYSTEM FOR BAHIR DAR CITY WATER

School: School of Computing and Electrical Engineering

Program: Information Technology

Name of program coordinator Signature

Name of Advisor …Getasew T…………….Signature ……………………………..

Examining committee members signature Date

1. Chairman _____________________ ________________ ____________________

Chapter one: INTRODUCTION

Existing System Study

The following table shows current water meter rent

Statement of the problem

Objectives of the Project

 Study the existing system and find out the problem.

Scope of the project

Data / requirement collection method

System analysis & design methodology

Software tools to be used

Benefit and Beneficiary of the project

Beneficiary of the project

Organization of the Project

Chapter Two: SYSTEM FEATURES

Hardware and Software Requirements

 Commit Bird  Google chrome……..etc

But the system needs to fulfill the following software:

Non Functional Requirements

Audit and Analysis

Delete Customer* «uses» «uses»

Use Case List and Descriptions

Use case name: Apply Registration

Use case name: Login

Use case name: Audit and analysis

Use case name: Bill collect

Use case name: View Message

Use case name: Update customer information

Use case name: Delete customer.

Post condition: The customer will be blocked.

Use case name: Order maintenance

Use case name: Receive maintenance Order

Post condition: Assign technician for the service being transferred.

Use case name: Update maintenance order

Use case name: Meter read

Use case name: Generate report

Use case name: View Report

User Home Page User Login Login

click the login tab

2. click login tab <<creates>>

4. Redirect to the page

Figure 2: Sequence Diagram-Login

Apply Registration:: Basic

Click registration link

fill the required information

4. The reply is send back to customer. Successfully registerd

Figure 3: Sequence Diagram-Apply registration

audit and analyze:

anAccountant auditAnalysis Login Customer payment

Wish to audit and analyse

Enter userName and Password

add the payment and debit value of the customer

Figure 4: Sequence Diagram-Audit and Analysis

aBillCollector billCollector Login Monthly payment

Wish to check the audit

Enter userName and Password

1. Chairman _