Web Enabled Estate Agent

Objective of the Project

The Objective of this project is to develop a online real estate agent system that is of beneficial
to either a real estate agent or a prospective. The “Web Enabled Estate Agent”(WEEA) is an
Internet based application. This system can be used to store and search the property
portfolios. On the website, real estate agent can put the information regarding property
portfolios. A general user can browse such portfolios.

Functional components of the project

Following is a list of functionalities of the system. More functionality that you find appropriate
can be added to this list. And, in places where the description of functionality is not adequate,
you can make appropriate assumptions and proceed.

There are registered people in the system. They are real estate agents. Registered real estate
agents can create/modify property portfolios. Non-registered people can also use the system
to search the desired property.

1. A registered person should be able to

• Login to the system through the first page of the application

• Change the password after logging into the system

• See his/her property portfolios

• Create new property portfolio

• Modify an existing property portfolio.

2. A property portfolio contains details about the property like description of property,
area, to be sold or to be rented, approximate price, name and details of the person to
be contacted.

3. Details in property portfolio are editable except property id.

4. A new realtor should be able to register himself.

5. When a new property portfolio is created, it will be assigned a unique property id.
System will generate this id.

6. System should not let unauthorized/non-registered persons to create/modify property

portfolios.

7. Another realtors cannot modify property portfolio created by a realtor.

8. A prospective buyer should be able to search for the property. S/He can enter search
criteria like area name, price range, sell purchase/rent etc.

Software Requirement Specification

Software requirements specification is a specification of requirements for the software product.

The goal of software requirements definition is to completely and consistently specify the
technical requirements for the software product in a concise and unambiguous manner. During
analysis we found the minimum s/w requirements for the proposed system are as follows:

• Back-end tool: Oracle

• Operating System: Windows/Linux
• Front-end technologies: HTML, JavaScript, JSP, Servlets
• MVC Framework: Struts 1.3
• Application Server: Tomcat 6 or Glassfish V2
• Browser: Cross Browser Compatible

Hardware requirements:
• P4 with minimum 1 GB RAM

Requirements Specification (RS)

Following are the requirement specifications. That would help in validating the system during
testing.

No. Requirement Essential Description of the Remarks

or Requirement
Desirable
RS1 The system should Essential A login box should
have a login appear when the system
is invoked.
RS2 The system should Essential For new users who want
have registration to register with the
facilities. system
RS3 The system should Desirable This feature will improve Since the
‘lock’ the login id if the robustness of the application is
wrong password is application. going to be
entered 3 times in a Application will keep used only by
row counts of login attempts the employees
for a valid login id. If this of the
count exceeds 3, organization,
application will this feature is
temporarily block further not essential.
login attempts for the id. However, if time
is there, this
will be
implemented.
RS4 Once any authorized Essential Property portfolio Property
person logs in, he creation means to enter Portfolio Data
should be able to data for the said will be saved
create property property. Definition of into a database
portfolio. the property related data system.
is provided in section
RS5 Once any authorized Essential
person logs in, he
should be able to
modify details of
previously created
portfolios.
RS6 A simple user can use Essential Search criteria includes
this website to search 1. Area in the city
for the property 2. Available for
o Rent
o Sell
 3. Type of property,
e.g.

• Row house
• Bungalow
• 1BHK flat
• 2 BHK flat

Property Portfolio Data

Property portfolio data contains following things:

Property Address
Property Description
Type of availability, e.g. Rent or Sell
Expected Rent/Selling price (Optional information)
Property’s Photographs (Minimum 0 and maximum 3)
Person other than real estate agent to be contacted (Optional information)

Database Specification

Database will contain 3 tables as follows:

• User
• Property
• Photographs

Table definition for each of the above table is as follows:

User

No Field Name Range of valid values for Remarks

. the field
1 Login Id Alphanumeric field
Minimum size 6 char
Maximum size 15 char
2 Password Up to 15 characters in
length.
3 Address of Up to 100 characters in
user length.
4 Phone No. Numeric Field
5 Mobile No. Numeric Field
6 Access Flag Boolean
7 Mail id
This is the key field of the User table
as it is unique for an employee in
the organization. This will also serve
as the login for the system.
Special characters like (),[],*,^,$,
are allowed. Combination of
alphabets and numbers allowed as
valid password.
Optional
Optional
Optional
This field will be false if user has
made 3 consecutive unsuccessful
attempts to log in.
A system administrator can change
value of this field directly.
Mail id of the user

Property

N Field Name Range of valid values for Remarks

o. the field
1 Property Id This is key field of the Property
table. It is unique for each property.
It is application’s responsibility to
generate value for this id.
 2 Property
address
3 Type of Rent
property Sell
4 Property Minimum 50 char
description Maximum 1000 char
5 Expected Price
6 Person to be Optional. Will have value in case
contacted person other than estate agent can
deal for the property

Photographs

No Field Name Range of valid values for Remarks

. the field
1 Property Id Primary and foreign key for the table
Photographs
2 Photograph1 BLOB
3 Photograph2 BLOB
4 Photograph3 BLOB

Test-Plan (TP)

It is important to note that the testcases cover all the aspects of the system (ie, all the
requirements stated in the RS document).

No Testcase Description Expected The Result

. Title Outcome requirement in
RS that is
being tested
1 Successful The login to the Login should RS1 Passed
User system should be be successful
Verification tried with the login and the user
assigned by the should enter in
admin and the to the system
correct password
2 Unsuccessful Login to the system Login should RS1 Passed
User with a wrong fail with an
Verification password error ‘Invalid
due to Password’
wrong
password
3 Unsuccessful Login to the system Login should RS1 Passed
User with a invalid login fail with an
Verification id error ‘Invalid
due to user id’
invalid login
id
4 Successful Unique login id User should be RS2 Passed
Registration All the mandatory able to check
and optional fields Successful
have correct values Registration
page
5 Unsuccessful Login id not User should be RS2 Passed
Registration unique. able to check
Password and login Unsuccessful
id are same Registration
 page with
reason
6 Login Lock Wrong password User should RS3 Passed
will be entered 3 not be able to
consecutively for a login
correct login id
7 Successful User enters valid User should be RS4 Passed
property data. able to see
portfolio page showing
creation property id and
completion of
process.
8 Successful User enters valid User should be RS5 Passed
Property data for existing able to see
modification property page-showing
completion of
process.
9 Property User enters valid User is able to RS6 Passed
Search search criteria see the page
that lists
properties for
the criteria
specified.