75% found this document useful (4 votes)

9K views

Project Report On Real State Web App

Final year project report on web development

Uploaded by

Abdullah Ammar

Available Formats

Download as PDF, TXT or read online on Scribd

75% found this document useful (4 votes)

9K views

Project Report On Real State Web App

Final year project report on web development

Uploaded by

Abdullah Ammar

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 124

REAL-ESTATE WEB APP

A PROJECT REPORT

For partial fulfillment of the requirement

for the Award for degree of

BACHELOR OF COMPUTER SCIENCE

Submitted by:

ABDULLAH AMMAR (G.L) 16BS(CS)-10

TANVERR AHMED 16BS(CS)-43
ALI IRTIZA HOAT 16BS(CS)-37

Supervised by:

Engineer Amir Bhutto

Department of Computer Science

Quaid-e-Awam University of Engineering
Science & Technology

October – 2019
CERTIFICATE

This is certified that the work presented in this thesis on “Real-Estate Web App” is
completed and demonstrated by the following group of students of 16BS(CS) batch
themselves under the supervision of honorable Sir Mr. Muhammad Amir Bhutto.

ABDULLAH AMMAR (G.L) 16BS(CS)-10

TANVEER AHMED 16BS(CS)-43
ALI IRTIZA HOAT 16BS(CS)-37

__________________________ __________________________
Mr. Muhammad Amir Bhutto Dr. Muhammad Saleem Vighio
SUPERVISOR CHAIRMAN

_________________________
EXTERNAL EXAMINER

ii
ABSTRACT

The aim of this project was to build a real estate web application using Django
framework and Postgresql. The programming environment was VS code using the
Python programming language. The real estate system provides functionality for
buyers, allowing them to search for houses. It provides functionality for the seller,
allowing them to log into the system and add new listings or delete existing ones. For
this purpose, each user is provided a login account with login ID and password access.
This web application makes use of Django framework, including web controls, html
controls, custom web controls, CSS, error handling. The programming tasks included
building the customer web controls and deploying these on server.

This site is basically developed to provide property information

to User and Realtor. User can search any kind of Real Estate with multiple options in sort
or in details and also shows interest in desired property. Realtor post real estate properties
with full required information, add any location, modify property and view interested
user who interested in his property. Admin can add any location for real estate property,
view details and delete user, realtor and property information (product). As the website
is user-friendly, it contains both simple search for any general user and also advance
search option for us

ii
Acknowledgement

ACKNOWLEDGEMENT

We take this opportunity to express our thoughtful sense of gratitude and respect to all
those who helped us throughout the duration of my project. The beatitude, bliss and
euphoria that accompany the successful completion of any task would not be completed
without the expression of appreciation of simple gratitude to the organization and people
who made it possible.

We are highly indebted to our University for providing us with such a intellectual
platform and support to carry out our project work successfully.

We wish to express out deep sense of gratitude to, Mr. Amir Bhutto, Assistant
Professor, QUEST Nawabshah for his able guidance and useful suggestions, which
helped us in completing the project work, in time.

I express my heartfelt thanks and gratitude to the chairman of the department Prof.
Saleem Vighio, for giving me an opportunity to undertake this project.

Words are inadequate in offering thanks to all my teachers for their constant guidance
and support throughout this project work.

Finally, yet importantly, we would like to express my heartfelt thanks to our beloved
parents for their blessings, out friends for their help and wishes for the successful
completion of this project.

Project Team
Contents

CONTENTS

CERTIFICATE-------------------------------------------------------------------ii
ABSTRACT------------------------------------------------------------------------ii
ACKNOWLEDGEMENT------------------------------------------------------iii

Chapters Page Numbers

Chapter 1: Introduction ----------------------------------------------------------------1

1.1 Introduction
1.2 Objectives
1.3 Scope of Project

Chapter 2: Literature Review ---------------------------------------------------------9

2.1 Literature Survey
2.2 Risk in E-Commerce
2.3 Real-Estate Transaction Stages

Chapter 3: Design and Implementation --------------------------------------------13

3.1 System Requirements
3.2 System Design
3.3 Table Structure

Chapter 4: Flow Charts and DFDS -------------------------------------------------23

4.1 System Flow Charts
4.2 Data Flow Diagrams
4.3 Entity Relationship Diagram

Chapter 5: Testing ---------------------------------------------------------------------29

5.1 System Testing
5.2 Test Levels
5.3 Testing Methods

Chapter 6: Samples --------------------------------------------------------------------37

6.1 User Forms

Chapter 7: Conclusion ----------------------------------------------------------------42

7.1 Conclusion
7.2 Future Scope of the system
Contents

Appendix I: Overview-----------------------------------------------------------------47
A.I.1 Software Specification
A.I.2 Physical Specification

Appendix II: Coding ------------------------------------------------------------------54

A.II.1 Coding

Bibliography ---------------------------------------------------------------------------118
Chapter I: Introduction

1|Page
1.1 Introduction

Modern technology has been industrialized to the extent that even search for land,
apartments is made possible over the internet. The process of searching of dream house
or apartment can be done over the internet. Customer looking to buy or rent a new
home, apartment or any other property can search over the internet.

Customer looking to buy or rent a new home, apartment or any other property can
search over the internet, while sitting at their home. Now customers will not have to go
to the agents personally they can search for their desired home or apartment of a
reasonable rate which suits their pocket.

 Customer looking to buy or rent a new home, apartment or any other property
can search over the internet.

 Customer can search for desired plot or house in a particular area.

 They can specify the no of rooms ,bathroom they need and then can make the
search

 They can also describe what all facilities they want near their house like schools,
malls, garage, shops etc.

 They can search for apartment or plot which suits there budget they can also
specify the amount by entering the cost.

 . Now customers will not have to go to the agents personally they can search for
their desired home or apartment of a reasonable rate which suits their pocket.
And they can also have the view of apartment online

2|Page
The application will be a windows-based, self-contained and independent software product.

Request for Data

HTML/ASP Page .aspx page with

over Client the result (Server)
Machine
Database

Retrieve Data

3|Page
BLOCK DIAGRAM

Search property

Who are we?

Contact
Home

User Login
Product &services
Real-estate
website About us
Specialty
Employee Login
Staff
Employee profile
Username & password

Address
Contact
us Telephone
Update Add new Select
property property the seller Email id
listing listing of month Quick
search

4|Page
1.2 Objectives

 The major objective of real estate website is the convenience it offers.

 By sitting back at home customer looking to buy a new home, apartment or any
other property can search the desired property by several clicks of mouse
buttons.
 Customers do not have to go to the agents personally they can save their time
by making an online search
 To make the website user friendly.
 To reduce paper work
 To integrate all information which customer needs in the website
 To save people time
 To allow user to enter the acres of land & desired amount for which he wishes
to spend
 To allow the customers to have a pictorial view of the apartment he wishes to
buy
 To overcome the limitations being faced during the manual system of handling
the entire records of the company manager and to manage the work schedule as
well effectively and efficiently.
 To provide more accuracy.
 To provide more security by implementation of various validations.
 To provide easy updating of property listing that involves very little expertise or
knowledge.
 To provide quick and efficient listing of properties.
 To eliminate eligible handwriting, paper work and manual entry.

5|Page
1.3 Scope of Project

 To design a real estate website of a particular agency using information collected

through internet.

 To design a website which integrates all the information needed by user.

 To make the website user friendly.

 To allow the user to search plot & land according to his needs
 The user can specify the location where he wants the land.
 To save user‘s time by allowing easy access to the site.
 Shortens the time between data collection and data analysis.
 Reduces workload
 An advanced yet handy tool with an easy-to-use interface.
 Quickly and easily manages property listings.
 Contributes hugely in saving the time and enhances data quality.
 Data inconsistency almost eliminated

 Storage requirement highly reduced

6|Page
1.4 ADVANTAGES

 Customer can do 24*7 searching.

 More productive and efficient work.
 High degree of Authenticity.
 User friendly
 Time efficient
 Paper saving

1.5 METHDOLOGY USED FOR DATA COLLECTION

Data collection can be done through various sources like interviews, questionnaire,

document analysis or Internet.

1. Primary Data: Interview and Internet

2. Secondary Data: Document Analysis

1.5.1 DATA COLLECTED BY INTERNET

Data about the brief description of organization is collected through Internet i.e. through

the existing website of real estates like:-

 BTrealstate.com

 99 acres.com

 Magic bricks.com

 Scribd.com

7|Page
1.5.2 DATA COLLECTION THROUGH INTERVIEW

Interview is an easy way to interact with the customer. The objective of conducting an

interview is to understand the customer’s expectations from the software. Are you

satisfied with current website?

1. If not, what is the problem you are facing?

2. What all improvements are suggested?

3. Any suggestion to improve this website?

4. Any special feature that you want to be added to website?

1.5.3 DATA COLLECTED THROUGH DOCUMENT ANALYSIS

Data is also collected by various documents which demonstrate the working of the system

and through the newspaper’ Times Property’

8|Page
Chapter II: Literature Review

9|Page
2.1 Literature Survey

Past studies concerning the relationship between the Internet and real estate can be
classified into a few dominating themes. One direction is how the Internet has become
and continues to be a very important tool for marketing real estate and related services.
Rodriquez, Lipscomb and Yancey (1996) identified four different types of real-estate
related sites, including those that offered both real estate for sale and real estate
services, and provided an extensive list of these sites. Bond, Seiler, Seiler and Blake
(2000) examined the explosive growth of real estate-related websites and determined
the reasons why Ohio real estate brokerage firms did or did not use websites in their
businesses, the information contained in their sites and the technical requirements that
were necessary for maintaining them. Similarly, Muhanna (2000) examined how real
estate firms adapted to the use of the Internet and assessed their perceptions regarding
its potential.
A growing body of literature looks at the effect of the Internet on retail sales,
property and service (e.g., Mander, 1996; Wheaton, 1996; Schwarz, 1997; Borsuk,
1999; Hemel and Schmidt, 1999; Baen, 2000; and Miller, 2000). For example, Baen
and Guttery (1997) examined how the Internet threatened the traditional relationship
among licensees, real estate buyers and sellers, and how these developments would
create savings for real estate consumers. Similarly, Thrall (1998) discussed the
emerging trends and changes in the Internet for other real estate service providers,
including lenders, appraisers and commercial brokers. Baen (2000) examined the
impact of e- commerce on traditional retail sales, as well as its potential impact on
commercial property values and percentage rents. Tse and Webb (2002) studied the
impact of information technology on real estate brokerage in Hong Kong, using
regression models to investigate how page ‘‘views’’on the Internet affect real estate
transactions and commissions. Finally, Lucas (2001) believes that since information
technology facilitated the design of new types of organizations, institutions and
partnering arrangements, its implementation would have second-order effects on
demand for physical space of manufacturing, retailing and offices in the industrialized
world.

In older days when we want purchase a property we can’t directly communicate with
the owners. We must contact with the help of mediators, but the mediators takes lot of
amount and it is also time consuming process. In older days the property dealing
procedure consist of many steps like finding agent, appoint correct meeting time,
location and so on. Up till now there was no Security in Online Real Estate System,
Registration form improves the security by limiting user.

The existing sites are:

1. www.99acres.com: The site can be navigated by anybody. No issue of Security is

implemented.

2. www.zameen.com: It is the Pakistani real state website.

10 | P a g e
2.2 Risks in E-commerce

An expansive list of studies examines the risks in e-commerce transactions (e.g., Jung,
Han and Suh 1999; Hsiung, Scheurich and Ferrante, 2001; and Chan, 2001). One focus
is on how to develop technological methods to deal with these risks. For example,
Skevington (1998) outlined some of the technologies that were developed to address
security concerns and to apply them to facilitate trust in electronic trading. Atif (2002)
described a proposal for a trust web model based on a distributed search algorithm and
a network of trusted intermediaries that can establish a trusted channel through which
terminal transacting parties deal virtually directly and risk-free with each other.
However, the traditional models of trust between vendors and buyers fall short of the
requirements for an electronic marketplace, where anonymous transactions cross
territorial and legal boundaries, as well as traditional value-chain structures. To
overcome this problem, Manchala (2000) introduced a notion of quantiﬁable trust to
evaluate the transaction risk in such an environment. Another direction of the literature
focuses on the managerial perspective of the
transaction risks of e-commerce. Using case studies, Lee and Clark (1997) presented
suggestions on the analysis, design and implementation of electronic market systems by
market-making ﬁrms. Brice (2001) discussed some of the risks and considerations
involved in the use of electronic signatures. Westland (2002) developed a model for
evaluating and managing transaction risk in e-commerce in the migration from broker
mediated to electronic markets.

2.3 Real Estate Transaction Stages

Real estate agents and ﬁrms are essentially market intermediaries, connecting buyers
and sellers and facilitating the real estate transaction process. Traditionally, real estate
sales can be divided into ﬁve stages: property listing, buyer search, property evaluation,
negotiation and execution/closing. With the development and popularity of information
technology, each stage of this process has been affected profoundly.

Stage 1: Property listing. In the past, real estate agents listed houses and entered them
into a Multiple Listing Service (MLS) database. The MLS is today an online network
of properties listed for sale and supported by the NAR. In effect, the MLS created a
cartel-like role in managing information and virtually ensures that the agent will have a
pivotal role in the real estate transaction. However, this situation has since changed
with the introduction of websites in the market that provide property listings. Asurvey
by Muhanna (2000) found that about 23% of real estate agents actually list their
properties on their own websites. In addition, Fletcher (1997) found that their owners
were listing many homes for sale on websites. For example, on Microsoft’s network
system, Home Advisor (www.homeadvisor.msn.com), and national selling services,
such as Abele Owners Network, any seller’s listing can be posted for a nominal fee
(Guttery, Baen and Benjamin, 2000; and Bond, Seiler, Seiler and Blake, 2000).

Stage 2: Buyer search. Although potential buyers can search for homes on their own
through browsing newspaper advertisements or call owners directly, most prospective
buyers generally seek homes through agents that have access to MLS listings.
Nevertheless, buyers can now perform their own searches on the Internet easily. Many
MLS listings can now be reached directly (Aalberts and Townsend, 2002), such as the

11 | P a g e
NAR’s website (www.realtor.com) with more than a million listings. Established real
estate players, such as Coldwell Banker (www.coldwellbanker.com) and Prudential
(www.realbid.com) also have their own listings. Moreover, there are also upstarts doing
the same, including the For-Sale-By-Owner (FSBO) listing and Microsoft’s
Homeadvisor. Finally, some local newspapers provide their own websites
for real estate listings. For example, the Classified Federation, a subsidiary of the
Newspaper Association of America, created www.realfind.com, which is a free service
through which potential buyers may request a copy of the weekend real estate section
of newspapers in major markets and can link directly with the newspaper classifieds via
the Internet

Stage 3: Property evaluation. Traditionally, after buyers ﬁnd a property of interest, an

agent often arranges for a walk-through showing or has access to a house through a
lock-box. Now, it is possible to conduct a ‘‘virtual’’walk-through online. Since electronic
pictures can be downloaded into a computer’s hard drive, electronic cameras allow the
use of pictures to include landscaping, interior views and neighborhood scenes. In
addition, electronic versions of property photographs and information can be recorded
in VCR tapes and shipped overnight to prospective buyers around the globe.
Furthermore, websites can provide prospective buyers the option to examine the
surrounding neighborhood and environment, including shops, schools, parks,
entertainment, transportation, weather conditions and even crime statistics. As a result,
the number of properties that need to be physically inspected by a buyer can be
substantially reduced. In reality though, no current real estate website can make most
buyers conﬁdent enough to decide to buy without any actual physical inspection.

Stage 4: Negotiation and agreement. Negotiating the purchase agreement successfully

can be considered as the most challenging task for a real estate agent. It involves advice
regarding price, offers and counteroffers, and contract contingencies. It also requires
dealings with other real estate professionals, such as lenders, appraisers, title companies
and attorneys. Nevertheless, this stage has also been changed signiﬁcantly by
information technology. Now a buyer can identify their own appraisers, lenders, title
companies and attorneys, and negotiate with these parties directly through the Internet
(Aalberts and Townsend, 2002). In addition to the use of email, software is also
available that can support multi-party meetings on the Internet, such as Netmeeting.
Capabilities like that offered by Netmeeting allow for virtual negotiation instead of
relying on the physical presence of the different parties.

Stage 5: Execution/closing. The customary role of the escrow agent or attorney in

directing the closing is also changing. The Electronic Signatures in Global and National
Commerce Act or E-Sign legislation passed on October 1, 2000, signiﬁcantly removed
impediments for business and government transactions to be conducted electronically.
It was predicted that E-signature would allow real estate transactions, which are
traditionally slowed down by endless paper trails, to take place online (Brice, 2001).
Although the dream of ‘‘paperless transactions’’is not yet reality, there have been a few
notable ‘‘paperless transactions’’involving residential real estate. Last year, for example,
Orlando, Florida-based Attorney’s Title Insurance Fund participated in two closings
that met the strict deﬁnition of this highly automated process (Southerland, 2002).

12 | P a g e
Chapter III: Design & Implementation

13 | P a g e
3.1 System Requirements

FRONTEND PAGES

 Home
 About
 Listings
 Single Listing
 Search
 Register
 Login
 Dashboard (Inquiries)

DESIGN SPECS

 Use BTRE logo (Frontend and admin)

 Branding colors – blue(#10284e) green(#30caa0)
 Mobile Friendly
 Social media icons & contact info
 Doesn’t have to be too fancy but must be clean

FUNCTIONALITY SPECS

 Manage listings, realtors, contact inquiries and website users via admin
 Role based users (staff and non-staff)
 Display listings in app with pagination
 Ability to set listings to unpublished
 Search listings by keyword, city, state, bedrooms and price (Homepage &
search page)
 List realtors on about page with “seller of the month” (Control via admin)
 Listing page should have fields listed below
 Listing page should have 5 images with lightbox
 Lightbox should scroll through images
 Listing page should have a form to submit inquiry for that property listing
 Form info should go to database and notify realtor(s) with an email
 Frontend register/login to track inquiries
 Both unregistered and registered users can submit form. If registered, can only
submit one per listing

14 | P a g e
LISTING PAGE FIELDS

 Title
 Address, city, state, zip
 Price
 Bedrooms
 Bathrooms
 Square Feet
 Lot Size
 Garage
 Listing Date
 Realtor – Name & Image
 Main image and 5 other images

Possible Future Functionality

 Google maps on listing page

 Buyer testimonials

15 | P a g e
DESCRIPTION OF ‘INPUT TO’ AND ‘OUTPUT OF’ OF PROCESSES

Employee Login Process

EMPLOYEE USERNAME, PASSWORD ACCESS TO SYSTEM

SPECIFY PROPERTY (input) (output) SEARCH RESULT

TO BE SEARCHED
Searching
Process

Registering New User Process

ENTER NEW EMPLOYEE DETAILS Account STORE THE DETAILS

Creation
(Input) Process (Output) (Saved to reg table)

Update property listing process

PROPERTY UPDATED UPDATE

Data File
LISTING
(Input) (Output) (Saved)

Updating New Property Process

NEW PROPERTY UPDATED Data File

(input) UPDATE (Output) (saved )
LISTING

16 | P a g e
3.2 System Design

The system objective outlined during the system analysis serve as the basis from which

the work of system design is initiated. Much of the activities elaborate at this stage is of

technical nature requiring a certain amount of degree of experience in designing systems,

sound knowledge of computer related technology and thorough understanding of

computers related technology. However a system cannot be designed in isolation without

the active involvement of the user. The user has a vigorous role to play at this stage too.

As we know that data collected during the system requirement analysis will be utilized

systematically at this stage. Depending on the plan of system analysis, the level of

detailed study will differ and the system design stage will also differ in the amount of

investigations that still need to be done. This study is generally an activity during the

system design as the designer need to study the minute details in all aspects of the system.

Designing a new system is a creative process which calls for logical as well as lateral

thinking. The logical approach involves systematic moves towards the end product

keeping in mind the know-hows of the personnel and the equipment at each decision

making step. Lateral thought implies including of ideas beyond the usual functions and

equipment’s.

17 | P a g e
3.2.1 SYSTEM DESIGN CONSTRAINTS

The system design process is not a step by step adherence of clear procedures and

guidelines. When designer starts working on system design he will face different types

of problems. Many of these will be due to the constraints imposed by the use or

limitations of the hardware and software available in the market.

3.2.2 THE PRIMARY OBJECTIVE OF THE DESIGN IS:

Of course to deliver the requirements as specified in the SRS. In general, the following

design objectives should be kept in mind:

 Practicality: The system must be stable and can be operated by people with

average IQ.

 Efficiency: This involves accuracy, timeliness and comprehensiveness of the

system output.

 Cost: It is desirable to aim for a system with a minimum cost subject to the

condition that it must satisfy all the requirements.

 Flexibility: The system should be modifiable depending on the changing needs

of the user.

 Security: This is very important aspect of the design and should cover areas of

hardware reliability, fall back procedures, physical security of data and

provision for detection of fraud and abuse.

18 | P a g e
3.2.3 MAJOR SYSTEM DESIGN ACTIVITIES

Several development activities are carried out during structured design. They are data

base design, implementation planning, system test preparation, and system interface

specification and user documentation.

 Database Design: This activity deals with the design of the physical database. A

key is to determine how the access paths are to be implemented.

 Program Design: In conjunction with database design is a decision on the

programming language to be used and the flowcharting, coding and the

debugging procedure prior to conversion. The operating system limits the

programming languages that will run of the system.

 System and Program Test Preparation: Each aspect of the system has a

separate test requirement. System testing is done after all programming and

testing is completed. The test cases cover every aspect of the proposed system,

actual operations user interface and so on.

19 | P a g e
3.2.4 Use case Diagram:

A use case diagram is a diagram which consists of set of usecases and actors enclosed by
system boundary, and association between usecases and actors. Usecases diagram
especially important in organizing, modeling the behavior of the system.

Use case is a set of scenarios tied together by a common user goal. A scenario is a
sequence of steps describing the interaction between a user and system.

Use case Diagram for User:

HOME PAGE
REAL ESTATE
WEB APP

VIEW
PROPERTIES

User
ENTER DETAILS FOR
DESIRED PROPERTY

CONTACT THE
REALTOR

20 | P a g e
Use case Diagram for Admin:

Add listing Update listing

Delete listing View details

Admin

21 | P a g e
3.3 Table Structures

Category ID Category Name Categorydescription

Auto number Text text

EMPLOYEE

Empid Fname Lname Password Areacode Phone Email Gender Username Datestarted
Auto Text text Text text Text text text text text
number

LIST PROPERTY

Listgid Desclong Avaliability Acres Sqrfeet Numbath Numbed Streetnum Street Zip

Auto no Memo Text text number number number text text text

Catergoryid Schooldist Price Access Empid Proprtyid

number text currency currency Auto no Auto no

PROPERTY

Propertyid Propertyname Propertydescription

Auto number Text Text

CONTACT

Emailed subject query

Text Text Text

22 | P a g e
Chapter IV: Flowcharts & Data Flow Diagrams

23 | P a g e
4.1 System Flow Charts

A flow chart is defined as a pictorial representation describing a process being studied or

even used to plan stages of a project. Flow charts tend to provide people with a common
language or reference point when dealing with a project or process.
Four particular types of flow charts have proven useful when dealing with a process
analysis: top-down flow chart, detailed flow chart, work flow diagrams, and a
deployment chart. Each of the different types of flow charts tends to provide a different
aspect to a process or a task. Flow charts provide an excellent form of
documentation for a process, and quite often are useful when examining how various
steps in a process work together.
When dealing with a process flow chart, two separate stages of the process should be
considered: the finished product and the making of the product. In order to analyze the
finished product or how to operate the process, flow charts tend to use simple and easily
recognizable symbols. The basic flow chart symbols below are used when analyzing how
to operate a process.

24 | P a g e
USER SEARCH FOR PROPERTY

Listing

25 | P a g e
VIEW PROPERTY DETAILS

26 | P a g e
3.2 Data Flow Diagrams

A graphical tool used to describe and analyze the moment of data through a system
manual or automated including the process, stores of data, and delays in the system. Data
Flow Diagrams are the central tool and the basis from which other components are
developed. The transformation of data from input to output, through processes, may be
described logically and independently of the physical components associated with the
system. The DFD is also known as a data flow graph or a bubble chart.
A graphical tool used to describe and analyze the moment of data through a system
manual or automated including the process, stores of data, and delays in the system.

Data Flow Diagrams are the central tool and the basis from which other components are
developed. The transformation of data from input to output, through processes, may be
described logically and independently of the physical components associated with the
system. The DFD is also known as a data flow graph or a bubble chart.

27 | P a g e
3.3 Entity Relationship Diagram

28 | P a g e
Chapter V: Testing

29 | P a g e
5.1 System Testing

In this stages the test group of the development team, using the cases and the test data
already prepared will test the programs. Only after all the functions are tested singularly,
an integrated testing will be performed to see that inter-function dependability is
satisfied. Separate test cases and test data will be worked out for the integrated testing.

Any system, to be successful, must be thoroughly tested, and well managed test plan
should be prepared before actual testing is being performed. “Modules” have been
developed and need to be tested in a manner that can reduce occurring of defects as low
as possible. Following are the activities we planned to test the system.

1. This system is indeed an evolutionary system so every unit of the system is

continuously under testing phase.

2. One test activity “Basis Path Testing” that will try to cover all paths in the system.
This activity identifies all paths that provide different functionality of the system,
and also other paths to reach at that functionality.

3. Other testing activity is “Control Structure Testing”, which will test each and
every condition with positive and negative data combination.

4. This testing activity will also perform “Data Flow Testing” in which it will be
tested how the data re following the system. And will also check whether the data
entered from one procedure, is reflected whenever it requires or not.

5. All conditions will be tested with “Boundary Value Analysis” where different
input will be given to test whether the system is functioning with boundary values
or not.

6. Along with the boundary value analysis, the system is also tested with “Range
Value Tested” where editable values will be tested with ranges of values.

7. The system is being tested in “Unit Testing” manner where at the completion of
one unit that is tested thoroughly with above mentioned testing activities.

8. The integration testing will also be performed to ensure that the integrated unit is
working properly with other units or not.

30 | P a g e
5.2 Test Levels

5.2.1 CONTENT TESTING:

Errors in Project content can be as trivial as minor typographical error as incorrect

information, improper organization or validation of intellectual property laws. Content
Testing attempt to uncover this and many other problems before the user encounter them.

Content Testing Objectives:

There are three types of objectives.

 To uncover syntactic errors in text-based documents, graphical representation and

other media.

 To uncover semantic errors in any content object represented as navigation error.

 To find errors in organization or structure of content that is presented to the end-

user

5.2.2 INTERFACE TESTING:

Interface design model is reviewed to ensure that generic quality criteria established for
all user interfaces have been achieved and that application specific interface design issue
has been properly addressed.

Interface testing strategy:

The overall strategy for interface testing is to (1) Uncover error related to specific
Interface mechanisms (2) uncover errors in the way the interface implements the
semantics of navigation, Web Application functionality, or content display. To
accomplish this strategy, a number of objectives must be achieved:

 Interface futures are tested to ensure that design rules, aesthetics and related
visual content are available for the user without error.

 Individual interface mechanisms are tested in a manner that is analogous to unit

testing.

Testing Interface Mechanisms:-

When a user interacts with a system, the interaction occurs through one or more interface
mechanisms.

31 | P a g e
Forms: -

At a microscopic level, tests are performed to ensure that

 Labels correctly identified fields within the form and that mandatory fields are
identified visually for the user.

 The server receives all information content within the form and their no data are
lost in the transmission between client and server.

 Appropriate defaults are used when the user does not select from a pull down
menu or set of buttons.

 Browsing functions don’t corrupt data entered in the form.

 Scripts that perform error checking on data entered work.

 Properly and provide meaningful error message.

Client side scripting:-

Black box tests are conducted to uncover any error in processing as

The script is executed. These tests are coupled with forms testing because script input is
often derived from data provided as part of forms processing

Application specific interface mechanisms:-

Test conforms to a checklist of functionality and features that are defined by the interface
mechanism.

 Boundary test minimum and maximum number of item that can be placed in to
shopping chart.

 Test to determine persistence of image capture contents.

 Test to determine whether the system can be record co-ordinate content at some
future date.

5.2.3 USABLITY TESTING:-

Usability test may be designed by Project engineering team.

 Define a set of usability testing categories and identify goal for each.

 Design test that will enable each goal to be evaluated.

 Select participants who will conduct test.

 Instrument participant’s interaction with system while testing is conducted.

32 | P a g e
 Develop a mechanism for assessing the usability of the system.

The following test categories and objective illustrate establish testing:-

Interactivity- Are interaction mechanism easy to understand and use?

Layout- Are navigation mechanism, content and function place in a manner that allows
the user to find them quickly?

Readability- Is the text well written and clear?

Aesthetics- Do layout color, typeface, and related characteristics lead to ease of use?

Display Characteristics- Does the system make optimal use of screen size and
resolution?

Time Sensitivity- Can important features, functions and content be used in a timely
manner?

Accessibility- Is the system accessible to people who have Disabilities?

5.2.4 COMPATIBILITY TESTING:-

Project must operate within environment that differs from one another. Different
computer, display device, OS, browser and network connection speed can have
significant on system operation. The Project team derives a series of compatibility,
validation tests, derived from existing interface tests, navigation tests, performance tests
and security tests.

33 | P a g e
5.3 Testing Methods

Analyze and check system representation such as the requirement document, design
diagrams and the program source code. They may be applied at all stages of the process.

Unit Testing

Module Testing

Sub-system
Testing

System Testing

Acceptance
Testing

34 | P a g e
There are different Models of testing. On the basis of testing methods there are two types
of testing:

1. White-box testing.

2. Black-box testing

1. WHITE-BOX TESTING

White-box testing sometimes called glass-box testing, is a test case design method that
users the control structure of the procedural design to drive the test case.

 Logical errors and incorrect assumption are inversely proportional to the

probability that a program will be executed. Errors tend to creep into our work
we design and implement function, condition or control that is out of the
mainstream tends to be well understood.

 We often believe that a logical path is not likely to be executed when in fact it
may be executed on a regular basis. The logical flow of a program times counter
intuitive.

2. BLACK-BOX TESTING:

For our project periodically we have tested our software using black-box testing.
Thinking as a client we have evaluated the software for its easy going and convenience.

 Unit Testing:

During the programming stages each and every form, modules and class treated unit has
been put into the test data. Every module is tested independently. The steps are follows:

 Manually code is tested like spelling checks, logic and errors.

 Once the manual checking is over the complication has been done. Syntactical
errors if any have to be corrected.
 After the clean complication the program, some dummy data, as specification,
has been used for testing of the module to see if it works as specified.

 Integration Testing:

After our individual’s modules were tested out we go the integrated to create a complete
system. This integration process involves building the system and testing the resultant
system for problems that arise from component interaction.

35 | P a g e
 Performance Testing:

Performance testing is designed to test the runtime performance of the system within the
context of the system. These tests were performed as module level as well as system
level. Individual modules were tested for required performance.

 Condition Testing:

Performance testing is a test case design method that exercises the logical conditions.

 Interface Testing:

Interface sting is integral part of integration. We examined the code to be tested and
explicitly list each call to an external component. In the system standards tests for GUIs
have been performed, which are as follows:

 The position and related labels for all controls were checked.
 Validations for all inputs were done.
 Pull down controls was verified for proper functionality.
 Whether the non-editable text controls disabling and it was also verified that it
doesn’t exceed the maximum allowed length.

36 | P a g e
Chapter VI: Samples

37 | P a g e
6.1 Output Samples

Home Page

About Us

38 | P a g e
Featured Listing

39 | P a g e
Register

40 | P a g e
Dashboard

LighBox

41 | P a g e
Chapter VI: Conclusion

42 | P a g e
7.1 Conclusion

 This Real Estate Web App is a typical web application using Django framework,
PostgreSQL database in Python programming language.
 It uses a client/server architecture based on the HTTP protocol. It is developed
in VS Code editor in python programming environment.
 The buyer performs a search for the property listings by putting either Zip
code/City/State in the search textbox. The business logic tier communicates with
the database tier requesting the results of the query sent by it.
 The results obtained by the database are displayed on the data grid, by refreshing
the grid rather than refreshing the entire web page. Efficiency of the application
is improved by the using such a high level framework for web development.
 The performance of this application is evaluated by rigorously testing it against
various test scenarios. Some ways in which this system could be enhanced with
additional functionalities are discussed in the section.

7.2 Future Scope of the system

 This project is developed as a master’s project and still gives lot of scope for its
extension which could be made to the project if it is going to be developed as
commercial product.
 We can use pure object-oriented domain model to deal the database access tier
using VS Code editor. In doing this, we can get a better architecture design which
will improve code efficiency and running performance.
 This project just deals with the Home page and Search page to search for property
listings, more functionality can be added for searching the agents and offices
making it a complete application.
 The feature of providing Google Maps within this application can adds up to the
functionality of the website. With the advancement of technology, dynamic maps
can be generated which help the buyer can locate a particular area where the
property is located in the Google Map.
 Buyer testimonials can also be add in future if the it need it.

43 | P a g e
 Inclusion of all these features would make the application feature rich. The
advantages of putting these functionalities in the project are described in detail in
the following sections.

44 | P a g e
Appendix I: Overview

45 | P a g e
APPENDIX-I

A I.1 SOFTWARE SPECIFICATION

SOFTWARE REQUIREMENTS SPECIFICATION

A Software Requirements Specification (SRS) is a whole description of the behavior of

the system to be developed. It comprises a set of use cases that define all the connections

the users will have with the software. Use cases are also known as functional

requirements. In addition to use cases, the SRS also contains nonfunctional

requirements. Non-functional requirements are requirements which impose

limitations on the design or implementation (such as performance engineering

requirements, quality principles, or design constraints).

DESIGN SPECIFICATION

Design specifications are the measurements and characteristics of a structure or object

which provide for a workable, sustainable, or pleasing creation or construct. This can
apply to a wide variety of manufactured or fabricated objects, such as buildings,
automobiles, and clothes and also utility, computing, and distribution systems. Any
functional thing made by human beings has certain specific details.

FUNCTIONAL SPECIFICATION

In software development, a functional specification (also, functional spec or specs or

functional specifications document (FSD) or Program specification) is the set of
documentation that describes the requested behavior of an engineering system. The
documentation typically describes what is needed by the system user (design-goal),
which internal functions are necessary, as well as, requested properties of inputs and
outputs (for ex. of the software system). As a design document, a functional specification

46 | P a g e
does not typically define the inner workings of the proposed system, it means it does not
yet include the specification how the system function will be implemented. Instead, it
focuses on what various outside agents (people using the program, computer peripherals,
or other computers, for example) might "observe" when interacting with the system

PRODUCT DESIGN SPECIFICATION

A product design specification (PDS) is a statement of what a not-yet-designed product

is intended to do. Its aim is to ensure that the subsequent design and development of a
product meets the needs of the user. [1]

The PDS acts as an initial boundary in the development of products. However, it will
naturally evolve as it is progressed through the different stages of the design process.[2]

REQUIREMENTS ANALYSIS

In systems engineering and software engineering, requirements analysis encompasses

those tasks that go into determining the needs or conditions to meet for a new or altered
product, taking account of the possibly conflicting requirements of the various
stakeholders, such as beneficiaries or users. Systematic requirements analysis is also
known as requirements engineering[1]. It is sometimes referred to loosely by names such
as requirements gathering, requirements capture, or requirements specification. The
term requirements analysis can also be applied specifically to the analysis proper (as
opposed to elicitation or documentation of the requirements, for instance

SOFTWARE DEVELOPMENT PROCESS

A software development process is a structure imposed on the development of a software

product. Synonyms include software life cycle and software process. There are several

47 | P a g e
models for such processes, each describing approaches to a variety of tasks or activities
that take place during the process.

SPECIFICATION (TECHNICAL STANDARD)

A specification is an explicit set of requirements to be satisfied by a material, product,

or service.

USE OF A SPECIFICATION

In engineering, manufacturing, and business, it is vital for suppliers, purchasers, and

users of materials, products, or services to understand and agree upon all requirements.
A specification is a type of a standard which is often referenced by a contract or
procurement document. It provides the necessary details about the specific requirements.

Specifications may be written by government agencies, standards organizations (ASTM,

ISO, CEN, etc), trade associations, corporations, and others.

A product specification does not necessarily prove the product to be correct. Just because
an item is stamped with a specification number does not, by itself, indicate that the item
is fit for any particular use. The people who use the item (engineers, trade unions, etc) or
specify the item (building codes, government, industry, etc) have the responsibility to
consider the available specifications, specify the correct one, enforce compliance, and
use the item correctly. Validation of suitability is necessary.

48 | P a g e
SPECIFICATION AND DESCRIPTION LANGUAGE

Specification and Description Language (SDL) is a specification language targeted at the

unambiguous specification and description of the behaviour of reactive and distributed
systems. It is defined by the ITU-T (Recommendation Z.100.) Originally focused on
telecommunication systems, its current areas of application include process control and
real-time applications in general.

SDL provides both a graphical Graphic Representation (SDL/GR) as well as a textual

Phrase Representation (SDL/PR), which are both equivalent representations of the same
underlying semantics. A system is specified as a set of interconnected abstract machines
which are extensions of finite state machines (FSM).

SYSTEM REQUIREMENTS

To be used efficiently, all computer software needs certain hardware components or other
software resources to be present on a computer system. These pre-requisites are known
as (computer) system requirements and are often used as a guideline as opposed to an
absolute rule. Most software defines two sets of system requirements: minimum and
recommended. With increasing demand for higher processing power and resources in
newer versions of software, system requirements tend to increase over time. Industry
analysts suggest that this trend plays a bigger part in driving upgrades to existing
computer systems than technological advancements

49 | P a g e
A I.2 PHYSICAL SPECIFICATIONS

DATA FLOW DIAGRAM

It is common practice for a designer to draw a context-level DFD first which shows the

interaction between the system and outside entities. The DFD is designed to show how a

system is divided into smaller portions and to highlight the flow of data between those

parts. This context-level DFD is then "exploded" to show more detail of the system being

modeled.

Data flow diagrams were invented by Larry Constantine, the original developer of

structured design, based on Martin and Estrin's "data flow graph" model of computation.

Data flow diagrams (DFDs) are one of the three essential perspectives of Structured

Systems Analysis and Design Method SSADM. The sponsor of a project and the end

users will need to be briefed and consulted throughout all stages of a system's evolution.

With a dataflow diagram, users are able to visualize how the system will operate, what

the system will accomplish, and how the system will be implemented. The old system's

dataflow diagrams can be drawn up and compared with the new system's dataflow

diagrams to draw comparisons to implement a more efficient system. Dataflow diagrams

can be used to provide the end user with a physical idea of where the data they input

ultimately has an effect upon the structure of the whole system from order to dispatch to

restock. How any system is developed can be determined through a dataflow diagram.

Developing a DFD helps in identifying the transaction data in the data model.

There are different notations to draw data flow diagrams, defining different visual

representations for processes, datastores, dataflow, and external entities.

50 | P a g e
It is common practice for a designer to draw a context-level DFD first which shows the