College of Engineering & Technology

School of Computing & Informatics

Department of Information Systems

Project Title: Web based solo Real Estate Information management System

Group 2
Members:

Full Name ID

1. CHALA MERGA 1200215

2. ABDI MAZIGABU 1200261

Advisor: MR KHAN
Table of Contents
1.1. Introduction....................................................................................................................................1
1.2. Background.....................................................................................................................................1
1.3. Statement of problem....................................................................................................................1
1.4. Objective.........................................................................................................................................2
1.4.1. General objective.....................................................................................................................2
1.4.2. Specific objective.....................................................................................................................2
1.5. Proposed system............................................................................................................................2
1.6. Literature Review and Related Work..............................................................................................2
1.7. Scope and Limitation......................................................................................................................3
1.8. Methods and Tools.........................................................................................................................3
1.8.1 Data source and data collection methods................................................................................3
1.8.2 System Analysis and Design Methods.......................................................................................4
1.8.3 System Implementation Methods and How to use Methods...................................................4
1.8.4 Development Environment and programming Tools................................................................4
1.9. Significance of the project..............................................................................................................5
1.10. Beneficiaries of the system or application....................................................................................5
1.11. Feasibility study............................................................................................................................5
1.11.1 Technical Feasibility Study......................................................................................................6
1.11.2 Economic feasibility................................................................................................................6
1.11.3 Operational Feasibility study..................................................................................................6
1.11.4 Legal Feasibility study.............................................................................................................6
1.12. Project Plan...................................................................................................................................7
1.12.1 Time Schedule........................................................................................................................7
1.12.2 Budget Plan.............................................................................................................................8
1.1. Introduction
In today’s world, the numbers of Real Estate organizations are increasing time to time. These organizations are works
using manual systems. Mostly in our country Ethiopia, the real estate users are communicating with each other by
using different ways to manage the real estate property among those using call by phone, face to face by presenting
on the place. Our team members will develop a web-based application named Web based Real Estate Information
management System, the purpose here is to manage real estate owner and buyer, view or see the Real estate
property using this system. That is used to reduce the users finding time as well as they will able to access the system
anywhere through this web site but connection is mandatory. The system which would inform the user when
purchasing immovable property based on area of points of interest and encourages buyers to search more
intensively. The existing system is currently saving records (property, staff, customer, and seller) manually on
registers notebooks. Seller and customer record is saved via visit to the office; it wastes more time and energy.

1.2. Background
The establishment of Solo Real Estate was on January, 2009 E.C. It is located southern part of the country in hosanna
town, which is 230km far away from Addis Ababa. The Real Estate gets this name from the owner of Real Estate. They
started working with the initial capital of 5,000,000 birr and a few workers. Is a well-established property
development company dedicated to creating homes that are practical, convenient, and comfortable for today’s
modern lifestyle seeker. The building is delivered after all of the details have been completed. The real estate industry
has a bold vision. To become the most well-known brand in the real estate industry and to be associated with high-
quality construction – in terms of design, construction, and delivery. Solo real estate project consisted of 7
condominiums, 5 townhouses. To improve the efficiency of real estate searches, we developed an online home
buyer’s search program, based on an investigation of search behaviours Real Estate Information management system
that specializes in real estate property management by taking an immediate role between owners who wish to let or
sell their properties and clients who want to rent or buy these properties. However, the company is becoming so
large that more and more administration staff is being employed to cope with the ever-increasing amount of paper
work.

1.3. Statement of problem

The existing real estate activity is done through manually, due to these users are wasting their time and money.
There is a lot of duplication and common errors are faced while entering and updating property data, making it
inconsistent and unavailable at times for future uses. The office is situated at the particular location; the customer can not
able to come from other side only the people which near to the office can register for buy. In addition to this retrieval of
information is a slow and boring task to perform. The security of data is also a concern as it is placed in cabinets that could
be access by others. Therefore, our proposed system solves this problem.
1.4. Objective
1.4.1. General objective
Our major objective is to develop a Web based Real Estate Information Management System for the individual buyers in order
to solve the problem that stated in statement of problem.

1.4.2. Specific objective

In order to achieve the main objective, we have developed the following specific objectives:

To Studying about problem of the existing system of the real estate.

To Gathering required information for proposed system.
To Analysing the gathered information.
To considering applicability of proposed system for the real estate.
To designing the proposed system with attractive interface.
To Implementing the system.
To Testing the system.

1.5. Proposed system

In this proposed system we have tasks to do and needs to fulfil this project currently, where the technological
innovations and the use of computerized and mobilized systems are highly being increasing from time to time, the
knowledge of mobile and computers and knowing how to operate with them is very much important. So, as we
already tried to mention above it helps for sellers/buyers to get full information’s about the Real estate information
with their website easily through internet connection. The existing structure should be converted to the
computerized system, in which user can easily store every information regarding this system (i.e. manual records).
We prefer to make a web based system, that will be easily accessible by every customer and seller at any time. This
system will also be able to track all previous records.

1.6. Literature Review and Related Work

According to the National Association of Realtors Profile of Home Buyers and Sellers, 51% of buyers found the home
they purchased on the internet. To put this in perspective, only 29% found the home they bought through their
realtor, and 4% from a yard sign.

Real estate websites are attracting so many visits every month because they are adding value for both buyers and
sellers. Buyers can preview hundreds of homes within a few hours from the comfort of their couches. Home sellers
win, too; their homes are viewed by hundreds of shoppers in the market looking to buy a new home these websites
update listings quickly and accurately, provide a variety of tools for buyers and sellers to obtain the best information,
and streamline the buying and selling process to make it more efficient among this

Trulia is one of the top real estate websites for several reasons. It is also one of the more well-known sites on our list
it has various search features that make it easy to find exactly what you need The site is well laid out and easy to use.
When you view a home, you’ll see information about features along with map views, street views, data on nearby
schools and crime information Colourful graphs help you determine your potential mortgage payment. Better yet,
quotes from locals about the area give you an insider’s view about what it’s like to live in the neighbourhood .

1.7. Scope and Limitation

Scope
The proposed system focus on giving detail information about Real Estate for the customers. It allows visitor to get
information about properties available in their area so they can easily search property as per their requirements and
maintains all the Real estate property information online. The system displays various source of Real estate
properties with provide information. The various sources are Villa, condominium, row-house, etc. It provides
information to one and all who visit the site but to upload a Real estate property for sale and to send a request to buy
a desire Real estate property only can be made who register with the side.

Through this project, we have tried to automate the following tasks:

Buyer gets detail available real estate property information

Searching available of real estate property
Allow Post real estate property and updating of records.
Customer compliant management
It does include online payment
It have online agreement facility.

Limitation
Our proposed project is not including the following activities:

Only people that get internet access can use the system.
Web site promotion: Promotions about other websites will not be performed. project It does not include any
promotion of website
Insurance: System does not provide detailed information about the process of
Insurance
1.8. Methods and Tools
1.8.1 Data source and data collection methods
When we propose this project, we have used the following data source and data collection method.

Interview: -We have made an interview with our customers, stakeholders to get an overview of the current system
and the problem of the existing system.

Observation: - We observed the work of buying and selling real estate in Ethiopia.

Document analysis: -We also see different documents in order to obtain the information about the practices and
problems of the current manual system. We gathered information in regards to practices and problems of the
existing manual system.

1.8.2 System Analysis and Design Methods

In this project the team will use object oriented system development methodology (OOSD). This has two phases:

Object Oriented Analysis: - During this phase the team used to model the function of the system (use case
modelling), find and identify the business objects, organize the objects and identify the relationship between them
and finally model the behaviour of the objects.

Object Oriented Design: - During this phase the team uses Edrawmax and Enterprise Architecture software to refine
the use case model, and to reflect the implementation environment, model object interactions and behaviour that
support the use case scenario, and finally update object model to reflect the implementation environment.

1.8.3 System Implementation Methods and How to use Methods

Implementation is a realization of a technical specification or algorithm as a program, software component through
programming. there are different types of tools available to implement the system from those tools we select php to
develop front end of the system, Xamp2.5 server to develop back end of the system ,UML editor to sketch different
UML diagrams and Microsoft word 2010 to prepare the documentation part of the project .

1.8.4 Development Environment and programming Tools

Development Environment: -Different requirements and materials are required to implement the new system
includes: -

➢ CPU: -Also called processor, responsible for most data processing operation.

➢ RAM: - is temporary storage device or working storage area.

➢ Personal computer: - with Pentium (166 MHZ or higher) due to Microsoft data engine requirement.
Programming Tools

 Apache Server Version 2.1: - is the server of our project and used to manage our system Database.
 Database software: - MySQL database server that is built in xamp Server (xamp Server)
 Application Software: - MS – office 2010 for documentation.
 visual studio code: - used to written java script or PHP code on it.

Program Languages: - PHP used to develop implementation of our online webpage system. The reason why we are
selecting this software tool from others because, Firstly PHP is new server-side scripting language that has become
extremely popular with the programmers. It can be easily installed with the large number of features. PHP is a lot
faster than ASP and it work very well with My SQL. So, PHP is better choice to make in regards to syntax, connectivity
and toolbox in creating database table is the simplest of tools.

1.9. Significance of the project

Our project is important from many perspectives, like buyers and visitor in order to get information about real
estates, which can be rent or, sell available in their area so they can easily search real estate properties as per their
requirements. Also, provide facility of living for peoples who are outside city. In addition to this our project:

Save the time that is lost while searching Real Estate manually.
Improves accuracy by promoting effective communication.
Easy retrieval of information from the database.
Guide to people who are homeless and would wish to find a place to their home
Getting better and fast process of information about a given Real Estate.
Minimizes resource and unwanted cost
This reduce wastage of time because of the previous manual system is boring.
Avoiding data loss because improper data storage
Avoiding paper wastage to record Real estate information
Manual processing is minimized and quality of work and services became improved
Improve the quality of internal operations as well as service given to the users.
The system will provide proper real Estate information.
Easy to differentiate Real Estate property that is available for sell.

1.10. Beneficiaries of the system or application

Users of the system include:

 seller
 customer/buyer
  Users that registered as members of the Real estate and customer.
 Administrator/manager of the organization.

1.11. Feasibility study

Feasibility study is a study that determines whether a proposed system is technically, financially, and operationally
viable. Preliminary Investigation is the first phase in any system developing life cycle. The Feasibility Study is a major
part of this phase. Feasibility Study means selecting the best system that meet the performance requirement. The
feasible development of the software is going to be in terms of the following aspects:

1.11.1 Technical Feasibility Study

Feasibility our group members are expected the system to be technically feasible. The system is going to be
developed by following the Object Oriented System Development technique. The team has the ability to develop this
system without any difficulty since the team has studied the required methodologies and tools. So the system will be
technically feasible. The project members also have knowledge about PHP, JavaScript, CSS, MySQL database,
Edrawmax and Enterprise architecture to design the system. Besides, the group members have enough capability to
develop the project. So the system is technically feasible. In general, using the different techniques, we can perform
the work up to the desire of the organization, even though fulfilling human being’s need in all direction may be
difficulty.

1.11.2 Economic feasibility

The purpose of the economic feasibility assessment is to determine the positive economic benefits to the
organization that the proposed system will provide. It includes quantification and identification of all the benefits
expected. This assessment typically involves a cost/ benefits analysis. Real estate Property site is available to anybody
and anywhere. This saves a lot of time of the customer and in a very little span the register user may look what’s an
offer on the special products purchasing. This plan cost offered in economic too.

1.11.3 Operational Feasibility study

Operational feasibility it measures the degree of how much the proposed system reduce the existing system
problems. This project is surely operationally feasible because the proposed web system is a good solution maker of
the existing problem or specific solution will work in the existing system and create a good environment towards the
user so when the system is reached to the end users every personal or company that have a contact to the system
will gain a training form the developer how they use it and accessing every segments of the system part.

1.11.4 Legal Feasibility study

This Computerized project system will avoid conflict between the workers and organization. Instead both of them is
beneficial. This is the best method to serve customers with an efficient manner.
1.12. Project Plan
1.12.1 Time Schedule
The project team will finish all the things mentioned in the schedule provided by the instructor, so we are ordered to
finish on the time given. Since the project goes linearly, we have the responsibility to submit to our lecture with the
allocated time. This implies the project will go with specified time table sequentially

No task Nov. Dec Jan Feb Mar Apr

2015 2015 2015 2015 2015 2015
Two Three Four two two two
Weeks weeks weeks weeks weeks weeks

1 Information
gathering

2 Project
information and
planning

3 Project Analysis

4 project design

5 Project
Implementation

1.12.2 Budget Plan

NO TIME Quantity Total price(birr)

1 Computer and laptop 2 50000

 2 Printing 200~400

3 Ms visual studio free

5 Ms office free

6 paper 100

7 Mysql database server free

8 Xampp server free

10 Edrow max free

TOTAL 50400

CHAPTER -2-

DESCRIPTION OF THE EXISTING SYSTEM OR APPLICATION

2.1. Introduction

The existing system used manual record. This method of keeping the records is quiet time consuming and less
efficient. Also there are more chances of mistakes by keeping the records manually as human beings are
habitual of doing mistakes. The office is situated at the particular location; the customer can not able to come
from other side. If any person wants to buy a property, then he/she come to the office for registration of his /her
real estate property only the people which near to the office can register for buy Real estate property.
Registration process also involves lot of paper work. Searching the property was done by looking manually the
paper. A large number of manpower is involved to work within a manual system, which is very expensive to the
organization. This chapter presents the description of the existing system of solo real estate.

2.2. Business rules and Constraints

A business rule is effectively an operating principle or polices that we try to specify for both the existing
System and the new system must satisfy. The business rule is a principle or a policy in which the
Proposed system operates accordingly. It deals with access control issues. It often relates to access
Control issues, operating policies and principles of the organization.
The organization has the following principles in the existing system which includes:

BR1: Buyers must Fills the required detail information

BR2: The administrator select delete, view real estate property

BR3: Seller should immediately notify us for any price.

BR4: The administrator should send order to the seller

BR5: The administrator should View comment, process payments, view available real estate property.
BR6: customer expects to be treated with respect and concern.
2.3. Naming Convention and Definition
Naming conventions make programs more understandable by making them easier to read. They can also give
information about the function of the identifier-for example

 Variable Namespace -are essentially containers that will hold an applications environment separate from other
environments that could potentially conflict with your variables.
 Inline Commenting- This is often the most common and most underused commenting since it provides help
around a particular process or piece of code that might be confusing later.
 Class/Page Comments- This is perhaps the quickest to implement since it can be added to a default document
template easily in most authoring environments and provides much of the detail a later developer (or possibly
even you) will need when this document is opened years later.
 Code Blocks- In a language that supports code blocks using brackets, it is always better to use the brackets for
clarity than to eliminate them.
2.4. Functions or Main Activities of Existing System

The major functions done by the existing system are takes the list of builder’s details and
organizing them with coordination of the real estate agency manager’s. After arranging and
organizing these people they can identifies which builder is legal. This all activities can be done
in manual system.
Among these, the followings are major function of existing system:

Registration of owner and buyer manually

Mange Real estate property (record the property)

 Manage Real estate owner and buyer

In order to buy a RE property, then he/she come to the place for which the real estate found in
order to get information.

2.5. Players of Existing System or Application

Existing system users cannot get any information in computerized way. There are many works in the
office and they are done by face to face contact and players of Existing system are include:

Seller

Buyer

Administrator/manager of the organization.

2.8.1 Strength of the Existing system or Application

Even if existing system of real estate is manual, it has the strength that can be controlled directly
 Provide the required property for the customers as much as possible.
 Generating reports timely for their administrator that comes from customers
 Assessing discipline cases.
2.8.2 Weakness of the Existing system or Application

 The office is situated at the particular location; the customer can not able to come from other side.
Only the people which near to the office can register for buy.
 Retrieval of required information is become difficult and time consuming
 Lost productivity from manual records
 Real estate property registration process also involves lot of paper work
 Ineffective monitors staff performance when dealing with customer complaints.
 Fragmentation caused by manual record.
 Buyers are not to paying online

2.8.2.1. Alternative Solution

As we try to describe above the current system faces some problems and the problem’s primarily resulted
From the manual system of running the activities and we try to put an alternative solution to the problems
which are described in the above problem identifying in the existing system section.
  The best alternative solution to the existing system is to change the existing manual system and producing an
electronic (online) system for real estate information management system

CHAPTER 3

REQUIREMENT SPECIFICATION AND ANALYSIS

3.1 Introduction

In this chapter we want to describe the requirements of the system using UML. We divided the
description in to three sections. The first section is the use case model. In this section we can identify
actors, their specification, identify use case and use case diagram with use case description which briefly
describe the precondition, scenarios or basic course of action, and post condition of each use case.
3.1. Description of the Proposed System or Applications

3.2.1 User Characteristics

3.2.2 Constraints
3.2.3 Assumptions and Dependencies

The product must have an interface which is simple enough to understand.

All necessary hardware and software are available for implementing and use of the tool.
The proposed system would be designed, developed and implemented based on the software requirements
specifications document.
End user should have basic knowledge of computer.

3.2. Requirement Specifications

3.3.1 Functional Requirement
Functional requirements describe the interactions between the system and its Environment independent
of its implementation. The environment includes the user and any other external system with which the
system interacts. The system should provide how the system should react to particular inputs and how
the systems behave in particular situations.

The followings are the functional requirements of our proposed system with respect to the actors.
Login: For validating User
Registration: customer can register themselves, on our website to get information.
Manage the owner of real estate and the buyer, which registered in the site.
Search real estate property by real estate category which is available for sell.
Approve or reject real estate sell request.
 View the buyer’s requirement and send response if available.
Send and View feedback about the website
Manage Real estate – Adding, Update or Delete RE Property.
The system should store all the data related with all the tasks performed into a
database.
3.3.2 Non-functional Requirement

Nonfunctional requirements describe user-visible aspects of the system that are not directly
related with the functional behavior of the system. Nonfunctional requirements include
quantitative constraints, such as response time (i.e., how fast the system reacts to user
commands).

The nonfunctional requirements of our system will address are discussed as follows: -

 User interface:-Our proposed system should be easy to use for users. User can visit the home
page of real estate in which first the introduction of our site mention first. The registered user
can login from the login module.

User interface should be menu driven and attractive.

The interface should be user friendly.
The system should support error-handling mechanism that display graphic approach and
the system guide the user what will be the next action.
 Hardware consideration
The following sub-sections discuss the various aspect of hardware requirement.

Processing power: 32 or 64 bit operating system and Intel(R) core (TM) i3-237M CPU
@1.50GZ.
Memory and secondary storage: more than 4GB, 500GB hard disk and swap space (if the
RAM is insufficient).
Peripherals: includes CD ROM device, network device, etc.

 Software consideration
 Platform: includes operating system (window 8), programming language and their run time
libraries.
Web browser: support all browsers, but internet explorer is recommended.

 Performance consideration

System will have good performance as much as possible this will be attained via easily loadable
interface components and optimal algorithms which make searching, updating, deleting,
inserting and saving easy and fast. The system performs its task within a user acceptable time
and space. This includes the following: -

Response time: - depending on the strength of available network the system should be
response in short period of time.
Storage space: -to do work efficiently the processor to be more than 2GB RAM and
HD storage to be more than 20MB
Process data with high speed

Data redundancy problem will be avoided with the proposed system.

 Reliability

Reliability defined as a measure of the time between failures occurring in a system (measures
how frequently the system fails), so that our system shall operate without any failure for a
particular period of time. Users expect the system to be reliable which means users information
registered yesterday in the system shall be there today. Our proposed system easy to use stored
data.
 Security
The system should be secured and protected from unauthorized user. It should have a user’s
database and should authenticate each user on login and should grant user specific services.

3.3. System Modelling

Object-Oriented System Analysis (OOSA) looks at the problem domain, with the aim of producing
a conceptual model of the information that exists in the area being analyzed. The result of
object-oriented analysis is a description of what the system is functionally required to do,
in the form of a conceptual model. That will typically be presented as a set of Class responsibility
collaborator, use cases, sequence diagrams. The purpose of object-oriented analysis is to develop
a model that describes computer software (Website) as it works to satisfy a Set of customer defined
requirement.

3.5.1 Actor Identification

In UML, the person involved is called an Actor. An Actor is always outside of the Automation
Boundary of the system.

The proposed system will have the following actors.

Actors Description
Administrator Controls the whole system
Seller A person who sale real estate

Buyer A person who buys Real estate property

Table 1 Actor identification and description

3.5.2 Use-Case Identification

Use cases for our proposed system are:

Login
Register
Manage Real Estate Property
Approve/reject Sell Request Real estate property
Send requirement (buyer).
Manage user (admin: delete and view).
Update profile
Search Real Estate Property
Mange compliant
View requirement
Send Response for requirement
Send Feedback about the website.
Send request to buy
Send sell response to the buyer

3.5.3 Use-Case Diagram

3.5.4 Description of Use-Case
Use case name Login
UC Id 01
Actor Admin, Seller, buyer
Use case To authenticate the actors
description
Precondition:  Application exists on the computer
 The computer connected though Network.
 User must have a valid username and password

Basic Flow 1. Users starts up application

Event 2. User fill username, password
3. User click on Login button
4. Validate user name and password
5. The system displays appropriate page.
6. End use case

Post condition The authenticated person gets the appropriate page/leave out the system

Alternative 3.1 If the user name and password is incorrect the system
condition display incorrect user name and password message.

Table 2 use case description for login

Use case name Register
UC Id 02
Actor Seller, buyer
Use case add actors in the database (record seller and buyer data)
description
Precondition:  Application exists on the computer
 The computer connected through Network.
 The client side application must be open

Basic Flow Event

1. Open website and click on Registration button

2. The system displays the registration form
3. The user fills the required details /information’s
4. The users click on the submit button.
5. The system validates the registration forms
6. The system also checks the user details in the database
7. The user’s details recorded/ saved to database
8. The system displays successfully register message.
9. End use case

Post condition The system saves all user information.

Alternative 4.1 If the user fills invalid details the system displays error message
condition
6.1 If the user is already existed in the database, the system displays already
exits message try again with other detail.

Table 3 use case description for Register

Use case name manage Real estate property
UC Id 03
Actor Admin
Table 4 manage
Use case to manage Real estate property/ delete ,view Real estate
description property use
case description
Precondition:  Application exists on the computer for Admin
 The computer connected through Network.
 The system must be open.
 The administrator must be login to his/her homepage

Basic Flow Event 1. The administrator clicks on Mange real estate property button
2. The system displays view/delete button.
3. Administrator select delete, view RE property
4. Admin click on he/she wants to perform those activities.
5. The system displays a result.
6. Use case end.

Post condition RE property is display or Removed from database

1. If the required actions perform wrongly the system displays incorrect

Alternative action perform.
condition

Use case name search Real Estate Property

UC Id 04
Actor Buyer
Use case To search the available property which is found in the given site for buying
description

Precondition:  The computer connected through Network.

 The client side application must be open.
 Buyer must be login into his/her home page

Basic Flow of 1. buyer click on search menu.

Event 2. The system displays search form.
3. Buyer can fill form with the appropriate property attributes/fills
search details.
4. buyer click on submit button.
5. The system validates the search Forms.
6. The system displays the search result.
7. End use case

Post condition 1. view the Real estate which is available for buying.
2. Send feed back to the owner of the real estate

Alternative 1. If the property is not found at particular location or city, he can send
condition his requirement on website to the admin by perform Send
requirement flow of event.

Table 5 use case description for search Real Estate Property

Use case name Manage Real Estate Property

UC Id 05
Actor Seller
Use case To manage their own real Estate
description
Precondition:  Application exists on the computer
 The computer connected through Network.
 The system must be open.
 Seller must be login to his/her home page to perform those activities.

Basic Flow Event 1. The seller clicks on manage RE property button.

2. The system displays Add RE property button.
3. Seller click Add RE property button.
4. The system displays add RE form
5. The seller fills the RE property details.
6. Seller click on submit button.
7. The system validates the details entered by the Seller
8. The RE property saved to database.
9. The system displays successfully added /updated Message.
10. End use case

Post condition Updated current real estate property is displayed/Add RE to database.

6.1 If every required information has to be filled incorrectly the system
display message “Try again”
Alternative
condition

Table 6 use case description for manage Real Estate property

Use case name Manage users(seller and buyer)
UC Id 06
Actor Admin
Use case To view or delete users from the data base
description

Precondition:  Network connection must be existing.

 The system must be open.
 The admin must be login to his/her home page to perform those
activities.

Basic Flow Event 1. The administrator clicks on manage user button.

2. The system displays the user details.
3. the admin can view or delete user.
4. The system displays a message success.
5. End use case

Post condition View Success message deleted/view

5.1 if there is no registered user in the system, the system displays not
user found to view or delete
Alternative
condition

Table 7 use case description for manage Users

Use case name Approve/Reject RE sell request
UC Id 07
Actor Admin
Use case Display the available RE to the home page of the system and to give
description response for owner of the RE.

Precondition:  The system must be install on computer Network connection

must be existing.
 The admin must be login to his/her home page.
 the seller must upload /add the RE

Basic Flow 1. The administrator clicks on Approve/Reject button

Event 2. The system displays list of RE property.
3. View the RE list which have pending status.
4. Admin verifies the properties and then he can approve/Reject
property
5. The system displays success message.
6. End use case

Post condition approve or reject success message/RE property is post to home page

Alternative If there is no sell request RE properties, the user will back to homepage.
condition

Table 8 Use case description for Approve/Reject sell request RE

Use case name Send response for buyer’s requirement
UC Id 08
Actor Admin
Use case to view the necessary information and give response according to the
description asked information.
Precondition:  The system must be install on computer
 Network is the pre-condition to communicate each other.
 Admin must login to his/her home page.

Basic Flow Event 1. The admin clicks view Requirement button.

2. The system displays list of sent requirements from buyer.
3. The admin clicks on send response button.
4. The system displays send response form.
5. Admin fills the response details that he/she sent to buyers
6. Admin clicks on submit button.
7. The system validates the send response details.
8. The system displays “send response successfully’.
9. End use case.

Post condition view and send the response to the buyer

alternative if the form is not filled correctly, the system will display error message
and return back to step 5.
condition

Table 9 Use case description for send response for buyer’s requirement
Use case name send requirement
UC Id 09
Actor Buyer
Use case to send Requirement to Admin which is not found available RE during searching.
description
Precondition:  The system must be install on the computer.
 The application must be connected through network.
 The system must be open.
 Buyer must be login to his/her home page.

Basic Flow Event 1. The buyer clicks on search button.

2. The system displays search form.
3. Buyer fills the required details for search.
4. Buyer clicks on submit button.
5. The system validates the details that entered.
6. The system displays no RE found, then
7. The buyer clicks on send requirement button.
8. The system displays send requirement form.
9. The buyer fills the requirement detail information.
10. The buyer clicks on send requirement button.
11. The system validates the requirements details.
12. The system displays successfully send message.
13. End use case

Post condition send requirement to the admin is success.

Alternative 10.1. If the buyer fills the form incorrectly, the system will display error message.
condition

Table 10 Send Requirement use case description for Buyer

Use case name Manage compliant

UC Id 10
Actor Admin
Use case To helps businesses communicate more effectively with customers through
description various channels of communication.

Precondition:  The system must be existing on the computer.

 The system must be open.
 The application must be connected through network.
 Admin must be login to his/her home page

Basic Flow 1. The admin clicks on manage compliant button.

Event 2. The system displays create compliant form.
3. Actor fills the required detail information.
4. Actor clicks on submit button.
5. The system sends the compliant to receiver.
6. The system displays successfully send message.
7. End use case.

Post condition The message is visible to the user.

Alternative 3.1 The message is not send to the user the system display message “Please
condition try again”

Table 11 Use case description for Manage compliant.

Use case name update profile

UC Id 11
Actor Seller, buyer
Use case users can update their own profile
description
Precondition:  Application exists on the computer
 The computer connected through Network.
 Users must be login to the system

Basic Flow 1. Users starts up application

Event 2. User login to their own home page (by filling necessary details)
3. User click on update profile button
4. The system displays Update profile form
5. User fills form with required details
6. Submit the details to database.
7. Updated profile records on database.
8. Display the message update profile is Successful
9. End use case

Post condition Updated user profile is display.

Alternative 2.1 If the user name and password is incorrect the system display
condition incorrect user name (the system displays please login to your
appropriate page by filling required details)

5.1. If the user cannot fill required details the system displays”
please enter the required details again”.

Table 12 use case description for update profile.

Use case name Send Feedback

UC Id 12
Actor Seller, buyer
Use case give suggestion about the website
description
Precondition:  Application exists on the computer
 The computer connected through Network.

Basic Flow 1. Open website home page.

2. The Buyer/seller clicks on Feedback button.
Event
3. The system displays Feedback form.
4. Fills the required detail information.
5. Admin clicks on send button.
6. The system validates Feedback details.
7. Feedback send to the database.
8. The system displays “Thanks for your Feedback” message.
9. End use case.

Post condition the given Feedback will be shown to the admin

 3.1 If every required information has to be filled incorrectly the system display
“error” message
Alternative
condition

Table 13 use case description for Send Feedback

3.5. Requirement Analysis

3.5.1. Activity Diagram
We used activity diagram to graphically represent the sequence flow of activities or workflows of stepwise activities and
actions with support for choice, iteration and concurrency. It also used to model action that will be performed when an
operation is executing as well as the result of those actions. The activity diagram resembles the flow chart that shows the
actions and events as they occur and the order in which the actions take place and identifies the outcomes. In the Unified
Modeling Language, activity diagrams are intended to model both computational and organizational processes (i.e. workflows).
Activity diagrams show the overall flow of control.
Figure 14 Activity diagram for login for all user
Figure 15 Activity diagram of Registration for buyer and seller
Figure 16 Activity diagram for search RE property
Figure 17 Activity diagram for send response
Figure 18 Activity diagram for view Response
Figure 19 Activity diagram for manage Real Estate by admin
 Figure 20 Activity Diagram for Approve/Reject

3.5.2. Sequence Diagram

As the name indicates, we used sequence diagram to show sequence of operations or how processes operate with
one another and in what order. It is a construct of a Message Sequence Chart. It shows object interactions
arranged in time sequence. It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of the scenario. Sequence
diagrams are typically associated with use case realizations in the Logical View of the system under
development. A sequence diagram ties use cases with objects. It shows how the behavior of a use case (or
scenario) is distributed among its participating objects. Identifying the participating objects of our system and
classifying as entity, boundary, and control object, we have the following sequence diagram.

sd sequnce digram for

login

User WRER Login Login Databas User

s S Form Controller e Homepage

open( fillandsubmi
)
t ()

activate(
)

validate(
)
tray again()
Check user
name and
 result()

display(
)

wrong
Unameorpass()

User Registration

sd Dynamic Vi...
Users
WRERS RegistrationBtn RegistrationForm Registration Database
controller

startup()
Click()

Display()

fill and submit()

activate()
validate()

invalid()
checkexistance()

result()
alreadyexist()
save()

successfully register()

Figure 4 Sequence diagram for user registration

 sd Add RE
Property

Sell SellerHome ManageReB AddREButtonAddRE FormAddRE Datab

er Page utton controller ase

login
()

click
()

displa
y()

click
()

dipla
y()

fill and
submit()

activat
e()
Validat
e()
invali
successfully d() sav
added!!!() e()

Add RE property

Figure 5 sequence diagram for add RE property

View RE Property
sd ADmin
Manage ...

Admi AdminHomePa ManageRE View RE Databas

n ge Button Button Controller e

Login(
)

Click(
)

display(
)

view(
)
activate(
)

Check
()

Return
displa
()
y
result(
)

Figure 6 sequence diagram for View Real Estate

 Manage

sd ManageNe...

Admin AdminHomePage ManageNewsButton CreateNewsForm Mnage News Database

Controller

login()

click()

proceed()

Display News form tocreate()

Fill news Details()

Submitt()

verify()

saved()

return()

:Successfully created

Figure 7 sequence diagram for manage news by admin

Manage Users

sd
Manage
Us...

Ad AdminHo Mnageus ManageUser Data

min mepage erButton Controller base

logi click()
n()
Display
Delete/vie
w button()

Sent request
Delete/View()
verify()
SentReques
tDetials()
featch
details()
Deleted/
Show View
Deleted/View Result()
Success()

Figure 8 sequence diagram for manage user by admin

Send Response
sd SendResponse For
Admin

Admi AdminHomepa View SedRespponseButton ResponseContro Databa

n ge Requirement SendResponseForm ller se
Button
login(
)

Click
()

Display()

Click()
Display
()

Fill
details()

Submit(
)

:verify

save()
return()

:SendResponse
successFully

Figure 9 sequence diagram for send response by admin

Search Real estate by buyer

sd Dynamic Vi...

Buyer Buyer HOME SearchButton SearchForm Searchcontroller Database

PAGE

Login()

Click()

Display()

Fill search details()

submit()
:verify

Execute Request()

check()
tryagin()

Search result()

View search
result()

Figure 10 Sequence diagram for search

 Send requirements
sd send requirment

Buyer

Figure 11 sequence diagram for send requirement by buyer

View Requirement Response

sd viewResponse_Bu...

Buyer BuyerHomepage ViewResponsedButton ViewResponsecontroller Database

login()

click()

Excute Response details()

check()

return()

Display view result()

Figure 12 Sequence diagram for view Requirement response by buyer

Update Profile

sd update
profile

Seller/ Seller/ UpdateProfileButto UpdateProfil UpdateprofileControlle Databas

Buyer Buyer n e Detail form r e
HomePage
login to their own home
page()

click(
)

proceed(
)

display the details

form()

fill the required

deatils()

Submit(
)

:verify
update()

show update
details()
:Your profile is sucessfully
updated

Figure 13 Sequence diagram for update profile by buyer and seller

Approve/reject sell request RE

sd
APPROVEr
ej...

Ad AdminHom WRE Approve/ Approve/

min e page RS RejectButton RejectControllerDataabase

Logi
n()
Clic
k()

Displlay()

Approve/Reject
Request()

UpdateSt
atus()

Update
retur details()
n()

ApproveSucce
ssFully()
:Post
To

Figure 14 sequence diagram for approve/reject sell request RE

Feedback

Figure 15 Sequence diagram for send feedback

 CHAPTER -4-

SYSTEM DESIGN

4.1. Introduction
Systems design is the process of defining the architecture, components, modules, interfaces, and data for a system to satisfy
specified requirements. Systems design could be seen as the application of systems theory to product development . System
designing deal with how the system is to be looks like after the analysis is successfully completed, mean that functionality, non-
functionality and analysis modeling is clearly achieved the next step is followed by system designing. It shows also the
computerized part of the system. System design helps the programmer to configure the implementation or coding with the
customer or user of the software. The design part is very important to make the implementation very easy. The different types
of the system modeling techniques that are used for the implementation of the system such as deployment and component
modeling are show in detail. Not only the system modeling techniques but also some system design techniques such as system
decomposition design are cover in detail in this phase. The non-functional requirement is the description of the feature
characters and attributes of the system.

4.2. Class Diagram

We use class diagram to describe the structure of a system by showing the system’s classes, their attributes, operations (or
methods), and the relationships among objects. For designing of Class diagram, we have used Unified Modeling Language
(UML). This diagram is the main building block of our object-oriented modeling. The team applies it for both general conceptual
modeling of the systematic of the application, and for detailed modeling translating the models into programming code. The
classes in a class diagram represent both the main objects, interactions in the application and the classes to be programmed. In
the system, Classes are abstractions that specify the attributes and behavior of a set of objects and Objects are entities that
encapsulate state and behavior. Each object has an identity: It can be referred individually and is distinguishable from other
objects. In mapping the diagram, we have used the following criteria:

One –to- One relationship: -here when both involved entities exchange primary keys where the
new exchanged primary keys become the new foreign keys of the tables.
One –to- many relationships: -here the primary key on the many side has been mapped to the
one side.
Many-to-many: - here the primary key on the many side has been mapped to the many side.
The association of classes is described with diagrams as follows:
4.3. Database Model
Database model are used in almost every program or software system. Data structures provide a means to manage huge
amounts of data efficiently, such as large databases and internet indexing services. Usually, efficient data structures are a key to
designing efficient algorithms. Some formal design methods and programming languages emphasize data structures, rather than
algorithms, as the key organizing factor in software design
4.3.1. Entity Relationship Diagram (ERD)

4.3.2. Persistence Modelling

This modelling used to depict the design of the database. The persistent classes are used to store most important and
permanent in formation of the system. In persistent modelling the team member will perform the following activities.

• Identifying entities.
• Identifying keys.
• Data type and size

Figure 34 Mapping class to relational database

Figure 35 Persistent model of RE property

Figure 36 Persistent model of requirement

Figure 38 Persistent model of Administrator

 Figure 39 Persistent model of seller

Figure 40 Persistent model of buyer

Figure 41 Persistent model of Feedback
 4.3.3. Mapping with Normalization
4.4. Subsystem Decomposition
Subsystem decomposition describes the decomposition into subsystems and the responsibilities of each. This is the main
product of system design. To reduce the complexity of the solution domain, we decompose a system into simpler parts, called
subsystems. The main need of this portion is to design the external part of the system. The objects and classes from the object
model are the “seeds” for the subsystems.
Our project sub system decomposition as follow.

Figure 32 Sub system decomposition

4.5. Deployment Diagram
Deployment diagrams are used to visualize the topology of the physical components of a system where the software
components are deployed. So deployment diagrams are used to describe the static deployment view of a system. It consists of
nodes and their relationships.
Deployment diagram controls the following parameters

 Performance
 Scalability
 Maintainability
 Portability of a system.
 Figure 43 Deployment diagram

4.6. System Architecture (Layered Architecture of the System)

It is the architecture that determines the type of interactions that the components are going to have. The
architecture that this work uses is client/server-based architecture. In this type of architecture, the server is
responsible to receive a request from the client and respond to the request, whereas the client is
responsible to interact with that of the users of the system. The server parts of this work are of two types.
The first type is a web server, which is responsible to receive browsers’ request through http protocol and
responds accordingly. Whereas the second type of server is a database server, which is responsible to
provide the requested database services to the web server. The database server is generally responsible for
modification and insertion of data to the database. It can only communicate with the web server. The client
side is a web browser which receives requests from the user of the system and responds to the request by
communicating with the web server. If the user has a request on data, the browser passes the request to the
web server then the web server pass the request to the database server. Figure 1 shows the architecture of
the system.
4.7. User-Interface (UI) Design

1|Page
4.8.UI Flow Diagramming

User Interface Design is concerned with how users add information to the system and with how the
system presents information back to them.

act Dynamic View

website

Home

Login

Register
Admin
Seller

Buyer

Manage RE
proprerty

View
Delete
Search RE Manage RE
Update
property property

Approv
e/reject Post

SendRequ Add View

Manage User
uuirement

View Responce Update

profile
Manage
News CRUD Send Feed
Back

View Update
SendResponce Profile
Requirement
Logout

Logout
View Feed
Back

Logout

2|Page
3|Page
4|Page