Introduction

As things are going globally online the race to get availability increase. It’s especially helpful
for the people who want to rent a place and are having a difficult time finding a place and
also for students who are far from home for education and want to rent a place to stay without
the hassle of going door to door.

Scope
The Rental Management System is designed to facilitate in the problem of renting a place to
stay. Rental businesses can benefit a lot because finding a renter is made easy. The landlord
can benefit by renting his/her place with ease and find a renter and the person who us renting
the place can find the place they want to stay without the grind.

Functional Requirements
Following is the functional requirement of RMS:
1. Manager can get a list of landlords, registered renters, and properties.
2. Manager can request a summary by clicking the “Create Summary” button.
3. Sign up as a registered renter or a landlord.
4. Manager can change the state of property.
5. Landlord can view property, view emails, and add new properties.
6. “Add property” button will be in a second interface which allows the user to input the
necessary information of the place.
7. Renter can browse the available properties.
8. Renters can filter out houses based on specific specifications by click the “filter”
button.
9. Registered Renters have the option to email the landlord.

Non-functional Requirements
Following are the non-functional requirements of RMS:
1. Each page must load within 2 seconds.
2. Market feasibility should be maintained.
3. Frequency of failure must be reduced to a minimal to expect a regular flow without
interruption.
4. Start-up time should be minimal.
5. Recover-ability of the system from shut-down failure will be reduced to a minimal.
 FURPS+
Functionality:
Functionality requirements may include:
 Request a summary.
 View property and view emails.
 Run on Windows and JAVA.

Usability:
Usability requirements may include:
 Human factors.
 Help and Documentation will be provided with the software.
 Interface will maintain consistency.

Reliability:
Reliability includes aspects such as:
 Frequency of failure must be reduced to a minimal to expect a regular flow
without interruption.
 The system availability should be all the time.
 Recover-ability of the system from shut-down failure will be reduced to a
minimal.

Performance:
Performance involves things such as:
 System response time should be 2 seconds.
 Start-up time should be minimal.
 Availability should be all the time.
 The resource usage should not affect the system performance.

Supportability:
Specify number of other requirements such as:
 System should adapt hardware changes.
 Maintaining the software should be easy for the consumer.
 System compatibility should be flawless with windows OS.
 The configuration of the system should be easy and understandable.
 Scalability of the project.
 Constraints
Design constraints:
The database design for this system is constricted to SQL and the GUI theme should be
consistent with the software theme.
Implementation constraints:
The language used for coding is JAVA and IDE used is NetBeans on which it is implemented
on.

Interface constraints:
There are no interface constraints because the system is not interacting any external modules
or items.
Physical constraints:
The hardware of the system is restricted up until there is no JAVA or NetBeans in the PC, so
the requirement would be of 8GB RAM and 256GB SSD.