Dire Dawa University

Institute of Technology
School of Computing
Department of Computer Science
Project title:-Water Supply management system for dire
dawa city
3rd year section -2 group 3
Name
1. Nesru Abamoga
2. Jamal Abduremen
3. Getachew yeshimwondim
4. wosila Hassan

i
 Chapter One

1. Introduction
As we know, today our world is under the control of technology because of this reason the world
is related each other. Our country is one part of the world but, we are too late according to this
technology as compare as others western countries. Even if our country is not developed in this
project, we try to change the manual service of Dire Dawa city water supply service office
(DDCWSSO) into web-based system using today’s technology. DDCWSSO has many activities.
Such as, Customer registration, calculating bill based on their customer information and the
likes. Because every activity is performed on a paper so, we try to reduce this problem and
enable the office system to have very fast service to their customer by designing web based
service management system for them

1
 1.1. Background of the project

Water supply service enterprises need an effective and accurate customer service management
system to be able to assure their revenue. In today’s world of emerging technologies, companies
are moving their faces towards the Web based customer service management technologies. Web
based customer service management has given both an opportunity and a challenge to traditional
customer service. In the fast growing world Services have to be fast and reliable, which saves
much of our time processing services manually.

In manual way paying bills by paper, recording customer’s information on record folders, are all
time-consuming tasks. Web based customer service automates many of these Processes, saving
time and money. For all governmental and non-governmental companies, web based customer
service is a powerful tool to gain new customers while it helps to eliminates costly paper
handling and manual billing.
Water supply service enterprises have spent years with manual customer service processing, and
this project is developed for Dire dawa city Water supply service to make customer service
management system which is a user friendly, secure and reliable web based customer service
management

1.2. Statement of the problem

Dire dawa water supply and sewerage Authority service office is currently uses a manual service.
As it is manual service, it has its own problems. Like;
 The data will loss and it takes time to recover lost data.
 During requesting complaints, the customers may spend unnecessarily expense and waste
their time.
 The customers may not get the chance to request service of the organization at anytime
and anywhere.
 Documents are easily damaged.
 It may be difficult for customers to get the phone number or the location of the
organization
 It takes time and it may not be easy to manage and analyses the monthly work due to
massive collection of data and the generated report may not be accurate.
 1.3. Objective of the project
The objective of our project can be divided in to general and specific
1.3.1. General objective
The general objective of the project is to develop water supply management system for dire
dawa water supply authority

1.3.2. Specific objective

On the way of attaining the general objective, the project specifically attempts to achieve the
following.
 Gathering information and Analyze the existing system
 Identifying the problem under the existing system
 Specify functional and nonfunctional requirements
 Design a user Interface for the proposed system
 Test and implementation system
 Deploy the implemented system
 Giving training about the developed system.

1.4. Scope of the project and Limitation of the Project

The scope of project is proposed to focus on water billing and customer management web
application and other related services for customers are: -

 Customer registration and retrieval

 Registration of meter reading.
 Registration of the payment.
 Generate Report.
 Bill calculation and printing.
 Maintenance request
 Employee registration

There are many factors that limited us to minimize our scope, such as time limitation, resource,
place, and complexity of the system. In general our proposed system is limited to perform the
following tasks because of the above mentioned factors.
Even though customers can check how much they pay in each month from home they cannot
process payment from home since we do not include online payments It is also does not include
HRM and Other tasks within the organization due to limitation of: - Lack of materials: There is
no enough computer access with internet and lack of books and references used to show how
projects will be done. Shortage of time: We are student and in learning process we have shortage
of time to complete the project in one semester. This enforces our project team to minimize the
project scope. Lack of money: AS we are students it is difficult to spend much amount of money
on the project, so it will limit the effectiveness of the project.

1.5. Significance of the Project

The main Significance of this system as it is computerized web based system reduces the
customers accessing time to get service from the organization.

 It minimizes the customers losing time when they want to access service from the
organization.
 It provides timely information to their employees and also Process Customers request
on time.
 It can easily update customer’s record.
 It can generate appropriate reports automatically.
 Reduce material loss
 It increases performance of the organization
 Enhance employee morale of the organization by providing quality service.
 Improves the confidence of the system users.

1.6. Beneficiaries 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 SWSSO. 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 in them. So, within a short
time it becomes more profitable and famous office across the world.

Beneficiaries of the Project:

For the organization: -

 Save their time and Reduce work loads

 Reduce complexity
 Easily access customers’ information from organized database.
 Control customer’s records and reduce data redundancy for the Customer:
 It provides quick access

For the project developer team.

 The project has initiated our team to get knowledge of how to develop the required
system application.
 While struggling with some difficulties, the team got a lot of experiences of solving
problems.

1.7. Methodology
1.7.1 Data Gathering Methodology
We will use the following methods to collect relevant data required to our project.

Interview: - As an interview, we have contacted the manager of that organization and then
exchanged some ideas of this system how it have been working and the structure of this
organization have in its implementation also the aim of they have to change the current or
manual system to an online system. As a general, we gathered so many data in order to prepare
our project by interviewing them. we will gather necessary information about the background
of the Dire dawa city water supply and sewerage authority organization, their works activities
and the function of their existing system using some structured (when did the Dire Dawa city
water supply and sewerage authority was established, how does the existing system function,
how many customers get services per day, how many employers are there etc.) and unstructured
interview questions from management and workers.

 Observation: We will also arrive to the organization in Dire dawa water supply and
sewerage authority and observe how workers carrying out their work activities in a
natural setting. Observation will allows us to collect data in real time where activities are
being performed.
  Document analysis: - we will also collect certain relevant information from written
documents in the Office. Not only that but also we will tried to review other relevant
documents to develop our project.
 Brainstorming:-we will use our previous experience on the developing of other systems,
thinking and reasoning of real world problems.

1.7.2Development methodology
A software development methodology helps us to structure, plan and control the process of
developing software. There are several software methodologies that can be used in
developing software.
1. Waterfall model
2. Prototyping model
3. Spiral model
4. Iterative model and others.
By comparing the above methodologies our group selects ‘Iterative model’ because this
model is the following advantage
 Generates working software quickly and early during the software life cycle.
 This model is more flexible – less costly to change scope and requirements.
 It is easier to test and debug during a smaller iteration.
 In this model customer can respond to each built.
 Lowers initial delivery cost.
 Easier to manage risk because risky pieces are identified and handled during it’d
iteration.

1.7.3 Development tool

To develop this project some hardware and software tools will needed.
1.9.4.1 Hardware
Name of hardware Use
Desktop Computer or To perform any tasks
Laptop with (RAM
According to [7] a web server that is capable of serving
4.00GB,Storage space
300GB – 500GB , more than 1000 users should have the following
Processor 2.67GHz)
specifications
 Printer To print out the end report of the project
CD For backup the data.
Flash disk 16GB and Store and transfer file
Hard disk 1TB

Table 1: Hardware tools

1.9.4.2. Software
To develop our system we will use the following software tools:-
Software Use

Front end Software Programming Language: PHP, Coding purpose Why PHP?
HTML, JS, CSS
According to [8], there are
several types of web
programming language that are
used for making a site more
dynamic. But, for this project
chooses PHP scripting language
to design this database. Because
It’s fast and easy
It’s cross platform
It accesses everything
It’s free
Back end Software My SQL Database Store data in an organized form
Why MySQL?
According to [9], there are
several reasons to use MySQL.
It’s quick and powerful
It’s improving all the time
It’s free
Handles large database. MySQL
with some database that contains
50,000,000 records and users
MySQL with 60,000 tables and
 about 5,000,000,000 rows. All
columns have default values.
You can use insert a subset of a
table’s columns; those columns
that are not explicitly given
values are set to their default
value.
Wamp Server Package contain PHP and
MYSQL database for storing
data
Windows7, 8.1 and 10 Operating General purpose of computer
System
Microsoft Word Writing the document
Notepad For writing PHP and HTML
code
Browser (Chrome, Mozilla To running and testing our PHP
Firefox 43.0 and Internet and HTML code
Explorer)
E-draw max and Visio 2013 To draw UML
diagrams
Table 2: software tools

1.8Feasibility Study
The feasibility study is the preliminary study that determines whether a proposed system project
is financially, technically and operationally feasible.

1.8.1Economic Feasibility
Economically our project does costly more and also the materials to implement the system will
cost great amount of money, since this project will be computerize the current manual system. So
we will reduce the cost of materials used in manual operation such as paper, pen, human power,
space needed to record, and save data storage & time that we can be induced or bring on during
in the manual system . Here we have stated the costs related to the project and the benefits that
are going to be gained after the completion of the project by performing as a cost benefit
analysis. Let’s start from the cost by classifying them into tangible and intangible.

A) Intangible benefits our system will provide intangible benefits such as: -
• Increase accuracy
• Boost employee moral
• Fast decision making from reports
• It minimizes the work load of the employee
b) Tangible benefit: -Our system will provide tangible benefits such as
• Error reduction
• Material consumption reduction
• Increase speed of activities to the system
 Our system is economical feasible because the cost that we generate in order to develop
our system is less than that of we will get from market after produce this system.
 Once the system is developed the organization will be beneficiary by reducing the
amount of money they rely on the manual system.
 Minimize the payment for the customer that work in the manual system so the
organization is economically feasible.
1.8.2 Technical Feasibility
The system will be developed by following the object oriented system development technique,
and the team will have the ability to develop this system without any difficulty since the team
have studied the required methodologies and have tools for development, and also we will use
currently exist technology’s to perform and to develop the system. So the entire group members
are expected the system will be technically feasible.

1.8.3 Operational Feasibility

Since we will organize friendly user interface any user can easily interact with the system. Also
we will provide a help menu to give direction for users. As the users are almost educated there is
no more complexity to the users.
The system will be secured because of only authorized person can access information due to user
name and password, and also the system will be efficient because to develop this system we will
use object oriented concept due to this we reuse resources.
1.9. Project Plans
1.9.1. Project Time Schedule
Within the time duration, we will have identified the activities of the project in order to
accomplish the project objective within their schedule requirement which is on the table below

Table 3: Time Schedule for Our Project

2013/2021
No Activities June1- June21- July11 August1- August Sept11-
20 july10 -30 20 21-sept- 30
10
1 Information
gathering
2 System
Analyzing
3 System
Design
4 Coding
5 Testing
6 Delivery
1.9.2 Budget Plan
NO Item Description Quantity Price (Birr)
1 Paper 3 360
2 Internet Access --- 100
3 Mobile card --- 300
4 CD 3 75
5 Photo copy 500 500
6 Pen 6 30
7 Flash Disk (16GB) 2 500
TOTAL COST --- 1,865 ETB

Table 5: Budget plan

 Chapter Two
Requirement Elicitation
This chapter contains overview of existing system, business rule, drawback and advantage of the
existing system, proposed and preferred solution, domain modeling with CRC, essential use case
documentation, essential use case diagram and user interface prototype.
2.1. Overview of the Existing System
The main purpose of studying the existing system is to develop a new system which efficiently
performs activities than current one and understanding existing problems. To solve problems
document analysis, form designs, some constraints and rules of the existing system incorporated.
Dire dawa city water supply service office (DDCWSSO) is a water supply office; it is using
Desktop application system for customer information management and bill calculation.
Registration of new customers and bill calculating using by this system. But, the system can’t
generate organized report, when we see how the new customer joins the organization. The report
prepared by paper or manual.
Currently in water supply management system for Dire dawa city water supply authority which
is a customer can pay water billing by going to the office physically and by finding customer
information document manually. Dire dawa city water supply authority currently serves 30,000
customers that connect different parts of the city using 300 operational workers. The number of
customer shows high variability during each periods of time that requires fluctuation of number
of billing payment. This resulted in, the fact that, some customer can’t pay the billing, which
subsequently result in poor performance on resource utilization, number of customers and
service quality: From the interview conducted with the accounting and cashier personnel about
billing policies, they said that the billing procedures start with:
a.) The meter reader reads the water meter of the customer, then submits the meter reading list to
the accounting personnel,
b.) The accounting personnel posts meter readings individually then computes the cubic meter
consumed by every concessionaire and its charge in birr,
c.) After computation, the billing clerk prepares the notices of collection and a summary of bills,
d.) After billing, the Billing Clerk turns over the notices of collection to the accounting
personnel,
e.) Customer pay their water bills to the Cashier, and
f.) The Billing Clerk posts the paid bills based on the Cashier’s official receipt.
Generally system exists in Dire dawa city water billing system is manual which encounter the
following situation
 In existing system, there are various problems like keeping records of items, prices of per
water meter and fixing bill generation on each bill.
 If number of customers is increased some file is missed.
 In order to pay the billing, they have to go to the water office station and this make
customer waste his /her time, waste budget, etc.…
 Customer need to pay cash when they pay bill and sometimes needs to queue up long
time to get the pay the bill.
 When customer go to the water office he /she may face different social problems like
getting conflict with robust
 Existing system is totally on book and those a great amount of manual work has to be
done.
 The amount of manual work increases exponentially with increase in services.
2.2. Advantages of the existing system
The main advantages of the current manually water billing system gives an opportunity for
customer to have a good communication skill. In the existing system the workers only need
writing and reading skill to handle manual data that does not need any knowledge of skill to
register costumer needs and information. There are activities that are considered as strength of
the existing system or practices to be preserved Employee’s data, register form, Bill calculating
formula, Water preservation support agreement and Report generating form. It was easy to
understand and, had clear and precise customer identification/ code. Customer can easily view
and record the different information like card by their mobile devices by capturing a photo or
writing on paper. On the other hand, since, the system stored manually on paper, it did not
depend on on/off or availability of electric service. They also have some special functions like
calling the late payer customer when they going to finish other payment at the end of the month.
In addition it is not must the availability of network service to perform a task searching, storing,
updating data.
 2.3. Drawback of existing system
 The existing system performs manually and this leads to security weakness. Because of
the manual system, is time consuming and boring. This is the result of lack of
computerized system or web-based system. When the project team was analyzing the
existing system, the team has tried to study the detailed nature and procedure of the tasks
and operations performed by the system. It can only provide required information of the
users after a long period of time (takes a lot of time to perform a specific task).
 Time consuming when registered as a customer of the company.
 Time consuming to prepare a bill.
 Input (Inaccurate/redundant/flexible) and Output (Inaccurate)
 Problem in getting monthly (timely) Report about customer, consumption and bill
gaining incorrect customer bill.
Security and Control Storing data is not secure, because the existing system uses access and
excels as a front end. Anyone who opens the computers, in which the system is installed and
used, can access all the contents of the database why because every activity is performed in a
single computer, activities are not secure. It causes dissatisfaction of customer.
2.4. Proposed Solutions
The new system is targeted to address the problem of the current system and to support
additional manipulations or features. Our proposed system will overcome the problems being
faced by the manual management system. The newly proposed system is web based system that
the users can access the web page and can get different services from this website of Dire Dawa
city water supply and authority. The system requires very low system resources and will work in
almost all configurations. It has got following features:
1. Customer can pay the bill over the Internet, 24 hours a day, 7 days a week, and the payment
information cannot be lost, stolen or left behind.
2. Ensure data accuracy.
3. Records are efficiently maintained by DBMS which provides security
4. Any person across the country, having Internet can access this service.
5. Minimum time need for the various processing.
6. Better Service.
7. Minimum time required.
8. This would help the corporation prepare and organize its schedules more efficiently on the
basis of traffic demand.
2.5. Preferred solution
Easy to manage and update: web based systems only need to be installed once on the company’s
server rather than separately installed on each of the end users workstations. This makes any
updates to the web based system quick and easy to roll out. The proposed system has many
applications and advantages compared to the existing system. It solves the problems of the
existing system and increase the performance of the evaluation. In our proposed system, we
develop a web based application water billing system that is capable of controlling. Water billing
system is a web application more reliable and efficient service. Any operations can have done
easily with an easy interaction with the system. Furthermore, the system especially could handle
water bill payment and might calculate the water meter reader to Ethiopian birr more easily than
before the existing system.
The applications of proposed system are:
 Replace the manual to automated system.
 The proposed system enables to the water meter reader to Ethiopian birr and store bill
information in the database.
 The application composes different forms to store data to the database and retrieve required
information from the database.
 Create accounts for different users.
 It provides better and efficient service to the user.
 Reduce the workload of customer, employee, water bill reader and manager, quality
assurance and reform and staff members.
 Faster retrieval of information.
 Provides facility for proper monitoring, reduce paper-based work & provide data security.
 All details will be available in one click with the matter of second.

2.6. Domain Modeling With Class Responsibility Collaborator (CRC) Card

A Class Responsibility Collaborator (CRC) model is a collection of standard index cards that
have been divided into three sections, class, responsibility and collaborator. A class represents a
collection of similar objects, a responsibility is something that a class knows or does, and a
collaborator is another class that a class interacts with to fulfill its responsibilities.
 CRC card
Class
Responsibility Collaborator
What the class knows(Name, ID, Address etc.)
What the class does(class activity).
Table 2. 1: CRC card Customer

- Customer
Responsibility Collaborator
- Name -Cashier
- Take bill
- Pay bill

manager
Responsibility Collaborator
- Name - Customer
- ID - Cashier
Table 2. 2: CRC card for cashier
- Department
- Gender
- Birth place Cashier
Responsibility Collaborator
-- View
Name feedback - Manager
- ID - customer
- Adding information about
billing

- Collect bill payment

Table 2. 3: CRC card for manager

 2.7. Essential Use Case Diagram
A use case diagram is a dynamic or behavior diagram in UML. Use case diagrams model the
Functionality of a system using actors and use cases. Use cases are a set of actions, services, and
functions that the system needs to perform.
Relationships: Illustrate relationships between an actor and a use case with a simple arrow line.
 2.8. Essential use case documentation
Table 1 registration essential use case

Use Case Name Pay bill

Use Case ID UC#1
Brief description This use case represents the procedure which the customer in
charge goes to their information to the water office. It
typically accomplished by specifying customer name and id.
Actor Customer
Pre-condition The customer s must be go to water supply office
Post Condition The customer’s information will be reported as paid
Basic Course of Action 1. the use case starts before payment is done
(BCA) 2. The record officer adds the customer id per year
information to water office as input.
3. The record contains full customer information provided
and amount of bill to be paid.
4. The use case ends when all customer information gets
registered and added successfully.

Table 2 generate report essential use case

Use Case Name Generate report

Use Case ID UC2
Brief description This use case represents also which the manager in charge
accomplishes by generating reports from registration records
Actor Manager
Pre-condition The customer record must be exist in the system
Post Condition The report will be generated for director
Basic Course Of Action 1. The use case starts before payment is done
(BCA) 2. The administrator can generate report to the director as
input for billing payment
3. The director keeps the reports generated for payment
4. The use case ends when director gets all the generated
inputs successfully.
Table 3view bill essential use case

Use Case Name Take bill

Use Case ID UC3
Brief description This use case represents also which the customer in charge
Take his bill to water office
Actor Customer
Pre-condition The payment bill must be announced to watch
Post Condition The payment bill will become viewed.
Basic Course Of Action 1. The use case starts after payment bill become created
(BCA) and added.
2. The clerk in charge, vice customer will get the
payment bill.
3. The payment bills become visible and ready for
usability.
4. The use case ends when the bill is taken successfully.

Table 4 pay bill essential use case

Use Case Name Pay bill

Use Case ID UC4
Brief description This use case represents also which the customer in charge
accomplishes by paying the monthly bill.
Actor Customer
Pre-condition The customer r must go to water office
Post Condition The payment bill receipt will give to customer
Basic Course Of Action 1. The use case starts after the customer go to water office.
(BCA) 2. The administrator in charge will get the reports.
3. The payment bill becomes paid and ready for managing.
4. The use case ends when the payment bill is paid
successfully.
Table 5 View feedback essential use case

Use Case Name View feedback

Use Case ID UC5
Brief description This use case represents also which the manger in charge
accomplishes by seeing and visiting payment bill from.
Actor Manger
Pre-condition The cashier must get reports generated
Post Condition The payment bill reports will become seen after generation
Basic Course Of Action 5. The use case starts after the payment bill View feedback
(BCA) become seen.
6. The administrator in charge will get the bill View
feedback reports.
7. The View feedbacks become visible and ready for
managing.
8. The use case ends when the View feedback report is view
successfully.

Table 6 Manage cashier essential use case

Use Case Name Manage cashier

Use Case ID UC6
Brief description This use case represents also which the manager in charge
accomplishes by managing the cashier details
Actor Manger
Pre-condition The cashier information must be created and added.
Post Condition The cashier will become managed to solve bill reports
generated.
Basic Course Of Action 1. The use case starts after the cashier information become
(BCA) created.
2. The administrator in charge will generate reports on
payment bill
 3. The administrator manages the bill by the reports in
charge.
4. The use case ends when the cashier is managed
successfully.

2.9. Essential User Interface Prototype

In the existing system, they use different forms and reports to manipulate different records
associated with the different activities bill. Among them water billing form is one of the main
paper documents used in the existing system. The form is look like this:

The following are forms and other documents used in the existing system. Contract for supply of
water: date, full name, address, Keeble, house no, placement no, house phone no, mobile no,
email, service type, purpose of water is to be signature, contract no, power approved, application
tariff, purpose of electricity is to be supply, deposit birr, connector birr, total, receipt, customer
sign and authority sign.

The following table shows current tariff of water consumption

Number Consumption Tariff/Birr

1 From 0 - 5 m3 2.90

2 From 5.1 - 10m3 4.40

3 From 10.1 - 25m3 6.10

4 From 25.1m3 and above 8.20

 Water consumption table

CHAPTER THREE
SYSTEM ANALYSIS
3 overview of new system
As previously mentioned in statement of the problem, there are a lot of problems associated
with the current system of the organization. The main aim of the proposed system is to
implement web based water billing and customer service management system for DDCWSSO
which allows easily register customer, maintenance order request, search payment, and generate
report and to overcome the existing system problems.

3.1 System requirement

To distinguish the different features and aspects of the newly developed system we have tried to
use two approaches in requirement specification:
 Functional requirement
 Nonfunctional requirement
. 3.1.1 Functional requirement
Functional requirement describes the interaction between the system and its environment

 Add customer: The system registers applicant’s First name, Last name, Kebele,, House
number, Telephone number and then save to the database.
 Add Employee: The system registers employee’s First name, Last name, position,
telephone number and then saves to the database.
 Customer Maintenance orders: customers get services online by filling his/her ID and
description about the service to be ordered.
 Display customer’s payment information: The system displays customers’ bill detail
when they enter their ID number.
 Display news about the organization: The system can provide different information to
customers and post notices like vacancy announcement.
 Receive maintenance order: The system receives complaint from customers.
  Receive meter reader information: The system receives monthly customers’ water
consumption and calculate the bill.
 setting privilege for employee: the system give different privilege for each actors

 Generate Report: the system generates different reports. Like payment report,
maintenance report.

3.2.2 Nonfunctional requirement

Non-functional (supplementary) requirements relate to other information needed to produce the
correct system and are detailed separately. Constraints on the services or functions offered by
the system such as timing constraints, constraints on the development process, standards, etc.

 Performance:-The system should have a quick response time for a single request made. It
is expected that the software would perform functionally all the requirements that are
specified by the organization
 User interface:-is the design of websites, applications with the focus on the user's
experience and interaction. The system uses user interface design to make the user's
interaction as simple and efficient as possible, in terms of accomplishing user goals what
is often called user-centered design.
 Security and Access permissions: -The system of DBMS should be highly secured and
every users of the system should have their own privilege.
 Backup and recovery: - describe the process of creating and storing copies of data that can
be used to protect against data loss. This is sometimes referred to as operational recovery.
 Usability: Since the system is easily accessed it is easily used everywhere in which
internet connection is available. The application should have a user interface which is
simple to use and negotiable through each page. The system is user friendly.
 Reliability: The system calculates the customer’s bill rent, so it should give accurate
result.
 Supportability: the system can support many customers at a time where internet
connection is available.
 Legal: the system does not break any rules and regulations of the government.
 Storage capability: The system has an ability to store the required information of the
customer in the database.

3.2.3 System usecase diagram

Use Case Name Use Case Identifier Actor of the scenario
Login UC1 Bill-officer,Technician,Customer,
Meter Reader, Accountant
Update customer information UC2 Bill Officer.

Delete customer. UC3 Bill Officer.

Order maintenance UC4 Customer

Receive maintenance Order UC5 Technician

Update maintenance order UC-6 Technician

Meter read UC7 Meter reader

Generate report UC8 Bill officer

Register customer UC9 Customer
3.2.1.1 Use case description and Scenarios

Scenario represents a particular path through a use case or a specific instance of executing a use
case. Each use case encompasses multiple scenarios. Each Scenario involves certain data
combinations and branches takes through the use case execution.
Table 7: Use case description-Login

Use case name Login

Identifier UC1
Actor Bill officer, Technician, Customer, Data encoder, Meter
Reader.
Description A member login to AWSSO uses their appropriate user name
and pasword.
Precondition Must have valid username and password.
Basic course of action 1. Open home page
2. From home page there is login form with sign in button
3. Enter Username and password.
4. System validates the address.
5. User login to the system.
6. End use case.
Alternative action If the user name and password are not correct try again
Post condition The employees enter to the System.

Table 8: Use case description-Update Customer Information

 Use case name Update customer information
Identifier UC2
Actor Bill Officer.
Description Allow to update previously recorded customer data.
Precondition UC1, UC9.
Basic course of action 1. Sign in
2. Enter login address on the homepage.
3. The system should check if it is the correct address or
not.
4. Bill Officer enter customer ID of the intended
customer.
5. The system validates the customer ID.
6. The system searches and display customer details.
7. Bill Officer can modify the customer privileges and
display the information about customer.
8. Logout
9. End use case.
Alternative action If ID is not correct, try again.
Post condition Updated customer data.

Table 9: Use case description-Delete custome

Use case name Delete customer.

Identifier UC3
Actor Bill Officer.
Description Used to block customer from AWSSO system service.
Precondition UC1, UC9.
 Basic course of action 1. Login to the Bill Officer page.
2. Sing in
3. Enter user name and password
4. System validates the address.
5. Search the customer information in their database by
entering their appropriate ID.
6. Block the customer.
7. End use case.
Alternative action If not correct, enter appropriate ID again.
Post condition The customer will be blocked.

Table 10: Use case description Order maintenance

Use case name Order maintenance

Identifier UC4
Actor Customer
Description Allow customer to order maintenance for the office.
Precondition UC1.
Basic course of action 1. Open the homepage
2. Sign in
3. Enter user name and password
4. Customer selects maintenance order form
5. The customer enters their ID.
6. The customer enters maintenance detail in the form.
7. The system responses whether message is transferred
or not.
8. Logout
9. End use case.
Alternative action If the customer ID is not correct, try again and also if the
maintenance order is not correct, reject the order.
 Post condition Maintenance order will be recorded to the system.

Table 11: Use case descriptions-Receive maintenance order

Use case name Receive maintenance Order

Identifier UC5
Actor Technician
Description Assign technician and approve customer maintenance order.
Precondition UC1, UC5.
Basic course of 1. Open the homepage.
action 2. Sign in
3. Enter user name and password.
4. System validates the address.
5. Checks and see the problem and identify the customers who send
the order.
6. Take the order from the customer.
7. Assign technician
8. Logout
9. End use case.
Alternative action If the received maintenance order is not correct then reject the order.

Post condition Assign technician for the service being transferred.

Table 12: Use case description-Maintenance order

Use case name Update maintenance order

Identifier UC6
Actor Technician
Description Update the service order that would maintain.

Precondition UC1,UC5
 Basic course of action 1. Open the homepage.
2. Sign in
3. Enter user name and password.
4. System validates the address.
5. Check the weather the required service is maintained or not
6. If it was maintained report the maintained service
7. Calculate how much it cost to maintain,
8. Transfer the calculated cost to the accountant,
9. Update the received data to permanently
Alternative action If the service is not maintained, try again to check the service.

Post condition Update the maintained service and reassign the technician.
Table 13: Use case description-Meters read.

Use case name Meter read

Identifier UC7
Actor Meter reader
Description Read the value from Meter Reader (Machine).
Precondition know previous reading value
Basic course of action 1. Read the value from the meter reader
2. Take the data to the system
3. Open the homepage.
4. Sign in
5. Enter user name and password.
6. System validates the address.
7. meter reader Click meter read value link, Enter the value that
he/she read and Click send button
8. logout
9. End use case.

Alternative action If the meter reader has not read correct information he/she read
again.
Post condition Transfer the reading value to the system.
Table 14: Use case description-Generate Report

Use case name Generate report

Identifier UC8
Actor Bill officer
Description Generate report that was done monthly in the form of printable
data.

Precondition UC1, UC7

Basic course of action 1. Open the homepage
2. Sign in
3. Enter user name and password
4. System validates the address.
5. Click report link
6. Select report type that wants to generate then click
preview.
7. Click print button, logout, End use case.
Alternative action If the selected report is not correct then it does not display
anything through report.
Post condition Generate report.

Table 15: Use case description-Register Customer

Use case name Register customer

Identifier UC9
Actor Bill Officer
Description Register customer who don’t use the online request methods
Precondition UC1
Basic course of action 1. Open the homepage
2. Sign in
3. Enter user name and password
 4. System validates the address.
5. Click Customer Registration link
6. Fill Necessary information of the
customers.
7. Click register button.
8. Logout and End use case.

Alternative Action If the filled information is not correct, the system must display
the error message and recommended to fill the information
again.
Post condition Register customer.

igure 1: Class diagram

3.2.3 Dynamic model

3.2.3.1 Sequence Diagram

Sequence diagram is to provide a graphical representation of object interactions over time.
This typically to show a user or actor and the objects and components they interact with in the
execution of a use case. One sequence diagram typically represents a single use case scenario or
flow of events. The diagram shows the flow of message from one object to another and as such
correspond to the method and event supported by a class or object
Figure 2: sequence diagram for login
Figure 3: sequence Diagram to order maintenance
Figure 4: Sequence Diagram-Generate Reports
Figure 5: Sequence Diagram-Receive Maintenance Order
Figure 6: Sequence Diagram-View Message
3.2.3.2 Activity Diagram
Activity diagrams model is a high level business or processes or transitions between
states of a class. In this activity diagram tries to document the flow of logic for the major
business processes.

Figure 7: Activity Diagram for Login

Figure 8: Activity Diagram for maintenance order

Figure 9: Activity Diagram for receive maintenance order

Figure 10: Activity Diagram for generating report

Figure 11: Activity Diagram for assigning technician

Figure 12: Activity Diagram for Read meter

Figure 13: Activity Diagram for view massage

3.2.2.1 Class Diagram

Class diagrams shows the static structure of the model, in particular, the things that exist
(such as classes and types), their internal structure, and their relationships to other things. This
project used class diagram to design the structures that will be included in the system and the
things that will be exist in the system. Our class diagram includes different tables. Such as
customer, employee, maintenance, report, massage, registration, bill officer, meter reader,
accountant, technician and data encoder are inherited classes from employee.