House Rent Final7

ONLINE HOUSE RENT
MANAGEMENT SYSTEM IN DEBRE MARKOS TOWN
PROJECT REPORT
Submitted by:-
NAME…..…..……………………………………………………ID
1. Getahun Yadelew……………………………………………TER/4664/07
2. Weineshet Ayenealem…………………………………….. TER/4693/07
3. Betelhem Kelem….. ………………………………………..TER/4651/07
4. Salem HaileMariam……. ………………………………….TER/4684/07
In partial fulfillment for the award of the degree of
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

Under the guidance of
Addisu.M (Msc)
…………………..
Signature
DEPARTMENT OF INFORMATION TECHNOLOGY

COLLEGE OF TECHNOLOGY
DEBRE MARKOS UNIVERSIT
DEBRE MARKOS, ETHIOPIA
May, 2010. E.C

Online House Rent Management System 2010
Acknowledgment
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 Addisu Mesfin who gave sounding advice help us guide this project in
the right direction, in which he 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 kebele managers who gives the necessary
information for our project. Especially kebele 02 & 07 managers give the overall
Information and give feedback for the question that we arise.
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.
Page | i
Abstract
Renting a Home is popular with peoples from all around the world. Typically
students and employees that are moving temporarily will share house renting. The
existing house rental system in Debre Markos Town is done through 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.The proposed system stands for
avoiding the difficulties and side effects of the existing system. The system enables
online house rent management system to control house data in effective and
efficient way than the existing house rent management system. It also creates
security mechanism by authentication and encryption.
Page | ii
List of contents
Contents
Acknowledgment ........................................................................................................................................... i
Abstract ......................................................................................................................................................... ii
List of contents............................................................................................................................................. iii
List of table .................................................................................................................................................. vi
List of figure ............................................................................................................................................... vii
List of Acronym ......................................................................................................................................... viii
CHAPTER ONE ........................................................................................................................................... 1
1 Introduction ................................................................................................................................................ 1
1.1Introduction:............................................................................................................................................. 1
1.2 Background of project............................................................................................................................. 1
1.3 Statement of Problem .............................................................................................................................. 2
1.4 Objective of the Project .......................................................................................................................... 3
1.4.1 General objective ............................................................................................................................. 3
1.4.2 Specific objective ............................................................................................................................. 3
1.5 Scope of the project ................................................................................................................................ 4
1.6 Limitation of the project ......................................................................................................................... 4
1.7 Significance of project ............................................................................................................................ 4
1.7.1 Tangible benefits .............................................................................................................................. 5
1.7.2 Intangible benefits ............................................................................................................................ 5
1.8 System requirement ................................................................................................................................ 5
1.8.1 Hardware Requirement .................................................................................................................... 5
1.8.2 Software Requirements .................................................................................................................... 6
1.8.3 Programming and database tool ....................................................................................................... 6
1.9 Methodology ........................................................................................................................................... 7
1.9.1 Data Collection Approaches ............................................................................................................ 7
1.9.2 The System Analysis and Design Approaches................................................................................. 7
1.9.3 The System Development Model ..................................................................................................... 8
1.10 Feasibility study .................................................................................................................................... 8
Page | iii
1.10.1Technical feasibility ........................................................................................................................ 8

1.10.2 Economic feasibility ...................................................................................................................... 9
1.10.3 Operational feasibility .................................................................................................................... 9
1.10.4 Legal feasibility ............................................................................................................................. 9
CHAPTER TWO ........................................................................................................................................ 10
2 System Analyses ...................................................................................................................................... 10
Introduction:................................................................................................................................................ 10
2.1 Overview of the existing system ........................................................................................................... 10
2.2 System Requirement Specification ....................................................................................................... 10
2.2.1 Functional requirement .................................................................................................................. 11
2.2.2 Non-functional requirement ........................................................................................................... 11
2.2.3 Business Rule ................................................................................................................................. 12
2.3 System Requirement Analysis .............................................................................................................. 13
2.3.1 Actor and use case identification ................................................................................................... 13
Use case diagram ................................................................................................................................ 15
Use Case Description .......................................................................................................................... 17
2.3.2 Sequence diagram .......................................................................................................................... 25
2.3.3 Analysis class diagram ................................................................................................................... 29
2.3.4 Activity diagram ............................................................................................................................ 31
CHAPTER THREE .................................................................................................................................... 36
3 System Design ......................................................................................................................................... 36
3.1 Design class diagram ............................................................................................................................ 36
3.1.1 Class diagram description .............................................................................................................. 38
3.2 Database Design/Physical Data Model ................................................................................................. 39
3.3 User interface design............................................................................................................................. 41
3.3.1 Login page interface ...................................................................................................................... 41
3.4 Deployment Diagram ............................................................................................................................ 43
CHAPTER FOUR....................................................................................................................................... 45
4 IMPLEMENTATION .............................................................................................................................. 45
4.1. Introduction ...................................................................................................................................... 45
4.2. Overview of the programming language used ................................................................................. 45
4.3. Algorithms Used .............................................................................................................................. 45
Page | iv
4.4. Sample Codes................................................................................................................................... 47

CHAPTER FIVE ........................................................................................................................................ 51
5. Testing .................................................................................................................................................... 51
CHAPTER-SIX........................................................................................................................................... 52
6 .Conclusion and Recommendation .......................................................................................................... 52
6.1. Conclusion ........................................................................................................................................... 52
6.1.2 Recommendation ............................................................................................................................... 52
6.1.3. Future Enhancement ......................................................................................................................... 52
References ................................................................................................................................................... 53
Page | v
List of table
Table 1Login use case Description ............................................................................................................. 17
Table 2 create account use case Description ............................................................................................... 17
Table 3 upload house use case Description ................................................................................................ 18
Table 4 update house information use case Description ............................................................................. 19
Table 5 View Free House use case Description .......................................................................................... 20
Table 6 send request use case Description ................................................................................................. 21
Table 7 send response use case Description ............................................................................................... 22
Table 8 send feedback use case Description ............................................................................................... 23
Table 9 view request use case Description ................................................................................................. 24
Table 10 Admin table description ............................................................................................................... 38
Table 11 Account table description ............................................................................................................ 38
Table 12 Method for admin description ...................................................................................................... 38
Table 13 Method for customer description ................................................................................................. 38
Table 14 Method for owner description ...................................................................................................... 39
Table 15 Admin table.................................................................................................................................. 39
Table 16 Notice table .................................................................................................................................. 40
Table 17 Feedback table ............................................................................................................................. 40
Table 18 Account creation table ................................................................................................................. 41
Page | vi
List of figure
Figure 1use case diagram ............................................................................................................................ 16
Figure 2 login sequence diagram ................................................................................................................ 25
Figure 3 upload sequence diagram.............................................................................................................. 26
Figure 4 update house information sequence diagram ................................................................................ 27
Figure 5 view user sequence diagram ......................................................................................................... 28
Figure 6 send request sequence diagram..................................................................................................... 29
Figure 7 analysis class diagram .................................................................................................................. 30
Figure 8 Login activity diagram.................................................................................................................. 31
Figure 9 Upload activity diagram ............................................................................................................... 32
Figure 10 Update house activity diagram ................................................................................................... 33
Figure 11Create account activity diagram .................................................................................................. 34
Figure 12 Send request activity diagram..................................................................................................... 35
Figure 13 send feedback Activity diagram ................................................................................................. 35
Figure 14 design class diagram ................................................................................................................... 37
Figure 15 login page ................................................................................................................................... 41
Figure 16 upload house page ...................................................................................................................... 42
Figure 17 create account page ..................................................................................................................... 42
Figure 18 post notice page .......................................................................................................................... 43
Figure 19 deployment diagram ................................................................................................................... 44
Page | vii
List of Acronym
Acronyms Full Meaning
HTML------------------------------------------------------------------Hyper Text Markup Language
CSS---------------------------------------------------------------------Cascading Style Sheet
PHP--------------------------------------------------------------------Hyper Text Pre Processer
ID------------------------------------------------------------------------Identification
UML--------------------------------------------------------------------Unified Modeling Language
UC-----------------------------------------------------------------------Use Case
WAMP-----------------------------------------------------------------Windows, Apache, MySQL, PHP
MYSQL-----------------------------------------------------------------My Structured Query Language.
ACA---------------------------------------------------------------------Alternative course of action
DVD---------------------------------------------------------------------Digital versatile Disc
CD------------------------------------------------------------------------Compact Disc
PW------------------------------------------------------------------------Password
UN-----------------------------------------------------------------------Username
DMT---------------------------------------------------------------------DEBRE MARKOS TWON
BR------------------------------------------------------------------------Business Rule
Page | viii
CHAPTER ONE
1 Introduction
1.1Introduction:
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, and education.
Renting a home is popular with peoples from all around the world. Typically students and
employees that are moving temporarily will share house renting. The main purpose of this
project is to develop and implement “online house renting management system” in order to
implement online house property system to help renters and owner 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.2 Background of project

Debre Markos town is located in north western Ethiopia, in Amhara National Regional State,
East Gojjam Zone, at a distance 300 km from Addis Ababa, and 265 km from Bahir Dar the
regional capital. Its astronomical location is 10º 21” North Latitude and 37º 43’ East Longitude.
[1]
In Debre Markos Town the population growth is increasing day to day that means different
branch offices are opened like Debre Markos University, this university other company’s needs
employees and teachers to work in their company and these employees need house to serve their
life.
Page | 1
So we have started to develop new online house rent management of house renting relative with
current problem of the city we have started by studying the detail of the system.
1.3 Statement of Problem

The existing house rental system in Debre Markos 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.
This manual system has problems those are mentioned as follows.
 Notice may remove (i.e. the rain hits notice, someone tears of the notice etc.)Before the
client reads it.
 Luck of promotion and awareness creation of goods and services to customers especially
to foreigners.
 Security Issues, customers are vulnerable security risks.
 Wastage of time: There is wastage of time that the user searching the house to rent.
 Wastage of money: The user consuming money when they find the house to rent and
owner to advertise the house.
 Man power wastage:-renters lose their power by finding house on foot from place to
place even they can’t get house because most of houses are reserved and they can’t know
where they can get free house exactly.
 Users Lack of information (about town):-If the client is new to the town or doesn’t
have that much information about its surrounding, it will hard for him/her to look for
houses.
 Redundancy (overlap of user): 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.
 Presence of user: The user must be present from the house place to get full information
about the house.
 Disturbance: users disturb the renters by knocking windows to find renting house.
 Manual record: no computerized record of house (that is rented and unrented).
Page | 2
 Difficult to change: If user and owner do not agree users cannot change easily and the
owners cannot get new client quickly.
 Disable persons cannot get house easily.
 Manual record of agreement: no computerized agreements between renter and owner.
 No manual record of the system: renting system of the town is not even manually
organized
 Announcement problem: owner may not give 3 month to exit from house or give any notice.
 Payment: the payment on the house may not be fair.
 Tax collection problem: unfair tax for owners.
These problems are difficult for the client and the owner to perform the renting process.
In our project we try to solve this problem.
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

The general objective of our project is to develop online house renting management
system for Debre Markos Town.
1.4.2 Specific objective

In order to achieve the main objective, we have developed the following specific objectives:
 To make suitable condition for the customer and the owner.

 To upload new house online for renting purpose.
 To design and build the particular model of the proposed system.
 To submit agreement online.
 To develop communication system among members of the system.
 In order to view house availability anywhere anytime.
 In order to announce customer to leave from house.
 To form an easy platform for owner to post houses.
Page | 3
 To provide a way to keep track of the work progress, that offer both parties to create
agreements, communicate and share documents without ever living the site.
 To search houses anywhere in the town where there is an internet access.
 To give feedbacks to the system in different aspects.
1.5 Scope of the project

The proposed system focus on giving detail information about how customer can get house
for renting purpose and owners can post house for rent. The main scope of this project is to
develop online house renting system for Debre Markos Town.
Scope of project performs as:-
 The systems allow for owner register and post their house.
 The system used for owner to update their own resource.
 Owner and customer communicate about agreement.
 The system Secured by creating login account for users.
 The system providing search tool for a renter, owner in easy way.
 The system allows to renters view owner’s post house.
 The system allows owner and customer submit agreement.
 The system allows customer announce to search other house.
1.6 Limitation of the project

Our proposed project is not including the following activities:
 It does not include online payment.

 Only people that get internet access can use the system.
 The interface support only English language.
1.7 Significance of project

After implementing this project the system has the following benefits.
Page | 4
 Customers can reserve house by selecting the place the cost they can pay by viewing all
recorded house detail online.
 Houses rented on time with exact payment.
 Users can reserve house online even they are not in Debre Markos Town they can reserve
before coming and they can directly go to the house after they come.
 The system is more secured than existing one so users can simply believe it.
 Save time of customer and owner, customers can not lose their time to finding a house
and the owner cannot lose their time to advertise their own house property by post notice.
 Save energy of client so they cannot lose their power to search houses on foot.
1.7.1 Tangible benefits

These are benefits that can be measured in monetary terms. These include:
 Reduce the amount of paper need.
 Reduce the amount of pen need.
 Reduce cost of printer for printing notice.
 Reduce transport cost.
1.7.2 Intangible benefits

Intangible benefits cannot be measured in monetary terms directly but they do have a very significant
business impact. These include:
 Reliable data retrieval.

 Increased system performance.
 Data accessed easily.
 Data security is better.
 Improve customer satisfaction
 Decreased response time
1.8 System requirement
1.8.1 Hardware Requirement

The hardware tools needed to complete the proposed system are:
 PC-To store files, typing the document, to install and use required software’s.
Page | 5
 Flash Disk -To store and transfer files.

 CD -To submit the final document.
1.8.2 Software Requirements

In order to achieve our objectives successfully, we used various software tools depending on
their purpose. For example,
 Window7: -will be used for running the browser and the other software needed for this
project.
 Browser: - like chrome, Firefox, opera will be used for searching information for
designing and developing.
 Microsoft Word 2010/2016: -For writing documentation.
 Microsoft PowerPoint2010/2016: -will be used it 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 UML diagram of this project.
 Anti-Virus Software: - used to scan, fix Flash Disk.
1.8.3 Programming and database tool

The programming language the team uses are:
 JSP: to write server side scripting language.

 HTML: to display the web page.
 CSS: for the formatting of the web site.
 JavaScript: for validation and for dynamic page.
Database tools
Wamp Server Used to create database or back end of the system, to run and test system
application. Wamp Server consists MYSQL and APACHE
Reason behind MYSQL:
Page | 6
 Easily compatible with the programming tool indicated above

 Relatively secure than the previous database tools.
 Integrative database tool
Reason JSP:-
 Session management-User sessions are maintained on JSP server. PHP destroys the user sessions
every time
 Security.-JSP – own security framework.
1.9 Methodology
1.9.1 Data Collection Approaches

We use two data collection methods to collect the data need for the team project those
are:
 Primary data collection method
 Observation: to gather relevant information the project team observes how the
current system works.
 Interview:-We have used this method to gather information by asking the manager
of Keble 07 and the kebele manager of 02.
We have also interviewed the house of contract in the office of “file and
information handling”
 Secondary data collection methods
 Document analysis: the project team tried to discover written documents about the
organizational areas relevant to the project.
1.9.2 The System Analysis and Design Approaches

The goal of this section is to provide the basic overview of the system that we are
going to develop. The system analysis and design approaches for this project we
used the object oriented system analysis & design. Because
 It provides code and function reuse through the concepts of inheritance,
polymorphism, encapsulation, modularity, coupling and cohesion.
Page | 7
 To design the system the project team has choose Object Oriented Modeling
techniques and Unified modeling language tools.
 Understanding of the structure is easy because object oriented modeling and tools
used to represent real world entities.
 It enables us to comprehensively model a system before we develop it.
 Modification of the object implementation is easy because objects are loosely
coupled.
1.9.3 The System Development Model

There are various software development life cycle models defined and designed
which are followed during the software development process. These models are
also referred as “Software Development Process Models". Each process model
follows a Series of steps unique to its type to ensure success in the process of
software development. But the proposed system follows Incremental model.
Because In this model, each module passes through the requirements, design,
implementation and testing phases. A working version of software is produced
during the first module, so you have working software early on during the software
life cycle. Each subsequent release of the module adds function to the previous
release. The process continues till the complete system is achieved.
1.10 Feasibility study

Feasibility study is a study that determines whether a proposed system is technically, financially,
and operationally viable. A 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.1Technical feasibility
The proposed system can be easily maintain and repair, because the system is developed by
familiar programming language The project team members learned programming languages that
required for the successful completion of the project such as java script, CSS, HTML,
JSP,MySQL.These languages are simple, open source and already known, so the team developed
the system easily.
Page | 8
1.10.2 Economic feasibility

The purpose of the 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.
1.10.3 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 user’s .therefore, the system developed is operationally more
feasible.
1.10.4 Legal 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.
Page | 9
CHAPTER TWO
2 System Analyses
Introduction:
Requirement analysis is the main activities that must be undertaken to have a clear understanding
of the system that is being used. Studying the requirement analysis of the existing system brings
about an important contribution to the entire development process. It is after the compilation of
this step that we can realize what goes wrong, which activities are right and which activities
should be encouraged. And what alternative methods should be taken to increase the
performance of the proposed system and to make the new system fully applicable by the
particular organization.
2.1 Overview of the existing system

The existing house rental system in Debre Markos 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.
2.2 System Requirement Specification

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.
Page | 10
2.2.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:-
 The system store available information of house.

 The system store users record
 The systems provide communication between owner and customer.
 The system updates the house information by the owner.
 The system provide search tool for a Customers, owner and admin in easy
and efficient way.
 The system view feedbacks send from user.
 The system would enable to manage account i.e. Add new account, update
account, view account.
 The system store agreement
 System generate report
 System announce to customers to exit.
2.2.2 Non-functional 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.
Page | 11
 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.
2.2.3 Business Rule

Our proposed system includes the following operating principles or rules:
 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.
Business rules for the proposed system are as follows:
 BR1: Every house that wants to get service from the system must be registered.
 BR2: Every customer must be paid to register from the system in order to get
service.
 BR3: Agreement should be register to the system.
 BR4: customer and owner meet to submit agreement.
Page | 12
2.3 System Requirement Analysis
2.3.1 Actor and use case identification

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: manages the whole system of the project.

 Customer: search and view free house from the system online.
 Owner: view their house and update information.
 Record Officer: Record house, generate report and control their tasks related to
the owner and renters.
 Kebele manager: View & approve or confirm data recorder report
.Use Case Identification
A use case is a list of actions, roles or events that are performed by an actor, to achieve a system
goal. The project team identified the following use cases for the new system.
Use case name Use Case ID Uses/includes

Login UC1
Create account UC2 UC1
Upload house UC3 UC1
Update house information UC4 UC1
Update account UC5 UC1
Page | 13
View free house UC6

View reserved house UC7 UC1
View feedback UC8 UC1
View response UC9 UC1
View request UC10 UC1
Search house UC11 UC1
Send request UC12 UC1
Send response UC13 UC1
Send feedback UC14 UC1
Post notice Uc15 Uc1
View user Uc16 Uc1
Register owner Uc17 Uc1
View notice Uc18 Uc1
Register house Uc19 Uc1
Block account Uc20 Uc1
Generate report Uc21 Uc1
Send agreement Uc22 Uc1
View agreement Uc23 Uc1
Update agreement Uc24 Uc1
Approve report Uc25 Uc1
Announce Uc26 Uc1
View report Uc27 Uc1
Register kebele Uc28 Uc1
Register customer Uc29
View announce Uc30 Uc1
Update password Uc31 Uc1
Reject report Uc32 Uc1
Check payment Uc33 Uc1
Reject payment Uc34 Uc1
Send payment Uc35 Uc1
Page | 14
View account Uc36 Uc1

Register manager Uc37 Uc1
Logout Uc38
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
 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: -which the specific roles are played by the actors within and around the system.
 The relationships between the actors and the use cases
Page | 15
Register Manager view disagreement

Create Account
Register owner
View user
Check Payment
Register House
update password
Reject Payment
Upload house
View feedback «uses»

«uses»
«uses» view report result
«uses»
Admin Register kebele «uses» «uses»
«uses» «uses» Generet report
«uses»
Update account «uses»
«uses» «uses»
«uses» View reserved house

Block account «uses»
«uses»
«uses»
Register Recorder «uses»
View Agreement
«uses» «uses»
Login
Approve report «uses» «uses»
«uses»
post notice
«uses» Send response
«uses» «extends»
View Report
«uses» «uses»
«uses» Update Agreement
Kebele manager Reject report «uses»
Logout «uses»
«uses» View request

Vew Announce «uses»
Update House Info
«uses»
Send request
View free house Send Agreement Owner
View response
View account View Address

Customer Send receipt
Send Announcement
Search House
Send Disagreement
View Notice
Send feedback
Figure 1use case diagram
Page | 16
Use Case Description
Table 1Login use case Description
Use case name Login

ID Uc1
Actor Customer, owner,admin,kebele manager,recored officer
Description The Customer, owner, admin uses this form to login into the
system.
Pre-Condition The users must have username and password.
Post-Condition User successfully login into their page.

Basic Course Of Step:
Action 1.User open system to login
2. The system displays the login form
3. Fill user name and password and click login button
4. Validate user name and password
5 .The systems display the appropriate page.
6. Use case ends
Alternative course of action 1. The system returns the login form to resubmit valid data.
Table 2 create account use case Description
Use case name Create Account

ID Uc2
Actor Admin
Description Each user has its own account.
Pre-Condition Administrator must be authenticated and authorized.
Post-Condition User can use the account to interact the system.

Page | 17

3. Administrator enter username and password.
4. Administrator click on create account button.
5. System displays the form.
6. Administrator fills create account form.
7. Validate form.
8.the system display successfully message
9. Use case ends.
Alternative course of 1. If the administrator’s entry (user name and Password) is not
action Correct the system displays error message and return to step
2.
2.If an administrator fills invalid data the system display error
Message and go to step5.
Table 3 upload house use case Description
Use Case upload house

ID Uc3
Actor Record Officer
Description This use case permits to upload house information that they rent.
Pre-condition House must be Registered to the system.
Post-condition House information registered successfully.
3.owner enter user name and password
4. Systems directed to user page.
5. Click upload house link.
6.The system display forms
7. Owner enters the data and click upload button.
Page | 18
8. The form checks the validity of the input.

9.Display message successfully upload
10. Use case end.
Alternate Course Of 1. If the recorder entry (user name and Password) is not
Action Correct the system displays error message and return to step 2.
2.If an recorder fills invalid data the system display error
Table 4 update house information use case Description
Use Case Update house information

ID Uc4
Actor Owner
Description Only owner can update house information.
Pre-condition Owner must have an account to modify his house.
Post-condition The house information updated successfully.
3.User enter user name and password
4. Systems directed to user page.
5. Click update house link.
6.The system display forms
7. Owner enters the data and click update button.
8. The system checks the validity of the input.
9. Display message successfully updated.
10. Use case end.
Alternate Course 1. If the owner entry (user name and Password) is not
Of Action Correct the system displays error message and return to step 2.
2.If an owner fills invalid data the system display error
Page | 19
Table 5 View Free House use case Description
Use Case View free house

ID Uc6
Actor Customer, owner,recored officer ,kebele manager
Description When users choose view house information option, the system
displays registered free house information.
Pre-condition Uses want to see free house.
Post-condition User view free house online.
Action 1. User opens system.
2. Systems directed to home page.
3. Users click home link.
4. System displays free house and some descriptions.
5. User view free house.
6. Use case end
Alternate Course Of 1.If user enters into other page than view house return to
Action Step 1.
Page | 20
Table 6 send request use case Description
Use Case Send request

ID Uc12
Actor Customer, owner
Description User communicates by sending request.
Pre-condition User must be login to his/her home page.
Post-condition Send request success.

4. Systems directed to each user page.
5. The user clicks on send request button.
6. The system displays send request form.
7. The user fills the request detail information.
8. The system validates the request.
9. The system displays successfully sent message.
10.End use case
Alternate Course Of 1. If the user entry (user name and Password) is not
2.If an user fills invalid data the system display error
Page | 21
Table 7 send response use case Description
Use Case Send response

ID Uc13
Actor Owner,admin,record officer
Description To give response according to the asked information.
Pre-condition User already login to system.
Post-condition Response sent to the sender of request.
5. The user clicks on view request link.
6. The system displays request and click send response button .
7. The user fills the response detail information.
8. The user clicks on send response button.
9. The system validates the response details.
10. The system displays successfully send message.
11.End use case
Alternate Course Of 1. If the user entry (user name and Password) is not
2.If an user fills invalid data the system display error
Page | 22
Table 8 send feedback use case Description
Use Case Send feedback

ID Uc14
Actor Customer, owner
Description Give suggestion about renting system.
Pre-condition The user must be having a suggestion about the system as well as
houses property.
Post-condition Suggestion will be solved.
Action 1.User open system
2.User click on feedback link from home page
3. The system display feedback form.
4.User fills the form on the text area provided
5.User click on send button
6. The System displays the success message.
7. Use case end.
Alternate Course Of 1. If user does not get send feedback page go to step 2.
Action 2. If the user’s entry is not Valid the system displays error message
and return to step 3.
Page | 23
Table 9 view request use case Description
Use Case View Request

ID Uc12
Actor Owner,admin,record officer
Description When owner and admin choose view request option, the system
displays request.
Pre-condition Owner and admin need to have an account if they want to see more
requests.
Post-condition Owner and admin know there is request.
Basic Course Of 1.User open system to login
Action 2. The system displays the login form
5: user clicks the view request option.
6: System displays all the available requests, recorded in the
database.
7. User can view request.
8. Use case end.
Alternate Course Of 1. If the owner, admin entry (user name and Password) is not
Action correct the system displays error message and return to step 2.
2. If user does not send request the system display no request
Page | 24
2.3.2 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]
USER system login form Database
1. OPEN() 2. display
3. enter user name and password 4.check validation()

5. submit form()
7.re-enter un and pw() 6. if incorrect
9.user get thier specfic page() 8. else
Figure 2 login sequence diagram
Page | 25
Recorder<<actor>> SYSTEM LOGIN FORM OWNER PAGE UPLOAD HOUSE FORM DATABASE
1. OPEN() 2.display
3.enter username and password

4.validate form()
5.check() 6.check not true
7.invalid input()
8.check true
9.display()
10.click upload link()

11.display()
12.fill form and click upload button 13.validate form()

14.upload()
16.invalid input() 15.check not true
logout 18.succssesfully upload 17.check is true
Figure 3 upload sequence diagram
Page | 26
owner<<actor>> system login form owner page update form database

1.open() 2.display
3.enter user name and password 4.validate form()

5.check()
7.invalid input() 6.check not true
9.display() 8.check is true

10.click update link()
11.display()
12.fill form and submit update button

13.validate form()
14.update()
16.invalid input() 15.check is not true
18.successfully updated 17.check is true

logout
Figure 4 update house information sequence diagram
Page | 27
Admin system login form admin page database

1.open() 2.display
3.enter username and password 4.validate form()

5.check()
7.invalid input() 6.check is not true
9.display()
10.click view user linck()
8.check is true
11.display()
admin success
Figure 5view user sequence diagram
Page | 28
customer/owner system loginform userpage send request form database
1.open() 2.display
3.enter username and password

4.check un and pw
5.check()
6.check is not true
7.invalid input()
9.display() 8.check is true
10.click send request link

11.display()
12.fill form and click send button 13.validate form()

14.send()
15.check is not true

16invalid input()
18.sent successfully 17.check is true

logout
Figure 6 send request sequence diagram
2.3.3 Analysis class diagram

A class diagram is diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods) and the relationships among objects Class diagrams can also be used
for data modeling. Class diagram has three components. The top component contains the name of the
class. The middle components contain the attributes of the class. The bottom component contains the
operation the class can execute. [3]
Page | 29
1..1
1..1
have USER House

have -have 1..1
-User name -Username
1..*create Account -fname -KID
-lname -house number
-username -village
Admin -password
* -sex
1..* -age -area
-username -Role
-email -nroom
-password -status
-mobile phone -toilet
+create acount() view -shawer
+view user() -kebele
-woreda -price
+block account() 1..* -image
check feedback -zone 1..*
-regin -status
1..* -fid
-fname -scode
payment -email
-Username -subject send 1..*
-password
-content have
-tin number
-receipt -date *
* view
+Register()
send -status 1 1
+Update() reserve
+Generate report() Request
1..* owner
sened -reqid
1..1 1..*
send -username
+send response()
-request
customer +view house()
Response -date
Register 1..* +view notice()
-repid - email
+search house() +view response()
-username -reciver email
+view house() view
-response -nfamily Record
+view response() 1..*
-date -status 11..*1 1..*
1..1
-email 1
1..* -reciver email
1..*
-status 1
accept send
view
1 view Register
Notice
-noticeid send
-subject view
-content
-pdate
post -edate 1..* view
-status *
Agreement *
have
-AgreementID Report Recorder
1..* -Username
Kebele 1
Approve -kid
Manage Manager -house number +Register()
-KID
1..* -Username
-content +Update()
-Location
1..* -date +Generate report()
Announce 1..1 +Approve() -ckebele id
-AgreementID -status
-Username
-kid
1..* Work on
-house number 1..*
-reason Approve
-date
-status send
Figure 7 Analysis class diagram
Page | 30
2.3.4 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]
open home page
enter username and password
click login button
invalid valid
display error message display user page
Figure 8 Login activity diagram
Page | 31
Recorder system display login page enter un and pw click login button
invalid
re-enter correct un and pw
valid
system display owner page
click upload linck
system display upload form
Fill the form and press ok button
invalid
re-fill correct data
valid
upload successfully
logout
Figure 9 Upload activity diagram
Page | 32
Owner system display login page enter un and pw click login button
invalid
valid
system display owner page
click update linck
system display update form
Fill the form and press update button
invalid
valid
update successfully
logout
Figure 10 Update house information activity diagram
Page | 33
Admin system display login page enter un and pw click login button
invalid
valid
system display admin page
click create account linck
system display create account form
Fill the form and press ok button
invalid
valid
account creat successfully
logout
Figure 11Create account activity diagram
Page | 34
owner/customer system display login page enter un and pw click login button
invalid
valid
system display user page
click send request linck
system display send request form
fill form and press sent button
invalid
valid
request sent successfully
logout
Figure 12 Send request activity diagram
user open home page user click send feedback linck
system display feedback form
user fill form and click submit
invalid
system display error message
valid
system display success message
Figure 13 Send feedback Activity diagram
Page | 35
CHAPTER THREE
3 System Design
System design defines the architectures, components, modules, and data for a system to satisfy
specified requirements. It is concerned with how the data is represented and stored within the
system. Systems design is therefore the process of defining and developing systems to satisfy
specified requirements of the user.
The system design relates to the actual input and output processes of the system. This is laid
down in terms of how data is input into a system, how it is verified/authenticated, how it is
processed and how it is displayed.
3.1 Design class diagram

The class diagram is a static diagram. It represents the static view of an application. Class diagram is not
only used for visualizing, describing and documenting different aspects of a system but also for
constructing executable code of the software application. The class diagram describes the attributes and
operations of a class and the constraints imposed on the system. The classes diagrams are widely used in
the modeling of object oriented systems because they are the only UML diagrams, which can be mapped
directly with object-oriented languages. The class diagram shows a collection of classes, interfaces,
associations, collaborations and constraints. It is also known as a structural diagram.[5]
Page | 36
1..1
1..1
havehave create House

-have 1..1
USER
-User name:varchar() -Username:varchar()
1..* -fname:varchar() -KID:string()
Account
-lname:varchar() -house number:int
-username:varchar() -village:varchar()
Admin * -sex:varchar()
-password:varchar() -area:int
-username:varchar() -age:int
-Role:varchar() -nroom:int
-password:varchar() -emaiL:int()
-status:int -toilet:varchar()
+create acount() -mobile phone:int()
1..* -kebele:string() -shawer:varchar()
+view user() -price:int
+block account() -woreda:varchar()
1..* -zone:string() -image:varchar()
check view 1..*
feedback -regin:string() -status:varchar()
1..*
-fid:autoincment -scode:varchar()
payment -fname:varchar()
-Username:varchar() -email:varchar() send 1..*
-password:varchar() -subject:varchar()
-tin number:string() -content:varchar() reserve
-receipt:varchar() *
-date:date() have
+Register() * view
+Update()
send -status:varchar() 1 1
+Generate report()
1..* Request
sened 1..* owner
1..1 send -reqid:autoinc
-username:varchar()
customer -request:varchar() + response()
Response
1..* -date:date(0 +view house()
Register +search house() view -repid:autoincrement - email:varchar() 1..*
+view house() -username:varchar() -remail:varchar() 1
-response:varchar() 1..*1..*
1 Record
+view response() -nfamily:int
1..1
-date:date(0 -status:varchar()
1..* -email:varchar()
1..* -reciver email:varchar()
accept -status:varchar() 1 send
1
view
1 Register
Notice send
-noticeid:auto
-subject:varchar() send
view
-content:varchar()
post -pdate:varchar() 1..* view
-edate:varchar()
-status:varchar() *
have Agreement
Kebele -AgreementID:auto 1..*
1..* Recorder
-KID:string() -Username:varchar()
-Username:varchar() 1 -kid:string()
Manage Report
1..* - Manager Approve -house number:int +Register()
-content:varchar() +Update()
1..1 -date:date(0 +Generate report()
+Approve() 1..* -ckebele id:varchar()
Announce
-status:varchar()
-AgreementID:auto
-Username:varchar() 1..* 1..* Work on
-kid:varchar()
-house number:int
-reason:varchar() Approve
-date:date() send
-status:varchar()
Figure 14 design class diagram
Page | 37
3.1.1 Class diagram description
Table 10 Admin table description
Attribute Purpose data type

aid Uniquely identify the administrator Varchar
Fname First name of administrator Varvhar
Lname Father name of administrator Varchar
username Used to login to the system Varchar
password The secret code to login to the system Password
Table 11Account table description
Attribute Purpose data type

Username Uniquely identify user Varchar
Passwords The secret code to login to the system password
Role To identify users admin,customer or owner Varchar
Table 12 Method for admin description
Method Description
Login() To Login into the system
View feedback() View feedback from user
Create account() To create account for new user
Search house() Search house to view the information
Update account() Used to update the current account
View user() View how much user access system
Table 13Method for customer description
Method Description
View house() View unreserved house
Page | 38
Search house () Search house based on cost to rent

Send request() Sending request to owner of house
Send feedback() Send feedback about the renting system
View response() View response to their request
Table 14 Method for owner description
Method Description
Update house information() Update house information if some change
Send response() Give response to the request from customer
Send feedback() Give Feedback to admin about the renting
system
3.2 Database Design/Physical Data Model

Physical database design translates the logical data model into a set of SQL statements that
define the database. For relational database systems, it is relatively easy to translate from a
Logical data model into a physical database.
Rules for translation:
 Entities become tables in the physical database.
 Attributes become columns in the physical database. Choose appropriate data type for
each of the columns.
 Unique identifiers are not allowed to have NULL values. These referred to as primary
keys in the physical database. Consider creating a unique index on the identifiers to
enforce uniqueness.
 Relationships are module as foreign keys.[6]
Table 15 user registration table
Page | 39
Table 16Notice table
Table 17Feedback table
Page | 40
Table 18Account creation table
3.3 User interface design

User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that
the interface has elements that are easy to access, understand, and use to facilitate those actions.
3.3.1 Login page interface

In this interface the user enter username and password to login and it has many
additional elements: to successfully login to this system enter your username and
password correctly.to know the general information about the system visit the navigation menus
listed next to header.to get help about the system please visit the help menu.
Figure 15 login page
Page | 41
Figure 16 upload house page
Figure 17 create account page
Page | 42
Figure 18 post notice page
3.4 Deployment Diagram

A UML deployment diagram shows static view of the run time configuration of processing
system user and the components that run on system. In other words, deployment diagram shows
the hardware of our system, the software that to be installing in that hardware. It also shows how
hard ware and software components work together.
Page | 43
application database
client server server
create account
Admin
post notice
send response
security
view request
Owner
upload house
update house
view house
send feedback
Customer send request
view notice
Database
search house
Figure 19 deployment diagram
Page | 44
CHAPTER FOUR
4 IMPLEMENTATION
4.1. Introduction
In this phase what our group members have done is turning the physical design specification into
working computer code on the online house rent management system for Debre Markos Town,
and then the code is tested until most of the errors have been detected and corrected user sites are
prepared for new system and user must come totally on the new system rather than the existing
one to get there work done.
4.2. Overview of the programming language used

For implementing this project we use the following programing language:-
 JSP (We use java server page language for the system development, and our system (software)
will be compatible on all hardware platforms such as windows &Linux)
 Scripting language:-used to develop different validations.

 HTML:-to display the web page.
 CSS:-for the formatting of the web site
Reason JSP:-
 Session management-User sessions are maintained on JSP server. PHP destroys the user
sessions every time
 Security.-JSP – own security framework.
4.3. Algorithms Used

The project team used algorithm to develop this system. Since the system the project team
developed is counting based system.
Pseudo code for Login
Load Login Page
Fill
The Login Form
Click the Login button
Page | 45
If (Form is filled)
If (valid)
Generate SQL select queries
Connect to database
Pass queries to database
If (any query fails)
Display error message
Else
Read session
If session exists on database, user is already logged in,
Display the page
Else
If they're correct
Create session ID
Store session ID on database
Display the page
End if
End if
Else
Display error message
Ask the user to refill the form
End if
End if
Page | 46
4.4. Sample Codes

For login page
//for password encryption
<%@ page import="javax.crypto.Cipher"%>
<%@ page import="javax.crypto.spec.SecretKeySpec"%>
<%@ page import="org.apache.commons.cli.*, org.apache.commons.codec.binary.Base64,

org.apache.commons.logging.*"%>
%@page import="java.sql.*"%//database connection
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE html>
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>log Page</title><link rel="stylesheet" type="text/css" href="setting.css">
</head> <body>
<div id="container">
< %@include file="header.jsp"% >
<%@include file="logm.jsp"%>
<div id="left"> <%@include file="searchform.jsp"%> <br>
<img src="image/db.jpg" style=" margin-left: -1px; margin-right: -1px; margin-top: -0px;

margin-bottom: 1px; height: 300px;width: 230px;"/>
</div>
<div id="right">
<img src="logincon.jpg" width="200" height="100">
<table cellpadding="2" cellspacing="2" width="100%" bgcolor="#cceeff"> <form

method="post" action="" name="f1" ><h1>
<tr><td> <font color="blue" size="5">Username<input type="text" name="username"

placeholder="Username" size="15" required=""><br>
Page | 47
</td></tr><tr><td> <font color="blue" size="5"> Password <input type="password"

name="password" placeholder="Password" required="" size="15"><br></font>
</td></tr><tr><td> <input type="submit" name="login" class="login login-submit"

value="login">
<input type="reset" name="reset" value="reset">
<input type="button" name="newu" value="new user" onclick="window.location.replace

('accountrq.jsp')">
</form><br>
<input type="submit" name ="reg" value="ForgotPassword" onclick="window.location.replace

('searchaccount.jsp')" size="10"></table>
<%
String user = request.getParameter ("username");
String pw = request.getParameter ("password");
try {
Connection con = null;
ResultSet rs = null;
Statement stmt = null;
PreparedStatement pstmt = null;
int inserted = 0;
String url = "jdbc:mysql://localhost:3306/house";
Class.forName("com.mysql.jdbc.Driver").newInstance();
con = DriverManager.getConnection(url, "root", "");
stmt = con.createStatement();
if (user != null && pw != null) {
//encription
final byte[] key = {

Page | 48
0x4, 0x68, 0x69, 0x79, 0x49, 0x73, 0x66, 0x53, 0x65, 0x63, 0x72, 0x65, 0x14, 0x4f, 0x65, 0x60
}; Cipher cipher = Cipher.getInstance("AES/ECB/PKCS5Padding");
final SecretKeySpec secretKey = new SecretKeySpec(key, "AES");
cipher.init(Cipher.ENCRYPT_MODE, secretKey);
final String pass = Base64.encodeBase64String(cipher.doFinal(pw.getBytes()));
String sql = "select*from account where username='" + user + "'and password='" + pass + "'";
rs = stmt.executeQuery(sql);
while (rs.next()) {
String un = rs.getString("username");
String pas = rs.getString("password");
String role = rs.getString("role");
if (user.equals(un) && pass.equals(pas)) {
session.setAttribute("suname", user);
session.setAttribute("spass", pass);
if (session.getAttribute("suname") != null && session.getAttribute("spass") != null) {
if (rs.getString("role").equals("admin")&& rs.getString("status").equals("1")) {
response.sendRedirect("admin.jsp");
} else if (rs.getString("role").equals("recorder")&& rs.getString("status").equals("1")) {
response.sendRedirect("recorder.jsp");
} else if (rs.getString("role").equals("owner")&& rs.getString("status").equals("1")) {
response.sendRedirect("owner.jsp");
} else if (rs.getString("role").equals("manager")&& rs.getString("status").equals("1")) {
response.sendRedirect ("manager.jsp");
} else if (rs.getString("role").equals("customer")&& rs.getString("status").equals("1")) {
Page | 49
response.sendRedirect ("customer.jsp");
}} else if (session.getAttribute("suname") == null && session.getAttribute("spass") == null) {
response.sendRedirect ("log.jsp");
}} else {
response.sendRedirect ("log.jsp");
out.print("Inccorect username and password");
}}if(!rs.next()&& !rs.last()) {out.println("<FONT COLOR=RED>Account Not Authorized");}
}// else{out.println("not correct");}
} catch (Exception ex) {
out.println("Unable to connect to database.");
}%>
<br> <%@include file="calander.jsp"%> </div>
<div id="content">
<img src="image/dm1.jpg" style=" margin-left: -1px; margin-right: -1px; margin-top: -30px;

margin-bottom: 15px; height: 350px;width: 700px;"/>
<table width="70%" CELLPADING="2" height="44" ><br ><tr><td bgcolor="#000aaffff"

><font color="white">ABOUT US | ABOUT DEBRE MARKOS
HOUSE RENT! </td></tr></table>
</div>
<%@include file="footer1.jsp"%>
</div>
</body>
</html>
Page | 50
CHAPTER FIVE
5. Testing
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.
Integrated 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.
System testing:-In this testing, the team performs over all functional testing by checking
whether it meets the required target.
Figure 20Sample Test for owner property
Page | 51
CHAPTER-SIX
6 .Conclusion and Recommendation
6.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 online house rent management system for Debre Markos Town. It
is available, accurate and attractive with easy GUI approach. Generally, the team confidently can
say that the system is completed successfully with negligible errors. Finally the team expects the
software will change the house rent management system and makes it more reliable accurate and
secure.
6.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.

 Debre Markos Town kebele should have adequate computer facilities to use the new
system effectively.
 For the Town to have network connectivity.
6.1.3. Future Enhancement

 The system will be developed by using android in a way to support mobile users.
 By the future, technology user can view the proposal result on their mobile
phones in notification form.
 The system will be including tax collection.
 The system will be including online payment.
Page | 52
Declaration
We undersigned, declare that this project is our original work, has not been presented for a degree in this
or any other university and on the sources of materials used for this project have been acknowledged.
Approval of advisor and examiner

This project has been submitted for examination with my approval as a project adviser
Advisor name ………………………………………………… signature…………………
This project has been examined with my approval as a project examiner
Examiner name 1………………………………………. signature…………………
2……………………………………….. Signature…………………
3……………………………………….. signature…………………
Page | 53
References
[1].Background, Monday December 2017 4:20:28 AM. [Online]. Available:
https://www.mwud.gov.et/web/Debre Markos/home
[2].Sequence diagram, Thursday January 01, 2017 2:47:33 AM. [Online]. Available:
https://en.wikipedia.org/wiki/Sequence_diagram.
[3].class-diagram, Monday January 05, 2017 3:23:28 AM. [Online]. Available:
https://www.smartdraw.com/class-diagram.
[4].activitydiagram, Friday January 09, 2017 4:23:15 AM. [Online].Available:

https://en.wikipedia.org/wiki/Activity_diagram.
[5].Database design, Tuesday January 04, 2017 1:40:12 AM. [Online].Available:

https://en.wikipedia.org/wiki/Class_diagram
[6].Database design, Tuesday January 04, 2017 4:23:22 AM. [Online].Available:

https://en.wikipedia.org/wiki/Database design .
Page | 54

House Rent Final7

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

House Rent Final7

Uploaded by

Copyright:

Available Formats

ONLINE HOUSE RENT

MANAGEMENT SYSTEM IN DEBRE MARKOS TOWN

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

DEBRE MARKOS, ETHIOPIA

May, 2010. E.C

1.10.1Technical feasibility ........................................................................................................................ 8

4.4. Sample Codes................................................................................................................................... 47

CSS---------------------------------------------------------------------Cascading Style Sheet

PHP--------------------------------------------------------------------Hyper Text Pre Processer

UML--------------------------------------------------------------------Unified Modeling Language

WAMP-----------------------------------------------------------------Windows, Apache, MySQL, PHP

MYSQL-----------------------------------------------------------------My Structured Query Language.

ACA---------------------------------------------------------------------Alternative course of action

DVD---------------------------------------------------------------------Digital versatile Disc

DMT---------------------------------------------------------------------DEBRE MARKOS TWON

1.2 Background of project

1.3 Statement of Problem

This manual system has problems those are mentioned as follows.

1.4 Objective of the Project

1.4.1 General objective

1.4.2 Specific objective

 To make suitable condition for the customer and the owner.

1.5 Scope of the project

Scope of project performs as:-

1.6 Limitation of the project

 It does not include online payment.

1.7 Significance of project

1.7.1 Tangible benefits

1.7.2 Intangible benefits

 Reliable data retrieval.

1.8 System requirement

1.8.1 Hardware Requirement

 Flash Disk -To store and transfer files.

1.8.2 Software Requirements

 Anti-Virus Software: - used to scan, fix Flash Disk.

1.8.3 Programming and database tool

 JSP: to write server side scripting language.

Reason behind MYSQL:

 Easily compatible with the programming tool indicated above

1.9.1 Data Collection Approaches

1.9.2 The System Analysis and Design Approaches

1.9.3 The System Development Model

1.10 Feasibility study

1.10.2 Economic feasibility

1.10.3 Operational feasibility

1.10.4 Legal feasibility

2.1 Overview of the existing system

2.2 System Requirement Specification

2.2.1 Functional requirement

The main functional requirements of this system are:-

 The system store available information of house.

2.2.2 Non-functional requirement

2.2.3 Business Rule

2.3 System Requirement Analysis

2.3.1 Actor and use case identification

We identified the following actors.

 Administrator: manages the whole system of the project.

Use case name Use Case ID Uses/includes

View free house UC6

View account Uc36 Uc1

Use case diagram

Register Manager view disagreement