Declaration

This is to declare that the project is done with 4Th year information technology department
under title of web based house rental system for Gondar city.

Project advisor: signature Date

____________ __________ __________

Project examiner Signature Date

1 _______ ________ ________
2 ______ _______ ________
3 ______ _______ ________

Group Member Signature Date

Yihenew Assefa __________ ________
Amanuel likinaw _________ ________
Seid Yimer __________ ________
Tigist Mesafint __________ _________
Meseret G/mikael _________ _________

i
Acknowledgement
First of all, the project team would like to greatly thank God, who gave us the power to
understand and to better analyzed the system. Secondly, Advisor Instructor Daniel shimelis
who gave a sounding advice to help us guide this project in the right direction, in which she
enforce us to have a massive knowledge about the project to easily familiarize with the
concept of project development.
Thirdly, we would like to thank for all Gondar city house development office employees who
gives the necessary information for our project.
Finally the project team would like to say thank all Information Technology graduating who
help the team in all system development phases from starting to end.

ii
Table of Contents
Declaration ............................................................................................................................................... i
Acknowledgement .................................................................................................................................. ii
List of tables........................................................................................................................................... vi
List of figures ........................................................................................................................................ vii
Abstract ................................................................................................................................................ viii
List of Acronym’s .................................................................................................................................. ix
Chapter one ............................................................................................................................................. 1
1. Introduction ..................................................................................................................................... 1
1.1 Background of the organization .................................................................................................. 1
1.2 Detail study about the existing system ........................................................................................ 2
1.3 Statement of the problem ............................................................................................................ 3
1.4 Objective of the project ............................................................................................................... 4
1.4.1 General objective of the system .......................................................................................... 4
1.4.2 Specific objective of the system.......................................................................................... 4
1.5 System development Methodology ............................................................................................. 5
1.5.1 Data collection methodology ................................................................................................. 5
1.5.1.1 Primary data collection ..................................................................................................... 5
1.5.1.2 Secondary data collection ............................................................................................... 5
1.5.2 System development approach................................................................................................... 6
1.6 System development tools .......................................................................................................... 6
1.7 Scope of the project .................................................................................................................... 8
1.8 Constraints of the system ............................................................................................................ 8
1.9 Delimitation of the project .......................................................................................................... 9
1.10 feasibility study ............................................................................................................................ 9
1.10.1 Operational feasibility ......................................................................................................... 9
1.10.2 Economic feasibility ........................................................................................................... 10
1.10.3 Technical feasibility .......................................................................................................... 11
1.10.4 Organizational feasibility .................................................................................................. 12
1.11 Alternative solution of the system ............................................................................................ 12
1.12 Proposed solution of the system................................................................................................ 13
1.13 Significance of the project ........................................................................................................ 13
1.14 Beneficiary of the project .......................................................................................................... 14
1.15 Hardware and software tools..................................................................................................... 14

iii
 1.15.1 Hardware tools ..................................................................................................................... 14
1.15.2 Software tools ..................................................................................................................... 14
1.16 Overall cost estimation.............................................................................................................. 15
1.16.1 Cost cash for materials ...................................................................................................... 15
1.16.2 Time schedule ................................................................................................................... 16
Chapter two ........................................................................................................................................... 17
2 System analysis .................................................................................................................................. 17
2.1 introduction ................................................................................................................................. 17
2.2 description of the existing system ............................................................................................ 17
2.3 overview of the new system .................................................................................................... 18
2.4 inputs and outputs of the system .............................................................................................. 19
2.4.1 Input of the system ............................................................................................................. 19
2.4.2 Output of the system .......................................................................................................... 19
2.5 requirement analysis of the new system .................................................................................. 20
2.5.1 Functional requirement ..................................................................................................... 20
2.5.2 Nonfunctional requirement ................................................................................................ 22
2.6 business rule ............................................................................................................................. 23
2.7 system architecture diagram..................................................................................................... 24
2.8 system use case diagram .......................................................................................................... 25
2.9 system use case description..................................................................................................... 27
2.10 activity diagram ........................................................................................................................ 37
2.11 Sequence diagram ..................................................................................................................... 41
2.12 class diagram ............................................................................................................................. 47
Chapter three ......................................................................................................................................... 49
3 System design ................................................................................................................................. 49
3.1 introduction ................................................................................................................................. 49
3.2 Design goal ................................................................................................................................. 49
3.3 process modeling ........................................................................................................................ 50
3.3.1 Collaboration........................................................................................................................ 50
3.3.2 Persistence modeling ........................................................................................................... 55
3.3.3 Deployment diagram ............................................................................................................ 56
Chapter four .......................................................................................................................................... 57
4 Implementation and testing ................................................................................................................ 57
4.1 form or interface design .............................................................................................................. 57

iv
 4.2 programming or coding ............................................................................................................... 62
4.3 testing .......................................................................................................................................... 71
4.3.1 Unit testing ........................................................................................................................... 71
4.3.2 Integration testing ................................................................................................................ 71
4.3.3 System testing ...................................................................................................................... 71
4.4 installation ................................................................................................................................... 71
4.5 client feedback ............................................................................................................................ 71
Chapter 5 ............................................................................................................................................... 72
Conclusion and recommendation .......................................................................................................... 72
1.1 Conclusion ............................................................................................................................ 72
1.2 Recommendation .................................................................................................................. 72
5.3 references ........................................................................................................................................ 73
5.4 Appendix ......................................................................................................................................... 74

v
List of tables
Table 1 system development tools ......................................................................................................... 7
Table 2 cost cash for materials .............................................................................................................. 15
Table 3 time schedule ......................................................................................................................... 16
Table 4 login use case description ....................................................................................................... 27
Table 5 send request use case description .......................................................................................... 28
Table 6 register house use case description ....................................................................................... 29
Table 7 delete house information use case description ........................................................................ 30
Table 8view customer request use case description .............................................................................. 31
Table 9 view house use case description ............................................................................................. 32
Table 10 send response use case description ........................................................................................ 33
Table 11 update house use case description ......................................................................................... 34
Table 12 send feedback use case description ........................................................................................ 35
Table 13 logout use case description ................................................................................................... 36

vi
List of figures
Figure 1 system architecture diagram ................................................................................................... 24
Figure 2 use case diagram ..................................................................................................................... 26
Figure 3 login activity diagram ............................................................................................................. 37
Figure 4 register user activity diagram ................................................................................................. 37
Figure 5 reserve house activity diagram ............................................................................................... 38
Figure 6 generate report activity diagram ............................................................................................ 38
Figure 7 delete house activity diagram ................................................................................................. 39
Figure 8 send response activity diagram ............................................................................................... 39
Figure 9 post house activity diagram ................................................................................................... 40
Figure 10 create account sequence diagram ......................................................................................... 41
Figure 11 log in sequence diagram ....................................................................................................... 42
Figure 12 send request sequence diagram............................................................................................. 43
Figure 13 register house sequence diagram .......................................................................................... 44
Figure 14 send feedback sequence diagram .......................................................................................... 45
Figure 15 send response sequence diagram .......................................................................................... 46
Figure 16 class diagram ........................................................................................................................ 48
Figure 17 collaboration diagram for login ............................................................................................ 50
Figure 18 collaboration diagram for update house ............................................................................... 51
Figure 19 collaboration diagram for generate news .............................................................................. 52
Figure 20 create account collaboration diagram ................................................................................... 53
Figure 21 upload house collaboration diagram ..................................................................................... 54
Figure 22 send feedback collaboration diagram ................................................................................... 54
Figure 23 persistence diagram .............................................................................................................. 55
Figure 24 deployment diagram ............................................................................................................. 56
Figure 25 home page ............................................................................................................................. 57
Figure 26 register house page ............................................................................................................... 58
Figure 27 login page ............................................................................................................................. 59
Figure 28 create account page ............................................................................................................... 60
Figure 29 change password page .......................................................................................................... 61

vii
Abstract
The main objective of this project is to study and understand the current system problems and
provide an automated system as a solution to enable the house rent to cope up with
technological advancement. Web-based house rental system is a system designed to enable
staff members and users to manage all aspects of their work, efficiently, cost effectively and
transparently. The project provides a web-based house rental activities. This project is aimed
to develop a system that handles manual work operation of staff workers by providing
different utilities for the renting system. The project replaces the manual file handling system
into computerized system and it makes secure the processes by providing different security
mechanisms.

viii
List of Acronym’s
BR ………………..Business rule

CSS…………………cascading style sheet

DB …………………database

GCHDO……………Gondar city house development office

GCHRS …………… Gondar City House Rental System

GPS………………….global positioning system

HTML……………….hypertext markup language

OOA………………..object oriented analysis

OOAD……………..object oriented analysis and design

OOD……………….object oriented design

OOSAD……………..object oriented system analysis and design

OOSD………………. object oriented system development

PHP………………… hypertext pre processor

REQ………………… requirement

SQL………………… structured query language

SRS…………………. Software Requirement Specification

UI…………………..user interface

UML………………… unified modeling language

ix
Chapter one

1. Introduction
Due to its numerous benefits nowadays computers are involved in every sectors of life, in
wide range of applications. And even in some areas mankind has been totally dependent on
computers.
One of the remarkable and much known products of technology advancement is the
conversion of manually-operated system into automated system. Automation produces a great
impact in the lives of mankind, particularly in the field of industry, business, medicine,
technology and education.[7]

Renting a home is popular with peoples from all walks of life. Typically students and
employees that are moving temporarily will share house renting. Basically we are initiated to
develop this system because all most all of Gondar city employees get suffer about house
renting even they leave with their relatives until they find house that was really difficult to do
practically that’s why we are developing this system today.

The main purpose of this project is to develop and implement a web based application
“online house renting system” in order to implement web based house property system to
help renters to provide reliable services. These systems tend to us to find possible solution
about the problem it helps user to access the system easily.

1.1 Background of the organization

Gondar is one of the beautiful cities found in Ethiopia. The city is found in the northern parts
of Ethiopia. Which is 750km far from Addis Ababa Ethiopia and 175km far 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.

Gondar city house development office is a governmental institution which is located around
Piassa. The origin of the organization is in Addis Ababa since 1967 E.C. Now this 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. [8]

1
In Gondar Town the population growth is increasing day to day that means different branch
offices are opened like Gondar University, this university and other company’s needs
employees and teachers to work in their company and these employees need house to serve
their life.

So we have started to develop new web based application of house renting relative with
current problem of the city we have started by studying the detail of the system.

1.2 Detail study about the existing system

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 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 institution customers who need to
know their service status.

The existing house rental system in Gondar Town currently uses the traditional way of
searching of house.

2
Once a customer finds a vacant house after a long journey, they can call the renter of the
house by the contact information tagged to the house. And if they can reach at an agreement,
mutual third party is mandatory for them to sign an agreement contact that deals about price
and different conditions.

1.3 Statement of the problem

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

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.

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
employees loss their time to register each customer.
 Wastage of money:-renters waste their money for coordinators payment and for taxi in
order to go the office.
 Difficult for customers to withdraw from house: - 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.
 Data 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.

3
 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 prone to error.
 Files are not secure:-There is no authentication mechanism to secure the files.
Therefore files are easily accessible by any one.

 Notice may remove (i.e. the rain hits notice, someone tears of the notice etc.)Before the
client reads it.

1.4 Objective of the project

For a better understanding we put our objectives in two sections: specific and general
objective.

1.4.1 General objective of the system

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

1.4.2 Specific objective of the system

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

 To gather required information for proposed system by using interview, observation,

and document analysis.
 To Analyze the gathered information using SRS document
 To Compare and contrast the proposed system with existing system
 To Design a new proposed system to solve the existing problem.
 To Specify functional and non-functional requirements of the proposed System
 To Design the proposed system using UML diagram.
 To Design a user interface for the proposed system
 To Design a database for the proposed system
 To Design implementation for the proposed system
 To Test the proposed system

4
 1.5 System development Methodology
A system development methodology provides guidelines for every facet of the system
development life cycle. Some methodologies contain massive written documentation that
defines everything the developers may need to produce at any point in the project. [1]

1.5.1 Data collection methodology

We use two data collection methods to collect the data need for the team project those are:
 Primary data collection method and

 Secondary data collection methods

1.5.1.1 Primary data collection

When the data are collected directly by the researcher for the first time is called as Primary
Data. It is original in nature and is specific to a research problem under study.

 Observation: - It is fact finding technique where the system analyst either

participates in or watches a person performs activities to learn about the system. It
gives us better measurement than the authorized personnel and we will be able to see
exactly what is being done, it is expensive and highly reliable. By observing the
existing problem we are gathering the data. Also we have referred other senior
projects. And we observe the entire broker working procedures and renters.
 Interview:-It is fact finding technique where by the system analyst collects
information from individual face to face interaction. It gives as an opportunity to
motivate the interviewee to respond freely and openly and it allows us to prove for
more feedback from the interviewee. In addition we believe that we adapt reward
questions for each individual. Having an interview making questionnaires and
observing in the around problems. Also we collected raw data or documents which are
useful for the project should be implemented.

1.5.1.2Secondary data collection

When the data are collected by someone else for a purpose other than the researcher’s current
project and has already undergone the statistical analysis is called as Secondary Data.

 Document analysis: the project team tried to discover written documents about the
organizational areas relevant to the project.

5
1.5.2 System development approach
In this project, we would use object oriented system development methodology (OOSD) for
designing. OOSD in modern software engineering is best conducted in an iterative and
incremental way. Iteration by iteration, the outputs of OOAD activities, analysis models for
OOA and design models for OOD respectively, will be refined and evolve continuously
driven by key factors like risks and business value so in this project we use OOSD due to the
above task as well as easier to use in our skill and not as much cost.

We select this 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 software codes. Increased
consistency among analysis, design and programming activities

1.6 System development tools

Programming Language programming language is a formal computer language designed to
communicate instructions to a machine, particularly a computer.

The programming language we will use:-

 PHP: we will use PHP to write the code for implementation
 Html: we will use html to display the web page.
 CSS: we will use CSS for the formatting of the system.
 Java Script: we will use java script for animation purpose and to display prompt
boxes.
Reasons to use:
 They can make effective design easily and in understand way
 Web based application
 Ease of data base connectivity
 They can be easily updated or changed
 Simple and easy to learn
 PHP has the largest user base of any scripting language(compatible with)

6
Database design:
My SQL:-My SQL provides an implementation of a database very well suited for small to
medium web pages. The database is free and open source with a commercial license
available.
Reasons to use:
 Easily compatible with the programming tool indicated above

 Relatively secure than the other database tools.

 Integrative database tool

The team plan to use the following software Development tools for the development of the
system among different available tools.
Generally system development tools are summarized in the form of table as follows

Activities Tools/program

Documentation MS word 2007/10

Design Edrawmax

Editing Paint

Client side script java script

Database server MYSQL server

Interface Html

Presentations PowerPoint

Web server Apache Wamp server

Implementation html, php, notepad++,CSS

Table 1 system development tools

7
 1.7 Scope of the 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.
Generally our proposed system will support the following features.

 The system registers and post houses

 The system manages all users account.
 The system updates house information
 The system sends request.
 The system sends response to the customers.
 The system view houses information
 The system view customers’ requests
 The system send withdrawal request
 The system generates report
 The system send feedback

1.8 Constraints of the system

System constraints are elements, factors or sub system that works as a narrow part of a road,
when congestion occurs. It put a limit on an entity, project or system from achieving its
qualities that may be developed with reference to its goals.
The constraints may include the following:-

 Lack of adequate information:-There were problems while with difficult requirements

because the employees are not voluntary to give enough information about the rental
system.
 Lack of time: - The time given to complete this project is very short the reason is a lot
of other courses assignment and exam are loaded.
 Lack of comfortable place:-There was no comfortable place to do our project proposal
as well.
 Budget:-which means for writing we did not have enough money and other resource to
complete our proposal like printer, pc etc...

8
1.9 Delimitation of the project
 Our system does not support online money transactions.
 Our system has also limitations on a place that has not internet accessibility because it
is depend on connection since it is online.
 The limitation of our system is that all users may not be participating directly to the
system since it is not done by a local language.
 Our system does not support GPS system for locating houses
 It does not include kebele houses

1.10 feasibility study

A feasibility study is an analysis used in measuring the ability and likelihood to complete a
project successfully including all relevant factors. It must account for factors that affect it
such as economic, technological, legal and scheduling factors. Project managers use
feasibility studies to determine potential positive and negative outcomes of a project
before investing a considerable amount of time and money into it. It is the measure of
evaluates and analysis of the project’s potential for success. It is based on extensive
investigation and research to support the process of decision making.

Feasibility study is a test of system proposal according to its workability, impact on the
organization, ability to meet user needs and effective use of resources.

1.10.1 Operational feasibility

The proposed system has been operationally functional and user friendly. The users of
system use the system to perform its regular task without any ambiguity. The user of
the system can understand the new system with little trial. Operationally the system has
capable of producing quick and qualitative services to users therefore the system
developed is operationally more feasible.
Operational feasibility assesses the extent to which the required software performs a series of
steps to solve business problems and user requirements. This feasibility is dependent on
human resources (software development team) and involves visualizing whether the software
will operate after it is developed and be operative once it is installed. It determines how the
system satisfies the organizations need and it also offers secure, accurate and efficient system
to the organization. The system in which we will have developed is also compatible to all
operating systems.

9
Operational feasibility also performs the following tasks:-
 Determines whether the problems anticipated in user requirements are of high
priority.
 Determines whether the solution suggested by the software development team is
acceptable.
 Analyzes whether users will adapt to new software.
 Determines whether the organization is satisfied by the alternative solutions proposed
by the software development team.
 User friendly-the system will be easy and user friendly to be acceptable of users
 The system will perform tasks that users want to do according to rental service

Our project is operationally feasible because:

 The system will reduce the need of time and manpower to give service.
 Able to use and do according to the graphical user interface on the dynamic website.
 The system solves the problems of the existing system.

1.10.2 Economic feasibility

The purpose of economic feasibility assessment is to determine the positive economic
benefits to the organization that the proposed system provides. It includes
quantification and Identification of all the benefits expected. This assessment typically
involves a cost/benefits analysis.
House rent site is available to anybody and anywhere. So the system is more functional
in reducing costs from both users and the owner.
Some benefits the system provides are:-

 Small response time And many services

 Easy and fast file management.
 Reduce cost for manual data management(Reduced expenses)
 Easy update & retrieval on stored records
According to economic feasibility there are two types of benefits which are money
consideration and which are not money consideration. These are tangible benefits and
intangible benefits.
Tangible benefits: A tangible benefit of the proposed system includes:-
 Decrease work overload

10
  Improving file storing and retrieving process
 facilitate work management
 Decrease cost needed for preparing paper, printing, decrease time and data
redundancy
Intangible benefits: it is moral satisfaction for the system user

Those benefits are intangible benefits of the new system

 Increase consistency
 Improving information accuracy
 Enable to make fast decision
 Work flow will be efficient

Getting positive result informs the economic feasibility. Therefore, the system is
economically feasible

1.10.3 Technical feasibility

The technical feasibility is primarily concerned with ascertaining whether the needed
technology is existed to accomplish things as have been suggested. Technical feasibility
assesses the current resources (such as hardware and software) and technology, which are
required to accomplish user requirements in the software within the allocated time and
budget. For this, the software development team ascertains whether the current resources and
technology can be upgraded or added in the software to accomplish specified user
requirements. Technical feasibility also performs the following tasks.
Analyzes the technical skills and capabilities of the software development team members,
and determines whether the relevant Technology is stable and established. Whether the
required technology is available or not-based on the system it is accessible on internet
enabled devices such as computer and whether the required resources are available-
Manpower or labor, Software and hardware. The proposed system is technically feasible as:

 This project is practically applicable with in the current technology.

 The software used to implement the system is well understood by the group members.
We have technical knowledge about:
 PHP used as an interface with WAMP.
 Notepad/Notepad++ to write and edit the code.

11
  MYSQL to build the database for storing the data.
 Unified Modeling Language (UML) model to do analyzing and designing in good
manner.
 The technical requirement for house system services in order to do their operation by
the new computerized system is training on the new system to know how it operates
and how to use the computerized system.
Technical feasibility assessment is focused on gaining and understanding of the present
technical resources of the organization and their applicability to the expected needs of the
proposed system. For instance we evaluate hardware and software resources to meet our
needs for project in a good manner, thus our system is Technical feasible.

1.10.4 Organizational feasibility

The proposed system is legally feasible since it does not violet or contradict any law,
regulation, custom, value of Ethiopian constitution and Ethiopian statistical agency.

1.11 Alternative solution of the system

The alternative solutions to solve the problems of the organization are:
Develop desktop application
It is application use to solve the problem that exists on the current system by storing all the
data of the organization in a well manner and it will also retrieve without much effort.
Develop Mobile Application
Another alternative way of solving the existing system problems is by creating a software
application that can be run on mobile devices such as smart phones and tablet computers.
This application use for storing large amount of data and exchange notification between each
actor of the system in a fast way than websites can.

Develop web based system

Now a day the people need to gather information using a web. The web can contain
information on house rental service at all and it simplifies the problem of getting enough
information for the employee, who needs to be a member of the organization and also for
others. The user will simply expect to be online on searching house rental system in case of
Gondar town to access any information on the house rental system.

12
1.12 Proposed solution of the system
Our team investigates the alternative solutions that can solve the problem and after detail
investigation, we select web based system for the new system because of the following
reasons:
 It meets our knowledge qualification.
 It meets our specification.
 It is easy to use.

1.13 Significance of the project

After implementing the project our proposed system provides many advantages for
customers, employees as well as administrator.

The main significance of the project includes:

 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 disabled 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

13
1.14 Beneficiary of the project
The target beneficiary groups from this project are:-

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

Organization and owners: - the organization and owners can rent the house within a short
period of time.

Developers:-We are also beneficiary from the system because we are going to know detail
information about the existence system and also we are going to gain knowledge of 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.

1.15 Hardware and software tools

1.15.1 Hardware tools

The hardware tools needed to complete the proposed system are:
 Flash Disk -To store and transfer files.
 CD -To submit the final document.
 Computer to develop our system we use a laptop which has the following properties.
 Windows 7 or 10 OS
 The capacity of RAM is 4GB
 The capacity of Hard disk is 464 GB

1.15.2 Software tools

In order to achieve our objectives successfully we are using various software tools
depending on their purpose. For example:-
 Microsoft Office Word 2007:- to write proposal and documentation part of the project
 Edraw Max:-for drawing UML software diagrams.

 Browser:-like chrome, Firefox, opera will be used for searching information for
designing and developing.

14
  MicrosoftPowerPoint2007/2013:-will be used to prepare presentation of this
project documentation.
 MYSQL server: -for developing the database
 Wamp Server- used to run server side scripting language of the project.
 Microsoft office Visio 2007:-used to design the schedules of this
project.

1.16 Overall cost estimation

1.16.1 Cost cash for materials

No Item Quantity Unit price Total price

1 Pen 2 6Birr 12Birr

2 Paper 1 100 100

3 Print cost 2 125 250

4 Telephone 25
expense

5 CD 2 8 16

6 laptop 1 27000 27000

7 Flash 1 210 210

Total Price Currently total

price is 27690
birr

Table 2 cost cash for materials

15
 1.16.2 Time schedule
This refers the tasks that will be performed in the scheduled time. Based on the time we have,
each task of our project will be proceeding based on the following time line.

Nov 2018 Dec 2018 Jan 2019 Feb 2019 Mar 2019 Apr 2019 May 2019 Jun 2019
ID Task Name
11/4 11/11 11/18 11/25 12/2 12/9 12/16 12/23 12/30 1/6 1/13 1/20 1/27 2/3 2/10 2/17 2/24 3/3 3/10 3/17 3/24 3/31 4/7 4/14 4/21 4/28 5/5 5/12 5/19 5/26 6/2 6/9 6/16

1 proposal

2 System analysis

3 presentation

4 System design

5 implementation

6 conclusion

Table 3 time schedule

16
Chapter two

2 System 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 description of the existing system

The existing house rental system in Gondar Town currently uses the traditional way of
searching of house. The owner that wants to rent writes the vacancy (some information)
about house and tag it on the door then the customer read that vacancy and contact with him
for renting purpose.
Once a customer finds a vacant house after a long journey, they can call the renter of the
house by the contact information tagged to the house. And if they can reach at an agreement,
mutual third party is mandatory for them to sign an agreement contact that deals about price
and different conditions.

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

17
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.

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 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.

2.3 overview of the new system

House rental system is designed 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 the system allows to manage all house related files. This includes posting,
deleting and updating 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 communication held between customer, admin, employees and private
owner.

18
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.

2.4 inputs and outputs of the system

2.4.1 Input of the system

The inputs of the project include the following: -
 Requires username to login to system.
 Requires password to login to system.
 customer information (username, email, usertype, password ,status)
 house information (fname , lname, email, phone no, kebele,room ,house
no,price,floor,image,type,date)

2.4.2 Output of the system

In order to make the system functional it requires input and according to the given input it
would provide output.
The output of the system includes: -
 Customer can get good information about the house.
 The employees can communicate easily and share information
 Display feedback
 Total number of houses
 Quality of service and satisfaction
 Respond general report about the house information
 Record necessary information about the house
 Good environment
 Display error message

19
2.5 requirement analysis of the new system
The purpose of requirement is used to prepare requirement specification before starting the
actual design. This enables the designer to have a clear idea about the structure and content of
the information system.

2.5.1 Functional requirement

Functional requirements that are statements of services the system should provide how the
system should react to particular inputs and how the system should behave in particular
situations. It specifies the software functionality that the developers must build into the
product to enable users to accomplish their tasks.

The main functional requirements of this system are:-

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REQ-28: The system shall allow Employee to View customer feedback.

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

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

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

21
2.5.2 Nonfunctional requirement
Non-functional requirements are requirement, which are not very basic or essential for the
system, but it can support and give more quality for the system. The non-functional
requirement of the system deals with how well the system provides service to the user. They
are also called technical requirements. It concerns to the technical aspects that your system
must fulfill, such as performance-related issues, reliability issues, and availability issues. The
new system had the following Non-functional requirements.

 User friendly interface:-since the system has attractive interface therefore users are
interested to use it.
 Error handling: - when the user makes some mistakes the system responds that error
has occurred using easily understandable messages and allows the user to recover
from the error.

 Availability:-the system is available at any time with internet connection.

 Security issue-the system is secured, users can't access the system without
authentication.

 User satisfaction:-we will satisfy all requirement of the user as much as possible by
using prioritization and negotiation.

 Efficiency: - The system responds to user requests as fast as possible and fully
operational every day for 24 hours.

 Time minimization the time taken to find a house to rent will be reduced.

 Cost minimization since searching is online expenses are reduced.

 Reliability: The system should handle invalid inputs and displays error message to
users. Reliability is one feature of the system significantly validates user inputs

 Portability: This system is portable, since it runs on different platforms. Running on

different platforms makes the system accessible by users.

 Performance: there is no ambiguous data fetched on the system and no wastage of

time to organize and integrate file.

22
2.6 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:

2.6.1 Business rule of proposed system

Our proposed system includes the following operating principles or rules:

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

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

BR3: unauthorized users cannot use the system

BR4: username and password is required to use the system

2.6.2 Business rules of existing system

The business rules of the existing system

 BR 1: House should be registered in the kebele.
 BR 2: owner should pay tax on specified time.
 BR3: Both owners and customer should submit legal agreement and take full
accountabilities.
 BR4: Every house that wants to get service from the system must be registered.
 BR5: Every customer must be paid to register from the system in order to get service.
 BR6: Agreement should be register to the system.
 BR7: customer and owner meet to submit agreement.

23
2.7 system architecture diagram
The proposed system is expected to replace the existing manual system by online house rental
system, which is the software architecture used for the system is Repository architecture
because subsystems access and modify data from a single data structure which is called the
central repository. This architecture allows different user of the system access the data from
center database server. The central repository of the proposed system is MySQL database
server which is every data related with the system is stored.[6]

Figure 1 system architecture diagram

24
2.8 system use case diagram
Use case diagram Shows use cases, actors, and their inter-relationships. A use case
diagram is a graphic depiction of the interactions among the elements of a system. A use case
is a methodology used in system analysis to identify, clarify and organize system
requirements. Use Case Model describes the proposed functionality of a new system. A Use
Case represents a discrete unit of interaction between a user and the system
Actors: An actor represents a type of users of the system that the system interacts with. An
actor is a user of the system playing a particular role.
Use cases: A use case describes the sequence of events of some types of users, called Actors,
using some part of the system functionality to complete a process.
Actor Identification
An actor initiates a use case and receives something of value from the use case. Actors are
always external to the system being modeled i.e. they are not parts of the system.
We identified the following actors.
 Administrator:

 Customer

 Owner:

 employee:

A use case diagram contains four components.

 Boundary:-which defines the system of interest in relation to the world around it.

 Actors: -usually individuals involved with the system defined according to their roles.

 Use cases: - the specific roles are played by the actors within and around the system.

 The relationships:-between the actors and the use cases

25
Figure 2 use case diagram

26
2.9 system use case description
Use case name Login

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 home
event 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 1 If the entered user name and password is not valid it displays “please enter
course of valid user name and password” go to basic flow 2.
action 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.

Table 4 login use case description

27
 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 or
course of returns to step 4 of basic course of Action to fill valid data.
action
Post- Customer’s information is registered.
condition

Table 5 send request use case description

28
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 If landlords fields are not filled out correctly system goes back or returns
action to step 3 of basic course of Action. To fill valid field.

Post-condition Private Owner and Employee information is registered.

Table 6 register house use case description

29
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

Table 7 delete house information use case description

30
Use case View customer request

Actor Admin, Employee

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

Pre-condition Admin 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 and Employee clicks the
view customer request option.

2: The system displays available name of customer and some

descriptions.

3: Admin 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 and Employee want to know if there is customer’s request.

Alternative Admin and Employee only see the name and the description of customers
flow of event

Table 8view customer request use case description

31
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 Actors see only name of the Private Owner and Employee description if
of event they don’t want to login.

Table 9 view house use case description

32
Use case Send response

Actor Admin, employee

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

Pre-condition Admin or employee is already logged in

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

2. System display text area box and request button.

3. Employee 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

Table 10 send response use case description

33
Use case Update house

Actor Admin, Private Owner

Description Only Private Owner can update Their own house information and Admin can
update 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

Table 11 update house use case description

34
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

Table 12 send feedback use case description

35
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.

Table 13 logout use case description

36
2.10 activity diagram
Activity diagrams provide a way to model the workflow of a business process. Different tools
such as decisions, start states, end states, are used on the activity diagram. 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. [4]

Figure 3 login activity diagram

Figure 4 register user activity diagram

37
Figure 5 reserve house activity diagram

Figure 6 generate report activity diagram

38
Figure 7 delete house activity diagram

Figure 8 send response activity diagram

39
Figure 9 post house activity diagram

40
2.11 Sequence diagram
UML sequence diagrams are used to show how objects interact in a given situation. A
sequence diagram is a form of interaction diagram which shows objects as lifelines running
down the page, with their interactions over time represented as messages drawn as arrows
from the source lifeline to the target lifeline. Generally, a sequence diagram shows object
interactions arranged in time sequence [2]

Figure 10 create account sequence diagram

41
Figure 11 log in sequence diagram

42
Figure 12 send request sequence diagram

43
Figure 13 register house sequence diagram

44
Figure 14 send feedback sequence diagram

45
Figure 15 send response sequence diagram

46
2.12 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].

47
Figure 16 class diagram

48
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. 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.

49
3.3 process modeling

3.3.1 Collaboration
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 [10].

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

in the unified modeling language.

Figure 17 collaboration diagram for login

50
Figure 18 collaboration diagram for update house

51
Figure 19 collaboration diagram for generate news

52
Figure 20 create account collaboration diagram

53
Figure 21 upload house collaboration diagram

Figure 22 send feedback collaboration diagram

54
3.3.2 Persistence modeling
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.

Figure 23 persistence diagram

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

Figure 24 deployment diagram

56
Chapter four

4 Implementation and testing

4.1 form or interface design

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 [9].

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 25 home page

57
House registration page: this page is used to upload houses to the system

Figure 26 register house page

58
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.

Figure 27 login page

59
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 28 create account page

60
Figure 29 change password page

61
4.2 programming or coding

<HTML>

<html lang="en-US" xml:lang="en-US" xmlns=""/>

<head>

<title>House Rental </title>

<link rel="shortcut icon" href="favicon.ico" type="imagese/x-icon" />

<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />

<meta name="Keywords" content="XML,tutorial,HTML,DHTML,CSS,

XSL,XHTML,JavaScript,ASP,ADO,VBScript,DOM,W3C,authoring,programming,

learning,beginner's guide,primer,lessons,school,howto,reference,free,examples,

samples,source code,demos,tips,links,FAQ,tag list,forms,frames,color tables,Cascading

Style Sheets,Active Server Pages,Dynamic HTML,Internet database

development,Webbuilder,Sitebuilder,Webmaster,HTMLGuide,SiteExpert" />

<meta name="Description" content="HTML XHTML CSS JavaScript XML XSL ASP SQL
ADO VBScript Tutorials References Examples" />

<link rel="stylesheet" type="text/css" href="index's_file/globalcss.css" />

<script type="text/javascript">

var gaJsHost = (("https:" == document.location.protocol) ? "../https@ssl.\default.htm" :

"../www./default.htm");

document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js'

type='text/javascript'%3E%3C/script%3E"));

</script>

<script type="text/javascript">

62
var pageTracker = _gat._getTracker("UA-3855518-1");

pageTracker._initData();

pageTracker._trackPageview();

</script>

<script type="text/javascript">

if (document.images) { // Preloaded images

demo1 = new images();

demo1.src="imag/1.jpg"

demo2 = new images();

demo2.src="IMG/2.jpg"

demo3 = new images();

demo3.src="imag/3.jpg"

demo4 = new images();

demo4.src="imag/4.jpg"

demo5 = new images();

demo5.src="imag/5.jpg"

demo6= new images();

demo6. src="imag/6.jpg"

demo7=new images();

demo7.src="imag/7.jpg"

function timeimgs(numb) { // Reusable timer

thetimer = setTimeout("imgturn('" +numb+ "')", 3000);

63
}

function imgturn(numb) { // Reusable imagese turner

if (document.images) {

if (numb == "7") { // This will loop the imagese

document["demo"].src = eval("demo7.src");

timeimgs('1');

else {

document["demo"].src = eval("demo" + numb + ".src");

timeimgs(numb = ++numb);

}}}

</script>

</head>

<body onLoad="timeimgs('1');">

</style>

<center>

<table width="950" height="100" border=0px id="table1"bgcolor=""#000000"">

<tr>

<td align="center">

<table width="950px" border="0" cellpadding="0" cellspacing="0"

style="margin-bottom:-10px;margin-top:-4px;background-color:#787878;border-bottom:0px
color="#606060 ">

<tr border="0px">

64
<td width="529px" valign="middle" style="height:90px;text-align:left">

<img align="left" border="0" src="house photo/house 2.jpg" width="215" height="120" alt=

HOUSE RENTAL" title="Gondar City House Rental System" />

&nbsp;

<font color="#33ddaa"size="+2"><p align="left"valign="bottom"><img src="IMG/h4.png"

height="50%" width="70%"/></p></font>

</td>

<table width="950px" border="0px">

<tr>

<td width="950" height="29" background-color="606060" margin-top="-15">

<div id="topnav" >

<li><a href="home.php">Home</a></li>

<!--<li ><a href="services.php">services</a> </li> -->

<li><a href="login.php">Login</a></li>

</div>

</td>

</tr>

</table>

</table>

<table style="margin-top:-12px" width="950px" border="0"color:#606060 cellpadding="0"

cellspacing="0"background-color:#606060 " ><!--content table -->

<tr >

65
<td class="left_container" height="100" width="100px" valign="top" style="background-
color:#C0C0C0 " bgcolor="#C0C0C0 ">

<br> <br><br><br><br><br>

</td>

<td bgcolor=" #ffccff "valign="top"height="150px" width="325px" margin-top="0px"

border="0px" align-top="0px"><!--center -->

<div id="pagetitle" ><!-- InstanceBeginEditable name="pagetitle" --><b> User Account

Creating Page</b><!-- InstanceEndEditable --></div>

</br>

<?php

$con = mysqli_connect('localhost','root', '','house');?>

<FORM ACTION="register.php" METHOD=POST target="" onsubmit='return

formValidation()'>

<font face="timesnewroman" size="+1">

<fieldset><legend>All fields are required:</legend>

<center>

<table align="center" bgcolor="#ffccff" style="border:0px solid black;width:400px;border-

radius:15px">

<tr><td>Account_type</td><td><select id='usertype' name="usertype" required x-moz-

errormessage="Please select one"

style="width:135px;" "height:20px;" margin-left="20px">

<option></option>

<option>admin</option>

<option>customer</option>

<option>employee</option>

66
<option>landlord</option>

</select>

</td>

</tr>

<tr>

<td>UserName :</td><td><input name="username" type="text" id="username" size"20"

style="border:1px #480000 solid;width:144px;height:25px;background:#FFFFFF;border-

radius:5px;"

required="required" placeholder="Enter User Name" ></input></td>

</tr>

<tr>

<td>Email :</td><td><input name="email" type="text" id="email" size"30"

style="border:1px #480000 solid;width:144px;height:25px;background:#FFFFFF;border-

radius:5px;"

required="required" placeholder="Enter Email"></input></td>

</tr>

<tr>

<td>Password :</td><td><input name="password" type="password" id="password" size"20"

style="border:1px #480000 solid;width:144px;height:25px;background:#FFFFFF;border-

radius:5px;"

required="required" placeholder="Enter Password"></input></td>

</tr> <!--<tr>

<td>Middle Name :</td><td><input name="regmiddlename" type="text" id="middle"

size"20" required="required" placeholder="Enter MName"></input></td>

67
</tr>-->

<!--<tr>

<td>Photo :</td><td><input name="image" type="file" id="photo" input

required="required"></td>

</tr>-->

<td colspan="2" align="center"><input type="submit" value="Add User"

name="add"></input> <input type="reset" value="Reset"/></td></center>

</table></center> </form> <br><center>

</fieldset>

</FORM>

<?php

if(isset($_POST['add']))

//image script

/* $image = addslashes(file_get_contents($_FILES['image']['tmp_name']));

$image_name = addslashes($_FILES['image']['name']);

$image_size = getimagesize($_FILES['image']['tmp_name']);

move_uploaded_file($_FILES["image"]["tmp_name"], "upload/" .
$_FILES["image"]["name"]);

$location = "upload/" . $_FILES["image"]["name"];*/

$sql="insert into account (username,email,usertype,password,status)

values('$_POST[username]','$_POST[email]','$_POST[usertype]','$_POST[password]','1')";

$result=mysqli_query($con,$sql);// or die(mysql_error());

if(!$result){

68
print "<h3><img src='IMG/error.png' width='20px' height='20px'>&nbsp;<font face='arial'
color='red' size='2'>Already Exist!</font></h3>";

else{

print "<img src='IMG/tick.png' width='25px' height='25px'><font face='arial' color='green'

size='2'> Successfully registered</font>";

//mysqli_close($con,$result);

?>

</div>

</td><!--center end-->

<td class="right_container" valign="top" width="100px" height="100px"">

<table class="right" style="margin-top:0px;color:#FFFF00;background-color:#c0c0c0"

width="100%" cellpadding="0" cellspacing="0" bgcolor="#c0c0c0">

<tr>

<td class="right" height="100px" width="100px" border="1px" valign="top"

align="center"bgcolor="#c0c0c0 "border="1px" >

<br><br><br><br>

<fieldset style=" border-color:#45565C; height:160px;">

<img src="house photo/house 8.jpg" height="150px" width="67px" name="demo"

align="center">

</fieldset>

<br/><br/><br/><br/><br/><br/><br/><br><br/><br/>

69
</td>

</tr>

</table>

</td>

</tr></table><!--content table end-->

<table width="953px" height="42px" border="1" background-color="#282828">

<tr width="953"style="margin-bottom:1px;margin-top:1px;background-color:#606060
;border:0px solid #ffffff" border="0px" cellpadding="10" cellspacing="0">

<td valign="top" align="center">

<font color="#fef943" face="arial">&copy; 2019 @ Gondar City House Rental

System.</font>

</td></tr></table>

</td></tr></table>

</center>

</body>

</html>

70
4.3 testing

4.3.1 Unit testing

Every module of the System is separately tested. I.e. the team tests every module
by applying some selection mechanism. Through this mechanism every modules gets tested.
If an error occurs correction can be taken without affecting another module.

4.3.2 Integration testing

In this testing part, all the modules combined to gather and tested for fitness with
each other and with the systems functionality. If error occurs in combining them, the
module with problem can be identified and re combined.

4.3.3 System testing

In this testing, the team performs over all functional testing by checking whether it meets the
required target.

4.4 installation
After installing wamp server software do the following steps

Step1 Get the folder “house “from the Developing Team.

Step 2 Copy the folder to WWW folder in the c: \wamp\www

Step3 Paste into the folder ”data “in the C: \Wamp\www\house

Step4 Installation is Finished.

4.5 client feedback

By testing the system by user we get good feedback. Some of the comments are:

 Since many activities are automated many problems of house rental system of
organization are solved.
 The resources such as Cost, Man power and Time saved
 Since the system needs some knowledge about the system there must be some training
for the users of the system in the future.

71
Chapter 5

Conclusion and recommendation

1.1 Conclusion
It is known that developing a system for an organization is not easy. But the team has tried its
best and developed interesting web based house rental system for Gondar city. It is available,
accurate and attractive with easy GUI approach. Finally the team expects the software will
change the house rental system and makes it more reliable accurate and secure.

1.2 Recommendation
Finally, we would like to recommend some points on the usage and accessibility of this
system.
 For the user to use this system properly.
 Gondar house rental office should have adequate computer facilities to use the new
system effectively.
 For the Town to have network connectivity
Future enhancements to enhance the performance and functionality of the system for the
future we try to include the following:-

 Develop better security Mechanisms.

 Integrated with an android version.
 Performance of transaction.

72
5.3 references

[1] Wazlawick, Raul S. Object-Oriented Analysis and Design for Information Systems:
Modeling with UML, OCL, and IFML. Morgan Kaufmann, 2014. Retrieved from 2019/01/01
https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-activity-
diagram/

[2] Kurt Bittner, Ian Spence, Use Case Modeling, Addison-Wesley Professional, Aug 20,
2002.retrieved from 2018.12.12
https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-
communication-diagram/

[3] David Harel (2005-02-22). "LSCs: Breathing Life into Message Sequence Charts".
Formal Methods in System Design. 19: 45–80.doi:10.1023/A:1011227529550. Retrieved
2018-09-20.
https://www.smartdraw.com/sequence-diagram/

[4] Ekkart Rudolph; Jens Grabowski; Peter Graubmann (1999)."Towards a Harmonization

of UML-Sequence Diagrams and MSC".University of Göttingen. Retrieved 2018-08-25.
https://www.tutorialspoint.com/software_engineering/software_user_interface_design.htm

[5] "A Formal Treatment of UML Class Diagrams as an Efficient Method for Configuration
Management 2007" (PDF). Retrieved 2018-09-22.
http://www.agilemodeling.com/style/classDiagram.htm

[6] Systems Architecture, Mark Maier and Eberhardt Rechtin, 2nd ed 2002
https://en.wikipedia.org/wiki/Systems_architecture

[7]Kempf, Kar (1961). "Historical Monograph: Electronic Computers Within the Ordnance
Corps". Aberdeen Proving Ground (United States Army).

[8] Gondar city house rental office browsers

[9]https://www.tutorialspoint.com/software_engineering/software_user_interface_design.htm

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

73
 5.4 Appendix
1. When does the house rent system started?
2. What type of houses are reserved?
3. How your system performs, is it uses computer or manual system?

 Object oriented programming language: it is a server side language and means PHP
Hypertext Pre-processor

 Firewall: is a network security system that monitors and controls the incoming and
outgoing network traffic based on predetermined security rules.

 Hypertext Transfer Protocol: is an application protocol for distributed, collaborative,

hypermedia information systems.

 Apache: is a freely available Web server that is distribute under an "open source" license.

 Automation: the replacement of human workers by technology; a system in which a

work place or processes has been converted to one that replaced human labour with
electronic or mechanical equipment.

 Database: refers to an organized collection of data for one or more purposes, it is usually
in digital form.

 Actor: are users of a system that plays a role to one or more use cases.

 Use case: describes the sequence of action that provides a measurable value to an actor
and draw as horizontal ellipse and contains use case name inside the ellipse.

74