Professional Documents
Culture Documents
Customer Management System For Bahir Dar City Water Supply Service (Shumaboo Branch)
Customer Management System For Bahir Dar City Water Supply Service (Shumaboo Branch)
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
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
------------------------------------- ---------------------------------------------
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.
------------------------------------- ---------------------------------------------
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
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~3~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Specific Objective
Here are some specific objectives that would together help us achieve the overall the project as follows:
Methodology
~5~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~7~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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
~8~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Use case Diagram
*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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 13 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 14 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Post condition: The accountant takes the payment from customers according to the calculated bill value,
audit and transfer to the bill collector.
~ 15 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 16 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Post condition: Update the maintained service and reassign the technician to the unsolved service.
~ 17 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 19 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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.)
~ 20 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 21 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Figure 3: Sequence Diagram-Apply registration
~ 22 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 23 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 24 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 25 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 26 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 27 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 28 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 29 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 30 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 31 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 32 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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.
~ 33 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 34 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 35 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 36 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 37 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 38 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 39 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 40 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 41 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 42 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 43 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 44 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 45 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 47 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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
~ 48 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Database Design
~ 49 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 50 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
User interface is the external part of the system which is used to access and interact with the system
easily.
~ 51 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
(B) UI- Customer Registration
~ 52 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 53 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 54 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
(H) UI- Bill Interface
~ 55 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 56 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 57 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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
Empl_ID Name Sex Position Tell_No
Bill Officer
Empl_ID Name Position Position Tell_No
Bill Collector
Empl_ID Name Sex Position Tell_No
Technician
Empl_ID Name Sex Position Tell_No
Bill
Bill_Number Previouse read Current read Consumption Category Total
Report
Report_No ReportType ReportDate
~ 59 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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
Employee
Empl_ID Name Sex Position Tell_No
First normal form (remove multi valued attributes)
Empl_ID First Name Father Name Position
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 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Cust_Maintenance
CID MID Order _Date
Maintenance
Maintain_ID Type
Main_Technician
Empl_ID MID
Cust_Message
Msg_No Msg_Type CID Cust_Cus Relation
Empl_ID CID
Cust_Water Meter
Empl_ID MNo
Registration
Reg_No Date Time
Regist_WaterMeter_BillOfficer
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.
~ 61 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
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
~ 63 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Search (*Cust_ID*)
If (*inputs are valid*)
Then
Delete from table Customer (Cust_ID )
Otherwise
Display “inputs are not valid try again!”
End if
End
~ 64 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Search (*Mainten_No*)
If (*inputs are valid*)
Then
Update table Maintenance set (Mainten_No, Type, and Order_Date)
Otherwise
Display “inputs are not valid try again!”
End if
End
~ 65 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
~ 66 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Bibliography
Sawyer, I. a. Requirement Engineering a good Practice.
Elmasri, R.
FUNDAMENTALS OF DATABASE SYSTEMS. (2003).
~ 67 ~
CMS for Bahir Dar City Water supply Service (Shumaboo
2013
Branch)
Appendix A
~ 68 ~