UNIVERSITY OF GONDAR

FACULTY OF INFORMATICS

DEPARTMENT OF COMPUTER SCIENCE

WEB BASED GONDAR CITY HOUSE RENTAL

SYSTEM

PROJECT PARTICIPANTS ID NUMBER

Yichalem Gebeyaw 1728/07

Zerihun Melkamu 1747/07

Mandefro Cheklie 1556/07

Birhan Haymanot 1402/07

Saba Endalkachew 0065/08

Herya Hussen 6229/08

ADVISOR: FEDLU NURHUSSIEN

DATE FEBRUARY 07/2018

 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

CERTIFICATE
This is to certify that this BSc industrial project entitled Mobile based ATM Query and
Locator with speech recognition system for commercial bank of Ethiopia written by:

1. Yichalem Gebeyaw ________

2. Zerihun Melkamu ________
3. Birhan Haymanot ________
4. Mandefro Cheklie ________
5. Saba Endalkachew ________
6. Herya Hhussen _________
In partial fulfillment of the requirements for the award of Bachelor of Computer science
Is approved by me for submission. I certify further that, to the best of my knowledge, the
project represents work carried out by the students and the matter embodied in the project
has not been submitted to any other University / Institute for the award of any Degree.

___________________________ ____________________________________
Date Name and Signature of Supervisor

ii
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Declaration
This is to declare that the project work which is done under the supervision of Instructor
Fedlu Nurhussien and having the title Online House Rental System for Gondar City is the
sole contribution of:

Yichalem Gebeyaw

Zerihun Melkamu

Mandefro Cheklie

Birhan Haymanot

Saba Endalkachew

Herya Hussen

No part of the project work has been reproduced illegally (copy and paste) which can be
considered as Plagiarism. All referenced parts have been used to argue the idea and cited
properly. We will be responsible and liable for any consequence if violation of this
declaration occurs.

Date:

Group members:

FULL NAME SIGNATURE

YichalemGebeyaw _________________

ZerihunMelkamu _________________

MandefroCheklie _________________

BirhanHaymanot _________________

Saba Endalkachew _________________

HeryaHussen _________________

iii
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Acknowledgement

Any accomplishment requires the blessing of the God. So the first thanks goes to God!!

"We have taken efforts in this project. However, it would not have been possible without
the kind support and help of many individuals. We would like to extend our sincere
thanks to all of them.

We are highly indebted to Instructor Fedlu Nurhussien for his guidance and constant
supervision as well as for providing necessary information regarding the project & also
for his support in completing this documentation.

Our thanks and appreciations also go to people who have willingly helped us out with
their abilities."

iv
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table of Contents
CERTIFICATE ..................................................................................................................................... ii

Declaration...................................................................................................................................... iii

Acknowledgement.......................................................................................................................... iv

ACRONYMS ..................................................................................................................................... ix

ABBREVATIONS................................................................................................................................ x

ABSTRACT........................................................................................................................................ xi

CHAPTER ONE .................................................................................................................................. 1

1. PROJECT PROPOSAL................................................................................................................. 1

1.1 Introduction............................................................................................................................ 1

1.2 Statement of problem and justification ................................................................................. 2

1.3 Project Objectives................................................................................................................... 4

1.3.1 General objective of the system...................................................................................... 4

1.3.2 Specific objective of the system ...................................................................................... 4

1.4 Scope and limitation of the project........................................................................................ 4

1.4.1 Scope ofthe Project ......................................................................................................... 4

1.4.2 Limitation of the project.................................................................................................. 5

1.5 System Development Methodology....................................................................................... 5

1.5.1 Investigation (fact-finding) methods............................................................................... 5

1.6 System development tool ...................................................................................................... 6

1.6.1 Hardware tools ................................................................................................................ 6

1.6.2 Software tools ................................................................................................................. 6

1.7 Significance of the project...................................................................................................... 6

1.8 Beneficiaries ........................................................................................................................... 7

1.9 Time schedule......................................................................................................................... 7

2 REQUIREMENT ANALYSIS ........................................................................................................ 9

2.1 Introduction............................................................................................................................ 9

2.2 Current system ....................................................................................................................... 9

v
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.2.1 Major function of the current system description.......................................................... 9

2.2.2 Problem of the existing system..................................................................................... 10

2.3 Requirement gathering........................................................................................................ 10

2.3.1. Requirement Gathering Methodologies...................................................................... 10

2.3.1.2 Results Found............................................................................................................. 11

2.4 Business rule ........................................................................................................................ 12

2.5 Proposed system.................................................................................................................. 12

2.5.1 Overview ....................................................................................................................... 13

2.5.2 Functional requirement ................................................................................................ 13

2.5.3 Non-Functional Requirement ....................................................................................... 15

2.6 System model....................................................................................................................... 18

2.6.1 Scenario......................................................................................................................... 18

2.6.2 Use Case Modeling........................................................................................................ 21

2.6.3. Activity Diagram........................................................................................................... 36

2.6.4. Object Model ............................................................................................................... 40

2.6.5 Dynamic Modeling ........................................................................................................ 46

2.7 User Interface ...................................................................................................................... 61

CHAPTER THREE............................................................................................................................. 64

3 SYSTEM DESIGN..................................................................................................................... 64

3.1 Introduction ................................................................................................................... 64

3.2 Design goal........................................................................................................................... 64

3.3 Current software architecture ............................................................................................. 65

3.4 Proposed software architecture .......................................................................................... 65

3.4.1 Overview ....................................................................................................................... 65

3.4.2 Subsystem Decomposition............................................................................................ 67

3.4.3 Hardware and Software Mapping................................................................................. 69

3.4.4 Persistent Data Management ....................................................................................... 69

3.4.5 Access control and security........................................................................................... 71

vi
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

3.4.6Subsystem services.........................................................................................................72

3.4.7 Detailed Class Diagram..................................................................................................73

3.4.8 Package Diagram ...........................................................................................................74

References..................................................................................................................................79

List of figure
Table 1-1 Time Schedule .................................................................................................................. 8
Table 2-1.1 Table of login ..............................................................................................................23
Table 2-2Table of Send request ......................................................................................................24
Table 2-3Table of Register House ..................................................................................................25
Table 2-4Table of delete house information...................................................................................26
Table 2-5view Customer request ....................................................................................................27
Table 2-6table of view house..........................................................................................................28
Table 2-7Send response ..................................................................................................................29
Table 2-8 Table of Update house....................................................................................................30
Table 2-9Table of Send Feedback ..................................................................................................31
Table 2-10Table of Logout .............................................................................................................32
Table 2-11Use case description for generate report .......................................................................33
Table 2-12Use case description for register....................................................................................34
Table 2-13 use case description for manage account......................................................................35
Table 2-14Table of Data dictionaries .............................................................................................43
Table 3-1Table of Access control and security...............................................................................72

vii
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-1Use case diagram for Gondar city house rental system ................................................. 22
Figure 2-2Activity diagram for login ............................................................................................. 36
Figure 2-3 Activity diagram for register......................................................................................... 37
Figure 2-4 Activity diagram for Reserve house ............................................................................. 37
Figure 2-5 Activity diagram for Generate Report .......................................................................... 38
Figure 2-6 Activity diagram for Delete house................................................................................ 38
Figure 2-7Activity diagram for Send Response ............................................................................. 39
Figure 2-8Activity diagram for Create Account............................................................................. 39
Figure 2-9Activity diagram for Post house .................................................................................... 40
Figure 2-10Class diagram .............................................................................................................. 45
Figure 2-11Sequence diagram for Create account ......................................................................... 47
Figure 2-12Login Sequence Diagram ............................................................................................ 48
Figure 2-13 Send request Sequence Diagram ................................................................................ 49
Figure 2-15Send Response Sequence Diagram.............................................................................. 51
Figure 2-16 Register Houses Sequence Diagram ........................................................................... 52
Figure 2-17Delete house Information Sequence Diagram ............................................................. 53
Figure 2-18Send Feedback Sequence Diagram.............................................................................. 54
Figure 2-19Logout Sequence Diagram .......................................................................................... 55
Figure 2-20state chart diagram for log in ...........................................Error! Bookmark not defined.
Figure 2-21state chart diagrams for post house page .........................Error! Bookmark not defined.
Figure 2-22State chart diagram for generate report........................................................................ 56
Figure 2-23State chart diagrams for Register................................................................................. 57
Figure 2-24Collaboration diagram for login .................................................................................. 58
Figure 2-25Collaboration diagram for Generate report.................................................................. 59
Figure 2-26Collaboration diagram for update house...................................................................... 60
Figure 2-27user interfaces for home page ...................................................................................... 61
Figure 2-28user interfaces for login page....................................................................................... 62
Figure 2-29User interfaces for Create account page ...................................................................... 63
Figure 3-1System architecture model for proposed system ........................................................... 66
Figure 3-2Component Diagram of House Rental System .............................................................. 68
Figure 3-3Deployment diagram ..................................................................................................... 69
Figure 3-4Normalized data Base Schema ...................................................................................... 70
Figure 3-5Component diagram subsystem service......................................................................... 72
Figure 3-6Detail Class Diagram..................................................................................................... 73

viii
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 3-7Package Diagram ...........................................................................................................74

ACRONYMS
CPU: Central Processing Unit

CSS: Cascading Style Sheet

HW: Hardware

SW: Software

OOSD: Object Oriented System Analysis and Design

PHP: Hypertext Preprocessor

RAM: Random Access Memory

SRS: Software Requirement Specification

SDD: System Design Document

SPMP: Software Project Management Plan

STD: Software Test Documentation

SQL: Structured Query Language

SSN: Social Security Number

SW: Software

UML: Unified Modeling Language

RDBMS: Relational Database Management System

ix
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

ABBREVATIONS
BR: Business Rule

REQ: Requirement

UI: User Interface

GCHDO: Gondar City House Development Office

GCHRS: Gondar City House Rental System

Q: Questions

x
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

ABSTRACT
We are stuck with technology when what we really want is just stuff that works. With the
current paradigm shift in technological field, there is an urgent need to embrace and
appreciate the power of technology. Housing sector remains vigilant to face the
challenges of change by employing a new strategy that facilitates easy management of
housesrental. Hence there is need to develop a house rental system that can simplify work
for the rental managers so that all their work can be efficient and effective. To get
information about how house rental are currently being managed, we prepared questions
and ask them to a number of house rental managers, Employees and from the information
we gathered we realized all work was done manually with a lot of paper work involved.
Papers can easily get damaged or get lost leading to loss of data. It is also expensive to
keep on buying files to store your records. A lot of files make a place look untidy and also
consume a lot of space. Getting a certain file to check data from many files becomes a
difficult task. Considering those facts, I decided to develop a houserental system that can
solve all the problems experienced with the current manual system. The system was
developed in such manner that it provides maximum user friendly interface. Once you the
user logs in the system automatically show the forms. Each form has several command
buttons; new, save, cancel, delete, next, previous and exit. With the command Buttons
you can manipulate the database.

xi
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

CHAPTER ONE
1. PROJECT PROPOSAL

1.1 Introduction
House rental is one of the most popular actions taken by most people in this real world.
This is the reason why, now a day’s people move from place to place, city to city and
country to country for different purposes and they may have to stay there for limited and
unlimited time. People may move to Gondar for employment, business work, health
treatment, visiting historical places, for education, and for other purposes. The main
reason that people come to Gondar is that in Gondar there is a referral hospital witch
give’s better treatment for people who have any kind of sickness. And also in Gondar
there are different education colleges and universities witch give’s better quality
education for students. And finally Gondar is very well known historical place in
Ethiopia. Therefore many people come to Gondar for visiting such historical places.

In our project named as Gondar city online house rental system, we are going to develop
a system that provides an interactive house renting website for Gondar city. Gondar is one
of the beautiful cities found in Ethiopia. The city is found in the northern parts of
Ethiopia. Which is 750kmfar from Addis Ababa Ethiopia and 175kmfar from Bahir Dar.
Currently the city has no automated house renting system for customers. Since the city is
wide it is harder to find houses for renting in such wide city. The System feature includes
displaying posted houses with their properties, give GPS service for customers who are
going to rent the house, display withdrawal form for customers who want to leave the
house, allow managers and private owners to post houses and so many features are
included. In general our objective is to design and implement an easy to use system that
provides accurate Properties and location of houses.

Gondar city house development office is a governmental institution which is located

around Paisa. The origin of the organization is in Addis Ababa since 1967 E.C. Now this

1
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

time the office gives services for customers who live in Gondar. There are 289 living
houses and 189 houses which are used to do business activity. Since such house is found

In different Kebele, it is difficult to find the house easily. So our team members proposed
to develop the GPS based website for house rental system of Gondar city.

1.2 Statement of problem and justification

Since Gondar city is a very wide city, therefore to rent or finding a house in this city is
taken as a problem. The other problem is increasing the number of people come to
Gondar from day to day for different reasons and they want to rent a house. And also
GCHDO register customers on the paper. This paper based or manual based system leads
to different problems. One of the problems that is caused by this manual based system is
that loss of the file. This implies the information is simply put on paper without any
recovery mechanism. Since this papers are easily movable by peoples, other people may
intentionally loss the file. The main problem is that there is no any modern tool to search
and find houses for renting as well as showing the location of houses for customers. Due
to this reason new customers may face different difficulties. Among those difficulties
customers may lose money for brokers. Brokers may also give incorrect information
about the house. This leads to customers too difficult to change or leave the house after
renting if the house is not comfortable to live or work. New customer’s money or other
things may be stolen by thieves since there is no information about the thieves or the
people.

Moreover data is not secure from accident or damage as well as it is not well organized
because of this the efficiency of the working system is not good and as the amount of the
customer increase the waiting time of the customer will be increase also the customers do
not get better service as they need, then they may lose their time until they register.

The office requires significant volume of paper work to manage the habits for those
above-mentioned activities of the institution. It is time taking and even boring for the staff
or office to analyze and produce various types of reports for the management and the
institution customers who need to know their service status.

2
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Generally the main and observed problems are:-

 Man power wastage:-renters lose their energy by finding house on foot from place
to place even they cannot get house because most of houses are reserved and they
cannot know where they can get free house exactly.
 Wastage of time:-renters lose their time by searching houses in different places.
This is difficult for new customers because they may miss their work time. The
office manager loss his time to register each customer. Office employees and private
owners also loss their time to show the house and services for new renters.
 Wastage of money:-renters waste their money for coordinators payment and for taxi
in order to go the office and also private owners pay for coordinators to advertise
their house.
 Difficult to withdraw customers: - Since the system is manual it is difficult to drop
the files of customer’s on the paper.
 Coordinators or brokers false information:-coordinators give uncertain
information for renter when the renters will find the house with coordinators since
the renter did not get the house as he/she expect.
 Redundancy: - There is redundancy in renting new houses. Coordinators or brokers
may take payment from different peoples and they will give the house for the one
who gives more money for them this leads to conflict among them.
 Difficult reporting mechanism:-It is difficult to generate report about customers
and the number of house’s which is rented.
 Difficult to manage the house: - This is time killer and tedious to manage each
house.
 Prone to error: - Since manual systems are done by human being’s it is tolerable or
prone to error.
 Files are not secure:-There is no authentication mechanism to secure the
files.Thereforefiles is easily accessible by any one.

3
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

1.3 Project Objectives

1.3.1 General objective of the system

The general objective of the system is to develop a web based house rental system for
Gondar city.

1.3.2 Specific objective of the system

To achieve general objective of the system we used the following specific objectives.

 Gathering required information for proposed system by using interview,

observation, and document analysis.
 Analyzing the gathered information using SRS document
 Compare and contrast the proposed system with existing system
 Design a new proposed system to solve the existing problem.
 Specifying functional and non-functional requirements of the proposed System
 Design the proposed system using UML diagram.
 Design a user interface for the proposed system
 Design a database for the proposed system

1.4 Scope and limitation of the project

1.4.1 Scope ofthe Project

The scope of the project can be described as the overall features of what the new system
is capable of doing. This system has different features which make things easier for the
office as well as for private owners. Generally our proposed system will support the
following features.

 The system allows private owner and employee to register and post the house
and properties
 The system allows user to manage their own account and allows admin to manage
all users account.
 The system allows private owner ,Admin and employee to update the house
information
 The system allows customers to send request to the private owners and to the
admin.
 The system allows private owners and admin to send response to the customers.

4
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

 Email message notification for private owners and admin when the customer
reserves the house
 Make the system more secured by creating login account for all customer, private
owners, employees and administrators
 The system providing search tool for customers, private owner, employee , and
admin in easy and efficient way
 The system allows to private owner, admin ,employee and customers to view
houses and their information
 The system allows private owners and admin to view customers’ requests
 Our system uses GPS to indicate the place of house.
 The system allows customer to send withdrawal request

1.4.2 Limitation of the project

Generally our proposed system is limited to do the following activities.

 Our proposed system will not support online money transaction

 The proposed system uses only English language

1.5 System Development Methodology

Software development begins with a certain human need which can be taken as a
problem. We stated the statement of problem above then we develop complete
understanding on the topic. Next we had some idea to solve the problems and then we
formalize and change our idea to reality by producing software. This will be achieved by
software development, which involves eliciting system requirements specification, system
design, system implementation and finally system testing. In other words, we also had to
follow methodologies used in software engineering.

1.5.1 Investigation (fact-finding) methods

There are several fact finding techniques or methods involved in system analysis phase
that we will use them throughout the system development life cycle.

1.5.1.1 Interviewing
Help us to collect information about the current situation from the customer and the office
Manager and private owners face-to-face by asking questions prepared by the team.

5
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

1.5.1.2. Observing the organization

It allows as watching a person perform activities to learn about the current situation or

System. This is using full when the validity of date collection is in question or when the
Complexity of certain aspect of the system prevents a clear explanation by the system.

1.5.1.3 Document analysis

Study the documents that are used in the day to day activity enables the team to get more
information in order to understand about problems with the existing system,
organizational directions and rules for processing data. Furthermore, the captured
information via document analysis is very vital to use as input for the development of our
System.

1.6 System development tool

1.6.1 Hardware tools

Computer:-To develop our system we use a laptop which has the following properties.

 Windows 10 OS
 The capacity of RAM is 4GB
 The capacity of Hard disk is 640GB

1.6.2 Software tools

 Wamp Server:- is used for storing of information permanently
 Sublime Text Editor :- we used this software to edit html, PHP, JavaScript and
css codes
 Microsoft Office Word 2010:- to write proposal and documentation part of the
project
 Edraw Max:-for drawing UML software diagrams.
 Browser:-is used to display or view or access the website

1.7 Significance of the project

After implementing our proposed system provides many advantages for customers, office
workers as well as private owners and administrator. The main significance of the project
includes:

6
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

 Customers will reserve house by selecting the place, type of house and the cost
they can pay by viewing all recorded house details
 Houses will rent with short time
 Houses can become available to customers within the time of they want to rent
 Minimizes money, time, and other unnecessary wastages.
 The system is more secured than existing one so files cannot be lost easily
 It increases performance of the system.
 It makes handicap persons participant in the service
 Save time, money, and other related things.
 Decrease the difficulties of customer
 Makes the system user friendly
 Motivate the people to use online system
 Provide knowledge and internet service for the people
 Easy and manageable report
 GPS based information for the houses

1.8 Beneficiaries
Customers: - This system prevent customers from extra expense and they can get the
service everywhere at any time.

Admin, Employee and private owner: - the owners can rent the house within a short
period of time.

Developers: - We developers are also beneficiary from the system because we are going
to know detail information and understanding about the system and we can gain
knowledge how to develop new system.

Other people:-Other people may also benefited by referring the document of our project
to retrieve information related to house rental.

1.9 Time schedule

All the team members expect that the project should completed within the time frame
stated, So that the system is feasible regarding schedule.

7
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Number Task November December January January

25/2017 16/2017 10/2017 07/2018

1 Chapter One

(Proposal)

2 Chapter Two

(Requirement
Analysis)

3 Chapter Three

(System Design)

4 Whole Document

Table 1-1Time Schedule

8
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

CHAPTER TWO

2 REQUIREMENT ANALYSIS

2.1 Introduction
Requirement analysis is the initial step of constructing the whole software system. It is a
description of the project requirements that we have been gathered and analyzed. Without
requirements, the goal is not clear and understandable. In this chapter, requirements of the
software system are defined through human natural language and use case. The document
is provided in order to ensure that the software we produce will be consistent with the
need of the system’s user or customer.

During this phase, the analysis and system modeling must become full aware of
functional requirements, nonfunctional requirement of the proposed system, boundaries
of the system using use case description, Use-case diagram, showing the behavior of the
system and the communication among objects using sequence diagram and describing the
structure of the system using class diagram.

The aim of this document is to gather and analyze and give an Interactive system by
defining the current system problem statement in detail.

2.2 Current system

2.2.1 Major function of the current system description

Currently the office work’s manually. The office register customer’s on the paper.

Since it is paper based or manual based it leads to different problems. One of the
problems that are caused by this manual based system is that loss of the file. This implies
that the information is simply put on paper without any recovery mechanism. Since this
papers are easily movable by peoples, other people may intentionally or unintentionally
loss the file. The main problem is that there is no any modern tool to search and find
houses for renting as well as showing the location of houses for customers. Due to
thisReason new customers may face different difficulties. Among those difficulties
customers may lose money for brokers. Brokers may also give incorrect information
about the house. This leads to customers too difficult to change or leave the house after
renting if the house is not comfortable to live or work. New customer’s money or other

9
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

things may be stolen by thieves since there is no information about the thieves or the
people.

Moreover data is not secure from accident or damage as well as it is not well organized
because of this the efficiency of the working system is not good and as the amount of the
customer increase the waiting time of the customer will be increase also the customers do
not get better service as they need, then they may lose their time until they register.

The office requires significant volume of paper work to manage the habits for those
above-mentioned activities of the institution. It is time taking and even boring for the staff
or office to analyze and produce various types of reports for the institution customers who
need to know their service status.

2.2.2 Problem of the existing system

Since it is manual based the existing system has faced many problems. Among Those
problems which includes poor performance, prone to error and poor productivity are
listed out. The other problem is that data management related problems this implies the
data is not easily accessible, not well organized, not secure from damage and the data is
stored redundantly in the form of multiple copies of files. Since it is manual based the
system is not efficient, do not give better quality service as customers need. Due to this
reason customers do not satisfy with the service. As customer increase the waiting time of
customer to register is increase. Due to this reason customers lose their time and money
until they are registered.

2.3 Requirement gathering

This section describes the data collection methods that we use to solve the problem. How
information is gathered.

2.3.1. Requirement Gathering Methodologies

2.3.1.1. Observing the organization

We observe that in the office there are a lot of papers put on the shelf that contains the file
of customers, the information about business house and living house as well as the file of
employees who works in the office. We also saw that the office manager register
customer’s on paper. A lot of customer’s are citing in the office to wait until they can be
registered.

10
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.3.1.2. Interviewing
Help us to collect information about the current situation from the user face-to-face by
asking questions prepared by the team. The team prepares two types of questions:

2.3.1.2.1 Open-Ended Questions

The team prepares questions that require explanation or justification. The answers come
in the form of a list, a few sentences or something longer such as paragraph or essay.
Generally we are asking the following questions.

Q.1 how the customers are register?

Q.2 how many Numbers of governmental Houses are rented?

Q.3 How customers reserve house?

Q.4 How to determine the price of each house?

2.3.1.2.2 Close-Ended Questions

The team prepares questions which are simple, clear, to the point and can be answered by
"yes" or "no" response.

2.3.1.2 Results Found

These Observations had given us an extraordinary data towards developing our problem
statement and objectives. As we investigated we saw a lot of files stored on shelf. The
working environment is bad lack of good customer service. From the requirement
gathering we get what the current system look like, how the current system works and the
drawback of current system from the fact finding methods we conclude the current
system follow manual system and works are done on a paper form so we can see this
system create conflict between employees.

Generally the following results are found while gathering requirements regarding the
problem of the current house rental system.

 The office manager says that since the number of customers is becoming large
from day to day it is difficult to register, allocate and manage the rented houses for
each registered customer
 Customers say that “we are losing time to wait in the office until they become
registered or a lot of time is wasted to find a house for rent by asking the house

11
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

owner”. They also lost a lot of money for taxi to go to the office or by paying a lot
of money for brokers to show a free house.
 Private owners say that “we are losing a lot of money by paying for brokers in
order to advertise their own house”. A lot of time is wasted to show the house
properties for customers.
 Office employees say that “we are losing a lot of time to show the place of the
house and to keep the order of customers while registering”.

These results are used to identify the functionalities of our proposed system.

2.4 Business rule

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
related to access Control issues, business calculations, or operating polices and principles
of the organization. The rules have included below:

BR1: For accessing governmental houses every customer must have an ID.

BR3: To access private owned houses customers must have an ID.

2.5 Proposed system

The aim of proposed system is to develop improved facilities that can overcome all the
problems of the existing system. The system provides proper security and reduces a wide
range of manual work.

Our proposed system is better from the existing system because of the following
advantages.

 Improved accessibility of customer data.

 Reduce data redundancy.
 Maintain quality data.
 Avoid inconsistency.
 Maintain integrity.
 Enforce security measures.
 Centralized information control.

12
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.5.1 Overview
House rental system is design to provide fast and easy way of controlling all the
activities of house renting. It is also used to communicate with customer’s using the web,
keep the data for the longest time with in the database.

Our proposed system provides an easy way for customer’s to check available house’s
for renting. And also allow admin, employee and private owner to manage all customers
and house related files. This includes posting new happenings deleting updating and
posting houses .The system also provides an easy way for admin and private owner to see
customer’s request on the web and sending their response to the customer.

Generally, house rental system is concerned on managing house’s, providing easy and
understandable way of controlling the activities of house renting, and making easy
and fast of communication held between customer, admin, employee and
private owner.

The major solutions to address the problems of the existing system are as follows. Better
utilization of resources, performance, security, reliability, accuracy and in general better
service and the new system is aimed to perform basic and crucial tasks of the
organization. It contains a well-organized database server which makes data to retrieve,
update easily. Since the computer is capable of performing and processing many and huge
tasks too faster, efficient and more correct it is preferred to apply it on the system.

This section of the document provides a general description including high level
functionality of the system and the systems non-functional requirements defined in terms
of human natural language and use cases.

2.5.2 Functional requirement

Functional requirements consist of a specification of a function that the system must
support. In this section we discuss what is our web based system is expect to do. The type
of user in this system is customer (user), employee, Private owner and administrator.

Administrator:

REQ-1: The system shall allow Administrator to login before accessing system.

REQ-2: The system shall allow Administrator to manage user account.

REQ-3: The system shall allow the administrator to delete governmental house.

13
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

REQ-4: The system shall allow the administrator to update governmental house.

REQ-5: The system shall allow the administrator to view customer feedback

REQ-6: The system shall allow the administrator to view customer request.

REQ-7: The system shall allow the administrator to Generate report.

REQ-8: The system shall allow the administrator to Generate news.

REQ-9: The system shall allow the administrator to send response for customer.

Private owner:

REQ-10: thesystem shall allow Private owner to login before accessing system.

REQ-11: The system shall allow Private owner to manage user account.

REQ-12: The system shall allow the private owner to post their house.

REQ-13: The system shall allow the private owner to send response to customer.

REQ-14: The system shall allow the private owner to register their house.

REQ-15: the system shall allow the private owner to delete their house.

REQ-16: The system shall allow the private owner to update their house.

REQ-17: The system shall allow the private owner to view customer feedback

REQ-18: The system shall allow the private owner to view customer request.

Customer:

REQ-19: The system shall allow Customer to login before accessing system.

REQ-20: The system shall allow Customer to create user account.

REQ-21: The system shall allow Customer to manage user account.

REQ-22: The system shall allow Customer to send request.

REQ-23: The system shall allow Customer to give feedback.

REQ-24: The system shall allow Customer to view houses.

REQ-25: The system shall allow Customer to view response for their request.

REQ-26: The system shall allow Customer to view report generated by admin.

REQ-27: The system shall allow Customer to view location of house.

14
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

REQ-28: The system shall allow Customer to register their detail to the database.

REQ-29: The system shall allow Customer to reserve house.

REQ-30: The system shall allow Customer to change house.

REQ-31: The system shall allow Customer to view news.

REQ-32: The system shall allow Customer to send withdrawal request.

Employee:

REQ-33: The system shall allow Employee to login before accessing system.

REQ-34: The system shall allow Employee to manage account.

REQ-35: The system shall allow Employee to View and delete customer feedback.

REQ-36: The system shall allow Employee to post governmental houses.

REQ-37: The system shall allow Employee to view and delete customer request.

REQ-38: The system shall allow Employee to View and delete report generated by
Admin.

REQ-39: The system shall allow Employee to register governmental house.

REQ-40: The system shall allow Employee to View and delete news generated by Admin.

Anonymous users

REQ-41: The system shall allow Anonymous users to view services given by the office.

2.5.3 Non-Functional Requirement

2.5.3.1 User Interface and Human factors

The knowledge required from the user to access the system is: - computer usage and
website interface access. The interface of the proposed system is very easy for users.

2.5.3.2 Documentation
The documentation should only contain user manual to provide a small help guide.

2.5.3.3 Hardware Consideration

The hardware required to use the system are a computer device. The computer device can
be a laptop computer or desktop computer or a tablet with capability of connecting to the
internet and provide connection to the system.

15
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.5.3.4 Performance Characteristics

The proposed system must have 2 second response time and 3 second response time in
the worst case.

 Response Time: The output should be generated within a maximum of 3seconds

depending on the performance of the computer device.
 Resource Utilization: The application should utilize minimum amount of CPU
and memory of the device.

2.5.3.5 Error Handling and Extreme Conditions

If the user enters incorrect input like inserting empty string, inserting an incorrect
username in to the database or login with unregistered username and password the system
should display an appropriate message for each error.

The system should handle exceptions listed below

 Login error (unauthorized login): the system shall handle an attempt to login with
incorrect username and password and display appropriate message.
 Submitting Empty String.
 Inserting alphabetic value in integer text field.
 Inserting numeric or integer value in the alphabetic text field.

2.5.3.6 Quality Issues

 Efficiency: Since we will use web based system the proposed system is efficient
regarding to response time.
 Usability: The system that we develop should be easy to learn and operate or use.
 Availability: The system should be available for all working hours (24 hours).

2.5.3.7 System Modifications

As the world is capable of change from time to time; there will be future change to the
system as a result of new technology invention. Therefore the system can be upgrade to
the new technology by the system developers.

2.5.3.8 Physical Environment

This GCHRMS is affected by weather condition when the hardware and software
available for our system may be crash by weather condition. Weather conditions like

16
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

earthquake or the available resources or materials are damaged by fire. And also server or
other available software and hardware are affected by virus.

2.5.3.9 Security Issues

Security objectives will be done by using login username and password for each users and
members. User information like password should be stored in the database in encrypted
form. So it can prevent unauthorized login.

For instance, normal users are not allowed to view report except manager or admin due to
reports is considered as private and confidential. All data are stored in databases
.Therefore data’s are not erased easily.

2.5.3.10 Resource Issues

Server:

The minimum hardware requirement for MySQL is-

 CPU: 32 bit or 64 bit

 Cores: AMD Dual-core processor C70
 RAM: 2GB (or higher is recommended)
 Display resolution 1366x768(or lower is recommended)

Client:

 Web browser
 Graphics and interface tools to load display
 Internet connection

17
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.6 System model

2.6.1 Scenario
Scenario Name: login

Participating actor: Admin/Private Owner/Employee/Customer

Event: User Log-In

User select Log-In and system displays login form. Then user enters username and
password the system checks weather the username and Password is valid. If it’s valid
admin login to the system and the system displays all available operations.

If the entered values are incorrect error message is displayed.

Scenario Name: Create Account

Event: Create Account

User select create account link and system displays create formthen user fill the form and
then click create link. Then the system displays please insert correct username and
password.

Scenario Name: Manage Account

Participating actor: Customer, Employee, Admin, Private Owner

Event 1: Event: Change password

Customer or employee log in to the system with user name and password. Then select
account menu and then select change password Customer and employee select
change password link and the system Prompts the admin to enter the previous
password .The system display enter new password and confirm password Form then
customer or employee enters new password and submit the form. System validates the
entered password and displays a message Password changed successfully.

Event 2: Change username

18
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

customer or employee log in to the system with username password and then select
account menu and then select change user name link system display enter new username
form then customer or employee enters new username and submit the form .The system
validate it and display a message username changed successfully.

Scenario Name: View

Participating actor: Customer, Employee, Private Owner, Admin

Event 1: View request

Admin, Private Owner, Employee log in to system with password and user name and
select view link then system displays View feedback, View Request , View House then
select View Request link after that system displays Customer request.

Event 2: View Feedback

Admin, Private Owner, Employee log in to system with password and user name and then
select view link system displays View Feedback, View Request, View House link then
select View Feedback link system displays Customer Feedback.

Event 3: View House

Customer log in to system with password and user name and then select view link system
displays View Feedback, View Request, View House link then select View House link
system displays all available houses.

Scenario Name: Register

Participating actor: Customer, Employee, Private owner

Event: Registration

Customer, Private owner or Employee log into the system and click to registration link,
the system displays the register form. Then customer or Employee fills all data’s into the
form and click register and the system validates if the entered values are correct. If the
values are correct the system will display the message correctly registered. But if the
entered values are incorrect the system asks the user to enter valid data.

Scenario Name: Generate Report

Event: Generate report

19
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Admin log in to the system and click on generate report then system displays the report
form Admin writes the report and click submit button. If the values are incorrect system
displays please fill with correct value.

Scenario Name: Send

Participating actor: Customer, Private Owner, Admin

Event 1: Send Request

Customer log in to the system and click on send menu then system displays the request
and feedback linkcustomer then select request link and writes the request and then clicks
send. If it is correct system display your request has been sent message. Otherwise try
again message will be displayed.

Event 2: Send Feedback

Customer log in to the system and click on send menu then system displays the request
and feedback link. Customer selects feedback link System displays feedback form then
customer writes feedback and then clicks send. If it is correct system display your
feedback has been sent message. Otherwise try again message will be displayed.

Event 3: Send Response

Admin or Private Owner login to the system and select send response link. Then system
displays response form. After that admin or private owner writes the response and click
on submit button .then system displays you have sent correctly message. Otherwise please
try again message will be displayed.

Scenario Name: Delete

Participating actor: Admin, Private owner

Event: Delete House

Admin login to the system and click on delete link and select on delete house menu after
that system prompts to enter house number ,then admin enter house number and click on
delete button then system displays are you sure to delete this house message with yes or
no button will be displayed. If admin selects yes option house is deleted from database
message will be displayed. Otherwise house is not deleted message will be displayed.

Scenario Name: Logout

20
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Participating actor: Customer, Private Owner, Admin, Employee

Event: Logout

User clicks the logout menu then the system display login form of the data.

2.6.2 Use Case Modeling

In this section we are going to see about use case diagram, description of use case
diagram and activity diagram this helps to know the functional interaction between user
and the system. Use cases are drawn by examining the actors and defining what the actor
will be able to do with the system.

2.6.2.1. Use case diagram

21
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-1Usecase diagram for Gondar city house rental system

22
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.6.2.2 Description of Use case Model

Table 2-1.1 Table of login

Use case Login

name

Actors Customer, Private Owner, admin, Employee

Description The Customer, Private Owner, admin and Employee uses this form to log
into the system.

Pre-condition The Customer, Private Owner, Employee and admin should be register first
or need to have an account to login.

Basic flow of 1. The customer, Private Owner, Employee and admin enter to the
event home page
2. system displays login form
3. Enter user name and password and click login button
4. The system checks for the validity of the user name and password
5. The system displays the customer, Private Owner, Employee or
admin page
6. Use case Exit

Alternate A2.1 If the entered user name and password is not valid it displays “please
course of enter valid user name and password” go to basic flow 2.
action B3.2 If the user forgot the user name and password display reset user name
and password page.

Post condition The users (Customer, admin, Private Owner and Employee) logged in to the
main page.

23
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-2Table of Send request

Use case Send request

Actor Customer

Description This use case permits to register rental information of the customers
and the house that the customers rent.

Pre- Login
condition

Flow of 1: This use case is initiated when the actor’s clicks on send request .
event option.
2: System displays the page that contains information to be
registered
3: Actors fill all the information
4:customerclicks or press on the
Save or insert button.

5: The system verifies that the fields have been filled out correctly.

6: System displays send successfully.

7: Use case Exit

Alternate 4.1 If the customers fields are not filled out correctly system goes back
course of or returns to step 4 of basic course of Action to fill valid data.
action
Post- Customer’s information is registered.
condition

24
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-3Table of Register House

Use case Register House

Actor Private Owner and Employee

Description This use case permits to register rental information of the Private Owner
and Employee and the house that they register

Pre-condition Login

Flow of event 1: This use case is initiated when the actors clicks on register houses
option.
2: System displays the page that contains information to will be
registered.
3: Private Owner and Employee fill all the information
4: Private Owner and Employee click or press on the save or Register
button.
5: The system verifies that fields have been filled out correctly.
6: The system displays inserted successfully message.

7: Use case Exit

Alternate course of 4.1 If landlords fields are not filled out correctly system goes back or
action returns to step 3 of basic course of Action. To fill invalid field.

Post-condition Private Owner and Employee information is registered.

25
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-4Table of delete house information

Use case Delete house information

Actor Admin, Private Owner

Description Only admin can Delete Governmental house information and Private Owner
deletes their own house

Pre-condition Admin and Private Owner need to have an account to manage

Flow of event 1: This use case is initiated when admin and Private Owner click on
manage delete house option.
2: System displays the page that contains delete buttons.
3: Admin Private Owner deletes resources.
4: System displays deleted successfully if admin and Private Owner delete
house information.

5. Use case Exit

Post-condition Admin and Private Owner want to manage resources

26
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-5view Customer request

Use case View customer request

Actor Admin, Private Owner, Employee

Description When Admin, Private Owner and Employee choose view customer request
option, the system displays information.

Pre-condition Admin, Private Owner and Employee need to have an account if they want
to see more requests.

Flow of event 1: This use case is initiated when the Admin, Private Owner and
Employee clicks the view customer request option.

2: The system displays available name of customer and some

descriptions.

3: Admin, Private Owner and Employee click the view request option.

4: System displays all the available requests, recorded in the database.

7: Use case Exit

Post condition Admin, Private Owner and Employee want to know if there is customer’s
request.

Alternative 7: Admin, Private Owner and Employee only see the name and the
flow of event description of customers

27
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-6table of view house

Use case View house

Actor Customer, Private Owner And Employee

Description When actors choose view house option, the system displays all
available resources.

Pre-condition User need to have an account if they want to see more house
information.

Flow of event 1: This use case is initiated when the actors clicks on view
resources option.
2: System displays available name of the Private Owner, employee
and some descriptions.
3: customer click on house option
4: System displays all the available resources recorded in the
database.

7: Use case Exit

Post-condition Customer wants to know if house information is reserved or not.

Alternative flow 7: Actors see only name of the Private Owner and Employee
of event description if they don’t want to login.

28
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-7Send response

Use case Send response

Actor Admin, Private Owner

Description When Admin, Private Owner choose view Customer request option, the
system displays information about who is requested

Pre-condition Admin or Owner is already logged in

Flow of events 1. The Admin, Private Owner click view request button.

2. System display text area box and request button.

3. Landlord fills necessary notification and click request button to send

it.

4. The system will display send successfully message.

5. Use case Exit

Post condition Response is send to the Customer

29
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-8Table of Update house

Use case Update house

Actor Admin, Private Owner

Description Only Private Owner can update Their own house information and Admin can
delete Governmental house Information

Pre-condition Admin, Private Owner need to have an account to modify the property

Flow of event 1: This use case is initiated when Admin, Private Owner click on house
information option.
2: System displays the page that contains update buttons.
3: Admin, Private Owner updates resources.
4: System displays update successfully.
5. Use case Exit

Post-condition Admin, Private Owner want to modify house information

30
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-9Table of Send Feedback

Use case Send Feedback

name
Actors Customer

Description: To enable the users to send the feedback, to comment any Suggestion on
text area.

Precondition: The customer must be having a suggestion about the system as well as
houses property.

1. The customer click feedback button.

Flow of 2. System display text area box.
event
3. The customer writes some necessary information and click post button.

4. The system can validate if writes on text area or not.

5.the system can make save on database and post on home page

6. Use case Exit

Post Suggestion will be posted

condition

31
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-10Table of Logout

Use case name Logout

Participating actors: System administrator, customer, Employee

and Private Owner

Pre- Condition: System administrator, customer, Employee

and Private Owner should be logged in

Description: To Exit from services.

Flow of action: System administrator, customer, Employee

and Private Owner clicks on logout button.

32
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-11Use case description for generate report

Use case Name: Generate report

Actor: Admin

Description: Admin prepare a report about the houses that is rented,

Customers that is rent the house, number of houses rented

Precondition: Admin must be log in to the system

System action User action

Main course of 1) System display menu 2)Admin clicks on Generate

action: 3) System displays interface report

for generate report. 4)Admin fill report

6) Systems validate the user 5) Adminclicks on save button.

input and unfilled input.

7) Use case Exit.

Post condition Generate report successfully

4) A)If the fill form is invalid system display the form again

Alternative flow of
event

33
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-12Use case description for register

Use case Name: Register

Actors: Customer, Employee and Private Owner

Description: Customerinsert his/her Details information

in to the system orEmployee and Private
Owner inserts all detail information of
houses

Precondition: Customer, Employee and Private Owner

must be access the webpage

System action User action

1) System give 2) Customer or

Flow of event: menu bar Employee and Private

3) System display Owner click on

registration form register

6) Systems 4) Customer or

validate the user Employee and Private

input and unfilled Owner fills the form

input 5) Customer or

7) Use case Exit Employee and Private

Owner clicks the
submit button.

Post condition: Successfully register

Alternative flow of event 4.A)If the fill form is invalid system

display the register form again

34
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Table 2-13use case description for manage account

Use case Name: Manage account

Description: Admin and privateowner, employee and customer can

create, delete, change user name and password

Actors: Admin , Private Owner,employee and customer can

Precondition: Admin , Private Owner, employee and customer can

must be log in to the system

System Action User action

Main course of action: 1)System display menu option 2) Admin , Private

3)System display detail data of Owner, employee

customer and customer can

click on account
5) Systems validate the user input
and unfilled input 4) Admin, Private
Owner, employee
6) Use case Exit
and customer can fill
manage account
form.

6) Admin , Private
Owner , employee
and customer can
click on submit
button

Post condition Send successfully

Alternative: - N/A. 4. A)If the fill form is invalid system display the form
again

35
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.6.3. Activity Diagram

Activity diagram is another important behavioral diagram in UML diagram to describe
dynamic aspects of the system. Activity diagram is essentially an advanced version of
flow chart that modeling the flow from one activity to another activity.

Activity Diagrams describe how activities are coordinated to provide a service which can
be at different levels of abstraction. Typically, an event needs to be achieved by some
operations, particularly where the operation is intended to achieve a number of different
things that require coordination, or how the events in a single use case relate to one
another, in particular, use cases where activities may overlap and require coordination. It
is also suitable for modeling how a collection of use cases coordinate to represent
business workflows [1].

Figure 2-2Activity diagram for login

36
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-3Activity diagram for register

Figure 2-4Activity diagram for Reserve house

37
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-5Activity diagram for Generate Report

Figure 2-6Activitydiagram for Delete house

38
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-7ActivitydiagramforSendResponse

Figure 2-8Activity diagram for Create Account

39
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-9Activity diagram for Post house

2.6.4. Object Model

In this section we will describe the class diagram depicting the inheritance relationships
and associations that exist between the entities objects that are available on the system.
The class diagram focuses mainly on the relationship among application domain
concepts.

2.6.4.1 Data Dictionary

40
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Object Attribute Description

Admin, First Name This describe first name of an employee and admin

Employee Last Name This describe the last name of an employee and admin

User name This describes the user name of the authenticate user

Password This describes the password of the authenticate user

Age Describes the age of an employee and admin

Sex is describes the state of being male or female

Phone _ no is describes phone number of an employee and admin

Address is describes address of an employee and admin

Staff _ Id This describe the identification number of an employee and

admin

Qualification This describe the position of an employee and admin

Salary This describe the monthly income of an employee and admin

Private First Name This describe first name of the customer and private owner
Owner,

Customer

Last Name This describe the last name of the customer and private owner

User name This describes the user name of the authenticate user

Password This describes the password of the authenticate user

Age Describes the age of the customer and private owner

Sex is describes the state of being male or female

Phone _ no is describes phone number of the customer and private owner

Address is describes address of the customer and private owner

Id _ No This describe the identification number of the customer and

private owner

41
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

House House _ no is describe the identification number of House

Price This describe the monthly renting amount for the house

Size This describe width of the house measured in square meter

Kebele This describe specific place of the house

Current This describe the current property or appearance of the house

status

Photo This shows the background image of the house

Longitude This describe the location of the house along the longitude

Latitude This describe the location of the house along the equator

Location House _no This describe the identification number of the house
indicated by the location

Location This describe the name of the location

name

Longitude Is describe the distance of the location from the Greenwich

line

Account User name This describes the user name of the authenticate user

Password This describes the password of the authenticate user

Id This describe the Identification number of the authenticate

user

Type This describe the type of account weather it is gust account

or administrator account

42
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Response Id This describe the identification number of the given response

Date Describes the date on which the response is being submitted

Content Describe the written response for a particular request

Sender This describe the information of the person who sends the response

Report Id This describe the identification number of the given report

Date Describes the date on which the report is being generated

Content Describe the written report about specific issue

Reporter This describe the information of the person who is being generate the
report

News Id This describe the identification number of the news

Date Describes the date on which the news is being generated

Content Describe the generated report

Request Id This describe the identification number of the request about specific
service

Date Describes the date on which the request is being submitted

Content Describes the written request for specific service

Sender Describe customer information who sends the request

Feedback Id This describe the identification number of the given feedback

Date Describes the date on which the feedback is being submitted

Comment Describes the written comment about specific issue

Sender Describe customer information who writes the comment

Table 2-14Table of Data dictionaries

43
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.6.4.2Class Modeling

2.6.4.2.1 Class Diagram

UML class diagrams show the classes of the system, their interrelationships (including
inheritance, aggregation, and association) and the operations and attributes of the classes.
Class diagrams are used for a wide variety of purposes, including both conceptual/domain
modeling and detailed design modeling. A class model is comprised of one or more class
diagrams and the supporting specifications that describe model elements including
classes, relationships between classes, and interfaces. UML class diagrams show the
classes of the system, their inter-relationships, and the operations and attributes of the
classes [5].

44
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-10Classdiagram

45
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.6.5 Dynamic Modeling

We have identified a number of entity, boundary and control objects, along the way we
have also identified some of their attributes and associations, we represent this objects in
a sequence diagrams, depicting the interaction that occur during the use case to identify
additional associations and attributes.

2.6.5.1 Sequence diagram

Sequence diagrams describe interactions among classes in terms of an exchange of
messages over time. They're also called event diagrams. A sequence diagram is a good
way to visualize and validate various runtime scenarios. These can help to predict how a
system will behave and to discover responsibilities a class may need to have in the
process of modeling a new system [3].

UML sequence diagrams model the flow of logic within our system in a visual manner,
enabling you both to document and validate your logic and are commonly used for both
analysis and design purposes. Sequence diagrams are the most popular UML artifact for
dynamic modeling, which focuses on identifying the behavior within your system.

46
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Home page Create account

Create Account AccountDatabase
UI form

1:click Create account

button()
2: display
Account form ()

3: fill the
Required info()

4: click create
Button () 5: Validate ()

6: display alert
Message if not
Correct
7: registered ()

8: Successfully
Created ()

<<Destroy>> <<Destroy>>

Figure 2-11Sequence diagram for Create account

47
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

<<UI>> <<UI>> User Home Login

Login Home Login form Controller
AccountDatabase

User
1: Browse
home page

2:Click login()

3: Initiate ()

4: Display form
5:fill user name ()
and password
()

6: Click login ()
7: send fill form
()
8: validate fill
Form ()

9: check user
Name and
Password ()

10: Invalid user

Name &
11: Error Password ()
Message ()
12: success
Membership ()
13:Display()

Destroy
Destroy
Destroy

Figure 2-12Login Sequence Diagram

48
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Home page Request Controller RequestDatabase

Send Request Form
Customer

1:select house ()

2: processing ()

3: Display form ()

4:Customerfill
info()
5: Click send
Button() 6: Check Validity
()
7: If correct ()

8: send ()

9: sent ()
10: Your request
Successfully ()
11: if Not correct

12: Display alert

Message ()

Figure 2-13 Send request Sequence Diagram

49
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

"UI" Customer RequestDatabase

User Page
View Request

User
View Request
1: click view
Request option ()

2: Initialize ()

3: match
Customer
Request

4: Get matched
Request
5: retrieve request
()

6: show request ()

Figure 2-14View Request Sequence Diagram

50
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Response
Response Controller Database "Profile"
User Page Form User &
CustomerDB
Admin or Private Owner
1: Click
Response
Send response
Button () 2:Display

3: Fill form ()

4: Click send ()

5. Initialize ()

6: check fill

7: Check user

8: Validate ()

9: Send
Message

10: Deliver ()

11: Send
Success ()

Figure 2-15Send Response Sequence Diagram

51
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

<<UI>> Registration form Controller

Home Register HouseDatabase
Register Employee or Owner
Houses
1: Click register
Button ()

2: Initiate ()

3: Display form ()
4: Enter house
Information

5: Click Post ()
6: check validity
()
7: If correct ()

8: Register ()

9: Registered ()
10: Successful
Registered ()

11: IF not correct

()

12: Display alert

Message () <<Destroy ()

Destroy <<Destroy>>

Figure 2-16Register Houses Sequence Diagram

52
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

"UI" "Controller" HouseDatabase

Home Delete Form Delete
Admin or Private Owner
1: Click delete
Button ()
2: Initialize ()
3: Request
Record

4: Retrieve
Records
5: Display list of
Recorded ()
6: select record
()

7: click delete ()
8: Initiate delete
Record () 9: Validate ()

10: Display
Error message
() 11: Delete
Resources ()

12: Deleted ()
13: Successful
y message ()

<<Destroy>>
<<Destroy>>
<<Destroy>>

Figure 2-17Delete house Information Sequence Diagram

53
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Text Area Feedback

Send Feedback Home page
Box database

Customer

1: Click
Feedback
Button ()

2: Display ()

3:Write
Suggestion ()

4:Click Post () 5: Validate ()

6: Send ()

Figure 2-18Send Feedback Sequence Diagram

54
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

User page
Controller AccountDatabase
Home page
User
1:Click logout
Logout button()

2: processing ()

3: Query ()

4: Display ()

Destroy

Destroy

Figure 2-19Logout Sequence Diagram

55
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.6.5.2 State chart diagram

This section highlights the sequence of states that an object goes through the events that
cause the transition from one state to the other and the actions that result from a state
change.

Figure 2-20State chart diagram for generate report

56
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-21State chart diagrams for Register

57
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.6.5.3. Collaboration Diagram

UML communication diagrams, like the sequence diagrams - a kind of interaction
diagram, shows how objects interact. A communication diagram is an extension of object
diagram that shows the objects along with the messages that travel from one to another. In
addition to the associations among objects, communication diagram shows the messages
the objects send each other [2].

A collaboration diagram is an illustration of the relationships and interactions among

objects in the unified modeling language.

9: 9.check ()

6: 6.validate ()
Login form Database

10: 10.response ()

7: 7.try again () 8: 8.step 4 continues () Login

Controller

4: 4.fill user name and password ()

3: 3: Display the login form ()

5: 5.submit ()

2: 2.select login form ()

: User
1: 1: customer activates UI ()

User
Interface (UI)

Figure 2-22Collaboration diagram for login

58
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

report link

report form

1: select report link 3:the manager fill the form

2: display search form

6:try again
: Manager
9: response

4: submit
5: validate 8: check

7: step 4 will continue

report data base
controller

Figure 2-23Collaboration diagram for Generate report

59
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

update update
link form

3: fill update form

1: select update link 10: save
6: try again
2:display update form 9: edit

5:validate 8: check

4: submit
7: step 4 will continue
update data base
controller
: administrator

Figure 2-24Collaboration diagram for update house

60
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

2.7 User Interface

User interface is the front-end application view to which user interacts in order to use the
system. User interface is designed such a way that it is expected to provide the user
insight of the system [4].

The user interface is the main component that is used as a communication medium
between the user and the system. We do have a user Interface as described below.

Home Page: this page appears as the site in which the system is deployed is opened or
accessed and contains some links which lead the user to other pages according to his/her
privilege, and if the user is authorized user or has an account, he/she will directly go to
the page that he want by entering correct username, password. Otherwise they will sign
up to have an account and access the system.

Figure 2-25user interfaces for home page

Login page: this page appears as user has signed up and created its account .it gives a
choice for the role of the user to enter and also the user must enter a password in order to
access the next pages of the website .it gives a chance for the user to reset the password if
the password is not remembered by him.

61
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 2-26user interfaces for login page

62
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Create Account Page: this page appears as user has navigated to the home page .it has a
form that a user fills to create an account. User must fill username, password, Id and type
of an account weather it is an administrator or gust account to create his or her own
account.

Figure 2-27User interfaces for Register House

63
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

CHAPTER THREE

3 SYSTEM DESIGN
3.1 Introduction

In the previous chapter we have discuss the functional and non-functional requirements of
the system and produced the analysis model. In this chapter we are going to describe the
current and proposed system of architectural design. In addition to this we describe the
access control and security of our system. In addition to this we describe the access
control and security of our system. The overall system design objective is to give an
efficient, modular design that will reduce the system complexity, facilitate change and
leads to an easy implementation.

3.2 Design goal

Design goals describe the important system qualities. Design goals also define the values
against which options are evaluated. When designing a new system, a system designer
creates a model of the system from requirements made. The quality of the model highly
determines the quality of the product and future maintainability.

Design goals:-

 Response time: taking less time for system to respond to the request.

 Simplicity: we develop the new system can make user friendly graphical user
interface.

 Reliability: the system must perform its intended functions and operations in a
system's environment. Without experiencing failure or system crash.

 Security: the system must be protected from an authorized access, threats, attacks and
vulnerabilities.

 Fault tolerance: the system must have the ability to satisfy requirements despite
failures such as hardware, software or network failures.

64
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

3.3 Current software architecture

Since it is manual system there is no current software architecture for house rental
system.

3.4 Proposed software architecture

3.4.1 Overview
The architecture used for the proposed system is a 3 tier Client/Server Architecture. The
client tier is the applications user interface containing data entry forms and client side
applications. It displays data to the user. Users interact directly with the application
through user interface. The client tier interacts with the web/application server to make
requests and to retrieve data from the database. It then displays to the user the data
retrieved from the server. A client can use Internet browsers to access information from
the server.

The middle tier (web/application server) implements the business logic, controller logic
and presentation logic to control the interaction between the application’s clients and
data. The controller logic processes client requests such as requests to view customer’s
request, to record or to retrieve data from the database. Business rules enforced by the
business logic dictate how clients can and cannot access application data and how
applications process data.

A web server is a program that runs on a network server (computer) to respond to HTTP
requests. The most commonly used web servers is Apache. The web server used in this
system is Apache. HTTP is used to transfer data across an Intranet or the Internet. It is the
standard protocol for moving data across the internet.

The third tier, called the data tier, maintains the applications data such as house’s data
customer data etc. It stores these data in a relational database management system
(RDBMS).

65
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Client

HTTP
Internet

Application PHP

Database server

Web server/Application server

Figure 3-1System architecture model for proposed system

66
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

3.4.2 Subsystem Decomposition

System decomposition is undertaken to reduce the complexity of the system and gaining
insight into the identity of the constituent components. The system is decomposed in to
sub-systems which are a collection of classes, associations, operations, events and
constraints that are closely interrelated with each other.

The proposed web based house rent system is decomposed in to smaller sub-system as
shown in the following figure. These sub-systems are further decomposed in to other sub-
systems. The major sub-system identified includes:-

Registrationmanagement: -this sub-system concern with customer to register their

personal details and allow private owner and employee to register house information as
well as allow admin to register employee.

AccountManagement:-this subsystem allow customer and employee to create user

account before accessing the system as well as allow private owner and admin to delete
user account

FeedbackManagement: - in this sub system the customers can raise their comments as
well as suggestions about the resource and system as well as allow private owner and
administrator to view and delete customer feedback.

Requestmanagement: - in this sub system the customers can send their request about the
house want to rent as well as allow private owner and administrator to view and delete
customer request.

HouseManagement: - in this sub system the customers can view houses to be rented as
well as allow private owner and administrator to delete and update house information.

LocationManagement: - in this sub system the customers can view location of houses;
administratorand private owner can set location of houses

ReportManagement: - in this sub system the customer and employee can view report
generated by admin and allow admin to generate report about rented as well as unrented
houses.

ResponseManagement: - in this sub system the customer can view response generated
by admin and private owner and allow admin and private owner to send response to
customer.

67
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 3-2Component Diagram of House Rental System

68
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

3.4.3 Hardware and Software Mapping

This section describes the HW/SW mapping of the proposed system. To describe this we
have use the UML deployment diagram.

Figure 3-3Deployment diagram

3.4.4 Persistent Data Management

Persistent data management is basically used to represent the design of the database.
Database design is the process of producing a detailed data model of a database. Web
based house rent system will have database tables to store, access and maintain
information that flows in the system.

69
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Figure 3-4Normalized data Base Schema

70
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

3.4.5 Access control and security

In the systems, different actors have access to different functionality and data.
Therefore these privileges prevent unauthorized users from accessing data’s which
they don’t have granted to access. Authentication: This take place by letting users to
insert their user name and password in the displayed login form.

Authorization: This takes place by preventing users from participating in specific tasks
on which he/she doesn’t have grant to access.

Actor

Function

Customer Private Admin Employee

Owner

View location    

send request  

Register house information  

View house information     

View customer request   


Delete house information  

Send response   

Update house information  

Give feedback   

71
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Generate 
Report

Generate News 

View Report  

View News  

Delete Report 

Delete News 

Table 3-1Access control and security

3.4.6Subsystem services
In this section we describe the service provided by each sub system. In this case, we will
define the subsystem decomposition by identifying the services provided by each
subsystem. Generally this section describes the service provided by each subsystem.

Figure 3-5Component diagram subsystem service

72
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

3.4.7 Detailed Class Diagram

Class diagram with visibility and signature specified for each attributes and operations. In
this class diagram we define which attributes and operations are private to that class,
which attributes and operations can be accessed by the class decedents (protected), and
which attributes and operations are publicly accessible by the class user (public). We also
define the return type of each operations as well as the number and type of parameters of
each operations.

Figure 3-6Detail Class Diagram

73
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

3.4.8 Package Diagram

GCHRS takes 3 tier architecture styles. There are sub systems listed above and the
dependency between them is described also. In this sub topic we try to draw packages for
each subsystem.

Figure 3-7Package Diagram

74
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

CHAPTER FOUR

IMPLEMENTATION

4.1 MAPPING MODELS TO CODE

4.1.1. Bidirectional One-to-One Associations

public class Customer { public class Account {

private Account account; private Customer owner;

public Customer() { public Account (Customer

owner) {

account = new Account (this); this.owner = owner;

} }

public Account getAccount() { public Customer getOwner()

{

return account; return owner;

} }

public Account setAccount(Account public Customer setOwner(

Customer

account) { owner){

this.account=account; this. owner=owner;

} }

75
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

} }

76
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

4.1.2. One-to-Many Associations

Public class Admin { public class

NewEmployee{

Private Set NewEmployee; Private Admin admin;

Public Admin () { public void setadmin

NewEmployee = new HashSet(); (Admin newAdmin) {

} if (admin != newAdmin) {

Public void addNewEmployee(NewEmployee E) { Admin old = admin;

NewEmployee.add(E); admin= newAdmin;

setEmployee(this); if (newAdmin != null)

} addNewEmployee(this); }

} }

} }

4.1.3. Many-to-Many Associations

Public class Customer { public class Requests {

77
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

Private List Requests; private List Customer;

Public Customer () { public Requests () {

Requests = new ArrayList(); Customers = new ArrayList();

} }

Public void SendRequests public void addCustomer

(Request R) { (Customer C) {

if (Requests.contains(R)) { if (!Customers.contains(C)) {

Requests.add(R); Customers.add(C);

addCustomer(this); SendRequests (this);

} }

} }

} }

78
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

1.1.1. Mapping the Class Model to a Storage Schema Is Performed

A schema is a description of the data, that is, a meta-model for data. In UML, class
diagrams are used to describe the set of valid instances that can be created by the source
code. Similarly, in relational databases, the database schema describes the valid set of
data records that can be stored in the database. Relational databases store both the schema
and the data.

One-to-One Cardinality

Primary key

username usertype email password Status

brsh customer [email protected] 12345 1

Table 2 Customer Table

Foreign key

Sav_no fname lname AccNumber Balance Date

1 hana hayesh 2278 1200 2017-07-20

Table 3 Saving Table

1.2. SOURCE CODES FOR MAJOR CLASSES, PACKAGES OR

INTERFACES

References
[1] https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-ac
tivity-diagram/

[2] https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-
communication-diagram/

79
 WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

[3] https://www.smartdraw.com/sequence-diagram/

[4] https://www.tutorialspoint.com/software_engineering/software_user_interface_design.htm
[5] http://www.agilemodeling.com/style/classDiagram.htm

80
WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

81
WEB BASED GONDAR CITY HOUSE RENTAL SYSTEM 2018

82