Software Requirements

Specification
for

Online Real Estate

Management System
Version 1.0 approved

Prepared by

Raghwendra Pratap Singh,Shalini Singh,Soumodip Sinha,

Subham Gupta,Vishma Pratap Kumar.

Techno India College Of Technology

22.02.2016

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions...................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective.........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces.............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1.............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6

Revision History
Name Date Reason For Changes Version
Srs for online real 22.02.16 NA 1.0
estate management
system
Software Requirements Specification for <Project> Page 1

1. Introduction
1.1 Purpose
Online real eastate management system is an indian real estate website.The purpose of this
website is to present a deatailed description of the Online real eastate management system.The
system srs will explain the purpose and features of the system,the constraints under which it must
operate and how the system will react to external stimuli. The purpose of this software is to make
the process of purchasing,selling and renting properties easier and convenient for users, which
saves time and manual effort.

1.2 Document Conventions

This documentation is available in Microsoft Word format or PDF format contains docx to facilitate
access by the users.We use various conventions in text to help more quickly identify special terms.
FONT-Arial and Times.
BOLD-Bold interface indicates the terms that are defined in the text or terms that appear in the
glossary or both.
ITALIC-It is used to label and recognize the diagrams.
UPPERCASE-It has been used to emphasize section headings.
LOWERCASE- It has been used to emphasize sub-section headings.
HIGHLIGHT-Highlighting is to point out words in the glossary.
UNDERLINE-It is mainly for the URLs.

1.3 Intended Audience and Reading Suggestions

The SRS for this system is intended for

Development Teams.
 Project Manager.
 Marketing Staff.
 Testers.
 Documentation Writers.
It has been organized approximately in order of increasing specificity.
Associated organizations may review the document to learn abouy the project and to understand
the requirements.
The developers and project managers need to be familiar wih the SRS.
Testers need an understanding of the system features to develop meaningful test cases and give
useful feedback to the developers.

1.4 Product Scope

This is an real estate management website.The website features property listings from
builders,dealers and property owners from all indian cities
 The system has three featues BUY,SELL AND RENT..
 In our website users can find four types of properties;newly launched,ready to move
property,under construction and spare lands in a particular locality or cities.
Software Requirements Specification for <Project> Page 2

 Visitors can compare the price of a property in different locality

 The system provides information about the current price rates and quarter to quarter
analysis of the area.
 The system releases its property report insite which highlights the trend across major
metropolitan cities of India.
 It saves time and effort of users.
Our future goal is to launch property search on mobile and provide a mobile site and
application for android and ios users.

1.5 References

2. Overall Description
2.1 Product Perspective
The software product being developed is for a online real estate management system which
functions as a online portal for buy,sell and rent properties.The real estate website will serve two
areas mainly potential clients and realtors.Since this system will be a web based site/application a
proper internet connection will be needed for viewing and interacting with its contents.The website
is developed with the intention to ease the work,decreasing paper work and flourishing E-
Commerce.The website is completely user friendly with different language translation,loan
facility,price analysis etc.This will be just a tap away for buyers,sellers and tenants as well.The
system is very useful for the companies or builders,buyers and investors whose proper records of
their account will be maintained.

2.2 Product Functions

.Online real estate management system contains the following key features.
 Homepage
 Visitor (SIGNUP/LOG IN)
 Updating buyers information
 Updating sellers information
 Updating property and price information
 Transaction Details
 LOG OUT

2.3 User Classes and Characteristics

Expected user(client) scope is anybody who has an internet connection.The application does not
require any extra knowledge or skills other than basic browsing experience.Any user can search
the contents in the website and open and ue it to seek real estate.

2.4 Operating Environment

Software will operate:

 Hardware specification
Software Requirements Specification for <Project> Page 3

1. Server:
i. Processor: 2.4 GHz or higher (Intel / AMD)
ii. RAM:512 MB (or above).
iii. HARD DISK:20 GB (or above)
2. Client:
i. Processor: 2.4 GHz or higher (Intel / AMD)
ii. RAM:512 MB (or above).
iii. HARD DISK:10 GB (or above)
 Software specification
I. Operating System: Windows XP / 7 / 8 / 8.1 / 10, Mac OS, Linux.
II. Web Server:IIS Server.
III. Web Browser:IE 4,Firefox,Chrome or others.

2.5 Design and Implementation Constraints

2.6 User Documentation

Clients need some user manuals, on-line help, and tutorials that will be delivered along with the
software.

2.7 Assumptions and Dependencies

 Assumptions:
 Any user with basic internet knowledge can use it independently since it is an web-
based software.
 It will be an user friendly software.
 It will provide unlimited searching criteria for registered as well as unregistered users.
 It will be a time saving as well as secure system.

 Dependencies:
 Only the registered user can add and remove any particular listings of a property.
 In case of any invalid user id or password, login cannot be done.
 Without proper registered profile user cannot perform transaction.
 Loan facility or emi options will not be available for users with insufficient bank balance.

3. External Interface Requirements

3.1 User Interfaces
 The interface should be completely user friendly so that the client can use this system
independently.
Software Requirements Specification for <Project> Page 4

 GUI should be designed in a concentrated manner so that it attract users attention.

 Help desks numbers and email id should be there for user’s convenience.
 Proper error messages should be displayed in case of any irregular syntax.

3.2 Hardware Interfaces

 Processor: 2.4 Ghz or higher (Intel /AMD)
 System bus: 32 bit / 64 bit
 RAM: 1 GB or more
 Hard disk drive: 40 GB or more
 Monitor: SVGA color
 Keyboard: QWERTY keyboard Ps2 / USB
 Mouse: Ps2/USB
 Modem:256 kbps / ADSL broadband

3.3 Software Interfaces

 Operating System: Windows XP / 7 / 8 / 8.1 / 10, Mac OS, Linux.
 Web Server:IIS Server.
 Web Browser:IE 4,Firefox,Chrome or others.

3.4Communications Interfaces
 Main communication protocol over the internet Hyper Text Transfer Protocol(HTTPs) will
be used..
 TCP /IP protocol will be used as a backend of HTTPs i.e,for the intranet communication.
 A web browser such as IE 6.0 or equivalent.

4. System Features
4.1 HOMEPAGE

4.1.1 DESCRIPTION & PRIORITY

The homepage will display featured property listings,have quick search,and other various
links such as contact us.sitemap that will provide the user with more relevant type of real
estate informations.

4.1.2 STIMULUS / RESPONSE SEQUENCES

Software Requirements Specification for <Project> Page 5

When the user mentioned his desired search in the search listings dialog box the search listing page
will allow the user to perform a detailed search of any available properties within the website as per
the requirement.

4.1.3 FUNCTIONAL REQUIREMENTS

Purpose:
To browse the real estatement properties.

Inputs:
The input will be the property according to the requirement such as flats,bungalows,spare land,etc.

Output:
The user will be transferred to the main page of the search listings of the property on its availability
in a mentioned area and requirement.

4.2 VISITOR SIGN UP/LOGIN PAGE

4.2.1 DESCRIPTION & PRIORITY

Any user can search the website and open and use it to seek real estate without registering.User can
login into the sytem if already exists or can register to the system and create its profile completing
the sign up process.

4.2.2 STIMULUS / RESPONSE SEQUENCES

On successful validation of each data field, the registration procedure takes place.

4.2.3 FUNCTIONAL REQUIREMENTS

Purpose:
To edit,delete his/her profile.

Inputs:
The required data for updating the information of a user would be given ie;basic contact information.

Output:
Either a successful acknowledgment is displayed or else an error message is displayed.

4.2.4 BENEFICIERY REGISTRATION

Users’ will have to be registered otherwise they wont be able to send and receive in application
messages and adding items to their wishlist.

4.3 UPDATING SELLER INFORMATION

Software Requirements Specification for <Project> Page 6

4.3.1 DESCRIPTION & PRIORITY

To update and change certain features of their account such as listing a new property,changing
selling price,can edit the details and remove existing ones.

4.3.2 STIMULUS / RESPONSE SEQUENCES

On successful validation of each data field, the updating procedure occurs.

4.3.3 FUNCTIONAL REQUIREMENTS

Purpose
To update and change the selected Account Details.

Inputs
The required data for updating the information of an Account would be given.

Output
Either a successful acknowledgment is displayed or else an error message is displayed.

4.4 UPDATING BUYER/TENANT INFORMATION

4.4.1 DESCRIPTION & PRIORITY

When a user wants to buy or rent a property user simply opens the website and enter its desired
criteria and location constraints to see the properties according to his/her choice.

4.4.2 STIMULUS / RESPONSE SEQUENCES

On successful validation of each data field, the transaction takes place.

4.4.3 FUNCTIONAL REQUIREMENTS

Purpose
To perform the different functions in a general account like , adding to its favourite list, updating
user profile,and see the property details and contact information.
Inputs
The required data like Name, address for performing the specific transaction operation like opting
emi and loan facility.
Output
The success message is displayed if the transaction was successful or else an error
message is displayed.

4.5 UPDATING PROPERTY DETAILS

Software Requirements Specification for <Project> Page 7

4.5.1 DESCRIPTION & PRIORITY

This feature would be used to view the details of any property,land etc.

4.5.2 STIMULUS / RESPONSE SEQUENCES

On selecting a property from a Location the corresponding property details would be displayed.

4.5.3 FUNCTIONAL REQUIREMENTS

Purpose
To view the details of any branch registered.
Inputs
The property would be selected by the user from the List of All the real estate
registered under the website.
Output
On successful validation, the property details are displayed or else an error message is
displayed.

4.7 TRANSACTION AND PAYMENT DETAILS

4.7.1 DESCRIPTION & PRIORITY
This feature would display the transaction details or payment details like loan facility of an account
when the buyer or tenant basic account and bank details meet the requirement.

4.7.2 STIMULUS / RESPONSE SEQUENCES

On clicking the hyperlink the transaction or payment details are displayed.

4.7.3 FUNCTIONAL REQUIREMENTS

Purpose
To display the transactional/payment details of an account.

Inputs
The user has to click on the payment Hyperlink in the transaction summary page
or Main Page

Output
The payment details are displayed in a tabular format according to the eligibility criteria.

4.8 LOGOUT

4.6.1 DESCRIPTION & PRIORITY

This feature would enable the user to successfully end his session and Logout of the system. After Logging
Out, he/she would not be able to perform any of the buyer or seller role,until he/she is again Logged In.

Priority of this module is that this module should be performed last.

Software Requirements Specification for <Project> Page 8

4.6.2 STIMULUS / RESPONSE SEQUENCES

On clicking the Logout Button, the session is terminated and the Login screen appears.

4.6.3 FUNCTIONAL REQUIREMENTS

Purpose
To successfully end the user session and Logout of the real estate management system.

Inputs
NA

Output
On successful termination of the session, the Login Screen is displayed.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.2 Safety Requirements

 The web should provide strong encryption. The address bar should show the padlock and ‘HTTPS,’
because we want to make sure we are transmitting any information over an encrypted channel

5.3 Security Requirements

5.4 Software Quality Attributes

6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are perltinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>
Software Requirements Specification for <Project> Page 9

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

Appendix C: To Be Determined List

<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they
can be tracked to closure.>