Software Requirements

Specification
For

Web App for VIT Students to search

properties for rent around the University
Version 1.0 approved

Prepared by

Rutanshu Jhaveri(15BCE2016), Justin Joy(15BCE2021),

Aniruddho Dutt(15BCE0967)

VIT University

23rd August 2018

i
Table of Contents
Table of Contents ................................................................................................. 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 ........................................................................... 3
2.6 User Documentation ........................................................................................................ 3
2.7 Assumptions and Dependencies ....................................................................................... 3

3. External Interface Requirements ....................................................................3

3.1 User Interfaces................................................................................................................. 3
3.2 Software Interfaces .......................................................................................................... 3
3.3 Communications Interfaces.............................................................................................. 3

4. System Features ...............................................................................................4

4.1 System Feature 1 ............................................................................................................. 4
4.2 System Feature 2 ............................................................................................................ 4

5. Other Nonfunctional Requirements................................................................4

6. Other Requirements ........................................................................................5

ii
1. Introduction
1.1 Purpose

The aim of this project is to provide a better and much more efficient alternative to students who
would like to access a web or a mobile app for viewing properties in and around a university that can
be beneficial for likely tenants. It also aims later to build a recommendation system for students to
view any other properties that they are interested in.

1.2 Document Conventions

We have used Times New Roman format. Bold and subsection headings. Bold-faced text has been
used to emphasize sections and sub-section headings. Highlighting is to point out words in the
glossary and italicized text is used to label and recognize diagram

1.3 Intended Audience and Reading Suggestions

This staff, t document is to be read by the development team, the project managers, marketing
esters and documentation writers. hardware, company providing embedded operating system,
shareholders and distributors who markets the finished product, may review the document to
learn a bout the project and to understand the requirements. The SRS has been organized
approximately in order of increasing specificity. The developers and project managers need to
become intimately familiar with the SRS. Our stakeholders, company manufacturing associated.
This document is also intended for VIT University students, stockholders and other users.

1.4 Product Scope

This project would be able to influence the lives of students where they can view and access relevant
data at the tip of their fingers. Students from other universities could also adopt the same concept and
change the way in which this system works for different environments.

1.5 References

David Ingham, Mark Little, Steve Caughey, Santosh Shrivastava “W3Objects: Bringing Object-
Oriented Technology to the Web”, WWW4, PP2, 141

https://www.google.com/url?hl=enGB&q=https://googleweblight.com/i?u%3D
https://www.w3.org/Conferences/WWW4/Papers2/141/%26hl%3DenIN&source=gmail&ust=1532
776345578000&usg=AFQjCNF9iX7HtZ1tO3Er4bd502fIoT71kA

1|Page
2. Overall Description
2.1 Product Perspective
This product originated from the need to have a localized way to access rental properties for students
around the university. There are various websites and applications that cover rental properties
however, our application is a follow-on member and partially self-contained. We believe features
such as tenants asking for request-to-upload in the search of new tenants stands out and an intuitive
UI, which is familiar and minimalistic to students, would be attractive. In the future, an ecosystem
for students/tenants will be developed by introduction of moderated chat rooms, tenant details and
recommendation system for different properties making it self-contained.

2.2 Product Functions

Major functions of the product:
 Posting property for rent
 Request to Upload “tenant search” by existing tenants
 View Properties
 Filter Search for Properties
 Favorite Properties you like
 Payment for rent (May remain under construction)

2.3 User Classes and Characteristics

Most important use classes include:

1) Students – This user classes looks at specific customers that stay in and around the University.
The product functions allow people to view and filter search results and hence this class would
be most affected, especially students who are potential tenants.
2) Agents – This user class mainly looks at people who generally are in charge for the rent of
properties around. These include caretakers, proprietors, owners, or managers. The product
functions allows them to post a property for rent and allow tenants to search for other potential
tenants.
3) Tenants – This class indicates tenants who are staying at the properties and want to search for
new tenants or want to bond with their neighbors. Functions such as chat and request to upload
allows them to do this.

Not so important use class includes:

1) Faculty – This class either is important however not so much as many faculties already have
an accommodation for themselves at the hostel or provided by the university outside.

2.4 Operating Environment

The software will operate on every and any platform that consists of a web browser and as it develops
further, even on Android and iOS Mobile platforms

2|Page
2.5 Design and Implementation Constraints
Since this software is mainly Web Based, we do not believe there would be any physical constraints,
however since there are few systems which have old browsers then it would not be able to use the
power of Bootstrap 4. Policies of rent and brokers must also be taken in to account, as the website
should not be held of any wrong information posted by agents or tenants. In addition, each agent
should digitally sign an MOU so that he/she do not take advantage of the website in a malicious way.

2.6 User Documentation

For user documentation and information, please consult section 3: External Interface Requirements.

2.7 Assumptions and Dependencies

 We assume that the information posted by each agent is true and we take their word for what
details they have provided.
 We assume the tenants and agents have an open and clear-ended communication and both
work cooperatively in order for requests to be allocated.
 We depend on agents to be cooperative and incur the monetary charges imposed by the
website
 We depend on the routes to be protected by any form by unauthorized access controls. This
dependency lies on functioning of Node js and Express and our route controls.
 We depend on Passport js to authenticate users and provide with a robust system of user
management.

3. External Interface Requirements

3.1 User Interfaces
The user interface provides an easy access to the facilities offered by the web app. The color scheme
used will bring attention to detail and will bring the important aspects over to the forefront.
Bootstrap was used to create interactive and responsive buttons with dynamic layouts that change in
real time.

3.2 Software Interfaces

This web app is developed in HTML, CSS and JavaScript. Bootstrap framework is used for the front-
end layouts and dynamic constraints that will perfectly fit for every screen. MongoDB is used for the
back end as it provides robust and intuitive methods to store and manipulate date, CRUD operations
and create model schemas, which uses NoSQL.

3.3 Communications Interfaces

Bcrypt is a password hashing function designed by Niels Provos and David Mazières, based on
the Blowfish cipher, and presented at USENIX in 1999. Besides incorporating a salt to protect
against rainbow table attacks, Bcrypt is an adaptive function: over time, the iteration count can be

3|Page
increased to make it slower, so it remains resistant to brute-force search attacks even with increasing
computation power. Passport is authentication middleware for Node.js. Extremely flexible and
modular, Passport can be unobtrusively dropped in to any Express-based web application. A
comprehensive set of strategies support authentication using a username and
password, Facebook, Twitter, and more.

4. System Features
As a centralized portal for students to find housing and sharing accommodations, the web app
provides a host of features.

4.1 Search for Housing

Students can search for different types of properties and filter and sort it based on their personal
preference, giving a more detailed and descriptive searching feature

4.2 Put up Space for Rent

Owners or property owners can sign up on the website, put their properties on for rent, and specify
the price and the provided amenities.

5. Other Nonfunctional Requirements

Security
 Login / Access levels
 Create, Read, Update, and Delete (CRUD) levels.
 Access permissions for application data may only be changed by the system’s data
administrator
 Password requirements – length, special characters, expiry, recycling policies, 2FA
 Inactivity timeouts – durations, actions, traceability
 System data backed up every x hours and copies stored in a secure off-site location
 Encryption (data in flight and at rest) – All external communications between the
system’s data server and clients must be encrypted
 Data Classification / System Accreditation: All Data must be protectively marked
and stored / protected.

Capacity
 Throughput – how many transactions at peak time does the system need to be
able to handle.
 Storage – (memory/disk) – volume of data the system will page / persist at run time
to disk.
 Year-on-year growth requirements (users, processing & storage).

4|Page
 Performance
 Response times – application loading, browser refresh times, etc.
 Processing times – functions, calculations, imports, exports.
 Query and Reporting times – initial loads and subsequent loads, ETL times.

Availability
 Hours of operation.
 Holidays, maintenance times, etc.
 Locations of operation.

Reliability
 The ability of a system to perform its required functions under stated conditions for
a specific period.

Integrity
 Application Integrity.
 Data integrity – referential integrity in database tables and interfaces.
 Information Integrity – during transformation.

Maintainability
 Conformance to Enterprise Architecture standards.
 Conformance to Technical design standards.
 Conformance to coding standards.
 Conformance to best practices.

Usability
 User Standards, i.e., the look and feel of the web site.
 Internationalization / localization requirements – languages, spellings, keyboards
and others.

6. Other Requirements
Software Packages required would be the following:-
 Node Js
 Express Js
 HTML and CSS
 Bootstrap
 MongoDB
 Passport Library for User Management
 Other Node Packages such Multer, bcrypt and others.

5|Page