HARAMAYA UNIVERSITY

College of Computing and Informatics

Department of Information Systems

Project Report
Title: Haramaya Town Planning and Development System

Group Members

Name ID

1. Kebede Tegene……………………………617/08

2. Zegaye Tafese……………………………..641/08

3. Rabia Ahmed………………………………635/08

4. Eden Yehualashet…………………………594/08

ADVISER BY:

Dr. Zafar Ahmed Sheik

Supervisor Affiliation
June 21, 2019
 HARAMAYA UNIVERSITY
College of Computing and Informatics

Department of Information Systems

CERTIFICATE
This is to certify that the work embodies in this project entitled “Haramaya Town
Planning and Development System” being submitted by following students for
partial fulfillment of the requirement to ―Haramaya University‖ during the
academic year 2018-19 is a record of bonafide piece of work, carried out by them
under my supervision and guidance in the “Department of Information Systems”,
College of Computing and Informatics.

Name ID

1. Kebede Tegene 617/08

2. Zegaye Tafese 641/08
3. Rabia Ahmed 635/08
4. Eden Yehualashet 594/08

ADVISER BY: CO ADVISER BY:

Dr. Zafar Ahmed Mr. Tagir Amin

Assistant Professor Instructor at HU

Head of Department

Mr. Beyene Bedasa

Head of Department of Information System

II
 HARAMAYA UNIVERSITY
College of Computing and Informatics

Department of Information Systems

CERTIFICATE OF APPROVAL

The project report entitled “Haramaya Town Planning and Development system‖
being submitted by following students has been examined by me/us and is hereby
approved for project work which it has been submitted. It is understood that by this
approval the undersigned do not necessarily endorse or approve any statement
made, opinion expressed or conclusion drawn therein, but approve the project
report only for the purpose for which it has been submitted.
Name ID

1. Kebede Tegene 617/08

2. Zegaye Tafese 641/08
3. Rabia Ahmed 635/08
4. Eden Yehualashet 594/08

APPROVED & ADVISER/ CO ADVISER BY:

Name: Dr. Zafar Ahmed Sheik Name: Mr. Tagir Amin

Signature_____________ Signature___________

III
Acknowledgment
First and for most we would like to express our special thanks to almighty God for helping us
through all our steps start and finish of our work in such beautiful manner. Then we would like
to thank our advisor, Dr. Zafar Ahmed Sheik for the valuable guidance and advice. He inspired
us greatly to work in this project; his willingness to motivate us contributed tremendously to the
project and at the same time we would like to thanks to project co-adviser Mr. Tagir Amin for
his advice and guidance. Also, we would like to thank Mr. Beyene Bedasa; Information System
Department Head for his encourage to developing this project.

Last but not list our thanks for the employee of Haramaya town planning and development office
for giving us the necessary information about how the current system works.

IV
Table of Contents
CERTIFICATE .......................................................................................................................................... II
CERTIFICATE OF APPROVAL ........................................................................................................ III
Acknowledgment ......................................................................................................................................... IV
Abstract ......................................................................................................................................................... X
CHAPTER ONE ........................................................................................................................................... 1
1. Introduction ........................................................................................................................................... 1
1.1. Background of the Organization ................................................................................................... 2
1.2. Statement of the problem .............................................................................................................. 2
1.3. Objective of the project ................................................................................................................. 3
1.3.1. General Objective ................................................................................................................. 3
1.3.2. Specific Objective.................................................................................................................. 3
1.4. Methodology ................................................................................................................................. 3
1.4.1. Fact finding techniques ......................................................................................................... 3
1.4.2. System analysis and design techniques ................................................................................. 4
1.4.3. Tools used in the project ....................................................................................................... 4
1.5. Scope of the Project ...................................................................................................................... 5
1.6. Significance of the Project ............................................................................................................ 5
1.7. Feasibility Study of the new System ............................................................................................. 5
1.7.1. Operational Feasibility ......................................................................................................... 6
1.7.2. Technical Feasibility ............................................................................................................. 6
1.7.3. Economic Feasibility............................................................................................................. 6
1.7.4. Schedule Feasibility .............................................................................................................. 7
1.8. Management Issue ........................................................................................................................ 7
1.8.1. Team configuration and management ................................................................................... 8
1.8.2. Communication plan ............................................................................................................. 8
1.8.3. Change management ............................................................................................................. 9
1.9. Limitation...................................................................................................................................... 9
CHAPTER TWO ........................................................................................................................................ 10
2. MODELING AND PROTOTYPING ................................................................................................. 10
2.1. Description of existing system .................................................................................................... 10
2.1.1. Problems of existing system ................................................................................................ 10

V
 2.2. Proposed system.......................................................................................................................... 12
2.3. Functional requirement ............................................................................................................... 12
2.4. System Requirement Specification and Analysis Modeling (SRS) ............................................ 12
2.5. Class Responsibility Collaboration Diagram (CRC) .................................................................. 12
2.6. Use case modeling ...................................................................................................................... 16
2.6.1. Essential Use Case .............................................................................................................. 16
2.6.2. System Use Case ................................................................................................................. 20
2.7. Features ................................................................................................................................... 31
2.8. User interface prototyping ...................................................................................................... 32
2.8.1. Traditional user interface prototyping ................................................................................ 32
2.8.2. User-Interface Flow Diagramming..................................................................................... 33
2.9. Supplementary specification ................................................................................................... 33
2.9.1. Business rules...................................................................................................................... 33
2.9.2. Non-functional requirement ................................................................................................ 35
2.10. Constraints ..................................................................................................................................... 35
CHAPTER THREE .................................................................................................................................... 36
3. Design Document................................................................................................................................ 36
3.1. Classes-type layered approach .................................................................................................... 36
3.2. Class Modeling ........................................................................................................................... 37
3.3. Sequence Diagram ...................................................................................................................... 39
3.4. Activity Diagram ........................................................................................................................ 43
3.5. User Interface Design.................................................................................................................. 47
3.5.1. Form Design ....................................................................................................................... 47
3.5.2. Dialogue and Interface Design ........................................................................................... 49
3.6. State Chart Diagram .................................................................................................................... 50
3.7. Object Diagram ........................................................................................................................... 52
3.8. Persistence modeling/ Database Design ..................................................................................... 53
3.9. Component Diagram ................................................................................................................... 60
3.10. Deployment Diagram .............................................................................................................. 60
CHAPTER FOUR....................................................................................................................................... 62
4. Implementation Document .................................................................................................................. 62
4.1. Report on Implementation .......................................................................................................... 62

VI
 4.3. Testing......................................................................................................................................... 81
4.3.1. Unit testing .......................................................................................................................... 81
4.3.2. Integration testing ............................................................................................................... 81
4.3.3. System testing ...................................................................................................................... 81
4.4. Conclusion .................................................................................................................................. 82
4.5. Clients Feedback ......................................................................................................................... 83
4.6. User Manual Preparation ............................................................................................................ 83
Appendix ..................................................................................................................................................... 88
Reference .................................................................................................................................................... 89

List of Figures
Figure 1: Gantt chart for time Schedule ........................................................................................................ 7
Figure 2: CRC Diagram for Actor Class ..................................................................................................... 14
Figure 3: CRC Diagram for User Interface Class ....................................................................................... 15
Figure 4: CRC Diagram for Business Class................................................................................................ 15
Figure 5: Essential Use Case...................................................................................................................... 16
Figure 6: System Use case .......................................................................................................................... 20
Figure 7: Login form traditional UI ........................................................................................................... 32
Figure 8: Create User account traditional UI .............................................................................................. 32
Figure 9: User interface flow diagramming ................................................................................................ 33
Figure 10: Class type layered approach ..................................................................................................... 36
Figure 11: Class Diagram for HTPDS ....................................................................................................... 38
Figure 12: Sequence diagram for login ................................................................................................... 39
Figure 13: Sequence diagram for add user ............................................................................................... 40
Figure 14: Sequence diagram for prepare sector plan ................................................................................ 41
Figure 15: Sequence diagram for send plan ............................................................................................... 42
Figure 16: Activity diagram for login ........................................................................................................ 43
Figure 17: Activity diagram for work plan preparation ............................................................................. 44
Figure 18: Activity diagram for send plan .................................................................................................. 44
Figure 19: Activity diagram for manage plan ............................................................................................ 45
Figure 20: Activity diagram for manage account ....................................................................................... 46
Figure 21: User registration form................................................................................................................ 48
Figure 22: Home page design ..................................................................................................................... 48
Figure 23: Login form................................................................................................................................. 49
Figure 24: Error popup message ................................................................................................................. 49
Figure 25: state chart diagram for login ..................................................................................................... 50
Figure 26: state chart diagram for search plan ........................................................................................... 51

VII
Figure 27: Object diagram ......................................................................................................................... 52
Figure 28: Persistent Database Diagram .................................................................................................... 59
Figure 29 Component Diagram ................................................................................................................... 60
Figure 30: Deployment Diagram ................................................................................................................. 61
Figure 31: actual system home page .......................................................................................................... 84
Figure 32: actual system login page ............................................................................................................ 85
Figure 33: actual system sector plan form.................................................................................................. 86
Figure 34: sector project list ....................................................................................................................... 87

List of Tables

Table 1: Tools used in the project ................................................................................................................. 4

Table 2: Project Team members with their Responsibility .......................................................................... 8
Table 3: Use case description for Prepare work plan .................................................................................. 17
Table 4: Use case description for Submit Plan............................................................................................ 17
Table 5: Use case description for Prepare General Strategic plan .............................................................. 18
Table 6: Use case description for Manage development Plan ................................................................... 18
Table 7: Use case description for Generate Report..................................................................................... 19
Table 8: Use case description for Login ..................................................................................................... 21
Table 9: Use case description for Manage Account.................................................................................... 22
Table 10: Use case description for View Town development plan............................................................. 23
Table 11: Use case description for Upload Information ............................................................................. 24
Table 12: Use case description for manage Complaint .............................................................................. 25
Table 13: Use case description for View Report ........................................................................................ 26
Table 14: Use case description for Manage Notification ............................................................................ 27
Table 15: Use case description for Prepare Work Plan............................................................................... 28
Table 16: Use case description for Send Work Plan .................................................................................. 29
Table 17: Use case description for Generate Report ................................................................................... 30
Table 18: Use case description for Manage Staff ....................................................................................... 30
Table 19: Database Tables .......................................................................................................................... 53

VIII
List of Acronyms
BC…………………………………... Business Class

BR………………………….............. .Business Rule

CRC……………………….………….Class Responsibility Collaboration

CSS…………………………………..Cascading Style Sheet

DB…………………………………..Database

DBMS……………………………....Database Management System

FK...………………………….……. Foreign Key

GUI………………………………. .Graphical User Interface

HRM……………………………….. Human Resource Management

HTML…………………………….. Hyper Text Markup Language

HTPDS………………………….. ..Haramaya Town Planning and Development System

HTTP……................................... .Hyper Text Transfer Protocol

PHP…………………………… ….Hypertext Preprocessor

PK………………………………...Primary Key

SRS………………………………..System Requirement Specification

TCP/IP…………………………….Transmission Control Protocol/Internet Protocol

UI…………………………………User Interface

UML……………………………... Unified Modeling Language

IX
Abstract
The System so called HTPDS (Haramaya town planning and development system) is conducted
for town development sector like Education sector, Electricity sector, Road construction sector,
Sanitation clearness sector, water sector, Healthy sector and etc. and for the office of town plan
developing to facilitate the work between town development sectors and town planning office.
The aim of this project is to automate and solve the planning and development related task
problem which faces Haramaya town planning and development office employee.

This documentation contains three chapters. Chapter one deals with introduction of the project,
background of the organization, objective of the project, statement of the problem, scope and
methodology of data gathering. And the Next chapter also deals with the description of the
existing system, functional and non-functional requirement of the system and use-case modeling
with its description. Finally the last chapter contain UML diagram and also included persistent
/Database diagram.

X
CHAPTER ONE

1. Introduction
Technology is spreading its wing in almost every walks of human life activities. Now a day it is
better if every activity is done using new technology in order to fulfill the need of human being,
Organization, Enterprise etc. As today’s world there are many organizations and each
organizations needs to be preferable, computable and work on fastest way in order to satisfy
users interest etc. i.e. they should have facilitate their activities in computerized way.

The project so called ―Haramaya town planning and development system‖ is available in
Haramaya town. Town Planning and development involves both control of existing and new
development, and "strategic planning" to ensure town resources are carefully managed to match
community’s future needs and expectations. Now Haramaya town planning and development
system is going on manually. Because of this manual system there are so many difficulties on its
progress in terms of effectiveness and efficiency. Because of the weakness of existing system we
are going to develop web based Haramaya town planning and development system that
overcomes the problem of the existing system.

The project so called HTPDS (Haramaya town planning and development system) is conducted
for town sector development like Education sector, Electricity sector, Road construction sector,
Sanitation clearness sector, water sector, Healthy sector and etc. and for the office of town plan
developing for the above sectors to facilitate the work between town development sectors and
town planning office.

1
 1.1. Background of the Organization
Haramaya is a town in east-central Ethiopia which is located in the east Hararghe Zone of the
Oromia Region. The town has a latitude and longitude of 9°24′N 42°01′ECoordinates:
9°24′N 42°01′E with an elevation of 2047 meters above sea level. The town is about 500km east
from the national capital Addis Ababa and 10km west of Harar, on the road to Dire Dawa. Also
it is located on Lake Haramaya which a seasonal freshwater lake which supports a population
of flamingo, as well as other birds.

Based on figures from the Central Statistical Agency in 209, Haramaya has an estimated total
population of 45,317 of whom 22,796 are men and 22,521 are women. The 1994 national census
reported this town had a total population of 10,560 of whom 5,228 were males and 5,332 were
females. It is the largest of three towns in Haramaya woreda.

1.2. Statement of the problem

Currently Haramaya town planning and development office is facing many problems due to the
use of manual handling system in day to day activities. The problems that can be taken from
planning and development office in Haramaya town planning and development office are:-

 Need more effort and time to record the work in the plan office and development sector.
 The development sectors cannot get the response on time.
 Lack of an automated report generation.
 Information cannot reach on time to the employee of the office, because in the existing
system, information is posted on notice board or on any other manual way.
 Damage data easily.
 Difficult to retrieve any information related to town plan and development.
 Taking care of the town is difficult due to the manual system.

2
 1.3. Objective of the project

1.3.1. General Objective

The main objective of this project is develop a new Web Based Planning and Development
System for Haramaya town which solve the above mentioned problems with the existing system.
This is achieved by designing a web based application program that change the actual manual
processing into a computerized environment.

1.3.2. Specific Objective

 To reduce the time, cost and man power needed to job performance.
 To manage information that is related with town planning and development.
 To facilitate the communication between the town planning office and town development
sectors.
 To design an efficient, reliable and effective database to solve the problem of the existing
manual Record system.
 To minimize the work load of the employees.
 To develop general strategic plan for Haramaya town with in the short time.

1.4. Methodology
1.4.1. Fact finding techniques
The data collection instruments used to gather accurate information about the existing system
and the requirements for the new system. So to gather the information about the existing system
we have used primary data collection method such as interviews and observation and also we
have used secondary data collection method like review existing document.
To get a precise data, the team member has used the following data collection techniques. Those
are: -
A. Interview: - to get the basic information and background information about the existing
system, the team members has interviewed the employees of the office to know the
problems associated with that environment.
B. Direct observation: even though interview is very important to gather information,
direct observation is simple and physically we observe manual working system.
C. Existing document: To get more information about the existing system we use earlier
documents that are stored in town planning and development office. During the analysis

3
 of documents, we give a special consideration to those documents which can bring more
features to the project.

1.4.2. System analysis and design techniques

Here for the analysis of our project we have selected object oriented system analysis and design
method specifically UML (Unified Modeling Language) model because of the following
advantages:-
 To simplify the design and implementation of complex program.
 To make it easier for teams of designers and programmers to work in a single software
project.
 To enable a high degree of reusability of designs and of software codes.
 Increase reusability.
 Reduce maintenance burden.
 Increased consistency among analysis, design and programming activities.
 Improved communication among users, analysis, design and programming.

1.4.3. Tools used in the project

While developing the project starts from the documentation to the implementation we use the
following case tools:
Table 1: Tools used in the project

Activities Tools
Documentation MS word 2007,2010,2013,2016
Design Edrawmax, Visual paradigm for UML
standard design
Script languages PHP, JavaScript, CSS, HTML
Web server Apache Xamp server
Data base Server Mysql database

4
 1.5. Scope of the Project
Since Haramaya town planning and development performs its basic tasks manually. So the scope
of this project is to develop and implement a new web based Haramaya town planning and
development system which will avoid the problems associated with the manual processing.
The proposed system includes the following scopes:-
This online Town planning and development system enables system administrator to manage
user account.

 It enables system admin to manage town strategic plan.

 It enables town development sectors to prepare their own work plan structure.
 It allows planner to access detail information about town development sector’s plan and
analysis the plan to develop general town strategic plan for all sectors.
 It allows planner to plan the budget for strategic plan.
 It allows town development sectors to generate performance report online.
 Admin can view all information about past, current and future plan of town development
sectors.
 Admin can post information about town planning and development.
 Admin can manage complaint.

1.6. Significance of the Project

The new online Haramaya town planning and development system is highly reliable, easy, fast
and consistent and will play a crucial role for reliable service for the employee. The significance
of the system includes:
 To minimize time and efforts needed to perform tasks.
 To make tasks simple and efficient in every aspects.
 Providing a well-organized and guaranteed record keeping system with minimum space and
effort need.
 Developing effective communication between employees.

1.7. Feasibility Study of the new System

Feasibility study is essential to evaluate the cost and benefits of the new system. On the basis of
the feasibility study decision is taken on whether to proceed or to cancel the project.
Need of the feasibility study:

5
  It determines the potential of the existing system.
 It used to determine/finds out the problem of the existing system.
 To determine all goals of the new system.
 It finds all possible solutions of the problems of the existing system.

1.7.1. Operational Feasibility

The system requires very less human power. It provides simple user interface in which the
employee of office can access easily, and more accurately. Maintenance is less and easy. The
system will have GUI interface and very less user-training is required to learn it. The system is
so simple to use, so no any special skills will be required to use the system. So the system is
operationally feasible.

1.7.2. Technical Feasibility

The system to be developed by using technologically system development techniques such as
PHP, Java script, css and Mysql database without any problems and the group members have
enough capability to develop the project. So the system will be technically feasible.

1.7.3. Economic Feasibility

The system to be developed is economically feasible and the benefit is outweighing the cost.
Since this project already computerizes the existing system, by now the reduction of cost for
materials used in manual operation becomes beneficiary to the organization.
Generally the system that we developed, HTPDS brought a number of tangible and intangible
benefits.
Tangible benefits:
1. Cost Reduction
2. Error Reduction
3. Increase Speed of activity
Intangible benefits:
1. Reduce Resource Consumption
2. Increase security
3. Increase Management flexibility

6
 1.7.4. Schedule Feasibility
Schedule feasibility defines the starting and ending date of the project and manages duration of
activities until the given project is finished. The starting date of the project is Nov 25, 2018 and
the ending date of the project is June 21, 2019. So the schedule for this project will be feasible
due to proper information exchange between the developing team and the Advisor. We will do
all the tasks in this project according to a prescheduled plan specified in the below chart.

Figure 1: Gantt chart for time Schedule

1.8. Management Issue

Management issue is concerned about the team members and the way in which we are going to
use our effort on the system and a plan how we go with time based on the schedule to
accomplish within the time we have.

7
 1.8.1. Team configuration and management

Table 2: Project Team members with their Responsibility

Haramaya Town Planning and Development System

S.No Name ID NO. Email Address Responsibilities

-group Coordinator
1. Kebede Tegene 617/08 [email protected] -documentation
-Implementation
641/08 [email protected] -requirement analysis
2. Zegaye Tafese -Data gathering
Rabia Ahmed [email protected] -Data gathering
3. 635/08 -Requirement analysis

4. Eden Yehualashet 594/08 -Designer-

[email protected] -Testing

1.8.2. Communication plan

Our team member communicates with each other by discussing on the issues in general. Some
communication ways that takes place between in our team members are:

 We design our work on paper before writing on the system.

 We divide and do a separate task to facilitate the project to proceed based on the
schedule.
 We contact our advisor regularly (necessarily ones a week) to submit the progression of
work
 We contact our adviser irregularly (any times) to ask questions related to the project
development, to get advice and to get information related to our system.

8
 We contact our adviser as well as our group member by using the following communication
media:

 Email
 Phone
 Physical communication

1.8.3. Change management

Change management is an approach to transitioning individuals, teams to a desire future state.
And it is about how we group members are responsible for controlling change processes within
the project’s scope. As a group member we have the following rules and regulations for the
performance of our project:

 All of our group members have the responsibility in all activities of the project.
 If we want to update any part or our advisor tell us to update the part, all of group
members should discuss for any changes.
 Any member has a right to express his idea freely.
 We should use our resources properly such as budget, software, and another material.

Generally our project has its own rules and regulation in which all group members have to
accumulation accordingly to respond for any changes.

1.9. Limitation
 In case of Luck of time we have not done
 Google map for the planned area
 Some reports

9
CHAPTER TWO

2. MODELING AND PROTOTYPING

2.1. Description of existing system

The existing system of Haramaya town planning and development system is manually operated.
Different activities are performed as follows; Town development sectors like water sector,
electricity sector, road construction sector, Education sector, Healthy sector, sanitation clearness
sector and etc. are prepare their own work plan structure manually and then development sectors
submit their work plan structure to the town planning office. Also at the same time development
sectors submit their work plan to the town administration office to get approval. Again town
administration office approves the submitted work plan structure for each sector and sends it to
the town planning office manually. Town planning office prepares the general work plan
structure for all development sectors manually and town planning office submits the general
strategic plan to town administrating office by going to office physically. Then admin approves
the plan and distribute it to all sectors manually. And also information and report is generated
manually between town planning office, town administration office and town development
sectors.

Since the existing system is a manual system it is time taking, unqualified, costly and not
satisfactory because the system is not computerized system for town planning and development
purpose. Town development sectors are spend much time to prepare their own work plan due to
all activities are done manually by paper-based method and they must physically join town
planning office and town administration office to submit their work plan structure. So this
system consumes time and money.

2.1.1. Problems of existing system

Problems are undesirable situations that hinder the organization from fully achieving its purpose,
goals or objectives. The manual Haramaya town planning and development system is disposed to
various problems. These problems can be seen from the following perspectives like performance,
information, economic and efficiency.

10
Performance issue: The performance of any system is required to show to meet the needs of
users of that system. The current system’s performance is weak. This is due to the following
reasons: -
 The acceptable quantity rate is relatively high i.e. the time required from initiation to
completion of a particular task is relatively long. For example during preparation of
work plan structure for the town development is take about a month or more due to
its manual operation.
 The response time for a particular task is long. Example town development sectors
wait more than a month to get response from town planning office.

Information
 Inaccuracy- updating important information is not accurate because of manual
processing.
 No database completely – No computerized data gathering, storing, processing and
disseminating facilities.
 Data is stored repeatedly in different files – The same information is stored in many
copies repeatedly in different forms.
Economic- since all activities related with town planning and development are performed with
the use of paper, the expenditure for the paper is very high. And also the manual system requires
many employees to perform the activities related with town planning and development, so the
salary being paid to those employees is very high.
Efficiency- employees of the office wastes a lot of time:
 To prepare town work plan structure
 To plan the budget for each town development sector
 To generate report.

11
 2.2. Proposed system
Improve the current/existing manual system of Haramaya town planning and development, we
have done new system which called Haramaya town planning and development system HTPDS.
The newly proposed system is efficient in facilitating the tasks like preparation of town
development plan, budget plan for town development sector and report generating.

2.3. Functional requirement

Functional requirements capture the intended behavior of a system and it defines what a system
is supposed to do.

The following are the functional requirements of the new system.

 The system should display or upload the information about town planning and
development.
 The system should prepare town development plan.
 The system should distribute budget for each town development sector.
 The system should generate timely report about the prepared structured plan and
performance status of town development sectors.
 The system should store all the data related with all the tasks performed in town planning
and development office into a database.
 The system should support two languages; Oromic and English

2.4. System Requirement Specification and Analysis Modeling (SRS)

SRS is a document that completely specifies what the proposed system should do without
describing how the system will do it.

2.5. Class Responsibility Collaboration Diagram (CRC)

Class responsibility collaboration diagram (CRC) shows the classes of the system, their
interrelationships, and the operations and attributes of the classes. Class-responsibility-
collaborator cards (CRC cards) are not a part of the UML specification, but they are a useful tool
for organizing classes during analysis and design. Class responsibilities are the class's attributes
and methods. Clearly, they represent the class's state and behavior. (1)Collaborators represent the
associations the class has with other classes. Classes are shown as boxes with three sections:

 Top for the name of the class,

12
  Left for the attributes,
 Right for the operations.

Associations between classes are depicted as lines between classes. We will draw the class
diagrams in the next chapter, now we identify the class responsibility and the collaborators for
that class.

Here the following diagram is diagrams of CRC (class responsibility collaborators).A CRC
model is a collection of standard index cards that have been divided into three sections

 Class – collection of similar objects

 Responsibility – something that a class knows or does
 Collaborator - another class that a class interacts with it to fulfill its responsibilities

So we can classify the classes in to three:

Actor class: actors that appear in a use case like. People or organization

 Admin
 Development sectors
 Planner
 Manager
 HRM

User interface class: screens, menus,

 Login for
 Registration page
 Plan preparation form
 Send complaint form
 Post notification form
 Upload information form
 Assign budget form
 Report generation form

Business class: places, concepts, and events that describe what the business is all about including

13
the database information.

 Account
 Strategic plan
 Complaint
 Notification
 Report
 Information
 Registration

Figure 2: CRC Diagram for Actor Class

14
 Figure 3: CRC Diagram for User Interface Class

Figure 4: CRC Diagram for Business Class

15
 2.6. Use case modeling
The Use Case Model describes the proposed functionality of the new system. A Use Case
represents a discrete unit of interaction between a user (human or machine) and the system. It is a
single unit of meaningful work. (2) Each Use Case has a description which describes the
functionality that will be built in the proposed system. It has two types:
 Essential use case
 System use cas

2.6.1. Essential Use Case

It is known as bussiness or abstract use case. Intended to capture the essence of problems
through technology free, idealized and abstract descriptions.

Figure 5: Essential Use Case

16
 2.6.1.1. Essential Use Case Description
Table 3: Use case description for Prepare work plan

Name Prepare work plan

Id UC-01
Actor Town Sector
Description Each town sectors should prepare their own work plan.
Precondition They should know all works which include in their plan.
Basic course of 1. Town sectors want to prepare their work plan.
action 2. Review previous plan which is used as an input for the new plan.
3. Buy the material which is used for plan preparation example paper.
4. Create the form of plan on the provided paper.
5. Fill the provided paper form properly.
6. Use case ends.

Table 4: Use case description for Submit Plan

Name Submit plan

Id UC-02
Actor Town sector and planner
Description Each town sectors should submit their work plan to manager for general
town development plan preparation and planner submit town development
plan to manager..
Precondition They should know submission date.
Basic Course of 1. Town sectors or planner want to submit plan to manager.
action 2. Get notification of plan submission date from notice board or other
3. Search the plan to be submitted from paper based file storage.
4. Town sector or planner physically goes to manager office to submit the
plan.
5. plan is submitted.
6. Use case ends.

17
 Table 5: Use case description for Prepare General Strategic plan

Name Prepare General strategic plan

Id UC-03
Actor Planner
Description Planner prepare General strategic plan for town by analyzing town
sector’s plan
Precondition town sector work plan should be approved by manager
Basic Course of 1. Planner wants to prepare general strategic plan for the town.
action 2. All material should be ready for preparation of plan example paper.
3. Create plan preparation paper based form.
4. Fill the provided paper based form properly.
5. General strategic town plan is prepared.
6. Use case ends.

Table 6: Use case description for Manage development Plan

Name Manage development Plan

Id UC-04
Actor Manager
Description Manager manages town development plan by approving it, disapproving
it and distributing it to town sectors and planner.
Precondition Planner should submit general development plan to manager.
Basic Course of 1. Manager wants to manage strategic plan.
action 2. Manager should search general strategic plan from paper based file
store
3. Approve the plan and distribute it to town sector physically
4. Town development plan is managed.
5. Use case end.

18
 Table 7: Use case description for Generate Report

Name Generate Report

Id UC-05
Actor Town Sector and planner
Description Town Development sector and planner Generate report on their work.
Precondition There should be work done.
Basic Course of 1. Town sectors or planner wants to generate report on their work.
action 2. They should be creating paper based report form.
3. They should fill report info on the provided paper based report form.
4. Report is generated.
5. Use case ends.

19
 2.6.2. System Use Case
A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a particular goal. The use case
should contain all system activities that have significance to the users. (3) A use case can be
thought of as a collection of possible scenarios related to a particular goal, indeed, the use case
and goal are sometimes considered to be synonymous.

Figure 6: System Use case

20
 2.6.2.1. System Use case Description

Table 8: Use case description for Login

Name Login
ID UC-01
Actor Town Sector, Admin, planner, Manager, and Human resource
Description To authenticate the user
Precondition The user must have valid user name and password.
Post condition The authenticated person gets the appropriate page.
Basic Course of 1. Open the system on any browser
action 2. The system is displayed on the user computer
3. user Clicks login link
4. The system displays login form
5. User inputs user name and password
6. user click on login button
7. The system displays the appropriate page.
8. Use case ends
Alternative Course A5) If the username or password is incorrect.
of Action A.6 The system displays incorrect user name and password message.
A.7 The system redirects to go to step 5
A.8 Use case ends.

21
Table 9: Use case description for Manage Account

Name Manage Account

Id UC-02
Actor Admin
Description Administrator assigns privilege to the planner and Development sector’s
manager.
Precondition The Administrator must log in to the system.
Post condition The account will be activated, deactivated and removed.
Basic Course of 1. The administrator log to his/her page.
action 2. The system displays the administrator page.
3. The administrator click on manage account link.
4. The system displays the option as activate, deactivate and remove
account.
5. The administrator select activate account, remove account or
deactivate account link.
6. The system displays search user information form.
7. The administrator inputs unique identification of user on the provided
space and click on search button.
8. The system displays the user information
9. The administrator takes action to activate, deactivate or remove the
account.
10. The system displays succeed message as the account is activated,
removed or deactivated.
11. Use case ends
Alternative Course A7) If the administrator inputs the ID of the user that doesn’t match with
of Action any account.
A.8 The system displays error message as the no account exists with this
ID.
A.9 The system redirects to go to step7
A.10 Use case ends.

22
Table 10: Use case description for View Town development plan

Name Manage Town development plan

Id UC-03
Actor Manager
Description Manager manage town development plan from system database to
approve, disapprove and distribute it for all town sectors.
Precondition The Manager must log in to the system.
Post condition The plan will be approved, disapprove and distributed to the town sector.
Basic Course of 1. The Manager log to his/her page.
action 2. The system displays Manager page.
3. The manager click on view town development plan link.
4. The system displays town development plan information with options
approves and disapprove links.
5. The manager manage the development plan and select approve or
disapprove link.
6. The manager approves or disapproves the plan submitted by town
sectors or planner.
7. The system displays succeed message as the plan is approved or
disapproved successfully.
8. Use case ends.
Alternative Course A4) If the town development plan is not exist in the database
of Action A.5 The system display error message that the plan you want to approve
or disapprove is not exist.
A.6 The manager logout from the manage town plan page.
A.7 Use case ends.

23
 Table 11: Use case description for Upload Information

Name Upload Information

Id UC-04
Actor Admin
Description Administrator can upload any information that is related to the system
process.
Precondition The Administrator must log in to the system.
Post condition The information will be uploaded.
Basic Course of 1. The administrator log to his/her page.
action 2. The system displays administrator page.
3. The administrator click on upload information link.
4. The system displays upload information form.
5. Administrator fills the information on the provided form and upload it
6. The system displays succeed message as the information is uploaded
successfully.
7. Use case ends.
Alternative Course A5) if the form is not correctly filled
of Action A.6 The system display error message that please fill the form correctly.
A.7 The system redirects to go to step 4.
A.8 Use case ends.

24
Table 12: Use case description for manage Complaint

Name Manage Complaint

Id UC-05
Actor Manager , Planner
Description Manager and planner can manage the complaint that is sent by town
development sectors for the manager and planner also sent for the
manager in order to give response for the complaint.
Precondition They must log in to the system.
Post condition The response will be submitted to the complaint.
Basic Course of 1. The manager and planner log to his/her page.
action 2. The system displays their page.
3. The manager and planner click on manage complaint link.
4. The system displays complaints.
5. They manage the complaints and click on give response link.
6. The system displays complaint response form.
7. The manager and planner gives the response to the complainant and
submits it to the complaint.
8. The system displays succeed message as the response is submitted to
complainant successfully.
9. Use case ends.

25
 Table 13: Use case description for View Report

Name View Report

Id UC-06
Actor Manager
Description Manager can view the reports that are generated by town development
sectors and planner.
Precondition The Manager must log in to the system.
Post condition The comment will be submitted to the planner or town sector.
Basic Course of 1. The Manager log to his/her page.
action 2. The system displays manager page.
3. The manager click on view report link.
4. The system display search form.
5. The manager input report id and click on search button.
6. The system display the report
7. Use case ends.
Alternative Course A5. If the id entered by manager doesn’t match with any report,
of Action A6. The system displays error message as no report is available with
this id.
A7. The system redirects the manager to go to step 5.
A8. Use case ends

26
 Table 14: Use case description for Manage Notification

Name Manage Notification

Id UC-07
Actor Admin
Description Administrator can post, delete and update notification.
Precondition The Administrator must log in to the system.
Post condition The notification will be posted, updated or deleted.
Basic Course of 1. The administrator log to his/her page.
action 2. The system displays administrator page.
3. The administrator click on manage notification link.
4. The system displays the options post notification, update notification
and delete notification.
5. The administrator select post notification, update notification or delete
notification link.
6. The system displays post notification form or update notification form.
7. The administrator types the notification on the provided form or
deletes the notification or updates it and submits it.
8. The system displays succeed message as the notification is posted,
updated or deleted successfully.
9. Use case ends.
Alternative Course A7) If the form is not correctly filled.
of Action A.8 The system display error message that please fill the form correctly.
A.9 The system redirects to go to step 6.
A.10 Use case ends.

27
 Table 15: Use case description for Prepare Work Plan

Name Prepare Work plan

Id UC-08
Actor Town sector
Description Each town sector should prepare their current or future work plan
structure.
Precondition The town sector head must log in to the system.
Post condition Town sector’s work plan will be prepared.
Basic Course of 1. The town sector head log to his/her page.
action 2. The system displays town sector page.
3. The town sector head click on prepare work plan link.
4. The system displays work plan preparation form.
5. The town sector head prepare current/ future work plan for the sector
on the provided form and submit it.
6. The system displays succeed message as the work plan is prepared
successfully.
7. Use case ends.
Alternative Course A5) If the form is not correctly filled
of action A.6 The system display error message that please fill the form correctly.
A.7 The system redirects to go to step 4.
A.8 Use case ends

28
 Table 16: Use case description for Send Work Plan

Name Send Work plan Structure

Id UC-09
Actor Town sector
Description Each town sector should send their work plan structure to the manager to
get approval and for town final strategic plan including for budget
allocation.
Precondition The town sector head must log in to the system.
Post condition Town sector’s work plan will be sent to manager.
Basic Course of 1. The town sector head log to his/her page.
action 2. The system displays town sector page.
3. The town sector head click on send work plan link.
4. The system displays town sector’s work plan information.
5. The town sector head select the work plan to be sent and click on send
button and submit it.
6. The system displays succeed message as the work plan is sent to
manager successfully.
7. Use case ends.
Alternative Course A5) If the work plan is not selected
of action A.6 The system display error message that please select work plan you
want to send.
A.7 The system redirects to go to step 5.
A.8 Use case ends

29
 Table 17: Use case description for Generate Report

Name Generate Report

Id UC-10
Actor Town sector and planner
Description Each town sector and planner should generate the report on their work
Precondition The town sector head or planner must log in to the system.
Post condition Report will be generated.
Basic Course of 1. The town sector head or planner log to his/her page.
action 2. The system displays town sector or planner page.
3. The town sector head or planner Generate report link.
4. The system displays report generation form.
5. Town sector head or planner type report info on the provided report
generation form.
6. The system displays succeed message as the report is generated
successfully.
7. Use case ends.
Alternative Course A5) if the form is not filled properly
of action A.6 The system display error message that please fill the form properly.
A.7 The system redirects to go to step 4.
A.8 Use case ends

Table 18: Use case description for Manage Staff

Name Manage Staff

Id UC-11
Actor Human resources
Description Human resources manage staff from system database to add staff and
update staff information
Precondition The human resource head must log in to the system

30
post condition The staff will be added and updated staff information
Basic course of action 1. The human resource head log to his/her page
2. The system displays human resource page
3. The human resource head manage staff link
4. The system display manage staff form
5. The human resource head add staff and update staff information on
the provided form
6. The system display succeed message the staff added or updated staff
information
7. Use case end
Alternative course of A5) if the form is not filled properly
action A6) The system display error message that please fill the form properly
A7) The system redirects to go to step 4
A8) Use case end

2.7. Features
 Easy to control: the system enables the admin to manage users account and control
town strategic plan and development.
 efficient: the system will save the time of planner, admin and town development sector
by making the preparation of town plan and related works automate and fast access to
the system.
 Minimize work load: in the previous system there is work load to the planner and
development sector, so the new automated system will minimize the work load to the
employee of office.
 Effective communication: there is effective communication between the users of the
system. Development sectors can generate report and communicate with admin and
planner online easily.
 Paperless working: currently all tasks related with town planning and development is
done using paper. But the newly proposed system almost avoids paper working.

31
 2.8. User interface prototyping
Haramaya Town Planning and Development System is user friendly and interactive system. The
HTPDS interact with the user though a Graphical User Interface (GUI).

2.8.1. Traditional user interface prototyping

Figure 7: Login form traditional UI

Figure 8: Create User account traditional UI

32
 2.8.2. User-Interface Flow Diagramming

Figure 9: User interface flow diagramming

2.9. Supplementary specification

2.9.1. Business rules
A business rule is effectively an operating principle or polices that must be fulfilled and
obligated in order the system will function properly and effectively. It often pertain to access
control issues, business calculations, or operating polices and principles of the organization.
(4)Some business rules of proposed system are:
Identifier: #BR01

33
Name: Registration
Description: Any user cannot use the system without registered and authenticated with secure
username and password.

Identifier: #BR02
Name: form validation
Description: The system checks each field of a form whether they are empty or not, if not empty
the system checks whether they are the required format like their data type, minimum and
maximum characters in each field to validate the form.

Identifier: #BR03
Name: user account validation
Description: When the internal users attempts to login to the system, the system should validate
whether the input user name or password is correct or not.

Identifier: #BR04
Name: notification message
Description: The system should notify admin for incoming of new complaint for response.

Identifier: #BR05
Name: feedback
Description: any one can give feedback without logged into the system

Identifier: #BR06
Name: pop up message
Description: the system should return pop up message to notify user whether task is correctly
done or not.
Identifier: #BR07
Name: activate account
Description: when the admin wants to activate user account, the system should notify the
availability of user account.
Identifier: #BR08
Name: edit profile
Description: user can change their password and user name after they accepted it from admin.

34
 2.9.2. Non-functional requirement
Non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system or how the system do a given task, rather than what the system do. The
functional requirements of the new system are:

 Performance- the system should work properly with its storage capacity, accuracy and
speed
 User interface- the developed system should be user friendly by making it easily
accessible.
 Compatibility- The system would be fully compatible with different type of browser like
Microsoft Internet Explorer, Mozilla Firefox, opera mini and Google chrome.
 Efficiency- the new system should perform all tasks with low cost and within the short
time.
 Reliability- the new system will be able to process work correctly and completely without
being aborted.
 Security- The security Section describes the need to control access to the data. This
includes controlling who may view and alter application data by using strong password
on the system.

 Error Handling- Our system handles the errors in a very efficient manner. It can tolerate
to wrong inputs and prompts the users to correct the inputs. It gives notifications as and
when required, guiding the users to properly utilize it.

2.10. Constraints
A constraint refers any restriction that defines a project's limitations. The following are the
constraints of our system:
 Internet- if there is no internet or connection, nobody can access the system.
 Account- any one can’t access the system without having valid account.

35
CHAPTER THREE

3. Design Document

3.1. Classes-type layered approach

The different layers of the classes are interrelated as shown below

Figure 10: Class type layered approach

36
 3.2. Class Modeling
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the system's classes,
their attributes, operations (or methods), and the relationships among objects. The class diagram
is the main building block of object-oriented modeling. It is used for general conceptual
modeling of the structure of the application, and for detailed modeling translating the models
into programming code. Class diagrams can also be used for data modeling. The classes in a
class diagram represent both the main elements, interactions in the application, and the classes to
be programmed. (5)

In the diagram, classes are represented with boxes that contain three compartments:

 The top compartment contains the name of the class. It is printed in bold and centered,
and the first letter is capitalized.
 The middle compartment contains the attributes of the class. They are left-aligned and the
first letter is lowercase.
 The bottom compartment contains the operations the class can execute. They are also
left-aligned and the first letter is lowercase.

In the design of a system, a number of classes are identified and grouped together in a class
diagram that helps to determine the static relations between them.

37
 Figure 11: Class Diagram for HTPDS

38
 3.3. Sequence Diagram
UML Sequence Diagrams are interaction diagrams that detail how operations are carried out.
They capture the interaction between objects in the context of collaboration. Sequence Diagrams
are time focus and they show the order of the interaction visually by using the vertical axis of the
diagram to represent time what messages are sent and when. (6)

Figure 12: Sequence diagram for login

39
 Figure 13: Sequence diagram for add user

40
 Figure 14: Sequence diagram for prepare sector plan

41
 Figure 15: Sequence diagram for send plan

42
 3.4. Activity Diagram

Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system. So the control flow
is drawn from one operation to another. This flow can be sequential, branched or concurrent.
Activity diagrams deals with all type of flow control by using different elements like fork, join
etc. (7)

Figure 16: Activity diagram for login

43
 Figure 17: Activity diagram for work plan preparation

Figure 18: Activity diagram for send plan

44
 Figure 19: Activity diagram for manage plan

45
 Figure 20: Activity diagram for manage account

46
 3.5. User Interface Design
User interface design or user interface engineering is the design of computers, appliances,
machines, mobile communication devices, software applications, and websites with the focus on
the user's experience and interaction. The goal of user interface design is to make the user's
interaction as simple and efficient as possible, in terms of accomplishing user goals—what is
often called user-centered design.

3.5.1. Form Design

47
 Figure 21: User registration form

Figure 22: Home page design

48
 Figure 23: Login form

3.5.2. Dialogue and Interface Design

Figure 24: Error popup message

49
 3.6. State Chart Diagram
UML state chart diagrams depict the various states that an object may be in the transition
between those states. In other word it has initial and final states in addition to transition that is a
progression from one state to another. States are represented as a rounded rectangle with the
name of the state shown in the system. Connecting states together are transitions. (8)

Figure 25: state chart diagram for login

50
 Figure 26: state chart diagram for search plan

51
 3.7. Object Diagram
An object diagram is a graph of instances, including objects and data values. A static object
diagram is an instance of a class diagram; it shows a snapshot of the detailed state of a system at
a point in time. The use of object diagrams is fairly limited, namely to show examples of data
structure. (9)

Figure 27: Object diagram

52
 3.8. Persistence modeling/ Database Design
Database design is the process of producing a detailed data model of a database. This data model
contains all the needed logical and physical design choices and physical storage parameters
needed to generate a design. The term database design could also be used to apply to the overall
process of designing, not just the base data structures, but also the forms and queries used as part
of the overall database application within the DBMS. (10)

Database: - HTPDS

 User account
 Town Sector work plan
 Report
 Town strategic plan
 Budget plan details
 Complaint
 Notification
 Feedback

Table 19: Database Tables

User Account

Column Type

PK User id Int(20)

User name Varchar(50)

Password Varchar(50)

First name Varchar(50)

53
 Last name Varchar(50)
Town Sector work plan
Sex Varchar(10)
Column Type
Age Int(3)
PK Project id Int(30)
Address Varchar(50) Sector name Varchar(50)

User_type Varchar(50) Project name Varchar(50)

Starting date Date
Ending date Date
Duration of project/year Int(5)
Number of users Int(20)
Tow development plan
Place of the project Varchar(50)

Column Type Size of project Varchar(50)

PK Plan id Int(20) Estimated budget Varchar(20)

Plan type Varchar(

50)

Project name Varchar(

50)

FK Project id Varchar(
50)

Sector name Varchar(

50)

Starting date Int(20)

Ending date Varchar(

10)

Duration/year Varchar(

54
 50)

Number of users Varchar( Complaint

40) Column Type
PK Complaint id Int(20)
Place of project Varchar(
FK User id Varchar(50)
operated in 50)
Date Date
distributed Double Content Varchar(1000)
budget Respondent Varchar(50)
FK Budget id Int(20) name
Feedback
Status Varchar(
Column Type
50)
PK Feedback Id Int(20)
Email Varchar(50)
Column Type Phone Int(20)
Plan id Int(20) Content Varchar(1000)
Date Date
Content Varchar(10000)
Expended Double
budget
Remaining Double
budget

55
 Notification

Column Type

PK Notification Int(20)
id
Budget plan details
Writer name Varchar(50) Column Type

Subject Varchar(100) PK Budget id Int(20)

FK Plan id Int(20)
Content Varchar(1000)
Project name Varchar(50)

Date Date FK Project id Int(20)

Size of project Varchar(50)
Sector name Varchar(50)
Starting date Date
Ending date Date
Amount of distributed Double
budget in Birr

56
 id

57
Budget id Plan id Project id

User
First
Plan type

name
Plan id Project
name
1st normalization

Project
Last
name

Town development plan

Project Sector
Project id
Normalized Database

name name
User
name name

Project
Project id size Starting
date
Sector
name

Report
Size of Ending
User account

project Starting date

Budget plan details

Password Email

date
Town sector work plan

Sector Ending Duration

Sex

name date
Age

Starting Duration Number

date of users
Place of
Phone
number

Ending project Place of

date project
Number
Amount of of users
office

distributed Size of
budget Budget id project
type
User

Estimated Distributed Estimated

budget budget budget
 Remaining
Evaluation

Expended
Project id
Report id

Content

Budget
Sector
Report

budget
result
name

Date
type
Complaint
Complaint Complainant Date Content Respondent
id Name name

Notification
Notification Writer name Subject Content Date
id

Feedback
Feedback id First Last name Email Phone Email Content
name

Since there is no partial dependency in the above 1st normalized database, it doesn’t require 2nd
normalization form. So directly depict the database diagram from the above tables.

58
 Figure 28: Persistent Database Diagram

59
 3.9. Component Diagram
Component diagrams are used in modeling the physical aspects of object-oriented systems that
are used for visualizing, specifying, and documenting component-based systems. Component
diagrams are essentially class diagrams that focus on a system's components that often used to
model the static implementation view of a system. (11)

Figure 29 Component Diagram

3.10. Deployment Diagram

A UML deployment diagram is a diagram that shows the configuration of run time processing
nodes and the components that live on them. Deployment diagram is a kind of structural
diagram used in modeling the physical aspects of an object-oriented system. They are often be
used to model the static deployment view of a system (topology of the hardware). (12)

60
 Figure 30: Deployment Diagram

61
CHAPTER FOUR

4. Implementation Document

4.1. Report on Implementation

In our project the implementation phase describes the process that turn strategies and plan in to
actions in order to accomplished strategic objectives and goals. Implementation is a translation of
old system in to new system. The system is conducted for town sector development and planning
office. For example Education sector, Electricity sector, Road construction sector, Sanitation
clearness sector, water sector, Healthy sector and etc. The sectors also facilitate the task between
town development sectors and town planning office. previously Haramaya town plan and
developing office perform its work manually so now we have complete the implementation and
testing part of the system which is ready to use it. Except its limitation part of the system.

4.2. Sample code

<?php include('dbcon.php'); ?>

<link href="csss/layout.css" rel="stylesheet" type="text/css" >

<div class="navbar navbar-fixed-top navbar-inverse">

<div class="navbar-inner" style="background-color:#777777 ">

<div class="container">

<div class="rounded">

<nav id="mainav" >

<a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">

<span class="icon-bar"></span>

<span class="icon-bar"></span>

<span class="icon-bar"></span>

</a>

62
 <div class="nav-collapse collapse">

<ul class="nav">

<li class="divider-vertical"></li>

<li class=""><a rel="tooltip" data-placement="bottom" title="HOME" id="home"

href="index.php"style="font-size:
25px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<?php
echo lhome; ?></a>

</li>

<li class="divider-vertical"></li>

<li class="">

<a rel="tooltip" data-placement="bottom" title="Click Here to know About Us" id="aboutus"

href="aboutus.php" style="font-size:
25px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<?php echo labtus;
?></strong></a>

</li><li class="divider-vertical"></li>

<li class="">

<a rel="tooltip" data-placement="bottom" title="Click Here to see Latest Updates" id="news"

href="latestupdate.php" style="font-size: 25px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

<?php echo lInformation; ?></strong></a> </li>

<li class="divider-vertical"></li>

<li class="">

<a rel="tooltip" data-placement="bottom" title="Click Here to see Latest Programs" id="news"

href="notif.php" style="font-size: 25px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

<?php echo lNotification; ?></strong></a>

</li>

<li class="divider-vertical"></li>

<li class="">

63
<a rel="tooltip" data-placement="bottom" title="Click Here to Feedback" id="Feedback"
href="feedback.php" style="font-size: 25px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<?php
echo lFeedback; ?></strong></a> </li>

<li class="divider-vertical"></li>

<li class="" ><a rel="tooltip"> <li> <a style="margin-top:0px; margin-left:18px; margin-

right:10px; font-size: 25px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<?php echo lLanguage;
?></a></strong></a>

<ul>

<li><a href="switch_lang.php?lang=1" style="font-size: b 20px">English</li>

<li><a href="switch_lang.php?lang=2" style="font-size: 20px">Afan

Oromo</a></li>

</a>

</li>

</ul>

<li class="divider-vertical"></li>

<li class="">

<a rel="tooltip" data-placement="bottom" title="Click Here to Login" id="login"

href="#student" data-toggle="modal" style="font-size:
25px">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<?php echo lLogin; ?></a>

</li>

<li class="divider-vertical"></li>

<li class="signup"><span class="sg"></span></li>

</div>

</div>

</div>

</div>

64
 </div>

<!-- Modal login -->

<div id="student" class="modal hide fade" tabindex="-1" role="dialog" aria-

labelledby="myModalLabel" aria-hidden="true">

<div class="modal-header"><div class="alert alert-info"><strong style="color:black; font-size:

20px"><?php echo lwelcome; ?></strong></div></div>

<div class="modal-body">

<form class="form-horizontal" method="post" action="login.php" enctype="multipart/form-

data" id="validationform" data-parsley-validate="" novalidate="">

<div class="control-group">

<label class="control-label" for="inputEmail"><?php echo lusername; ?></label>

<div class="controls">

<input type="text" name="username" placeholder="Username" required="">

</div>

</div>

<div class="control-group">

<label class="control-label" for="inputPassword"><?php echo lpassword; ?></label>

<div class="controls">

<input type="password" name="password" placeholder="Password" required="">

</div>

</div>

<div class="control-group">

<div class="controls">

<p style="margin-left:-85px;"><a href="#students" data-toggle="modal" style="font-size:

15px;color: blue"><?php echo lforget; ?></a>

<button type="submit" name="login" style="margin-left:20px;" class="btn btn-

success"><i class="icon-signin icon-large"></i>&nbsp;<?php echo llogn; ?></button></p>

65
 </div>

</div>

</form>

</div>

<div class="modal-footer" style=" margin-top:-20px;">

<button class="btn" data-dismiss="modal" aria-hidden="true"><i class="icon-remove

icon-large"></i>&nbsp;<?php echo lclose; ?></button>

</div>

</div>

<div id="students" class="modal hide fade" tabindex="-1" role="dialog" aria-

labelledby="myModalLabel" aria-hidden="true">

<div class="modal-header"><div class="alert alert-info"><?php echo lemail;

?></div></div>

<div class="modal-body" style="margin-left:-40px;">

<form class="form-horizontal" method="post" action=" ">

<div class="control-group">

<div style="margin-left:40px;">

</div>

<label class="control-label" for="inputEmail">E-mail address</label>

<div class="controls">

<input type="email" style="height:20px; width:250px; margin-left:-10px;" id="inputEmail"

name="email" placeholder="e-mail address" required>

<button type="submit" name="submit" class="btn btn-success"><i class="icon-signin icon-

large"></i>&nbsp;Submit</button>

</div>

66
 </div>

</form>

</div>

<div class="modal-footer">

<button class="btn" data-dismiss="modal" aria-hidden="true"><i

class="icon-remove icon-large"></i>&nbsp;Close</button>

</div>

</div>

<?php

$link=mysqli_connect("localhost", "root", "");

mysqli_select_db($link, "htpds");

if (isset($_POST['submit'])) {

$posemail = $_POST["email"];

$count = 0;

$ros = mysqli_query($link, "select * from user where email = '$posemail'");

while ($row = mysqli_fetch_array($ros)) {

$user = $row["username"];

$pass = $row["password"];

$base_url = "Haramaya Town planning and development";

$mail_body = "

HI ".$user."

Thanks for Using Haramaya town planning and development

Your Password is ".$pass.",

67
 Best Regards Haramaya town planning and development

";

if (mail($posemail, $base_url, $mail_body)){

$messag = '<div class="alert-success">

<h1 style="font-family:Lucida Console; color: #182c3d; background-color:

white;">Your Password Is Sent To Your Email Check Your Email '.$posemail.' </h1>

</div>';

}else{

$messag = '<div class="alert-success">

<h1 style="font-family:Lucida Console; color: #182c3d; background-color:

red;">Some Error Accour Or Encorrect Email</h1>

</div>';

?>

Sample Code for Login

<?php

include('dbcon.php');

if (isset($_POST['login'])){

session_start();

//$_SESSION['id']

68
$username = $_POST['username'];

$password = $_POST['password'];

*$ecode = base64_encode($password);*/

$query = "SELECT * FROM user WHERE username='$username' AND

password='$password' ";

$result = mysql_query($query)or die(mysql_error());

$num_row = mysql_num_rows($result);

$row=mysql_fetch_array($result);

//$username=$row['username'];

$row_id=$row['id'];

$user_type =$row["user_type"];

$status=$row['status'];

$row=mysql_fetch_array($result);

if( $num_row > 0 ) {

if($user_type=="admin" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:admin/index.php');

$_SESSION['id']=$row_id;

else if($user_type=="hrm" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:HRM/index.php');

69
$_SESSION['id']=$row_id;

else if($user_type=="hrm" && $status=="Ignored"){

header('location:accesss_denied.php');

else if($user_type=="planner" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:planner/index.php');

$_SESSION['id']=$row_id;

else if($user_type=="planner" && $status=="Ignored"){

header('location:accesss_denied.php');

else if($user_type=="manager" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:Managerr/index.php');

$_SESSION['id']=$row_id;

70
 else if($user_type=="manager" && $status=="Ignored"){

header('location:accesss_denied.php');

else if($user_type=="road" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:Road_sector/index.php');

$_SESSION['id']=$row_id;

else if($user_type=="road" && $status=="Ignored"){

header('location:accesss_denied.php');

else if($user_type=="healthy" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:Healthy_sector/index.php');

$_SESSION['id']=$row_id;

else if($user_type=="healthy" && $status=="Ignored"){

header('location:accesss_denied.php’);

71
} else if($user_type=="water" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:Water_sector/index.php');

$_SESSION['id']=$row_id;

else if($user_type=="water" && $status=="Ignored"){

header('location:accesss_denied.php');

else if($user_type=="electricity" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:Electrity_sector/index.php');

$_SESSION['id']=$row_id;

else if($user_type=="electricity" && $status=="Ignored"){

header('location:accesss_denied.php');

else if($user_type=="education" && $status=="Active"){

$_SESSION['username']=$_POST['username'];

header('location:Education_sector/index.php');

72
$_SESSION['id']=$row_id;

else if($user_type=="education" && $status=="Ignored"){

header('location:accesss_denied.php');

else{

header('location:access_denied.php');

}}

?>

Sample Code for update sector plan

<?php

include ('../dbcon.php');

?>

<?php

?>

<?php include('navbar.php');

$project_id=$_GET ['ID'];

//echo "<script>windows: location='viewuser.php'</script>";

73
 $query=mysql_query("select * from sector_plan where id='$project_id' and
sector_name='healthy'") or die( mysql_error());

$row=mysql_fetch_array($query);

$id=$row['id'];

$plan_id=$row['plan_id'];

$pname=$row['pname'];

$sector_name=$row['sector_name'];

$duration=$row['duration'];

$sdate = $row['sdate'];

$edate = $row['edate'];

$nuser = $row['nuser'];

$place = $row['place'];

$measure = $row['measure'];

$psize = $row['psize'];

$catagory = $row['catagory'];

$completed = $row['completed'];

$ebudget = $row['ebudget'];

$details = $row['details'];

74
 ?>

<html>

<head>

<link href="css/deppp.css" rel="stylesheet" media="screen">

<link rel="stylesheet" type="text/css" media="all" href="css/contactstyle.css">

<link href="css/timeline.css" rel="stylesheet">

</head>

<head>

<link rel="stylesheet" type="text/css" href="css/form.css">

<script>

function Confirmupdate()

var x = confirm("Are you sure you want to save?");

if (x)

return true;

else

return false;

</script>

</head>

75
<div class="content mt-3">

<div class="animated fadeIn">

<div class="container-fluid container-fullw bg-white">

<div class="row">

<div class="col-md-12">

<div class="row margin-top-30">

<div class="col-lg-8 col-md-12">

<div class="panel panel-white">

<div class="panel-heading">

<h1 class="panel-title" style="color: #76a089">Please Fill the form Properly</h1>

</div>

<div class="panel-body">

<form id="formID" name="formID" method="post" enctype="multipart/form-data"

onsubmit="return Validate()" name="vform">

<div class="form-group">

<label for="firstname"> id</label>

<input type="text" readonly='readonly' name="id" class="form-control" value="<?php

echo $id ?>" >

</div>

<div class="form-group">

<label for="firstname">Plan_id</label>

76
 <input type="text" readonly='readonly' name="plan_id" class="form-control"
value="<?php echo $plan_id ?>" >

</div>

<div class="form-group">

<label for="lastname"> Project Name</label>

<input type="text" name="pname2" class="form-control" required="required"

value="<?php echo $pname ?>" >

</div>

<div class="form-group">

<label for="username">Sector Name</label>

<input type="text" name="sector_name" class="form-control" required="required"

value="healthy" >

</div>

<div class="form-group">

<label for="fess">Duration/year </label>

<input type="text" name="duration2" class="form-control" required="required"

value="<?php echo $duration ?>">

</div>

<div class="form-group">

<label for="fess">Starting date</label>

<input type="date" name="sdate2" class="form-control" value="<?php echo $sdate ?>">

</div>

<div class="form-group">

<label for="fess">Ending date </label>

<input type="date" name="edate2" class="form-control" value="<?php echo $edate ?>">

</div>

<div class="form-group">
77
 <label for="fess">Number of users</label>

<input type="text" name="nuser2" class="form-control" value="<?php echo $nuser ?>">

</div>

<div class="form-group">

<label for="fess">Place of project</label>

<input type="text" name="place2" class="form-control" value="<?php echo $place ?>">

</div>

<div class="form-group">

<label for="fess">Measurement unit</label>

<input type="text" name="measure2" class="form-control" value="<?php echo $measure

?>">

</div>

<div class="form-group">

<label for="fess">Project Size </label>

<input type="text" name="psize2" class="form-control" value="<?php echo $psize ?>">

</div>

<div class="form-group">

<label for="fess">Catagory</label>

<select type="text" name="catagory2" class="form-control" value="<?php echo

$catagory ?>">

<option value="none" selected="" disabled="">Type of plan</option>

<option value="current">current</option>

<option value="past">Past</option>

<option value="Future">Future</option>

</select>

</div>

78
 <div class="form-group">

<label for="fess">Completed</label>

<input type="text" name="completed2" class="form-control" value="<?php echo

$completed ?>">

</div>

<div class="form-group">

<label for="fess">Estimated Budget </label>

<input type="text" name="ebudget2" class="form-control" value="<?php echo $ebudget

?>">

</div>

<div class="form-group">

<label for="fess">Document</label>

<input type="file" class="form-control" name="details" value="">

</div>

<button type="submit" name="save" class="btn btn-o btn-primary">send </button>

<?php

if (isset($_POST['save'])) {

$status="pending";

$statuss="unseen";

$tm=md5(time());

$fnm=$_FILES["details"]["name"];

$dst="./document/".$tm.$fnm;

$dst1="./document/".$tm.$fnm;

move_uploaded_file($_FILES["details"]["tmp_name"], $dst);

$link=mysqli_connect("localhost", "root", "");

79
 mysqli_select_db($link, "htpds");

mysqli_query($link, "update sector_plan set

pname='$_POST[pname2]',sector_name='$_POST[sector_name2]',duration='$_POST[duratio
n2]', sdate='$_POST[sdate2]', edate='$_POST[edate2]',nuser='$_POST[nuser2]',
place='$_POST[place2]',measure='$_POST[measure2]',psize='$_POST[psize2]',catagory='$_
POST[catagory2]',completed='$_POST[completed2]',status='$status',ebudget='$_POST[ebud
get2]',details='$dst1',statuss='$statuss' where id = '$project_id'");

?>

<script type="text/javascript">

alert("successfully edited and sent");

</script>

<script type="text/javascript">

window.location = "disapproved_plan.php";

</script>

<?php

?>

</div>

</div>

</div>

</div>

</div>

<div class="col-lg-12 col-md-12">

80
 <div class="panel panel-white">

</div>

</div>

</div>

</div>

4.3. Testing
4.3.1. Unit testing
It is a level of software testing where individual units or components of the system are tested.
The purpose is to validate that each unit of the system performs as designed. In our project the
group members test each module of the system that perform its planned objectives or not. If
there is an occurrence of error the correction will be taken and the correction also does not affect
another part of the system. We have checked the system what we have develop.

4.3.2. Integration testing

Is a level of software testing where individual units are combined and tested as a group. The
purpose of this level of testing is to expose faults in the interaction between integrated units. Test
drivers and test stubs are used to assist in Integration Testing. all the modules will be combined
together and tested it for its fitness with each other and with the systems functionality.

4.3.3. System testing

Is a level of software testing where complete and integrated software is tested. The purpose
of this test is to evaluate the system’s compliance with the specified requirements.

81
 4.4. Conclusion
As country continues to rapidly town with the accompanying growth in social, economic and
environmental development and technological challenges. The need for comprehensive inclusive
approaches to town planning and development provision increases. Towns must grow to listen to
and accommodate the needs and priorities of the society. So generally Haramaya town plan and
development system also improve haramaya town planning and development manual problem
that to satisfy needs and priorities of the society. Since the manual system of haramaya town
office have a problem to provide customer need and satisfaction which are, we have mentioned
in the statement of the problem. So that our project may tried to solve that problem in
computerized method. The system contain all system development life cycle. System planning,
analysis and requirement gathering, system design, system development, implementation and
testing are contained in the system. As the end of the first three phases we need to review that we
have covered in accordance with what we have planned at the first semester and we have done
the last two phases which are implementation and testing in current semester. Now we have
fully implemented the automated system which converts the manual or old system to
computerized or new one. So we hope the implemented system will solve the Haramaya town
planning and development office problems.

82
 4.5. Clients Feedback
We have tested our system by involving users, we get good feedback from users. Some of the
comments are:

 Since many activities are automated, many problems of individual and organizations are
solved. These are resources such as Cost, Man power and Time
 It also attracts many users. Because it reduces man power, cost and time for the Town
planning office as well as for the development sectors.
 Since the system is easy to use or it is user friendly.

4.6. User Manual Preparation

When the system is web based everything important for the user. It will be explained and
implemented while giving a training when the system is deployed or hosted. For accessing the
all system service, they must have a user account, or they must be employee of haramaya town
planning and development office.

83
 a. User manual for homepage

Figure 31: actual system home page

84
 b. User manual for Login

Figure 32: actual system login page

85
 c. User manual for submit sector plan

Figure 33: actual system sector plan form

86
 d. User manual for project details

Figure 34: sector project list

87
Appendix
Here are the lists of questions that we were used to interview and data gathering with the
employees of Haramaya town planning and development office.

1, when the town established and organized this office? __________

2, how many sectors are there according to the current office strategies and work situation?

___________________________________

3, how the sectors and employees work their activity?

_________________________________________

4, how we could to get any manual data from the information store for example Annual plan,
List of sectors ….. Etc.

5. Who plan the annual and semi-annual plans? ____________________________________

6. How to plan the sectors their budget, resource, schedules, and so on?

_____________________

7. When the report is generated? ____________________________________

88
Reference
1. wikipedia.org/wiki/Class-responsibility-collaboration_card. [Online]
https://en.wikipedia.org/wiki/Class-responsibility-collaboration_card.

2. coursehero.com/file/p51an7/Concrete-Use-Cases-Essential-Use-Cases. [Online]
https://www.coursehero.com/file/p51an7/Concrete-Use-Cases-Essential-Use-Cases-describe-
functionality-in-implementation/.

3. searchsoftwarequality.techtarget.com/definition/use-case. [Online]
https://searchsoftwarequality.techtarget.com/definition/use-case.

4. wikipedia.org/wiki/Business_rule. [Online] https://en.wikipedia.org/wiki/Business_rule.

5. visual-paradigm.com/guide/uml-unified-modeling-language/what-is-class-diagram/. [Online]
https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-class-diagram/.

6. visual-paradigm.com/solution/uml/java-to-sequence-diagram/. [Online] https://www.visual-

paradigm.com/solution/uml/java-to-sequence-diagram/.

7. https:visual-paradigm.com/guide/uml-unified-modeling-language/what-is-activity-diagram/. [Online]
https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-activity-diagram/.

8. smartdraw.com/state-diagram/. [Online] https://www.smartdraw.com/state-diagram/.

9. en.wikipedia.org/wiki/Object_diagram. [Online] https://en.wikipedia.org/wiki/Object_diagram.

10. drdowwwbbs.com/persistence-modeling-in-the-uml/. [Online] http.drdowwwbbs.com/persistence-

modeling-in-the-uml/.

11. https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-component-
diagram/visual-paradigm.com/guide/uml-unified-modeling-language/what-is-component-diagram/.
[Online] https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-component-
diagram/.

12. uml-diagrams.org/deployment-diagrams-overview.html. [Online] https://www.uml-

diagrams.org/deployment-diagrams-overview.html.

13. wikipedia.org/wiki/Class-responsibility-collaboration_card. [Online]

https://en.wikipedia.org/wiki/Class-responsibility-collaboration_card.

14. wikipedia. [Online] https://en.wikipedia.org/wiki/Class-responsibility-collaboration_card.

15. 1. [Online] https://en.wikipedia.org/wiki/Class-responsibility-collaboration_card.

89