Visvesvaraya Technological University

Belagavi, Karnataka-590 018

A
MINI PROJECT REPORT ON

“Real Estate Management System”

Submitted in partial fulfilment of the requirements for the DBMS Laboratory with mini project
(18CLS58) course of the 5th semester

BACHELOR OF ENGINEERING IN COMPUTER

SCIENCE AND ENGINEERING

Submitted by,

THANUSHA R YASHASWINI H V
1JS20CS172 1JS20CS188
Under the guidance of
Mrs. K S Rajeshwari Mrs. Pooja H
Assistant Professor, Dept of CSE Assistant Professor, Dept of CSE
JSSATE, Bengaluru JSSATE, Bengaluru

JSS ACADEMY OF TECHNICAL EDUCATION,

BENGALURU
Department of Computer Science and Engineering
2022-2023
 JSS MAHAVIDHYAPEETHA, MYSURU

JSS Academy of Technical Education

JSS Campus, Uttrahalli Kengeri Main road, Bengaluru – 560060

Department of Computer Science and Engineering

CERTIFICATE
This is to certify that the mini-project work entitled "REAL ESTATE MANAGEMENT
SYSTEM" is a Bonafide work carried out by Ms. THANUSHA R (1JS20CS172) and Ms.
YASHASWINI H V (1JS20CS188) in partial fulfillment for the Database Management
Systems Laboratory with Mini Project (18CSL58) of 5th semester Bachelor of Engineering
in Computer Science and Engineering of the Visvesvaraya Technological University,
Belgaum during the academic year 2022-2023. It is certified that all corrections and
suggestions indicated for Internal Assessment have been incorporated in the report deposited
in the department library. The project report has been approved as it satisfies the academic
requirements in respect of project work prescribed for the said degree.

Mrs. K S Rajeshwari Mrs. Pooja H Mr. P B Mallikarjuna

Assistant Professor, Assistant Professor, Associate Professor and Head
Dept of CSE Dept of CSE Dept of CSE
JSSATE, Bengaluru JSSATE, Bengaluru JSSATE, Bengaluru

NAME OF THE EXAMINER SIGNATURE WITH DATE

1)…………………………………….. ……………………………………

2)…………………………………….. …………………………………….
 ABSTRACT

The World of data is constantly changing and evolving every second. This
inturn has created a completely new dimension of growth and challenges for
businesses around the globe .By accurately recording data ,storing, updating
and tracking them on an efficient and regular basis ,businesses can address
their challenges on one hand and make use of the immense potentials offered
by this sector om the other hand.

A database management system stores, organizes and manages a large

amount of information within a single software application. The use of this
system increases efficiency of business operations and reduce overall costs.

This application will help in smooth and easy functioning of selling and
buying the properties that are available in city. Users are prompted with a
login screen with their credential stored in the database.

Users will also be given with features to search the cities available, which
will help them to get a glance at the properties available around the city. The
user interface will be simple and easy to understand .Users will be able to
get the precise information about the properties that are available in the city.
 ACKNOWLEDGEMENTS
We express my humble pranamas to His Holiness Jagadguru Sri Sri Sri Shivarathri
Deshikendra Mahaswamiji who has showered their blessings on us for framing our career
successfully.

We express our sincere thanks to our beloved principal, Dr. Bhimasen Soragaon for having
supported us in our academic endeavors.

We are also indebted to Dr. P B Mallikarjuna, Head of Department of Computer Science and
Engineering for the facilities and support extended towards us.

We are thankful to the resourceful guidance, timely assistance and graceful gesture of our
guide Mrs. K S Rajeshwari, Assistant Professor, Department of Computer Science and
Engineering, and Mrs. Pooja H, Assistant Professor, Department of Computer Science and
Engineering, who has helped us in every aspect of our project work.

And last but not the least, we would be very pleased to express our heart full thanks to all the
teaching and non-teaching staff of CSE department and our friends who have rendered their
help, motivation and support.

The completion of any project involves the efforts of many people. We have been lucky
enough to have received a lot of help and support from all quarters during the making of this
project, so with gratitude, we take this opportunity to acknowledge all those who have given
guidance and encouragement helped us emerge successful.

THANUSHA R

1JS20CS172

YASHASWINI H V
1JS20CS188
 TABLE OF CONTENTS
CHAPTER TITLE PAGE NO
ACKNOWLEDGEMENT
ABSTRACT
TABLE OF CONTENTS
TABLE OF FIGURE
1 PREAMBLE
1.1 INTRODUCTION 1
1.2 DATA REQUIREMENTS 3
1.3 NORMALIZATION
4
2 SYSTEM DESIGN
2.1 INTRODUCTION 6
2.2 ER DIAGRAM 6
2.3 ER TO RELATIONAL SCHEMA 8
2.4 SCHEMA DIAGRAM 10
3 SOFTWARE REQUIREMENTS
3.1 HARDWARE REQUIREMENTS 11
3.2 SOFTWARE REQUIREMENTS 11
3.3 TECHNOLOGIES USED 11

4 DATABASE IMPLEMENTATION
4.1 ADVANTAGES OF USING 12
XAMPP
4.2 CREATE TABLES 13
4.3 TRIGGERS 25

4.4 VIEWS 27
 4.5 PSUEDOCODE 28

5 RESULTS
5.1 HOME PAGE 31
5.2 CONTACT US 32
5.3 PROPERTY PAGE 33
5.4 PROPERTY DETAILS 34
5.5 MORTAGE CALCULATOR 36
5.6 USER 37
5.7 USAGE PASSWORD 39
5.8 ADD PROPERTY 40
5.9 FORGET PASSWORD 43
5.10 ADMIN 44
5.11 REVIEW 45
5.12 SEARCH PROPERTIES 46
6 CONCLUSION
6.1 SUMMARY 48
6.2 LIMITATIONS 48
6.3 FUTURE ENHANCEMENT 49
7 REFERENCES 50
 LIST OF FIGURES
SL NO FIG NO WITH TITLE PAGE
NO.
1 Fig 2.1 E R Diagram 8

2 Fig 2.2 Relational Schema 10

3 Fig 4.2.1 Admin Table 13

4 Fig 4.2.2 City Table 14
5 Fig 4.2.3 Country Table 15

6 Fig 4.2.4 Enquiry Table 16

7 Fig 4.2.5 FeedBack Table 17

8 Fig 4.2.6 Page Table 18

9 Fig 4.2.7 Property Table 21

10 Fig 4.2.8 Property Type Table 22

11 Fig 4.2.9 State Table 23

12 Fig 4.2.10 User Table 24

13 Fig 4.3.1 Trigger1 25

14 Fig 4.3.2 Trigger2 26

15 Fig 4.3.3 Statelog Table 27

16 Fig 4.4.1 Views 27

17 Fig 5.1 Home page 31

18 Fig 5.2 Contact us 32

19 Fig 5.3 Property Page 33

20 Fig 5.4 Property Details 35

21 Fig 5.5 Pdf generated for Calculator 36
22 Fig 5.6 User Registration 37
23 Fig 5.7 User Login 37
24 Fig 5.8 User Profile 38
25 Fig 5.9 Change password 39
26 Fig 5.10 Add Property 41
27 Fig 5.11.1 Enquiry 42
28 Fig 5.11.2 Enquiry Details 42
29 Fig 5.12.1 Forgot Password Page 43
30 Fig 5.12.2 Rest Password Page 43
31 Fig 5.13 Admin Login Page 44
32 Fig 5.14 Admin Dashboard 44
33 Fig 5.15 Admin profile 45
34 Fig 5.16 Admin Change Password 45
35 Fig 5.17 Add Property Type Page 46
36 Fig 5.18 Manage Property Page 46
37 Fig 5.19 Review Page 47
38 Fig 5.20 Search Property Page 47
Chapter 1
Preamble
1.1 Introduction

A database is an organized collection of data. A relational database, more

restrictively, is a collection of schemas, tables, queries, reports, views, and
other elements. A database management system (DBMS) is a computer-
software application that interacts with end- users, other applications, and the
database itself to capture and analyze data. A general-purpose DBMS allows
the definition, creation, querying, update, and administration of databases.
There is a need for an application to make it easy for builder companies and
house or property owner to sale or rent there properties.

1.1.1 Project purpose

This website is a Online real estate business website through which a user
can access its information and manage all the adding, updating, deleting the
assets and some of its tasks. The Admin user can change the update the
information regarding property selling and buying and cancellation. The
system is very useful for the companies who developed apartments, hotels,
villa, residential properties and commercial properties. Companies or
individual agents can also advertise their property.

1.1.2 Project scope

The real of World Wide Web have spread across millions of household, so
naturally, Internet has become by far the best platform for real estate
marketing today. Now days when everything is online, how is it possible that
real estate left web application behind. There are lots of real estate
companies who advertise their property online so idea behind developing
this application is that their property can also sell, or buy rental property
using this. These applications are not widely popular but in future, they have
large scope of growth. This website is a online real estate management
through which individual agents or buyer can maintain their property
document keeping and managing property registration and also access its
information and manage all the adding, updating, deleting the as and some
of its tasks.

1.1.3 Project Objectives

• The system should have a login. A login box should appear when the
system is invoked.
• The Admin should have all the type of authority.
• The Admin should maintain property . Admin identify property type
as it is residential or commercial property.
• The Admin user can inform their agents for regarding to property
and update the information regarding property and cancellation of
property or changing buyer choice.
• The user should book the property for sell or rent with detail of
property.
• The system is very useful for the companies or builders that can post
and edit their properties and their personal info and admin can monitor
records of all of them.
• The system is also useful which also keeps track of Account details
of buyers and Investors and also RES Industry.

1.1.4 Project Goals

• Planned approach towards working: - The working in the
organization will be well planned and organized. The data will be
stored properly in data stores, which will help in retrieval of
information as well as its storage.
 • Accuracy: - The level of accuracy in the proposed system can not
be decided. Because here user buy and another user build the home.
There is no guarantee.
• Reliability: - The reliability of the proposed system will be high due
to the above stated reasons. The reason for the increased reliability of
the system is that now there would be proper storage of information

1.2 DATA REQUIREMENTS:

Register
After filling the required data, the client can register himself/herself in our
proposed system.
Login
Admin/user will be able to Login into the system with his unique username
and password.
Add Property
Property can only be added by the authenticated users.
Ask Questions
User can ask questions and get answers on this platform.
Manage Profile
User can view, update or delete the profile of his/her own.
Manage Property
Property management can be done by the user in which the user has a facility
to view, edit or delete it.
Search Property
User has the facility to search the best available property within the budget
on the basis of:
• The area covered by property
 • City
• Location
• Price range
• Property type
• Property subtype
• Purpose
Create Alert
Creation of the alert can be done by the user, through providing the data so
he/she gets a notification that property is posted on the proposed system
according to his/her requirement.
NON FUNCTIONAL REQUIREMENTS:
• Usability: Every consumers can use this Web site easily.
• Security: The consumer enter this Web not only by password, it's by
making security to our web site and network server.
• Performance: The customer can enter quickly, easy without any effort
as an organized way and our web site will be more reliable.

1.3 NORMALIZATION
Normalization is a process of organizing the data in database to avoid data
redundancy, insertion anomaly, update anomaly & deletion anomaly. To
overcome
these anomalies, we need to normalize the data. There are 4 basic types of
normalizations. They are:
• First normal form(1NF)
• Second normal form(2NF)
• Third normal form(3NF)
• Boyce & Codd normal form (BCNF)
First normal form (1NF) is defined as per rule as: an attribute (column) of a
table
Cannot hold multiple values. It should hold only atomic values. This means
that there
shouldn’t be repetition of data in the tables.
A table is said to be in 2NF if the two conditions stated are satisfied. The
table is in
First normal form and all the non-prime attribute are dependent on the proper
subset
of any candidate key of table. The attribute that is not part of any candidate
key are
known as non-prime attribute.
A table design is said to be in 3NF if the table is in 2NF Transitive functional
Dependency of non-prime attribute on any super key are removed.
Boyce Codd normal form (BCNF) is the advance version of 3NF that’s why
it is also
referred as 3.5NF. BCNF is stricter than 3NF. A table complies with BCNF
if it is in
3NFand for every functional dependency X->Y, X should be the super key
of the
table.
CHAPTER 2
SYSTEM DESIGN

2.1 INTRODUCTION
It is the process of defining, developing and designing systems which
satisfies the specific needs and requirements of a business or organization.
The purpose of the System Design process is to provide sufficient detailed
data and information about the system and its system elements to enable the
implementation consistent with architectural entities as defined in models
and views of the system architecture. The designer determine what data must
be stored and how the data elements interrelate. With this information, they
can begin to fit the data to the database model. Database management system
manages the data accordingly. Database design involves classifying data and
identifying interrelationships.

2.2 ER DIAGRAM:
An entity–relationship model or the ER Diagram describes inter-related
things of interest in a specific domain of knowledge. An ER model is
composed of entity types and specifies relationships that can exist between
instances of those entity types.
Entity Type :
It refers to the category that a particular entity belongs to.
Entity Set :
An entity set is a collection or set of all entities of a particular entity type at
any point in time. The type of all the entities should be the same.
Attributes:
In a database management system (DBMS), an attribute is a piece of data
that describes an entity.
Types of attributes:
• Single valued Attribute:
Attributes having a single value for a particular item is called a single valued
attribute.
• Multi-valued Attribute:
Attribute having a set of values for a single entity is called a multi-valued
attribute.
• Derived Attributes or stored Attributes:
Derived attribute is a type of attribute where the value for that attribute will
be derived from one or more of the other attributes of the same entity set.
• Complex Attribute:
The attributes that are formed by arbitrarily nesting the composite and
multivalued attributes are called complex attributes.
Relationship type:
A Relationship Type is a type of association that can exist between two
different (or same) entity types.
Constraints:
Constraints are used to limit the type of data that can go into a table.
Types:
• NOT NULL constraints.
• Unique constraints.
• Primary key constraints.
• (Table) Check constraints.
• Foreign key (referential) constraints.
2.3 ER TO RELATIONAL SCHEMA:
Steps to convert Entity Sets to Tables.
1. Create a table for the entity set.
2. Make each attribute of the entity set a field of the table, with an appropriate
data type.
3. Declare the field or fields comprising the primary key

Steps to convert Relationship sets to tables

1. Create a table for the relationship set.
2. Add all primary keys of the participating entity sets as fields of the table.
3. Add a field for each attribute of the relationship.
4. Declare a primary key using all key fields from the entity sets.
5. Declare foreign key constraints for all these fields from the entity sets.

Steps to translate Translating Relationship Sets with Key Constraints

to tables
1. Create a table for the relationship set.
2. Add all primary keys of the participating entity sets as fields of the table.
3. Add a field for each attribute of the relationship.
4. Declare a primary key using the key fields from the source entity set only.
5. Declare foreign key constraints for all the fields from the source and target
entity sets.

Steps to translate relationship sets with participation constraints

1. Create a table for the source and target entity sets as usual.
2. Add every primary key field of the target as a field in the source.
3. Declare these fields as not null.
4. Declare these fields as foreign keys.

Steps to translate weak entity set to tables.

1. Create a table for the weak entity set.
2. Make each attribute of the weak entity set a field of the table.
3. Add fields for the primary key attributes of the identifying owner.
4. Declare a foreign key constraint on these identifying owner fields.
5. Instruct the system to automatically delete any tuples in the table for which
there are no owners.
2.4 SCHEMA DIAGRAM:
The schema diagram of a database system is its structure described in a
formal language supported by the database management system (DBMS).
The formal definition of a database schema is a set of formulas called
integrity constraints imposed on a database.
CHAPTER 3
SOFTWARE REQUIREMENTS

3.1 HARDWARE REQUIREMENTS:

• Any processor after Pentium 4.
• Any version of Windows XP or later.
• Processor speed: 2.0 GHz
• RAM : 1GB
• Hard disk: 40GB to 80 GB

3.2 SOFTWARE REQUIREMENTS:

• Database : MySQL
• Server : Apache
• IDE : Sublim

3.3 TECHNOLOGIES USED :

Front end : HTML ,CSS , JAVASCRIPT

Connection /Controller: PHP
Back end : My SQL
CHAPTER 4
DATABASE IMPLEMENTATION
The database implementation or deployment is the process of
installation of database software, configuration and customization,
running, testing, integrating with applications, and training the
users.
Real Estate Management System Implemented using XAMPP

4.1 Advantages of using XAMPP

We can start and stop the whole webserver and database stack with one
command.
The security settings are strict by default, nobody but you will be able to
access the web server.
Php error reporting is enabled by default, which helps when debugging
scripts.
4.2 CREATE TABLES:
Admin table:
CREATE TABLE tbladmin (
ID int(10) NOT NULL,
AdminName varchar(120) DEFAULT NULL,
UserName varchar(120) DEFAULT NULL,
MobileNumber bigint(10) DEFAULT NULL,
Email varchar(120) DEFAULT NULL,
Password varchar(120) DEFAULT NULL,
AdminRegdate timestamp NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.1 Admin Table

City Table:
CREATE TABLE tblcity (
ID int(10) NOT NULL,
CountryID int(5) DEFAULT NULL,
StateID int(5) NOT NULL,
CityName varchar(120) DEFAULT NULL,
EnterDate timestamp NOT NULL DEFAULT current_timestamp() ON
UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.2 City Table

Country Table:
CREATE TABLE tblcountry (
ID int(10) NOT NULL,
CountryName varchar(120) DEFAULT NULL,
EnterDate timestamp NOT NULL DEFAULT current_timestamp() ON
UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.3 Country Table

TABLE ENQUIRY
CREATE TABLE tblenquiry (
ID int(11) NOT NULL,
PropertyID int(10) NOT NULL,
FullName varchar(200) NOT NULL,
Email varchar(200) NOT NULL,
MobileNumber bigint(10) NOT NULL,
Message mediumtext NOT NULL,
EnquiryNumber varchar(200) NOT NULL,
EnquiryDate timestamp NOT NULL DEFAULT current_timestamp(),
Status varchar(10) DEFAULT NULL,
Remark varchar(200) DEFAULT NULL,
RemarkDate timestamp NULL DEFAULT NULL ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.4 Enquiry Table

TABLE FEEDBACK
CREATE TABLE tblfeedback (
id int(11) NOT NULL,
UserId int(11) NOT NULL,
PropertyId int(11) NOT NULL,
UserRemark mediumtext NOT NULL,
PostingDate timestamp NULL DEFAULT current_timestamp(),
Is_Publish int(1) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.5 FeedBack Table

TABLE PAGE
CREATE TABLE tblpage (
ID int(10) NOT NULL,
PageType varchar(120) DEFAULT NULL,
PageTitle mediumtext DEFAULT NULL,
PageDescription mediumtext DEFAULT NULL,
Email varchar(120) DEFAULT NULL,
MobileNumber bigint(10) DEFAULT NULL,
UpdationDate timestamp NULL DEFAULT NULL ON UPDATE
current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.6 Page Table

TABLE PROPERTY
CREATE TABLE tblproperty (
ID int(10) NOT NULL,
UserID char(20) DEFAULT NULL,
PropertyTitle mediumtext DEFAULT NULL,
PropertDescription mediumtext DEFAULT NULL,
Type varchar(50) DEFAULT NULL,
Status varchar(100) DEFAULT NULL,
Location varchar(200) DEFAULT NULL,
Bedrooms varchar(200) DEFAULT NULL,
Bathrooms varchar(200) DEFAULT NULL,
Floors varchar(200) DEFAULT NULL,
Garages varchar(200) DEFAULT NULL,
Area varchar(50) DEFAULT NULL,
Size varchar(50) DEFAULT NULL,
RentorsalePrice varchar(120) DEFAULT NULL,
BeforePricelabel varchar(120) DEFAULT NULL,
AfterPricelabel varchar(120) DEFAULT NULL,
PropertyID varchar(120) DEFAULT NULL,
CenterCooling int(4) DEFAULT NULL,
Balcony int(4) DEFAULT NULL,
PetFriendly int(4) DEFAULT NULL,
Barbeque int(4) DEFAULT NULL,
FireAlarm int(4) DEFAULT NULL,
ModernKitchen int(4) DEFAULT NULL,
Storage int(4) DEFAULT NULL,
Dryer int(4) DEFAULT NULL,
Heating int(4) DEFAULT NULL,
Pool int(4) DEFAULT NULL,
Laundry int(4) DEFAULT NULL,
Sauna int(4) DEFAULT NULL,
Gym int(4) DEFAULT NULL,
Elevator int(4) DEFAULT NULL,
DishWasher int(4) DEFAULT NULL,
EmergencyExit int(4) DEFAULT NULL,
FeaturedImage varchar(200) DEFAULT NULL,
GalleryImage1 varchar(200) DEFAULT NULL,
GalleryImage2 varchar(200) DEFAULT NULL,
GalleryImage3 varchar(200) DEFAULT NULL,
GalleryImage4 varchar(200) DEFAULT NULL,
GalleryImage5 varchar(200) DEFAULT NULL,
Address varchar(200) DEFAULT NULL,
Country varchar(200) DEFAULT NULL,
City varchar(220) DEFAULT NULL,
State varchar(200) DEFAULT NULL,
ZipCode varchar(200) DEFAULT NULL,
Neighborhood varchar(200) DEFAULT NULL,
ListingDate timestamp NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
Fig 4.2.7 Property table
TABLE PROPERTY TYPE
CREATE TABLE tblpropertytype (
ID int(10) NOT NULL,
PropertType varchar(120) DEFAULT NULL,
EnterDate timestamp NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.8 Property Type Table

TABLE STATE
CREATE TABLE tblstate (
ID int(10) NOT NULL,
CountryID int(5) DEFAULT NULL,
StateName varchar(120) DEFAULT NULL,
EnterDate timestamp NOT NULL DEFAULT current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.9 State Table

Table User
CREATE TABLE tbluser (
ID int(10) NOT NULL,
FullName varchar(120) DEFAULT NULL,
Email varchar(120) DEFAULT NULL,
MobileNumber bigint(10) DEFAULT NULL,
Password varchar(120) DEFAULT NULL,
UserType int(5) DEFAULT NULL,
PostingDate timestamp NULL DEFAULT current_timestamp(),
Aboutme mediumtext NOT NULL,
UpdationDate timestamp NOT NULL DEFAULT '0000-00-00 00:00:00'
ON UPDATE current_timestamp()
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Fig 4.2.10 User Table

4.3 TRIGGERS:
Triggers are stored programs, which are automatically executed or fired
when some event occurs. Triggers are written to be executed in response to
any of the following events. A database manipulation (DML) statement
(DELETE, INSERT, or UPDATE). A database definition (DDL) statement
(CREATE, ALTER, or DROP).
The code of trigger is given below:
Trigger 1:
CREATE TRIGGER ‘STATEUPDATE’
AFTER UPDATE ON ‘TBLSTATE’
FOR EACH ROW
INSERT INTO STATELOG
VALUES(NULL,NEW.ID,NEW.COUNTRY ID,NEW.STATE NAME,
‘STATE UPDATED’,NOW());

Fig 4.3.1 Trigger 1

Description:
A trigger named STATE used in this project which upon updating the value
in the TBLSTATE updates and displays the ‘STATELOG’ with a newly
updated value.

Trigger 2
CREATE TRIGGER ‘STATE’
AFTER INSERT ON ‘TBLSTATE’
FOR EACH ROW
INSERT INTO STATELOG
VALUES(NULL,NEW.ID,NEW.COUNTRY ID,NEW.STATE NAME,
‘STATE INSERTED’,NOW());

Fig 4.3.2 Trigger 2

Driscription: A trigger named STATE used in this project which upon
adding the value in the TBLSTATE updates and displays the ‘STATELOG’
with a newly added value.
 Fig 4.3.3 Statelog Table

4.4 VIEWS
A view is virtual table based on the result set of an SQL statement .It contains
rows and columns , just like a real table. The fields in view are fields from
one or more real table in a database.
CREATE VIEW VIEWPROP AS
SELECT ID, UserID , PropertyTitle ,Area ,Size , RentorsalePrice
FROM `tblproperty`
4.2 PSUEDO CODE:
4.2.1Algorithm for admin login
Step 1: BEGIN
Step 2: Enter username and password
Step 3: Verify the credentials entered with that in the login table
Step 4: If Credentials match, then proceed to the
Admin page Else show login failed
Step 5: End if
Step 6: END

4.2.2 Algorithm for table display

Step1: BEGIN
Step 2: Establish connection with the database using the username and
password ofthe database.
Step 3: Define the select query to retrieve all the values from the
DBMS
Step 4: Define Default TableModel for the table and fetch
the details from thedatabase.
Step 5: END

4.2.3 Algorithm for insert

Step 1: BEGIN
Step 2: Get all the necessary values required for insertion into variable
defined in themehod.
Step 3: Define the query for insertion as stated above.
Step 4: Execute the Query using the (Select * from) the required table.
Step 5: END

4.2.4 Algorithm for update

Step 1: BEGIN
Step 2: Get all the necessary values required for updating the values into
the variable defined in the method
Step 3: UPDATE table name
SET column1 = value1, column2 = value2, ...
WHERE condition;
Step 4: Define the Query for Updating as stated above.
Step 5: Execute the Query using the execute Update() method defined.
Step 6: END

4.2.5 Algorithm for delete

Step 1: BEGIN
Step 2: Get the model number of the instrument which is to be deleted into
a variable defined in the method.
Step 3: Delete from table_name where condition;
Step 4: Define the Query for deleting as stated above.
Step 5: Execute the Query using the execute Update() method defined .
Step 6: END

4.2.6 Algorithm for jFrame Transition

Step 1: BEGIN
Step 2: Define the object for the class that the transition frame is defined in.
Step 3: use the ‘this’ keyword to point to the current frame object and
use the set Visible method and set it to false. This makes the existing
jFrame disappear.
Step 4: use the object name from the above created object and use the
Set Visible method and set it to true. This makes the next Frame appear.
Step 5: END
CHAPTER 5
RESULTS
These are some snapshots of Real Estate Management System.

HOME PAGE

Fig 5.1 Home Page

• Home page contains login options for users and Admin login for
admin.
• It has property search option .One can search the property only after
login.
 Fig 5.2 Contact us

• Fig 5.2 Is the contact us page of the Website .

• Users or customers can get address of head quarters or office address,
Customer Care number and email address.
Fig 5.3 Property page
Fig 5.3 Is property page of the website.
In Property page User can get to see list of Property types, Property status,
Properties in different city on left side .
Various properties are also displayed. Search option is provided for
searching the properties by their city, property status and property type.

Property Details
 Fig 5.4 Property Details
Property Details Page appears when user clicks on the Property they want to
see .
Posted by column contains the details of the person who posted the property.
Features of Properties which are present and not present will be specified.
Location of the property is also available on this page.
MORTAGE CALCULATOR

Fig 5.5 Pdf generated for Calculator

Outcome of Calculator is generated in pdf format.
User

Fig 5.6 User Registration

Fig 5.7 User Login

User Registration and Login Pages appears as shown in Fig 5.6 and 5.7
 Fig 5.8 User Profile
User profile has user details and users can eidt their profiles.
Change Password:

Fig 5.9 Change Password

Change Password option is provided for user to Reset their passwords.
Add Property
 Fig 5.10 Property Adding Page

While adding Property One should give Description of property,

Property features which are available and Exact Location of the property.
 Fig 5.11.1 Enquiry

Fig 5.11.2 Enquiry Details

User or Customer can Contact Owner of property by sending messages and
gets answers back.
Forgot Password:

Fig 5.12.1 Forgot password page

Fig 5.12.2 Reset Password Page

Password can be reset by giving forgot password and providing email and
mobile Number.
ADMIN

Fig 5.13 Admin Login Page

Fig 5.14 Admin Dashboard

Admin Dashboard has total count of various aspects like properties ,total
no of cities in which properties are available ,total users registered ,number
of owners and so on..
 Fig 5.15 Admin Profile

Fig 5.16 Admin Change Password Page

 Fig 5.17 Add property Type Page

Fig 5.18 Manage Property Page

Adding of property types and management of property Types like editing

can be done by admin.
Review

Fig 5.19 Review Page

Reviews by users will appear in in the reviews section .
Reviews are categorised as approved and unapproved reviews
Search properties:

Fig 5.20 Search Property Page

Admin can search the properties either by giving the Property Id or User
name of one who added property to website or by giving mobile number of
one who added property to website.
CHAPTER 6:
CONCLUSION
6.1 SUMMARY:
Summary of Project work In whole procedure to prepare project, we first
gather the requirement of the project and decide the time schedule. After
planning we design the documentation of project. After the design we
generate the code of system. In design the code we do the error estimation
and effort estimation. If error is occur then solve it. Finally when code is
designed then test the project and decide the cost of project.
6.2 LIMITATIONS:
Although I have put my best efforts to make the software flexible, easy to
operate but limitations cannot be ruled out even by me. Though the software
presents a broad range of options to its users some intricate options could
not be covered into it. Partly because of logistic and partly due to lack of
sophistication. Paucity of time was also major constraint, thus it was not
possible to make the software foolproof and dynamic. Lack of time also
compelled me to ignore part such as transaction of the money etc.
Considerable efforts have made the software easy to operate even for the
people not related to the field of computers but it is acknowleged that a
layman may find it a bit problematic at the first instance. The user is provided
help at each step for his/her convenience in working with the software.
List of limitations which is available in the Real Estate Management System:
• The transactions are executed in offline-mode ,hence on-line data for
PropertyDetails, Flats capture and modification is not possible.
• Off-line reports of Property, Location, Property Details cannot be
generated due to batch mode execution.
6.3 FUTURE ENHANCEMENTS
• We can give more advance software for Real Estate Management
System by including more facilities.
• We will host the platform on online servers to make it accessible
worldwide.
• Integrate multiple load balancers to distribute the loadsof the system.
• Create the master and slave database structure to reduce the overload
of the database queries.
• Implement the backup mechanism for taking backup of codebase and
database on regular basis on different servers.

The above mentioned points are the enchancements which can be

done to increase the applicability and usage of this project. Here we can
maintain the records of Property and Property Type. Also,as it can be
seen that now-a-days the players are versatile, i.e. so there is a scope for
introducing a method to maintain the Real Estate Management System.
Enhancements can be done to maintain all the Property, Property Type,
Property Details, Flats, Locations.
We have left all the option open so that if there ia any other future
requirement in the system by the user for the enchancement of the System
the it is possible to implement them.
CHAPTER 7
REFERENCES
WEB REFERENCES:
For PHP
https://www.w3schools.com/php/default.asp
https://www.sitepoint.com/php/
https://www.php.net/
For MySQL
https://www.mysql.com/
http://www.mysqltutorial.org
For XAMPP
https://www.apachefriends.org/download.html
BOOK REFERENCES:
1. Fundamentals of Database Systems, Ramez Elmasri and Shamkant B.
Navathe, 7th Edition, 2017, Pearson.