Real Estate Management System
Software Requirements Specification
Version 1.0
Group Id: S18020F15E (MC170201198, MC170201911)
Supervisor Name: Fahad Naseem
1
Revision History
Date Version Description Author
(dd/mm/yyyy)
21/05/2018 1.0 SRS is a description of a software MC170201198,
system to be developed. SRS MC170201911
Document is on following contents
Scope of the Project
Functional Requirements
Non-functional
Requirements
Use Case Diagram
Usage Scenarios
Adopted Methodology
Work Plan
2
Table of Contents
Sr. No. Title Page No.
1. Scope (of the project) 04
2. Functional Requirements, Non Functional requirements 04
3. Use Case Diagram 06
4. Usage Scenarios 07
5. Adopted Methodology 15
6. Work Plan (Use MS Project to create Schedule/Work Plan) 19
SRS Document
1. Scope of Project:
Real Estate Management System (REMS) is a web application that will allow its users to
view, compare, bid and make advance payments for the properties listed over the web site.
Page 3 of 19
The application will also provide its users with the facility of searching for different
properties. We will use PHP programming language and MySQL database to develop this
application. There will three types of users (Owner, User and Administrator) in this
application. Admin can manage user, manage property categories, manage property
advertisements and verify posted property by owner. Owner can search property
advertisement, post property advertisement and manage advertisements. User can view
property advertisements and explore all categories on home page GUI. User can also compare
different properties and give his bid for specific property, after approval bid user can make
payment and purchase property. There will a proper registration/login interface for Owner,
User and Administrator to access application.
2. Functional Requirements & Non Functional requirements
Functional Requirements:
System/Software requirements which specify functions that a system must be capable of
performing in correct way are known as functional requirements. Following are the
functional requirements of project.
Three types of users will be using this application.
Admin:
Admin should be able to create/remove/modify registered owners
Admin should be able to accept or reject any registration request submitted by the
property owners
Owner:
The registered Owner should be able to add properties through their account and those
properties should be visible to the users after the admin’s approval.
The property details should include
o Property Title
o Area Covered
o Location
o Bedrooms
o Stories
Owner can add any other parameters suitable for describing property specifications
The registered owner should be able to accept or reject bids made by the users and
should be able to ask for the down payment from the user to secure the bid.
User:
User should be able to view all the information available on the website
User should be able to search the for the properties different parameters (already
mentioned above)
User should be provided with the facility to compare different properties in the tabular
form.
Page 4 of 19
User should be able to bid and if the bid is accepted by the property owner, user
should be able to make the advance payment online as well. Bid and payment option
should be available to the registered users only
We can use any payment method Credit card/ PayPal etc
Non Functional Requirements:
Those requirements which are not specified by system but software will perform those how to
do tasks are referred as non-functional requirements. Following are the non-functional
requirements of project.
Operating system: System has capability to run on all widows’ versions, Windows XP,
Window 7 Linux or apple as well as mobile devices.
Maintainability and capacity: System volume to store user’s records and maintains it
performance of system must stand reliable.
Recoverability: System manages data, save data, recovers data very well.
System Security: System should be reliable or flexible for user to feel free about security
needs.
User Friendly interface: System Software design should simple and user friendly so user
can understand it and perform functions easily.
Usability: Usability of System must be easy so that User can use it without any difficulty.
Flexibility: System must be flexible so that it can easily accept all changes at low cost, time
and experience.
Reliability: The ability of a system to perform and maintain its functions in routine
circumstances, as well as hostile or unexpected circumstance
Performance: System should perform all of its functions excellently and effectively without
any inconvenience.
Scalability: System should be more scalable and allow management to add more
functionality.
3. Use Case Diagram:
Register
Page 5 of 19
Sign in
Add/Update/Delete User
Property Categories
Management
Owner Post property
Approve property
Admin
Update/Delete
property
View property
Search property
Compare property
User
Purchase Property
Make Payment
Sign Out
4. Usage Scenarios:
Use Case Title Register
Use Case ID UC-01
Page 6 of 19
Description The system will allow User to register and login to system
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of Register
Enter registration details
submit registration form
Post condition User/Owner has registered successfully
Authority User/Owner
Exceptions User already exists
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Sign in
Use Case ID UC-02
Description The system will allow registered user to login by providing user
name and password and Logged in User can logout from
application
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select the option of Sign in
Enter user name and password
Click submit button
Post condition User/Owner/Admin has signed in successfully
Authority User/Owner/Admin
Exceptions Wrong id or password
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Add/Update/Delete User
Page 7 of 19
Use Case ID UC-03
Description Admin will perform User Management
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select the link of Manage
Add new user
update above user
delete above user
Post condition Admin has performed User Management successfully
Authority Admin
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Categories Management
Use Case ID UC-04
Description Admin will manage in different categories
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select the option of Categories Management
add property categories
update above categories
delete above categories
Post condition Admin has managed different categories successfully
Authority Admin
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Page 8 of 19
Author MC170201198, MC170201911
Use Case Title Post property advertisement
Use Case ID UC-05
Description Owner will post property advertisement in categories
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of post property advertisement
Post property advertisement of Area covered by property
Post property advertisement of Location (by province or
city)
Post property advertisement of Price range
Post property advertisement of Number of bedrooms
Post property advertisement of Number of Stories
Post condition Owner has post property advertisement in categories successfully
Authority Owner
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Approve property advertisement
Use Case ID UC-06
Description Admin will Approve property advertisement in different categories
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select the option of Approve property advertisement
Check a property advertisement details
If property advertisement is according to terms and
condition then approve it
Post condition Admin has approved property advertisement successfully
Authority Admin
Exceptions N/A
Page 9 of 19
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Update/Delete property advertisement
Use Case ID UC-07
Description Owner and Admin can Update/Delete property advertisement
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of Update/Delete property advertisement
Update property advertisement
delete property advertisement
Post condition Owner and Admin has managed property advertisement
successfully
Authority Owner and Admin
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Use Case Title View property advertisement
Use Case ID UC-08
Description User, Owner and Admin can view property advertisement in
different categories
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of view property advertisement details
View property advertisement of Area covered by property
View property advertisement of Location (by province or
city)
View property advertisement of Price range
View property advertisement of Number of bedrooms
Page 10 of 19
View property advertisement of Number of Stories
Post condition User has viewed property advertisement successfully
Authority User
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Search property advertisement
Use Case ID UC-09
Description Registered User can visit the web pages and can search for
property advertisement through different filters.
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of search property advertisement
Search property advertisement of Area covered by property
Search property advertisement of Location (by province or
city)
Search property advertisement of Price range
Search property advertisement of Number of bedrooms
Search property advertisement of Number of Stories
Post condition User has searched property advertisement successfully
Authority User
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Compare property
Use Case ID UC-10
Page 11 of 19
Description Registered User can compare property
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of compare property advertisement
Select two properties and compare them
Post condition User has compared property successfully
Authority User
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Purchase property
Use Case ID UC-11
Description Registered User can purchase property
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of purchase property
Give bid
Upon approval of bid user can purchase property
Post condition User has purchased property successfully
Authority User
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Make Payment
Use Case ID UC-12
Page 12 of 19
Description Registered user can make payment for purchased property
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select option of make payment
Enter Card details
make payment for purchased property
Post condition User has made payment for purchased property successfully
Authority User
Exceptions N/A
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Use Case Title Sign Out
Use Case ID UC-13
Description The system will allow logged in user to logout from application
Pre condition Real Estate Management System Web Based Application should
running in web browser.
Action Select the option of Sign out
Post condition User/Owner/Admin has signed out successfully
Authority User/Owner/Admin
Exceptions Wrong id or password
Modification 1.0
History
Modification Date 21-05-2018
Author MC170201198, MC170201911
Page 13 of 19
5. Adopted Methodology:
The adopted ways of doing things for this project is vu process model. It is
combination of water-fall model and spiral model. This model is easy to understand and use.
Now first of all discuss water fall model.
Waterfall Model
Page 14 of 19
Requirement Analysis
This is the first phase of waterfall model which includes a meeting with the
customer to understand his requirements. It is very important to understand the
customer requirements and expectations so that the end product meets his
specifications. All the requirements related to system to be developed are analyze in
this place.
System Design
System Design helps in specifying hardware and system requirements and
also helps in defining overall system architecture.
Implementation
First of all designed the system in small units and implemented for testing its
functionality.
Testing
In this stage, both individual components and the integrated whole are
methodically verified to ensure that they are error free and fully meet the
requirements. All the units developed in the implementation phase are integrated into
a system after testing of each unit. Post integration the entire system is tested for any
faults and failures.
Deployment
Once the functional and non functional testing is done, the product is
deployed.
Maintenance
This is the final phase of the waterfall model, in which the completed software
product is handed over to the client after alpha, beta testing.
Spiral Model
Page 15 of 19
Spiral model is a combination of iterative development process model and sequential linear
development model. The spiral model has four phases like as
Identification:
The business requirements in the baseline spiral. This also includes
understanding the system requirements by continuous communication between the
customer and the system analyst. At the end of the spiral the product is deployed in
the identified market.
Design
It involves architectural design, logical design of modules, physical product
design and final design in the subsequent spirals.
Construct or Build
Construct phase refers to production of the actual software product at every
spiral.
These builds are sent to customer for feedback.
Evaluation and Risk Analysis:
Page 16 of 19
After testing the build, at the end of first iteration, the customer evaluates the
software and provides feedback.
Vu Process Model
This process model is combination of water fall and spiral model. This process model
maximizes the quality of system and reduces the risk and disadvantages.
Page 17 of 19
Reasons for Choosing:
VU process methodology is suitable for our project for following reasons:
It is of iterative nature.
It is a sequential model.
It provides better project vision and control over milestones.
VU process model is relatively simple and advanced but yet effective.
Our project is divided into different phases like gathering and analyzing requirements
phase, planning phase, analysis and design phase, development & final project report
phase, and final report/viva phase. Therefore it helps to implement effective progress
tracking due to these distinct development stages.
We complete each phase in sequence and submit it to our supervisor. Then he suggest
us some improvement in each phase if needed before starting the next accepted by our
Supervisor then we proceed to next phase. This reflects the phase. When the phase is
well-improved and well worked-out, and also nature of waterfall and spiral model.
5. Work Plan (Use MS Project to create Schedule/Work Plan)
Page 18 of 19
Page 19 of 19