WOLKITE UNIVERSITY

COLLEGE OF COMPUTING AND INFORMATICS

DEPARTMENT OF INFORMATION TECHNOLOGY
REAL ESTATE RECOMMENDATION SYSTEM
SUBMITED TO DEPARTMENT OF INFORMATION TECHNOLOGY
IN PARTIAL FULFILMENT OF THE REQUIREMENT FOR
THE DEGREE OF BACHLER OF SCIENCE IN INFORMATION
TECHNOLOGY

SUBMITTED BY
STUDENT NAME ID NO.
1. ISHETU HUSEN ……………………………………………………...CIR/165/08
2. KANBRO ORKAIDO…………………………….………………… CIR/171/08
3. BEZAWIT MULUKEN……………………………………………... CIR/069/08
4. GALMA MIYO ………………………………………………………. CIR/133/08
5. SAMRAWIT HAGOS……………………………………………… CIR/240/08

ADVISOR: AMANUELT

Wolkite University, Wolkite, Ethiopia

Jan 9/2018
Contents
1. Chapter one ........................................................................................................................................... 4

1.1. Introduction ................................................................................................................................... 4

1.2. Background of the project ............................................................................................................. 4

1.3. Statement of problem .................................................................................................................... 5

1.4. Purpose of the project ................................................................................................................... 5

1.5. Objectives of the project .................................................................................................................... 5

1.5. Feasibility study ............................................................................................................................ 6

1.5.1. Technical feasibility .............................................................................................................. 6

1.5.2. Operational feasibility ........................................................................................................... 7

1.5.3. Economic feasibility ............................................................................................................. 7

1.6. Scope and Limitation of the project .............................................................................................. 8

1.6.1. Scope of the project............................................................................................................... 8

1.6.2. Limitation of the project ....................................................................................................... 8

1.7. Significance and beneficiary of the project ................................................................................... 9

1.7.1. Significance of the project .................................................................................................... 9

1.7.2. Beneficiary of the project ...................................................................................................... 9

1.8. Methodology of the project ........................................................................................................... 9

1.8.1. Data Collection Methodology ............................................................................................... 9

1.8.2. System analysis and design ................................................................................................. 10

1.8.3. System development Model ................................................................................................ 10

1.8.4. Testing methodology........................................................................................................... 10

1.8.5. Development and technology tools ..................................................................................... 12

1.9. Document organization ............................................................................................................... 13

2. Chapter Two........................................................................................................................................ 15

2.1. Description of existing System ................................................................................................... 15

2.2. Major Functionality of the Existing System ............................................................................... 15

2
 2.3. User of the current System .......................................................................................................... 15

2.4. Forms and Other Documents of the Existing Systems................................................................ 16

2.5. Bottlenecks /Problem of the current System ............................................................................... 16

2.6. Business rules of the Current System ......................................................................................... 17

3. Chapter Three...................................................................................................................................... 19

3.1. Proposed System ......................................................................................................................... 19

3.2. Overview ..................................................................................................................................... 19

3.3. Requirements of the project ........................................................................................................ 20

3.3.1. Functional Requirement ...................................................................................................... 20

3.3.2. Nonfunctional Requirement ................................................................................................ 21

3
1. Chapter one
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 Recommendation
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 web based real estate recommendation system which would advise 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 are saved via
visit to the office; it wastes more time and energy. To improve the efficiency of real estate
searches, we developed an online homebuyer’s search program, based on an investigation of
search behaviors, and implement a user-oriented recommendation system for user. Real Estate
Recommendation systems that specializes in 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. The company has a number of branches all over the country. 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.2. Background of the project

Nowadays, Real Estate organizations are found in Ethiopia. These organizations are
communicating with the users by different means of communication. So, it is possible to observe
that the owner of the Real estate waste their money for Brokers and advertisers. Because those
are large, work for the owner to communicate with the buyer the owner/seller must pay money.
In addition, the buyer consumes his money and time to get information. A home is the most
valuable asset for all of us. The safety and future of our family depend on it. For most of us it

4
embodies achievements and aspirations. In addition to this anyone that plans to buy a home
searching information, and visit more properties of the Real Estate. Country developers are one
of the real estate’s operating in Ethiopia. Currently building many types of houses with in Public
facilities like swimming pools, Tennis & Basketball courts, clinic & Health center, School and
another social activity function are also included. For this instance, we initiated to develop Web
based Real Estate Recommendation System to solve the problem searching, managing
information manually.

1.3. Statement of problem

The existing real estate information system 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 real estate property data, making it inconsistent and unavailable at
times for future uses. 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. Searching the property was done by the persons own self from the property Dealer or
through internet sites; there was a limitation of matching choice of their property. If any person
wants to sell or buy a property, then he has to come to the office for registration of his property
so it is difficult to users to find a real estate on the specific time. Therefore, our proposed system
solves this problem.

1.4. Purpose of the project

The main purpose of the project is overcome the problems of the current system that exists in the
operation of the Real estate and Changing the whole current system in to computerized system,
through which a user can access its information and manage all the adding, updating, deleting the
assets and some of its tasks.

1.5. Objectives of the project

1.5.1. General objective

Our major objective is to develop a Web based Real Estate Recommendation system for the
individual buyers and sellers in order to solve the problem that stated in statement of problem. 1
1.5.2. Specific objective

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

 To plan the design and development of our system

 Gathering required information for proposed system.
 Studying about problem of the existing system of the real estate.
 Analyzing the gathered information.
 Considering applicability of proposed system for the real estate.
 Designing the proposed system with attractive interface.
 Implementing the system.
 Testing the system.

1.5. 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.5.1. Technical 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.

6
1.5.2. Operational feasibility
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 for 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 from the
developer/us how they use it and accessing every segments of the system part.

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

Economic feasibility consists of tangible and intangible feasibility.

Tangible:
 Reduce the amount of resource required in real estate’s such as pen, paper etc.
 Reduce data redundancy storing in the database.
 Improve real estate efficiency, speed and flexibility.
 Applicable even for a non-technical person can use it. When we say non-technical
person, who has no experience of using computer or new for the system.
Intangible:
 Improved customers and owners time and money wastage
 To make quick decisions based on the organized information retrieved
 Better service to customer.
 Reduce responsibility of employee.

7
1.6. Scope and Limitation of the project

1.6.1. Scope of the project

The proposed system focuses 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 property information online. The system
displays various sources of real estate properties with provide information. The various sources
are Villa, apartments, condominium, row-house, etc. It provides information to one and all who
visit the site but to upload a property for sale and to send a request to buy a desire property only
can be made who register within the site. Through this project, we have tried to automate the
following tasks:

 Buyer gets detail available real estate property information

 Searching available real estate
 manages real estate property owner
 Allow Post real estate property and updating of records.
 Send request to buy

1.6.2. 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.
 It does not have online agreement facility.
 The interface support only English language.
 For the time being System admin approve sell request through cross checking
either by property taxations number or image of real estate.

Time: -Is the main factor of limitation of our proposed systems that limit its performance
because while we are developing the system it takes more time and we may not get enough time
to automate the system.

8
1.7. Significance and beneficiary of the project

1.7.1. 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.7.2. Beneficiary of the project

The main users of the system are the following people

 Sellers/owners of the real estate

 Buyers/customers of the real estate

1.8. Methodology of the project

1.8.1. Data Collection Methodology

When we propose this project, we have used the following data collection method.

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

9
  Observation: - We observed the work of buying and selling real estate in Ethiopia.
 Document analysis: we can’t get document of the existing system to analyze.
1.8.2. System analysis and design

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

1.8.2.1.Object Oriented Analysis: -

During this phase the team used to model the function of the system (use case modeling), find
and identify the business objects, organize the objects and identify the relationship between them
and finally model the behavior of the objects.

1.8.2.2.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
behavior that support the use case scenario, and finally update object model to reflect the
implementation environment.

1.8.3. System development Model

Our proposed system follows the Incremental Model. Weuse this model because it’s designed,
implemented and tested as a series of incremental builds until the product is finishes the
requirements, design, coding and testing phases. And each subsequent release of the system adds
function to the previous release until all designed functionality has been implemented so this
type of feature of incremental model is the best for our project. Because,It is flexible and less
expensive to change requirements and scope and uses new technology. This model combines the
elements of Waterfall model with the iterative philosophy of prototyping. However, unlike
prototyping the incremental model focuses on the delivery of an operational product at the end of
each increment. The first increment is usually the core product, which addresses the basic
requirements of the system.

1.8.4. Testing methodology

Testing is the process of executing a program with the intension of finding errors. In order to
know whether there is an error or not in our system, we will perform the following testing
strategies; these strategies are used to test the functionalities and the working style of the system.

10
1.8.4.1. Unit Testing
In these strategies, we will concentrate on each component/function of the software as
implemented in the source code. It is used to check whether each module in the software works
properly so, that gives desired outputs to the given inputs. To perform these, we will use two
approaches/techniques of unit testing.

A. Black box testing

This testing technique focuses on the functional requirements of the software. In this technique,
we will test to see if the function of the system is operational or error free. This includes, testing
the interface of the system rather than the logical structure of the system. Our project can be
viewed solely in terms of its input, output and transfer characteristics without any knowledge of
its internal workings.

We used this testing technique for the following reasons:

 More effective on larger units of code.

 Tester needs no knowledge of implementation; including specific programming
languages Tester and programmer are independent of each other
 Tests are done from a user's point of view.
 Will help to expose any ambiguities in the Specifications.

B. White box testing

We will use this approach to know the internal working style of the system, test that all internal
operations are performed according to specifications and all internal components have been
exercised and the logical path of the system are correct.

We use this testing technique for the following reasons:

 It is easy to find out which type of input/data can help in testing the application
effectively.
 To optimize the code.
 It helps in removing the extra lines of code, which can bring in hidden defects.
 Early detection of errors during software development.

Tasks that we have performed under unit testing phase are the following:

11
  Prepare unit test plans.
 Identify the unit test objectives.
 Prepare test cases that include information such as set of test inputs, execution condition
and expected output.
 Perform the tests according to our plan and analyze the test results.
 Document the test results
1.8.4.2.Integration Testing

In these strategies the group member will focuses on testing the design and construction of the
software architecture. To do the two techniques of integration testing will have considered.

A. Top –Down integration testing

This will perform starting from the top module up to the last or bottom module individually (tests
were run as each individual module is integrated).

B. Bottom-up integration

We will begin with the lowest –level modules, which are combined to cluster, or build that
perform a specific software sub-function (top-level).

Tasks that we have performed under integration phase are the following:

 Prepare integration test plans.

 Identify integration test objectives and acceptance criteria.
 Perform the tests according to our plan.
 Document the test results

1.8.5. Development and technology tools

Here we will include programing languages and its editor, database technologies, documentation tools,
unified modeling language (UML) design tools, hardware tools for deployment purpose etc.

1.8.5.1.Front end technology

We use markup languages to design this phase

HTML/HTML5, CSS, JavaScript, bootstrap, jQuery and others may be included.

12
1.8.5.2.Back end technology
We use php to design the server-side script and we use mysql to design our database

1.8.5.3.Modeling tools
We will use unified modeling language to draw different diagrams of our project by using EdrawMax,
vision or enterprise architect

1.8.5.4. Deployment environment

I don’t understand this part

1.9. Document organization

Overview of the project phases

Defining the project phases is One of the essential steps in order to monitor and control the
successful project. Without breaking down project management into various phases it is not
possible to launch a project. Even if we manage to begin the project, we will not be able to
complete the project successfully. So, we need to define the phases of project management to
successfully manage the project. Here are some of the most common phases of our project:

1. Initiation Phase

Starting from the current problem we initiate to develop web based real estate recommendation
system that allow customer, visit to get information about properties available in their area online
so they can easily search property as per their requirements. When client found their desire
property then they can contact to the owner of the property and can make a good at the end we
can say in project anyone can easily sell and buy.

2. Planning phase

When we develop this project, we have plan to group task to reduce work complexity. Based on
the plan we have document design, code implementation and testing whole program. When we
finish this project, it gives the assumed service to the given user. Code implementation phase is
phase that is writing the program or the code. In this code writing we assume to develop in
programming language in the php. The final phase is the project test phase. This is testing the
functionality of the project when we develop reject there may be error .by nature project is error
full otherwise we take care to develop.

13
3. Closing Phase

During the final closure, or completion phase, the emphasis is on releasing the final deliverables
to the customer, handing over project documentation to the Real Estate organization, releasing
project resources, and communicating the closure of the project to all stakeholders. Finally
conduct lessons-learned studies to examine what went well and what didn’t. Through this type of
analysis, the wisdom of experience is transferred back to the project organization, which will
help future project teams.

14
2. Chapter Two
2.1. Description of existing System

Currently in Ethiopia, most real estate organization information Management system is mostly
used manual record different real estate attribute information’s. 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. Real estate
property registration process also involves lot of paper work. For every property separate file has
be maintained according to name of seller property details. Searching the property was done by
the persons own self from the property Dealer or by looking manually the paper. If any person
wants to sell or buy a property, then he/she comes to the office for registration of his /her real
estate property.

2.2. Major Functionality of the 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 managers. After arranging and
organizing these people they can identifies which builders are legal and have license
requirements. This all activities can be done in manual system.

Among these, the followings are major function of existing system:

 Mange Real estate property (record the property)

 Manage Real estate owner and buyer
 Registration of owner and buyer manually
 In order to buy a real estate property, then he/she come to the place for which the real
estate found in order to get information.

Generally, in the current 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 with the owner and buyer.

2.3. User of the current System

Users of the existing system include real estate bureau admin, seller/owner, customer/buyer and
users that registered as members of the Real estate to make communication between builder and
customer.

15
  Owner/Seller
 Buyer
 Agent
 Administrator/manager of the organization.

2.4. Forms and Other Documents of the Existing Systems

We have tried to get reports, forms and other related documents that are used in the existing
system but unfortunately, we are failed to get those samples.

2.5. Bottlenecks /Problem of the current System

The current system is having different problems. Those are first the company record and retrieve
all information manually and recorded only on the excel sheet, the agency has not a secured data
base, the registration system is too much time consuming, it’s hard to retrieve all member’s
information from the system, the communication between the agency and stake holders are
manually and because of this the communication is very slow.

The following are the problems in the existing system:

 At the time of searching about the real estate property information all the records have to
be scanned and even after that people cannot be sure that they will be able to find a
proper real estate property.
 A large number of manpower is involved to maintain the whole system, which is very
expensive.
 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 sell or buy.
 Retrieval of required information is become difficult and time-consuming
 Lost productivity from manual records Fragmentation caused by manual record.

More on bottlenecks/problems of the Existing System Using PIECES Frame Work

 Performance (Response time) since it is manual system, the response time for
performing every process is very slow, and Many of the documents are stored physically
it increases the space complexity. Because of the above problem the performance of the
existing system is low.

16
  Input (Inaccurate/redundant/inflexible) and Output (Inaccurate)

As a manual system, redundant documents are submitted as an input and maybe it is inaccurate
Document, this makes difficult to find the desired document (output) from the stored documents
in the existing system. This results inaccurate output.

 Security and Controls

Security and Control Storing data is not secure, because the existing system uses access and
excels as a front end. Anyone who opens the computers, in which the system is installed and
used, can access all the contents of the database why because every activity is performed in a
single computer, activities are not secure. It causes dissatisfaction of customer.

 Efficiency

As we have seen, the existing system encounter different problems like, it consumes man power,
time, space and redundancy of data. Because of such problem the existing system is not enough
efficient.

2.6. Business rules of the Current System

The followings are the business rule of the existing system.

 ID: BR1: -The seller should have kebele/city identification card that indicates he/she is
resident of the city/kebele and shall get registered to be members of the Real estate
organization.
 ID: BR2: - Seller should immediately notify us for any price/rate change, change of mind,
or when the property is taken.
 ID: BR3: -If someone is found to buy or rent a real estate property, that arrange a visit
too, without paying our service fee, then the company will request double of the payment
stated above through the legal way.
 ID: BR4: - The real estate organization should verify the seller whether he/she is legal or
illegal license for the land that building location.
 ID: BR5: - The users of the System must have user name and Password to access the
system.

17
 ID: BR6: - User of the system must fill the form correctly and fill all the required
information.
 ID: BR7: - for the users of the system i.e., owners and customers only the system admin
creates, update and delete the account.
 ID: BR8: - when the customers’ needs to buy property they must first register in to the
system by their own account.

18
3. Chapter Three

3.1. Proposed System

3.2. Overview
In this proposed system we have tasks to do and needs to fulfill this project. This chapter is for
identifying requirements to accomplish and diagrams to represent the users or participator. All
models represented in this chapter are based on the tasks or the user relationships. Models are
diagrams that represent or show relationship of one to another. 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.

The proposed solution is aimed at to explore on develop web based real estate recommendation
system. So that, users can interacts with the system in user-friendly manner. This proposed
system solves the problems faced in the current manual system.

The following are the major functionalities provided by the proposed system

 Participating in the proposed system it takes relatively less time compared to the existing
system.
 Anyone who privilege to internet services can use the proposed system any time they
want.
 Will avoid the need of large human resource; minimize cost of papers and data storage.
 No need of the program host, operators, and phone calling to administrator office.

Besides of issuing Real estate property, the proposed system update users’ information needs
about current issues happening all over the world; especially, within the country.

19
3.3. Requirements of the project
Requirement gathering is a way of collecting information to improve or change the existing
system by the new system. Requirement is a major base for better solution or for solving
problem which exists in the current system. The new system is based on the interest and
understanding of the users. The sequence of activities which are performed in the current system
also impacts the development of new system. Having such kind of understanding helps us to
distinguish modules which are going to be changed in the new system and to determine how
proposed system can solve the current problems and also able to design other new features which
are user interactive.

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 WRERS 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 location, price, real estate category which is available for
sell, rent and commercial.
 If the property is not found at particular location or city buyer can send his requirement
on website.
 Approve or reject real estate sell request.
 View the buyer’s requirement and send response if available.
 Send and View feedback about the website
 Add News to announce the user which is available real estate property in news day.
 Manage Real estate – Adding, Update or Delete real estate Property.
 Allow User to update his/her profile.
 The system should store all the data related with all the tasks performed into a database.

20
3.3.2. Nonfunctional 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: -

3.3.2.1.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. Here guest can register free account to sell and buy property &buyer verify each-
other & make reliable communication to each other.

User can search the property and it can find the type of property and its budget and also find the
location of property.

 User interface should be menu driven and attractive and user friendly.
 The navigational schema is flexible.
 The interface is easy to adapt.
 The forms are user friendly, easy feeling and don’t need any extensive training.
 The system requires users to have only basic computer knowledge.
 The system should support error-handling mechanism that display graphic approach and
the system guide the user what will be the next action.

3.3.2.2.Hardware Consideration
The following 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 Platform: includes operating system (window 8), programming language and
their run time libraries.

21
  Web browser: support all browsers, but internet explorer is recommended.

3.3.2.3.Security issues
Web based real estate recommendation 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. Customer’s information and data security and safety are
the included in the major concerns of the developers of the system. Identifying customer,
validating information, and making sure the right person gets the right service will be major tasks
performed in the system's security components.The login procedure is password protected. And
also, we used hash salt password encryption technique to secure password to avoid internal and
external intruders.

3.3.2.4.Performance consideration
Time consumption (resource consumption for given load): consumes less resource like time,
workers needed to perform the task.

 Effectiveness (resulting performance in relation to effort): More effective when

compared to the manual approach, resulting in fast accomplishment of task with in some
amount of time.
 Efficiency 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. The proposed system has fast response time. It needs at
least 3 second response time and the worse response time is 7 second.
 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.
 Interoperability: it can work with web-based applications developed using PHP and java
script
 Extensibility: Adding features and carry-forward of customizations at next major version
upgrade.

22
3.3.2.5.Error Handling and Validation
Error handling

When we say error handling, we mean referring to conditions when the administrators/users
insert erroneous inputs (data), the system should have some mechanism to trace the error and
report the error made by the administrator/users. WRERS must have error handling mechanism.
It is not stop functioning rather it will report an error message.

Validation: - each field in the form and login page should take the proper data type as input and
must display error message if invalid data inserted. Example if the field requires number it
should take number else it should display warning message.

3.3.2.6.Quality Issues
Reliability

Reliability defined as a measure of the time between failures occurring in a system (measures
how frequently the system fails).

❖ The performance of the software shall be better which will increase the reliability of the
Service

❖ Reliable way of keeping or maintaining information of customers by using External hard disks
before encounter a viruses or other problems damage the organization data.

❖If a computer has a USB port, we can attach an external hard disk to it and then back up files
to the external disk.

❖ If the user inserts correct input, the result will be correct.

❖ The system shall require guide and help to be understood by user.

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

Availability: All data in the system will be available in 24 hours and 7 days.

Usability

23
❖ By using simple menus and controllers for GUI make the users to understand and use
proposed system easy for workers.

Robustness

If there is any error in any window or module, then it should not affect the remaining part of the
software

❖ The operation shall be flexible and reports will be presented in different ways.

❖ The end user shall be able to access any page fast according to the internet connection speed

3.3.2.7.Backup and recovery

To reduce data loss and other risks there shall be a frequent and full back up mechanism to avoid
any information loss and inconsistency using copy of the system to restore when hard ware and
software failure occur. We will use removable flashes and disks such as CD ROM, DVD for
backup and recovery mechanism. Because the risks of data lost might be happen due to a number
of reasons such as: computer viruses, sudden accident on data storages, data theft or power
fluctuation.

3.3.2.8.Physical Environment
Since our system is web-based system it is accessible anywhere and anytime which installed on
one single server and distributed or accessed by another terminals or computers only what we to
do is taking care of the environment where our system should be installed from external and
internal factors that can harm the system.

3.3.2.9.Resource Issues
Sir I can’t understand this portion

3.3.2.10. Documentation
Our proposed system provides full documents that guides users and has its own manual for
future maintain ace and all the development process are documented. We have tried our best to
include

 all requirements that identify attributes

 capacities

24
  characteristics or qualities of system
 architecture/design
 codes/algorithms and interfaces

It is an easy task for developers who want to add some features to this system for farther
scalability.The system shall require guide and help to be understood by user.

25