LAND PRICE

PREDICTOR
By

Muhammad Abdullah Waheed

Ibtisam Zubair

DEPARTMENT OF COMPUTER SCIENCES

COMSATS UNIVERSITY ISLAMABAD,
ATTOCK CAMPUS – PAKISTAN

SESSION 2017-2021

1
 LAND PRICE
PREDICTOR

Undertaken by

Muhammad Abdullah Waheed

CIIT/FA17-BCS-028/ATK

Ibtisam Zubair
CIIT/FA17-BCS-065/ATK

Supervised By:

Mr. Armughan Ali

A DISSERTATION SUBMITTED AS A PARTIAL FULFILLMENT OF THE

REQUIREMENTS FOR THE DEGREE OF BACHELOR OF COMPUTER SCIENCE

DEPARTMENT OF COMPUTER SCIENCES

COMSATS UNIVERSITY ISLAMABAD,
ATTOCK CAMPUS – PAKISTAN

SESSION 2017-2021

2
 Submission Form for Final-Year project
PROJECT REPORT

NUMBER OF
PROJECT ID 2
MEMBERS

PROJECT TITLE LAND PRICE PREDICTION

SUPERVISOR NAME SIR ARMUGHAN ALI

MEMBER NAME REGISTRATION NO EMAIL ADDRESS

IBTISAM ZUBAIR CIIT/FA17-BCS-065/ATK fa17-bcs-065@ciit-attock.edu.pk

M ABDULLAH WAHEED CIIT/FA17-BCS-028/ATK fa17-bcs-028@ciit-attock.edu.pk

CHECKLIST:
Number of pages in this report

I/We have enclosed the soft-copy of this document along-with

YES / NO
the codes and scripts created by myself/ourselves

My/Our supervisor has attested the attached document YES / NO

I/We confirm to state that this project is free from any type of
YES / NO
plagiarism and misuse of copyrighted material

MEMBER’S SIGNATURE:

__________________________

_______________________________

SUPERVISOR SIGNATURE

_______________________________

3
 DECLARATION

We hereby declare that this software, neither whole nor as a part has been copied out from any
source. It is further declared that we have developed this software and accompanied report
entirely on the basis of our personal efforts. If any part of this project is proved to be copied
out from any source or found to be reproduction of some other. We will stand by the
consequences. No Portion of the work presented has been submitted of any application for any
other degree or qualification of this or any other university or institute of learning.

IBTISAM ZUBAIR M ABDULLAH WAHEED

_________________________
______________________

4
 CERTIFICATE OF APPROVAL

It is to certify that the final year project of BS(CS) “LAND PRICE

PREDICITION” was developed by IBTISAM ZUBAIR
(CIIT/FA17-BCS-065/ATK) and M ABDULLAH WAHEED (CIIT/FA17-BCS-
028/ATK), under the supervision of SIR ARMUGHAN ALI and in his opinion; it
is fully adequate, in scope and quality for the degree of Bachelor of Science in
Computer Sciences.

Supervisor
Sir Armughan Ali
Lecturer

Computer Science Department

COMSATS University Islamabad, Attock Campus

Dr. Khalid Mehmood Awan

HOD
Computer Science Department
COMSATS University Islamabad, Attock Campus

5
 ACKNOWLEDGEMENT
All praise is to Almighty Allah who bestowed upon us a minute portion of His
boundless knowledge by virtue of which we were able to accomplish this
challenging task.

We are greatly indebted to our project supervisor SIR ARMUGHAN ALI.

Without his personal supervision, advice and valuable guidance, completion of
this project would have been doubtful. We are deeply indebted to them for him
encouragement and continual help during this work.

We are grateful and thankful to our parents, who are always being supportive to
us, helped and kept us motivated throughout the journey from then to now with
this project. Not only that but they also gave us moral support and financial help.
In true meanings, we would have not made till now without them. We are truly
thankful to our whole family for being supportive and helping us in every aspect
to be mentioned.

IBTISAM ZUABIR MUHAMMAD ABDULLAH WAHEED

_________________ _________________

6
 PROJECT BRIEF
PROJECT NAME Land Price Predictor

ORGANIZATION NAME COMSATS UIVERSITY ISLAMABAD,

ATTOCK CAMPUS

OBJECTIVE OUR WORK HELPS BUYERS TO PURCHASE

THE BEST AND PROFITABLE LAND.

UNDERTAKEN BY M.ABDULLAH WAHEED, IBTISAM ZUBAIR

SUPERVISED BY MR.ARMUGHAN ALI

COMPUTER SCIENCE
COMSATS UIVERSITY ISLAMABAD,
ATTOCK CAMPUS
STARTED ON SEPTEMBER ,2020

COMPLETED ON MAY 2021

COMPUTER USED DELL, HP

SOURCE LANGUAGE PYTHON, JAVA

OPERATING SYSTEM WINDOW 10

TOOLS USED PyCharm 2021.1 IDLE , ANDROID STUDIO 4.2.1

7
 EXECUTIVE SUMMARY
For many people, buying a property is one of the most important decision and purchase in life.
Besides the affordability of a house other factors such as the desirability of the location and the
long-term investment prospects also affect the decision-making process. Now-a-days people face
a lot of problems when they wanted to buy a new land or plot. The major issue is about its price
in future. It is very difficult to predict the price of land in future. According to previous
knowledge of price and area’s facilities experts can predict its price in future. But in this app we
can predict the land price for about 5 years further based on facilities, previous prices and
resources. It can help people to find a perfect land or plot for commercial use as well as
domestic. It will also help property dealers and real estate companies, so that they can invest
their money on right place.

We are going to make an Android based Land Price Prediction System to predict future land
prices in a specific area based on available resources and previous prices of that area using
machine learning algorithms. In our system user can easily find the best land for him/her so that
his problems get solved. We know that prices of lands are increasing day by day. It is a difficult
task to choose the best land for a user in coming years and predict the price of that land in
future. Our application provides an easy menu for user where he/she will choose their particular
areas, dimensions and orientations and our system will suggest the suitable land and predict
future price based on available resources and previous prices of that area.

There will also an Admin Menu where records are updated time to time. If resources increases
or availability of land increases or decreases in that particular area, then it will also be updated
in records.

Table of Content

8
s
1 Introduction...........................................................................................................................................................13
1.1 Brief.............................................................................................................................................................13
1.2 Relevance to Course Modules.....................................................................................................................14
Mobile Application Development.........................................................................................................................14
Machine Learning.................................................................................................................................................14
Report Writing Skills............................................................................................................................................14
1.3 Project Background.....................................................................................................................................14
1.4 Literature Review........................................................................................................................................15
1.4.1 Check land Prices....................................................................................................................................15
1.4.2 1.4.2 London House Pricing Application...............................................................................................15
1.4.3 Zillow......................................................................................................................................................17
1.5 Analysis from Literature Review................................................................................................................18
1.5.1.......................................................................................................................................................................19
1.6 Methodology and software lifecycle for this project..................................................................................19
2 Problem Definition................................................................................................................................................22
2.1 Problem Statement......................................................................................................................................22
2.2 Deliverables and Development Requirements............................................................................................23
3 Requirement Analysis...........................................................................................................................................26
3.1 Functional requirements..............................................................................................................................26
3.1.1 Use case diagrams...................................................................................................................................26
3.1.2 Detailed Use case....................................................................................................................................28
3.2 NON-FUNCTIONAL requirements...........................................................................................................30
3.2.1 Reliability................................................................................................................................................31
3.2.2 Speed.......................................................................................................................................................31
3.2.3 Security...................................................................................................................................................31
3.2.4 Performance............................................................................................................................................31
3.2.5 Portability................................................................................................................................................31
3.2.6 Complexity..............................................................................................................................................31
3.2.7 Testability...............................................................................................................................................31
3.2.8 Integrality................................................................................................................................................31
3.2.9 Robustness..............................................................................................................................................31
3.2.10 Modifiability.......................................................................................................................................31
3.2.11 Usability.............................................................................................................................................31
3.2.12 Efficiency...........................................................................................................................................31
3.2.13 Scalability...........................................................................................................................................31
3.2.14 Availability.........................................................................................................................................31
3.2.15 Maintainable.......................................................................................................................................31

9
4 Design and architecture.........................................................................................................................................33
4.1 System Architecture....................................................................................................................................33
4.2 Process flow/representation.........................................................................................................................34
4.3 Data flow Diagram level 0..........................................................................................................................36
4.4 Data flow Diagram level 1..........................................................................................................................36
4.5 Sequence Diagram.......................................................................................................................................37
4.6 Entity-Relationship Diagram.......................................................................................................................38
5 Implementation.....................................................................................................................................................40
5.1 Tools and Technologies..............................................................................................................................40
5.1.1 Android Studio........................................................................................................................................40
5.1.2 PyCharm/Jupyter.....................................................................................................................................41
5.1.3 Firebase:..................................................................................................................................................41
5.2 User Interface..............................................................................................................................................42
5.2.1 Splash Screen:.........................................................................................................................................42
5.2.2 Home Page:.............................................................................................................................................43
5.2.3 Login Activity.........................................................................................................................................43
5.2.4 Requirements Menu................................................................................................................................45
5.2.5 Results.....................................................................................................................................................47
6 Evaluation And Testing........................................................................................................................................52
6.1 Testing Objectives.......................................................................................................................................52
6.2 Types of Testing..........................................................................................................................................52
6.2.1 Unit Testing............................................................................................................................................53
6.2.2 Integration Testing..................................................................................................................................53
6.2.3 System Testing........................................................................................................................................53
6.2.4 Acceptance Testing.................................................................................................................................53
6.3 Test Cases....................................................................................................................................................54
6.3.1 User Test Cases.......................................................................................................................................54
7 Conclusion and Future work.................................................................................................................................56
7.1 Future Plan..................................................................................................................................................56
7.2 References...................................................................................................................................................57

10
List of Figures
Figure 1-1 Check Land Prices.......................................................................................................15
Figure 1-2 House Price predictions...............................................................................................16
Figure 1-3 Zillow...........................................................................................................................17
Figure 1-4 Zillow Interface............................................................................................................18
Figure 1-5 Agile Model.................................................................................................................19
Figure 3-1 Use case diagram.........................................................................................................27
Figure 4-1 System Architecture Diagram......................................................................................33
Figure 4-2 Activity Diagram.........................................................................................................35
Figure 4-3 DFD0 Diagram.............................................................................................................36
Figure 4-4 DFD1 Diagram.............................................................................................................36
Figure 4-5 Sequence diagram........................................................................................................37
Figure 4-6 Entity Relationship Diagram.......................................................................................38
Figure 5-1 Android Studio.............................................................................................................41
Figure 5-2 PyCharm......................................................................................................................41
Figure 5-3 Activity diagram: User.................................................................................................41
Figure 5-4 Splash Screen...............................................................................................................42
Figure 5-5 Home Page...................................................................................................................43
Figure 5-6 Login Activity..............................................................................................................44
Figure 5-7 Google account Login..................................................................................................44
Figure 5-8 Facebook account Login..............................................................................................45
Figure 5-9 Requirements Menu.....................................................................................................46
Figure 5-10 Predicted Prices..........................................................................................................47
Figure 5-11 View Resources.........................................................................................................48
Figure 5-12 Currency change........................................................................................................49
Figure 5-13 Graphical Representation...........................................................................................50

11
 List of Tables

Table 1-1 Analysis Table...............................................................................................................18

Table 2-1 Tools used in project.....................................................................................................23
Table 2-2 Technologies used in project.........................................................................................24
Table 3-1 Use case elements..........................................................................................................26
Table 3-2 Use case for User...........................................................................................................28
Table 3-3 Login/Sign up................................................................................................................29
Table 3-4 User Menu.....................................................................................................................29
Table 3-5 Resources......................................................................................................................30
Table 3-6 Currency converter........................................................................................................30
Table 3-7 User logout....................................................................................................................30
Table 3-8 Non-Functional Requirements......................................................................................31
Table 4-1 Activity diagram elements............................................................................................35
Table 6-1 User Test cases..............................................................................................................57

12
 Chapter 1

Introduction

13
1 INTRODUCTION

1.1 BRIEF
With the progression of time, the world is confronting numerous issues. Those issues are being
understood, yet additionally they are being modernized and enhanced each day. For instance,
open managing for buying and selling stuff. We used to go to the market and now, we have
applications like OLX where we can sell and buy stuff just by sitting at home. This tackled our
concern as well as revolutionized the business for better. Presently one of the issues the vast
majority face is the point at which they are going to buy some property or land. We have the
traditional method for reaching a property seller or visiting the land ourselves and accumulate
data about the region ourselves. Presently remember that a portion of the time this data can be
phony and can thoroughly blowback on certain individuals and in certain situations the cost may
likewise contrast and can without much of a stretch be controlled. After some exploration, we
thought of an arrangement to conquer this issue and take care of business. In the light of the
previously mentioned issues, we concocted the undertaking called “LAND PRICE
PREDICTION SYSTEM”. Imagine a scenario in which we disclose to you that all the data you
require is only a tick away. Imagine a scenario where I disclose to you that everything, from cost
to territory, Area portrayal (which includes fundamental living prerequisites) and by what
method will the land develop to be in the up-and-coming years, is exactly readily available. Okay
trust it? Well, it appears to be unbelievable, yet it isn't outlandish! With a little exertion, we will
have the option to accomplish this, what we can say is dream. For this reason, we need to chip
away at an application that will give us the interface that will assist us with interacting with the
client. The client will enter the subtleties of the plot for example Value, area, fourth and the
application will anticipate the estimation of the land or plot and how much of benefit will the
land give in the forthcoming years. From the start this application will be pertinent in a portion of
the piece of the city, later it will be a huge worldwide marvel.

14
1.2 RELEVANCE TO COURSE MODULES
Mobile Application Development
In our project we are using Android Studio. Android Studio is the IDE that provides Google to
develop professional Android applications. It is used to develop a different variety of
applications for the Android operating system. It is an
IDE & platform to design a user-friendly interface by drag and drop.

Machine Learning
In this course we have studied about different algorithms which are used to train models to
perform task automatically after getting the training data.

Report Writing Skills

This course is about learning how to write reports and other formal documentation, and in our
project, we need to write documentation of our project.

Software Engineering
In our project, we have different diagrams (erd, class diagram, dfd diagrams, sequence diagram,
use case diagram, activity diagram) that we learned in software engineering course.

1.3 PROJECT BACKGROUND

Now-a-days purchasing of land/plot is a major issue because fraud is very common in our
society. Future price prediction of a land for a normal or lay person is very difficult.
Unfortunately, there is no proper prediction system or application implemented in Pakistan.
Although there are many real estate’s buying and selling apps available but unfortunately there is
no proper prediction system or application implemented here. The traditional systems based on
property advisors might contain many drawbacks like fraud, robbery etc.
By keeping these problems in mind, we proposed this system in which all the predictions are
performed by system. Administration can easily modify data in the app and a lay person can
easily get benefited.

15
1.4 LITERATURE REVIEW
We started the project by searching for an android system that are predicting future house and
land prices. From research we came to know that there is no such system present in Pakistan that
works on prediction. But globally there are some other systems which perform prediction related
to houses but not for lands. Also, there is no proper android application available for that
purpose. Following are those systems.

1.4.1 Check land Prices.

This Android app has area wise land pricing details it works only in India. It deals with land
valuation and property valuation. If you want to buy land in another place or city, you can easily
find land prices of other cities through this app.

Figure 1-1 Check Land Prices

1.4.2 1.4.2 London House Pricing Application

The goal of the project is to create a mobile application that can provide users with location-
specific predictions and trends on London housing market. Users of the application should be
able to obtain the following information:

16
1. Future price changes of London properties that fall within a user-defined search radius, which
can be fine-tuned by options such as property type
2. Locations that can be considered within a search radius, given a purchasing budget from the
user.

Figure 1-2 House Price predictions

17
1.4.3 Zillow
Zillow launched in 2006 and is headquartered in Seattle (U.S.A).

Zillow is the leading real estate and rental marketplace dedicated to empowering consumers with
data, inspiration, and knowledge around the place they call home, and connecting them with the
best local professionals who can help.

Zillow serves the full lifecycle of owning and living in a home: buying, selling, renting,
financing, remodeling and more. It starts with Zillow’s living database of more than 110 million
U.S. homes – including homes for sale, homes for rent and homes not currently on the market, as
well as Z-estimate home values, Rent Z-estimates, and other home-related information. Zillow
operates the most popular suite of mobile real estate apps, with more than two dozen apps across
all major platforms.

Figure 1-3 Zillow

18
 Figure 1-4 Zillow Interface

1.5 ANALYSIS FROM LITERATURE REVIEW

Table 1-1 Analysis Table

Company Type Future Price House/Land Standar

Prediction d/Local
Curren
cy rate
London Android Yes House Local
Housing Price
Prediction

Check Land Android No Land Local

Prices
Zillow Android/Web No House Standar
d
Land Price Android Yes Land Standar
Predictor d

19
1.6 METHODOLOGY AND SOFTWARE LIFECYCLE FOR THIS PROJECT
Methodology used is “agile development methodology”. The software life cycle of agile model
is followed here.

Figure 1-5 Agile Model

Step of life cycle:
 Requirements
In this step we collect the requirements for our project through questioners and expert
views of different land dealers and advisors. From their knowledge we generate our Data
Set.
 Design
In this step, we first make the uml diagrams for the system and then make interfaces for
the system.
 Develop
In this step, we develop the system modules one by one.
 Test
In this step, we conduct the test of developed module in order to check its
functionality.

20
  Deploy
In this step, we first integrate the modules and then deploy the system in that
environment in which it is used.
 Review
After deployment, users of the system use it and give review about system. From these
reviews, we learn about the performance of our system.

Rationale behind Selected Methodology

We use “agile development methodology” for developing our project because the system is
developed in a series of versions or increments with the involvement of stakeholders in
specification of version and system evaluation.

21
 Chapter 2

Problem Definition

22
2 PROBLEM DEFINITION

For many people, buying a property is one of the most important decision and purchase in life.
Besides the affordability of a house other factors such as the desirability of the location and the
long-term investment prospects also affect the decision-making process. Now-a-days people face a
lot of problems when they wanted to buy a new land or plot. The major issue is about its price in
future. It is very difficult to predict the price of land in future. According to previous knowledge of
price and area’s facilities experts can predict its price in future.

To overcome the above problems, we introduced an automated system in the form of an Android
Application named “Land Price Predictor”. We are using records of lands of different areas and
provide most precise prediction using Machine Learning Algorithms in efficient way to help users.
This application will also be useable for land experts and dealers. In this app we can predict the land
price for about 5 years further based on facilities, previous prices, and location. It can help people to
find a perfect land or plot for commercial use as well as domestic. It will also help property dealers
and real estate companies, so that they can invest their money on right place.

2.1 PROBLEM STATEMENT

Now-a-days purchasing of land/plot is a major issue because fraud is very common in our
society. Future price prediction of a land for a normal or lay person is very difficult.
Unfortunately, there is no proper prediction system or application implemented in Pakistan.
Although there are many real estate’s buying and selling apps available but unfortunately there is
no proper prediction system or application implemented here. The traditional systems based on
property advisors might contain many drawbacks like fraud, robbery etc. Major problems with
traditional system are.
 Difficult to search specific land according to needs.
 Time and effort consuming.
 Risk of fraud.

23
2.2 DELIVERABLES AND DEVELOPMENT REQUIREMENTS
Deliverables:
 The Land Price Predictor is an Android based prediction system, in which the prices are
predicted by using Machine Learning model.
 There will be a proper verification system for user, so that the users having Google or
Facebook account can only interact with the system.
 There should be a User Menu, where user can set his/her requirements such as select
location, type, plot size etc., and in response the system predicts the most précised price
for that land in the future in numeric form as well as graphical form.
 For each phase, the available resources will be displayed to user.
 Also, we are displaying prices in standard currency rate i.e., ‘$’. So, there will also a
currency converter, that convert prices into the currency in which the user wants to see.
Development Requirements:
Development requirements include tools and technologies that we are using in our system.
Table 2-2 Tools used in project.

Tools Rationale

For implementation of Machine Learning algorithms

using python
Pycharm

Star Uml (version 2.8.1) Project diagrams

MS Word (2010) Documentation

MS PowerPoint (2010) Presentation

Android Studio (version 3.5.3) For making android application

Firebase For data storing purpose

24
Table 2-3 Technologies used in project.

Technology Rationale
SQL(version 2013) Query Language
Basic concepts of python For machine learning
Firebase database Database for android application

Java Programming Language Building block for android programming/ Designing and
development of application

25
 Chapter 3

Requirement Analysis

26
3 REQUIREMENT ANALYSIS

3.1 FUNCTIONAL REQUIREMENTS

3.1.1 Use case diagrams.

The system’s use case shows the user a full view of the scheme and how actors would interact
with the system. It is a graphical depiction of the interactions among the elements of the system.
In our system, there is only single actor and that is user. So, we construct the use case diagrams
in user’s perspective.

Table 3-4 Use case elements.

No Element’s name Symbols

1 Actor

2 Use case

3 Association

27
 Figure 3-6 Use case diagram.

28
3.1.2 Detailed Use case

Table 3-5 Use case for User.

Use Case ID: UC-1

Use Case User menu
Name:
Actors: User

User first enters the system, first he will be logged into the system
using Google or Facebook account and then enter the
requirements. After all this he will get the results against his
Description: inputs

User indicates that he /she want to enter and check the

Trigger: desired output.

Preconditions: User must have internet connection to logged into the system

Post After Logging into the system, portal is shown to User

conditions:

Click to Get Started Button and then Log in with user or

Normal Flow: Facebook account.

Alternative Flows: Cancel action.

 If the requirements entered by the user are not

matched with database, it will not process the results
and pop-up message will appear.
 If the input fields are empty or invalid, then again
Exceptions: pop-up message will appear.

29
These are constraints that must be followed during the coding and without satisfying these
constrains solution is not valid. Functional requirements describe the expected behavior of the
system. These are the core system requirement and without implementing any of these
requirements the system is supposed to be incomplete.

We document few functional requirements of our system, following are those:

Table 3-6 Login/Sign up

Identifier FR 1
Title Login/authentication
Requirement The login page will show two buttons i.e., Google and Facebook
login
User will select of his own choice and then they will lead the user to
Facebook or Google login page and then he will verify himself.
FR3, FR4, FR5.
Admin must be connected to the Internet since the App only works in
Dependencies online mode.
Priority High

Table 3-7 User Menu

Identifier FR 2
Title User menu
Requirement User will have various options to select the desired requirements and
the system will respond the user by predicting the price of that land.
.

Priority High

30
Table 3-8 Resources

Identifier FR 3
Title View Resources
Requirement The available resources will show against the phase which the user
selects.

Priority High

Table 3-9 Currency converter

Identifier FR 4
Title Currency converter

The user will select the currency in which he wants to check the price
Requirement and the resultant prices will convert into that currency type.
Priority High

Table 3-10 User logout

Identifier FR 5
Title Logout
Requirement After taking the required results, user can click on the logout button
and exits from the application.

Dependencies User must be logged into the system.

After logout, the User will exit from the system and will be redirected
Fit Criterion to the home screen.

3.2 NON-FUNCTIONAL REQUIREMENTS

Nonfunctional requirements are related to the environment in which system is going to be

Operated; it does not directly associate to the functionality of system.

Table 3-11 Non-Functional Requirements

31
 System should function properly at any given time and respond in the
3.2.1 Reliability
expected way.
System should not suffer from frequent down time.
The application will meet all the functional requirement without any
unexpected behavior and System should be Recoverable and Accurate
System should be robust and not lag or crash
3.2.2 Speed
User data integrity should not be at stake.
3.2.3 Security
Records should not be compromised and manipulated.
Fast Response time
3.2.4 Performance
high Throughput (number of operations performed per second)

3.2.5 Portability
Application runs on any android OS version
Application should be simple and all modules should avoid unwanted
3.2.6 Complexity
dependencies.
Ease of learning
3.2.7 Testability
Ease of reporting
All components well integrated and complement each other.
3.2.8 Integrality
In the presence of faults, stress, and invalid inputs
3.2.9 Robustness
Provision in system for future addition of new functionalities
3.2.10 Modifiability
Efforts require to learn, use, provide, input and interrupt result of the
3.2.11 Usability
program
Minimal use of resources (disk, network, memory, and processor)
3.2.12 Efficiency
For large number of user or quantities of data
3.2.13 Scalability
This application will available all time on the user android device
3.2.14 Availability
This application can maintain easily
3.2.15 Maintainable

32
 Chapter 4

Design & Architecture

33
4 DESIGN AND ARCHITECTURE
The overall structure of a project or a system is easily understandable graphically. The design
and architecture of system is explained with the help of the diagrams. All of these diagrams
provide clear picture of all the interactions taking place in the system. These diagrams provide
a detailed infrastructure of the project. Every step of the system is explained below with
diagrams.

4.1 SYSTEM ARCHITECTURE

Our system is a land Price Prediction System that contains two modules and one centralized
database. The rectangle shape shows the sub-systems/modules, and the circle shows the
centralized database. In our system, the two sub-systems works independently (means admin
and users) but both sub-systems are linked through one centralize database.

Figure 4-7 System Architecture Diagram

34
4.2 PROCESS FLOW/REPRESENTATION
Activity diagram is used for representing the process flow. In this diagram, we check the
graphical representation of process flow. Activity diagram is an important diagram in UML
which is used to describe the dynamic aspects of the system. Activity diagram is basically a
flowchart to represent the flow from one activity to another activity.

Table 4-12 Activity diagram elements

Starting symbol

Action state

Decision

Data flow

Final node

35
 Figure 4-8 Activity Diagram

36
4.3 DATA FLOW DIAGRAM LEVEL 0

Figure 4-9 DFD0 Diagram

4.4 DATA FLOW DIAGRAM LEVEL 1

Figure 4-10 DFD1 Diagram

37
4.5 SEQUENCE DIAGRAM

Figure 4-11 Sequence diagram

38
4.6 ENTITY-RELATIONSHIP DIAGRAM

Figure 4-12 Entity Relationship Diagram

39
 Chapter 5
IMPLEMENTATION

40
5 IMPLEMENTATION
In this section we are going to discuss about the tools and techniques and the execution process
being carried out to create this product. Execution process is the fundamental time of
programming change life cycle where the thoughts are being changed into physical product. It’s
being the original time where the programming improvement skills are on full swing.

5.1 TOOLS AND TECHNOLOGIES

Following are the tools and the advances that are being utilized in the development of the
product:

5.1.1 Android Studio

Android studio is the official IDE for the android platform, it is being used in the
development of the android application.

Figure 5-13 Android Studio

41
5.1.2 PyCharm/Jupyter
This tool is being used for backend development. This tool allow the developers to design
Machine Learning algorithms in python.

Figure 5-14 PyCharm

5.1.3 Firebase:
Firebase is a real time fata base which stores the data into its online servers. It is famous because
of its securities and fast responses on user queries. Also, it can be accessible between two
applications.

Figure 5-15 Activity diagram: User

42
5.2 USER INTERFACE
User interface is the fundamental part of the product. It is what that make the image of the
product in the mind of the customer. More the interface is interactive more the customer will be
comfortable to use it. The interface of the product must be user friendly and easy to use. A good
interface make the customer to use the product more and more. Efforts are being made to make
the interface more and more attractive so that the customer can use the product easily and
efficiently. The interface include the forms and the list views and many other stuff that is being
used to gather the data from the user or to show the data to the user depending upon the request
made by the customer.

5.2.1 Splash Screen:

Splash screen is the screen where the logo of an application is shown for few seconds. It has no
specific purpose related to the project. Its just like an advertisement or gives a better look to the
application.

Figure 5-16 Splash Screen

43
5.2.2 Home Page:
From this home page, user will select whether he/she is an admin or a normal user. If the
user is admin, then he will tap on the logo button that is given on the top and if he is a
normal user then he/she will tap on the Get Started button.

Figure 5-17 Home Page

5.2.3 Login Activity

Login/Signup or Verification page is the page where user will enter the system by using his/her
Google or Facebook account. He will enter his email id and password and then enters the system
if the fields are valid.

44
 Figure 5-18 Login Activity
5.2.3.1 Google account login
When the user touches at the “Sign in with Google” option, his all google accounts that
are used in the device are shown to him and he will select his desired account and then
logged into the system.

Figure 5-19 Google account Login

45
5.2.3.2 Facebook account Login:

When the user touches at the “Facebook account Login” option, his all google accounts
that are used in the device are shown to him and he will select his desired account and
then logged into the system.

Figure 5-20 Facebook account Login

5.2.4 Requirements Menu

In this menu, user will enter all his requirements that he wants. It is the input section of
our project. From here we take inputs and then generate outputs on their basis.

46
 Figure 5-21 Requirements Menu

47
5.2.5 Results
This is the output activity of our system. The output against user’s inputs are shown here.
It includes the further 5 years prices of the land, available resources in that phase,
currency converter and graphical presentation of the prices.
The pictures below include the current price and the next 5 years predicted prices of the
land.

Figure 5-22 Predicted Prices

48
The below pictures show the available resources in the phase that user selected:

Figure 5-23 View Resources

49
 If we want to see the values in our own currency or some other currency, then we can
change the currency of our own choice. Here is the opportunity for users of different
countries.

Figure 5-24 Currency change

50
 We also show the records in the graphical form for the expert’s help,

Figure 5-25 Graphical Representation

51
 Chapter 6
EVALUATION AND
TESTING

52
6 EVALUATION AND TESTING
System testing is the process which give the results about the products that is under test phases.
System testing shows how the system will respond under certain condition. Different test are
being imposed on the system which include real and fake data and in the result the system
respond is being check on the data being input. A successful testing is the one in which the
system respond negatively on the given fake input. Main factor to keep in mind is quality
insurance different organization that don’t compromise on quality of the product concentrate on
the evaluation and testing of the product.

6.1 TESTING OBJECTIVES

The thing to keep in mind while testing the system is to find the flaws and error being present in
the system which are creating hurdles to run the project efficiently and conveniently. The next
step is to remove those flaws and error from the system to make the quality of the product better
and flawless.
 Testing is performed with the intention to find the flaws and errors in the system.
 The successful testing is the one which reveals the hidden ambiguity in the project.
 Working and productivity of the system depend upon the testing technique being used.

6.2 TYPES OF TESTING

 Acceptance Testing
 System Testing
 Unit Testing
 Integration Testing

6.2.1 Unit Testing

Unit testing is the method of testing in which the smallest unit is being monitored before joining
different units together. Every module is being tested by the developers during the
implementation of the system so that the final product will be without mistake.

53
6.2.2 Integration Testing
When different units are combined together then integration testing is being performed. It is
being carried out after unit testing and before system testing. It is being used to check that how
well these units well together. We have performed integration testing while developing it so that
a mistake free project will be produced according to the requirements.

6.2.3 System Testing

In this the overall project is being analyzed and is being tested thoroughly. To check all the
failures, present in the system and find the solutions to them. It is the most important testing to
be applied. It shows weather the product is according to the requirement of the customer or not.

6.2.4 Acceptance Testing

In acceptance testing several test cases will be run on the system. The type of result being
returned by these is of Boolean type which means whether it is successful or failure. It is the
most valuable technique to check that the system meets the requirements of the user.

54
6.3 TEST CASES

6.3.1 User Test Cases

Table 6-13 User Test cases

STEP ACTION EXPECTED RESULT ACTUAL RESULT P/F

1 Empty username and Show message to enter Show message to enter username and P
press login username and password password
2 Empty Requirements Show message to enter all Show message to enter all P
requirements requirements
3 Enter valid requirements Success Success P
4 Graphical representation Show graph according to Graph according to prices is shown P
price variation
5 Resources Show the available Proper resources are shown P
resources in the phase that according to the database
user selected
7 Currency converter User choose the currency Prices converted into the currency P
type, and prices are rate that user select
converted according to
that type.

55
 Chapter 7
CONCLUSIONS AND
FUTURE WORK

56
7 CONCLUSION AND FUTURE WORK
In this project we have overcome the problems being faced by the citizens regarding the
buying and selling of Plots in Pakistan. We have done our best to make an automatic
system which is user friendly, cost efficient and beneficial for the people of all classes to
check the prices of lands based on their needs. We tried to cover every major factor that
is involved in LAND PRICING SYSTEM. There is a room for few improvements in our
project which make our project more efficient and reliable.

7.1 FUTURE PLAN

 Land Price prediction is basically a prediction system. It only predicts the
prices of various lands of different areas but not deals with a single plot
prediction. So, this thing can be added into our system.
 We can also add a feature of buying and selling of plots in this app. So
people can also buy or sell the plots as well as its price prediction.
 We designed our application in Pakistani context, but we use standard
currency ($) because the value or rupee is variable. So, there can also be a
dollar to rupee converter in the application, which takes the current dollar
price in rupees, so people show no efforts in this regard.

57
7.2 REFERENCES
 Real-estate-prediction-on-zillow-with-prophet K. P. Murphy,Machine
Learning: A Probabilistic Perspective. MIT Press,2012.
 S. J. Sheather, “Density Estimation,”Statistical Science, vol. 19, no. 4,
pp.588–597, 2004.
 B. W. Silverman,Density Estimation for Statistics and Data Analysis.CRC
Press, 1986.
 L. van der Maaten, E. Postma, and H. van den Herik,
“DimensionalityReduction: A Comparative Review,”Elsevier, 2008.
 C. J. C. Burges,Dimension Reduction: A Guided Tour. Now PublishersInc,
2010.
 A. Jain, M. Murty, and P. Flynn, “Data Clustering: A Review,” 2009.
 P. Dayan and C. J. Watkins, “Reinforcement Learning,” inEncyclopedia
ofCognitive Science. MacMillan Press, 2001.
 D. C. Montgomery, E. A. Peck, and G. G. Vining,Introduction to
LinearRegression Analysis. John Wiley and Sons, 2012.
 I. J. Myung, “Tutorial on maximum likelihood estimation,”Elsevier Sci-
ence, 2003.
 D. Lindley and A. Smith, “Bayes Estimates for the Linear Model,”Journalof
the Royal Statistical Society, vol. 34, no. 1, pp. 1–41, 1972.

58
59