1.

INTRODUCTION
Housing plays a critical part in personal fulfilment, with important economic, social,
cultural, and individual ramifications. A secure home is one of the most essential indications
of housing advancement, and it plays a key part in restoring monetary development in any
country. In recent years, the real estate industry has grown significantly. With the increasing
demand for rental homes, an internet platform that makes the process of discovering and
renting a house convenient, quick, and dependable for both tenants and landlords has become
vital. There is a scarcity of inexpensive housing in many places, making it difficult for people
to locate a decent place to live. Currently, the process of finding and renting a house is time-
consuming, exhausting, and labour-intensive. To discover a suitable property, tenants
frequently have to rely on various sources, such as classified advertisements, agents, or word
of mouth. Landlords, on the other hand, confront challenges in reaching out to potential renters
and managing the leasing process.
The goal of this project is to provide an online platform that allows people to search
for, find, and rent houses, as well as landlords to advertise and manage their properties all in
one spot. This project would be a fully functional and user-friendly house rental service
website that tenants and landlords could use to search and rent residences efficiently and
conveniently. It attempts to give tenants access to a wider pool of available houses, making it
easier for them to locate a place to live and landlords to manage their properties more
efficiently. They can list their properties and contact with tenants using the portal. They will
also be able to rate and review tenants based on their experience with them. This will give
other owners information about the tenant weather they are troublemaker or not. It also seeks
to be honest and dependable by giving thorough information about properties, including
reviews and ratings, as well as identity information for both tenants and landlords, in order to
foster confidence between tenants and landlords. Renters save time and money by searching
for and booking houses online, while landlords save money on advertising and property
management. This project also attempts to promote the homes to the relevant audience,
increasing the possibilities of landlords finding quality tenants and tenants finding the suitable
spot.

1
1.1. General Overview of the Problem
The main reason for developing the project is that the traditional process of finding
and renting a house is time-consuming and requires a lot of effort. Both landlords and tenants
find difficulty in finding potential quality tenants and proper house to rent due lack of online
platform to connect. The existing platforms are not secure and are unreliable. This project will
help people to find and rent their desired rooms in a easy way.

1.2. Aim and Objectives

• To create a user-friendly platform that will connect landlords and renters in one place.
• To provide a reliable and safe platform where renters can search for and rent houses as
well as landlords can advertise their rental properties.
1.3. Feasibility Study
Feasibility study for this project is:

• Technical Feasibility: Developing a house rental website requires technical expertise in

web development, database management, and security. The necessary technical resources
are readily available, and the project can be completed within a reasonable time frame.
• Financial Feasibility: The project's financial feasibility depends on expenses, such as
website hosting, maintenance. The Project can be made with a low initial investment and
has high potential for revenue generation, making it financially feasible.
• Operational Feasibility: The required system is very simple and easy to operate. The
project has easy to use and user-friendly interface which will make the booking process
convenient making this project operationally feasible.

2
1.4. Literature Study
Existing platform Description Limitations
Easy Shelter It is a real-estate-based venture Lack of available property list
which makes easier to find an
Facebook Page ideal premises for users.

Utsav Rentz It is a property management. Lack of available property list

Instagram page and house rental provider

service.

99 Acers.com A real-estate management site. Lack of available properties in

Sikkim.

Magic Bricks.com A website that provides a No available list of properties

common platform for property in Sikkim.
buyers & sellers to locate
properties of interest in India

Table 1: Literature Survey

1.5. Problem Definition
These are the problem definition:

• There is a shortage of affordable housing, making it difficult for people to find a suitable
place to live.
• The traditional process of finding and renting a house is time-consuming and requires a
lot of effort.
• Both landlords and tenants find difficulty in finding potential quality tenants and proper
house to rent as there is a lack of online platform to connect them.
• For landlords it is a time-consuming and challenging job to screen tenants. They have to
evaluate the tenants' credit history, employment status, and rental history to ensure they
are reliable and will pay rent on time.
• There is also a lack of reliability and transparency which causes distrust between landlords
and tenants.

3
1.6. Analysis of the Problem
The main reason for the development of this project is the following problems:
• Limited property inventory: There is a problem of low number of availabilities of suitable
rental property. This is due to a smaller number of property owner listing their properties
for rent. This creates a problem of a smaller number of tenants as buildings are seen to be
empty. Also, for tenants they have very limited number of options to choose a suitable
property for them. This is the reason why although there are many rooms available and
there are many renters there are still many unrented properties.

• Inefficient Search and Filtering Mechanism: There is no mechanism for search and
filtering properties making it difficult for renters to search for properties based on their
desired criteria like price, no of rooms, location, etc.

• Lack of Review and Rating System: Lack of a proper rating and review system hinders
user ability to decide about a potential booking. Rating and reviews provide insights from
pervious user experience helping user determine the quality of a rental property or the
tenant. Lack of such facility leaves limited choices for the users to make choices.
1.7. Solution Strategy
The proposed solution strategy
• Login/register Module for Tenants and Owner with necessary credentials and government
Id Aadhaar Card
• Search bar to search for properties based on various criteria such as location and price.
• Tenant module to view property, rate and review their experience with the landlord and
the rental property and book it. This feedback system can help build trust and provide
transparency to the rental process, as prospective tenants can use the feedback to make
informed decisions about renting a property.
• Landlord module to list properties, edit and delete them and see messages of tenets. They
will be able to view tenant profile and accept or reject their booking request. They will be
able to rate and review tenant based on their rental experience. They will also be able to
view tenants’ profile with their rating and reviews and police verification status.
• A messaging module will be included, allowing landlords and tenants to communicate
with each other directly. This will enable them to discuss rental terms, negotiate rent, and
clarify any questions or concerns.

4
• Police module to be used by police authorities to fetch a verification form and verify the
tenants. After verification police will provide the verification details to owner.
1.Tenant Module: The tenant will register with credentials like Name, Address, Email,
Contact no, occupation and Aadhaar card. The email, contact no and Aadhaar no should be
unique only then the tenant will be registered. After that tenant will be able to login with his
credentials. The tenant will be able to see his profile and update it. They can search and view
property, message owner, rate and review property and book property. Also, after booking
there will be a form for police verification which can be downloaded and submitted. The tenant
will also be able to see their ratings and reviews.

Fig1: Tenant module

2.Owner Module: The owner Module will allow Landlords to Register with credentials and
Id Proof Aadhaar card. After that owner will be able to login in. Owners can view their profiles
and update their information. They can list their property, edit, and delete them. They also can
view tenants’ messages, view booking request, and see view booked properties. They can view
tenants’ profile and rate and review them based on their tenancy experience. They also can
view rating and review given by other owners. A police verification from can be downloaded
from the booked property section and can be uploaded. They will also be able to view the
tenant verification by police

5
 Fig 2: Owner Module

3.Police Module: Police authorities can login and fetch the information of the tenant and verify
them. After verification they will send the verification details to the owner.

Fig 3: Police module

6
1.8. SRS
SRS document or Software Requirement Specification is a technical specification of
requirements for the software. The aim of software requirements definition is to specify the
technical requirements of the software completely and consistently in a concise and
unambiguous manner.
1.8.1. Functional Requirements
R1: Registration Process
Description: This requires the user to provide their valid details full name, email, phone no,
password, address, Occupation, Aadhaar No and Aadhaar card to register themselves.
R1.1: Registration for Tenants
Input: Full name, email, Phone no, password, address, occupation, Aadhaar No, Photo od
Aadhaar card.
Output: Tenant will be redirected to the Tenant Login Page
Processing: The details will be validated and if no duplicate entries are found and data is valid
then it will be entered into the database.
R1.2: Registration for Owners
Input:Full name, email, phone no, address, Aadhaar card.
Output: Owner will be redirected to the Owner Login Page.
Processing: The details will be validated and if no duplicate entries are found and data is valid
then it will be entered into the database.
R2. Login Process
Description: This requires the user to provide his valid login email id and password in order
to enter into his account.
R2.1: Login for tenants
Input: email id and password
Output: Tenant will be redirected to the homepage of his account.
Processing: The email id and the password entered by the user are verified against the
database entry. If found valid then the user will be redirected to his profile else an error
message will be generated “Incorrect email/password or not registered. click here to register”.
R2.2: Login for Owners
Input: email id and password
Output: Owner will be redirected to the homepage of his account.

7
Processing: The email id and the password entered by the user are verified against the
database entry. If found valid then the user will be redirected to his profile else an error
message will be generated “Incorrect email/password or not registered. click here to register”.
R2.3: Login for Police.
Input: email id and password
Output: Police will be redirected to the homepage of their account.
Processing: The email id and the password entered by the user are verified against the
database entry. If found valid then the user will be redirected to his profile else an error
message will be generated “Incorrect email/password”.
R3: Tenant Module
Description: Tenant can view their profile and update it. They can search for properties and
view properties to book, send message to owner, rate, and review property. After booking they
can download police verification form and upload it.
R3.1: Tenant profile
Input: Select the profile from My profile dropdown menu.
Output: A screen containing a profile card will be displayed containing the user’s
information.
Processing: The data will be retrieved from the database and will be displayed.
R3.2: Tenant Update
Input: press the update button from below the tenant profile.
Output: A card is displayed containing tenant details to update.
Processing: The updated information will be entered into the database.
R3.3: Tenant search
Input: Enter the desired criteria in the search bar and press the search button (Location, price,
no of rooms)
Output: A list of available properties will be displayed based on the searched criteria.
Processing: The search input is verified against the database entry and if matching results are
found it is displayed or else a massage is displayed: “No results found”.
R3.4: Book property
Input: click on the book property button(property_id,tenant_id)
Output: The button will change into Booking pending and will be disabled. A message will
be displayed “You have booked this property. Please wait for the owner to confirm your
booking”.
Processing: The details of the tenant and property will be sent to a database.
8
R3.5: Send Message
Input: Click on the send message button.(tenant_id)
Output: A Chat page will appear. Where user can type in the message and read messages
from the owner.
Processing: The message will be stored in the database. And the stored message will be
displayed here.
R3.6: Rate and Review.
Input: Click on the leave a review button (property_id)
Output: A review bar and rating stars will appear.
Processing: The rating and review will be stored in the database.
R3.7: Police verification:
Input: Click on the download form button and click on the upload form button(tenant_id)
Output: A police verification form will be downloaded which can be downloaded and will
be uploaded from there.
Processing: A form will be retrieved from the database and it will be uploaded in the database
with message “File uploaded successfully”.
R4: Owner Module
Description: The Owner will be able to add their properties, edit and delete them. They will
be able to see messages from tenants and see booking requests and accept or reject it. They
will also be able to view the tenant and see their ratings and reviews. Once they property is
booked, they will be able to download the police verification form and submit it also they will
be able to rate the tenants form there and see their police verification.
R4.1: Add property.
Input: Click on the add property button and fill in details of the property(district,
address,rent,city,no of rooms,contact no,photos, full description, address)
Output: A property will be added, and it can be seen form the owner profile with a message
“Property added successfully”.
Processing: The property details will be validated and added to the database.
R4.2 Edit/Delete Property.
Input: Click on update property and select edit or delete options.(property_id)
Output: The edit button will open a new window to edit property details and delete button
will delete the selected property.

9
Processing: The new data entered will replace the old data in the database with message
“Property updated successfully” else “failed to update property”. If delete is pressed, then data
will be removed from the database with message “property removed successfully”.

R4.3: See Messages

Input: Click on the message button.(owner_id)
Output: A Chat page will appear. Where user can type in the message and read messages
from the tenant.
Processing: The message will be stored in the database. And the stored message will be
displayed here.
R4.4: Booking request.
Input: click on the view booking request button(property_id)
Output: All the booking requests from the tenant can be seen along with the accept and reject
button.
Processing: If the accept button is clicked then the booking data will be inserted into the
database. And a message “You approved this request” will be displayed. If reject button id
pressed then the request will be cancelled and a message “ You rejected this request” will be
displayed.
R4.5: View tenant profile
Input: Click on the view button in the view booking request section.
Output: The tenant profile will appear along with the tenants’ details and their rating and
reviews.
Processing: The tenants’ details and his rating and reviews will be retrieved from the
database. After that the rating will be calculated to find the average rating and ten displayed.
If no rating or reviews are found, then a message “No rating available” will be displayed.
R4.6: View booked property.
Input: Click on the view booked property button.
Output: A list of booked properties will be displayed, and they will have view tenant profile,
download form, and upload form buttons.
Processing: The data will be retrieved from the database and will be displayed here.
R4.7: Rate and Review Tenants
Input: Click on the view button in the view booked property section.(rating, review and
tenant_id)

10
Output: The tenant profile with tenant details along with a rating and review section and a
police verification section is displayed.
Processing: The rating and review data will be stored in the database.
R4.8: Police verification
Input: The download form button is clicked, and upload button is clicked.
(owner_id,tenant_id, property_id)
Output: A form will be downloaded which can be filled and uploaded to the database.
In the view section the tenant profile is showed in verified and a police card is displayed with
police Verification details.
Processing: A download from is retrieved from the database associated with that tenant and
it will be submitted to the database with a message “File submitted successfully”. After that
the police verification details will be displayed in the view section.
R5: Police Module
Description: The Police will be able to fetch the booked property information and verify the
tenants and submit the results to owners.
R5.1: View booked property information.
Input: click the view booked property button
Output: A list of booked properties will be displayed.
Processing: The list of booked properties will be fetched from the database and displayed.
R5.2: Download verification from
Input: Click on the download button in each row to download the respective verification form.
Output: A police verification form will be downloaded.
Processing: The form will be fetched from the database associated with the tenant, owner and
property and will be downloaded.
R5.3: Verify tenant.
Input: Click on the verify button in each row to verify respective tenants.(tenant_id)
Output: A verification window will appear with the tenants’ details and a form with
verification questions.
Processing: When this form is submitted it will enter the data into a database.

1.8.2. Non-Functional Requirements

• Response Time: Response time is the expected time for the completion of an operation
under specified circumstances. To function the software efficiently, the response time

11
 should be low. The response time in this application is low. The lesser the response time,
the more the traffic. The Response to any request should be reasonably fast.
• Processing Time: The main Processing Time involved will be loading the data retrieve
from the database and displaying it in web pages. Static pages will be displayed quicker
than the dynamic pages where the data needs to be retrieved from the database.
• Stress Handling: The software that is developed is competent to be worked out in various
circumstances. Certain situation may arise when large numbers of data entries are required
to be done. Still, the software will function smoothly and be able to handle out such
overwork easily.
• User Friendliness: This web application has been developed keeping in mind the user
friendliness. Any person with good knowledge over the internet and computers can be the
user of the product.
• Accuracy: It provides an accuracy of keeping he records that cannot be done manually.
This is because, if incorrect data are given as input, the expected results will not appear.
• Reliability and Efficiency: The software is found to be very reliable and consistently
good to use. It is expected to produce desired and efficient outputs.
• Throughput: Throughput is the expected number of operations that can be performed in
a unit of time. Throughput should be maximum in order to have an efficient output.

12
2. PROJECT PLAN
2.1. Hardware and Software Requirements
Specifications Hardware Requirements:

• Processor: Dual core Processor or above

• RAM: 4GB or above
• Storage: 10GB or Above

Software Requirements:

• Frontend: HTML, CSS

• Backend: PHP, MySQL
• IDE: Visual Studio Code
• Sever: Xampp server

2.2. Team Structure

2.3. Software Development Life Cycle

Iterative waterfall model: In the Iterative Waterfall Model, the development process is
divided into a series of phases, similar to the Waterfall Model. However, instead of completing
each phase in a linear fashion before moving on to the next one, the model allows for feedback
and iteration between phases.

The advantages of Iterative Waterfall Model are:

13
• The iterative nature of this model allows for changes to be made at any point in the
development process, which can improve the final product and help respond to changing
requirements or unexpected challenges.
• By breaking the development process into smaller, iterative phases, this model can often
lead to faster delivery of the final product.
• The iterative approach can help identify and address problems earlier in the development
process, reducing the overall cost of the project.

Fig 5: Iterative waterfall model

14
 2.4 Gantt-Chart
Activity 24thJan 9thFeb 25thFeb 12thMar 28thMar 13thApril 29thApril 15thMay
9th Feb 25thFeb 12thMar 28thMar 13thApril 29thApril 15thMay 27thMay

Planning and
Requirement Analysis

Feasibility Study

Literature Review

Problem definition

Design

Implementation

Testing

Documentation

Fig 6: Gantt-Chart

15
3. DESIGN STRATEGY FOR THE SOLUTION
3.1 Data Flow Diagram

Fig 7: Data Flow Diagram (level 0)

16
 Fig 8: Data Flow Diagram (level 1)
user_details fullname+ email+phoneno+password+address+occupation+aadhaarno+tenant_id+owner_id

login_details email+password

property_details district+city+address+contactno+price+no of rooms+fullsedcription+photos+location+property_id

Booking_details property_id+tenant_id

Table 2: Data Dictionary for DFD (level1)

17
3.2 Entity Relationship Diagram

Fig 10: Entity Relationship Diagram

18
4. DETAILED TEST PLAN
This being a web application project, we need to consider various dimensions of
quality. It is incorporated into a web application as a consequence of good design.
The whole test plan is based on reviewing and examining the following dimensions:-
1.Content: this includes evaluation at both syntactic as well as semantic level. At the syntactic
level, spelling, punctuation and grammar are assessed for hard-coded tests appearing on the
client screen of the website. At the semantic level, correctness of information presented,
consistency and lack of ambiguity are all assessed.
1. Function: all the functions specified in the requirements specification document will be
tested. The errors in main function that can confuse and disappoint the client needs to be
handled with appropriate error messages. The three levels of testing were done i.e. unit
testing, system testing and integration testing.
2. Usability: this is tested to ensure that each category of user is supported by the interface
and can learn and apply all require navigation syntax and semantics.
3. Navigability: this is tested to ensure that all navigation syntax and semantics are exercised
to uncover any navigation errors (e.g. dead links, improper links etc). Every link on each
pages and frames were tested.
4. Performance: performance is tested under a variety of operation conditions, configuration
and loading to ensure that the system is responsive to user interaction and handles extreme
loading without unacceptable operational degradation.
This document describes the testing plan of the web application. Software testing
is a critical element of software quality assurance and represents the ultimate review of
specification, design and coding. The application will be successful with the acceptance of
the testing. All the major testing activities are specified here.

4.1 Test Units and Methods:

The testing process is divided basically into three major components i.e. unit testing,
integration testing and the system testing. A test case is a document that describes an input,
action or event and an expected response to determine if a feature of the application is working
properly. For proper functioning of the application these three levels of testing are necessary.
The basic units to be tested are:

19
4.1.1 Unit Testing:
In Unit Testing, we are required to identify the test units and test them separately after
the development of each module. The units to be tested are as follows:
• Unit 1-Tenant Module
• Unit 2-Owner Module
• Unit 3-Police Module

4.1.2 Integration Testing:

In Integration Testing, we are required to integrate the testing units from the unit-
testing phase and then test then as a whole unit. The testing to be done is Unit 1 and Unit 2
and Unit 3 together after integration.
4.1.3 System Testing:
In System testing we need to install the application on the server machine and then access it
from the other machines connected via intranet.
4.1.4 Features to be Tested:
All the functional features specified in the requirement documents will be tested. Functional
features are like adding property, booking property, editing and deleting property, rating and
reviewing tenants and properties, messaging, downloading and uploading forms and the
flexibility of the users will be tested. As software is a web application, system configuration
for the server as well as for the client plays an important role. Therefore, it should be properly
tested with the requirements of the application so that the generality of the application is
maintained. Not only this, even the platform on which the website will be hosted needs to be
checked to compensate with the minimum requirements of this web application.
4.2 Approach for Testing:
As the system is hierarchy of modules, and the development of the system has been
done in a bottom-up manner. This will facilitate integration testing and finally overall system
testing. For unit testing, structural testing on the branch coverage criterion will be used.
System Testing will be largely functional in nature. The focus is on invalid and valid cases,
boundary values and special cases. Any special observations during the testing will be noted
down and the cause of that will be further determined.
4.3 Test Deliveries:
The following documents are required during testing besides test plan:
• Test case specifications for unit testing.
• Test case specifications for integration testing.
20
 • Test report for system testing.
The test case specifications for unit testing, test case specification for integration
testing will be reviewed before system testing commences.
4.4 Schedules for Testing:
The entire Testing will start from March and will be finished within 4th week of May. The
schedule is consistent with overall schedule of the whole project.
4.5 Test Case Specifications:
4.5.1 For System Testing:
Here we specify all test cases that are used for system testing. First, the different
conditions that need to be tested, along with the test cases used for testing those conditions
and the expected outputs are given. The test cases have been selected using functional
approach. The goal is to test the different functional requirement, as specified in the
requirement document. Test cases have been selected for both valid and invalid inputs.

Sl. Test Cases Condition being Expected Output

no. checked

1. Concurrency Control Whether more than one Positive

client
can access the site from
the server.

Table 2: Test Case for System Testing

4.5.2 For Unit Testing:

A)Testing for Unit 1:

Sl. Test Cases Condition being checked Expected Output

no.

1. Registration for Tenant Weather entered data Print message

valid and unique and proceed.

2. Login for Tenant Weather entered data is Print message

authentic successful.

3. Search property Weather searched value Display searched value

is displayed or not

21
4. Book property Weather Booking request Print message
is send or not Successful.

5. Message Whether the message is Print message

sent or not Successful.

6. Download Form Weather the form is File Downloaded

downloaded or not Successfully

7. Upload form Weather the form is File Uploaded

Uploaded or not Successfully

8. Rate and Review Weather the ratings are Print message

submitted or not Successful.

Table 3: Test Case for Unit 1

B)Testing for Unit 2:

Sl. Test Cases Condition being checked Expected Output

no.

1. Registration for Owner Weather the entered data Print message and
is valid and unique proceed.

2. Login for Owner Whether the entered data Print message and
is authentic or not proceed.

3. Add property Weather entered data is Add property to

added in database or not database

4. Accept booking request Weather request is Add property to

accepted bookings and print
successful message.

5. Reject booking request Weather request is Print message

rejected Successful

6. Rate tenant profile Weather Rating is being Print message

submitted or not Successful

22
 7. Download form Weather the form is File Downloaded
downloaded or not Successfully

8. Upload form Weather the form is File Uploaded

Uploaded or not Successfully

Table 4: Test Case for Unit 2

C)Testing for Unit 3:

Sl. Test Cases Condition being checked Expected Output

no.

1. Login for Police Whether the entered data Print message and
is authentic or not proceed.

2. Download form Weather the form is File Downloaded

downloaded or not Successfully

4. Verify tenants Weather the uploaded Verify tenant and print

data is entered or not successful message

Table 5: Test Case for Unit 3

4.5.3 For Integration Testing:

Sl. Test Cases Condition being checked Expected Output

no.

1. All modules are tested Whether the modules are Positive

simultaneously. working in coordination
with one another.

Table 6: Test Case for Integration Testing

23
5. IMPLEMENTATION DETAILS
5.1. Pseudo Codes:
Following are the pseudo codes of some of the important algorithms used in developing the
application:
5.1.1. Pseudo Code for Tenant Register

24
5.1.2. Pseudo Code for Tenant login

25
5.1.3 Pseudo code for Owner Register

26
5.1.5 Pseudo code for Property search

27
5.1.6 Pseudo code for sending booking property request.

28
5.1.7 Pseudo code for accepting and rejecting booking request.

29
6. RESULT AND DISCUSSIONS
6.1 Snapshots
Following are the snapshots from the project.
6.1.1. Homepage: This is the Homepage of the website. From the navbar user can login,
register, contact and see about us of the website.

Fig 10: Homepage

6.1.2. Login Page: This the Login page the user can select between Tenant, Owner and
Police Login from here.

Fig 11: Login Page

30
6.1.3. Register Page: The user can Register as Tenant or Owner From here.

Fig 12: Register page

6.1.4. Tenant Register Page: From here The Tenant is able to Register Themselves by
entering their valid details (Full Name, Email, Password, Confirm Password, Phone No,
Address, Occupation, Aadhaar No, Upload Aadhaar card)

Fig 13: Tenant Register page

31
6.1.5. Owner Register page: Here the owner will enter their valid details (Full Name,
Email, Password, Confirm Password, Phone no, Address, Upload Aaddhaar card) To register
themselves.

Fig 14: Owner Register Page

6.1.6. Tenant Login page: The Tenant will enter their email and password to login

Fig 15: Tenant Login Page

32
6.1.7. Tenant Profile: This is the Tenant profile with all the Tenant details. From here the
tenant can update their details.

Fig 16: Tenant Profile

6.1.8. Tenant Ratings and review: Here the Tenant can see their Ratings and Reviews

Fig 17: Tenant View Ratings and Reviews

33
 6.1.9. Owner Profile: This the Owner profile where they can see their profile details.

Fig 18: Owner Profile

6.1.10. Add Property: The Owner can add property from here by fill in the detatils Of
Distect, City, Address, Contactno, Property type, Estimated Price, total no of rooms, Full
Description, Photos, Location.

Fig 19: Add property.

34
6.1.11. View Propety Page: The Tenant will be able to view the uploaded property here.
They can book property and send message to owner.

Fig 20: View property page

6.1.12. Send Booking Request: After clicking the Book property button the button will
change into Booking Pending and a booking request will be send. A message will be
diaplayed” Thank you fro booking this property,Please wait for woner to accept your
booking request.”

Fig 21: send Booking request

35
6.1.13: View Property after booking: This will appear the booking request is accepted.
Here They can download and upload a police verification form here.

Fig 22: View property after booking.

6.1.14: View booking request: Here the owner can see all the booking requests from
renters. They can view the tenant profile and reject or accept the request.

Fig 23: View booking request

36
6.1.15: View Tenant Rating and Reviews: Here the owner can see the Tenants Rating and
Reviews provided by other Owners.

Fig 24: View tenant Rating and Reviews

6.1.16: View Booked property:The owner will be ale to see list of all the booked
properties . They will be able to download and upload a police verification from. They will
be able to view Tenant profile here to rate them.

Fig 25: View Booked property.

37
6.1.17. View Police verification and rate tenants: Owner will be able to see the Police
verification details of the Tenant from here and Rate and review them based on their rental
experience.

Fig 26: View police verification and rate tenants.

6.1.18. Police view booked property: The police can view the list of booke properties.
They can Download the police verification from that is uploaded by the owner. They can
verify the tenants from here.

Fig 27: Police view booked property.

38
6.1.19. Police verification: The Police can see the Tenants details from here and verify
them by filling in the details of the from. The details will be send to the Owner.

Fig 28: Police verification.

6.1.20. Tenant Send Message: The Tenant can send Message to the owner here and
receive messages from owner.

Fig 29: Tenant Send message.

39
6.1.21. Owner receive messages: The owner can send message to tenants and receive
messages from tenants.

Fig 30: Owner receive messages.

40
7. SUMMARY AND CONCLUSIONS
7.1. Summary of Achievement
By integrating essential modules to serve the interests of tenants, property owners, and
authorised workers, the house rental website project successfully met its objectives. The
website gives users an easy-to-use interface for finding, viewing, and rating properties.
Property owners profit from simple listing management, which makes effective property
management possible. By giving authorised staff access to tenant information and verification
capabilities, the integration of a police module improves safety. User experience and
functionality were given considerable consideration throughout the whole development
process. While the rating and review tool allows tenants to share their experiences and provide
insightful feedback, the tenant module simplifies the process of finding, viewing, and
reserving properties. Using the Owner module, landlords can advertise their properties,
maintain listings, and interact with prospective tenants. For the purpose of screening, they can
also examine tenant profiles and Rate and Review them. By improving tenant verification, the
Police module ensures neighbourhood safety. Overall, the project delivers a useful and
practical rental platform and successfully satisfies the criteria.
7.2. Difficulties encountered during the project.
The seamless integration of numerous components was one of the challenges
encountered during the project. The Tenant, Owner, and Police modules, for example, each
have their own set of functionality and information needs. The technical difficulty was
ensuring smooth data interchange and connectivity between these units.

7.3. Limitation of the project

Despite the project's successes and effective implementation, there are still some
limitations that must be acknowledged. First off, depending too heavily on police verification
of tenant information might cause delays and raise privacy issues. The jurisdiction and
cooperation of law enforcement authorities may have an impact on the process's efficiency
and accuracy. The platform's success also depends on the active engagement of property
owners and their dedication to maintaining listings. An inadequate user experience might be
brought on by inaccurate or out-of-date property information. Finally, even though an effort
was made to design a user-friendly interface, certain users, especially those with minimal
technological expertise, may still have usability problems or have trouble navigating the
platform.

41
7.4. Future Scope of the Project
As for the future scope of this project, more features can be added to this project in
this project:
• Advanced identity card reading techniques like OCR for better validation of the user data
and prevent duplicate registration can be implemented.
• Another module for management of the tenant and property can be added for the
convenience of the owners to maintain their rental transactions like Rental agreements,
room management records, and rent payment records. Additionally, a payment gateway
can also be integrated to setup payment from there itself.
• If the website manages to attract a significant number of users, Mobile app can be
developed for the on the go use of this application.
7.5. Conclusion
In conclusion, the house rental website project met its goals by incorporating critical
modules to meet the demands of tenants, property owners, and authorised workers. The site
provides tenants with an easy-to-use interface for searching, viewing, booking, and rating
properties. Property owners can easily add, modify, and remove listings, resulting in more
efficient property management. The addition of a Police module allows authorised employees
to access tenant information and verify it, hence improving safety and security measures.
The user experience and functionality were carefully considered throughout the development
process.
The Tenant module provides users with an easy-to-use interface for searching for available
properties, seeing property details, and making bookings. Furthermore, the option to rate and
review properties enabled tenants to share their experiences while also providing useful
feedback to property owners and future tenants.

Property owners can list their homes, manage their listings by updating or deleting them, and
view messages from potential tenants thanks to the owner module. Additionally, landlords
have access to tenant profiles, can approve or decline booking requests, and can evaluate and
review renters based on their experiences renting from them. Landlords may choose
dependable tenants for their properties with the help of the ability to check tenant profiles,
which also include ratings, reviews, and the status of any police verification.

42
The police module is an essential part of the tenant verification process. It enables law
enforcement officials to get a verification form and interview potential tenants, safeguarding
the neighbourhood’s safety and security. Once verified, the police give the property owner
the verification information, adding another layer of assurance and trust.

These modules are integrated into the online platform to produce a complete and user-friendly
house rental solution that caters to the diverse needs and demands of both tenants and
landlords. The platform's objectives include streamlining the renting process, increasing
transparency, fostering trust, and eventually offering people looking to discover and rent
houses a practical and effective alternative.

43
REFERENCES AND BIBLIOGRAPHY
[1]"Easy Shelter Facebook Page," Facebook. [Online]. Available:
https://www.facebook.com/easyshelter/.

[2] “Quick Rentz Instagram Page,” Instagram. [Online]. Available:

https://www.instagram.com/rentz_official/.

[2]"99acres.com," [Online]. Available: https://www.99acres.com/.

[4]"Magicbricks.com," [Online]. Available: https://www.magicbricks.com/.

[5] W3Schools. "PHP Tutorial." Available :https://www.w3schools.com/php/default.asp.

[6] Sikkim Police. “Adverse form.”Available: http://sikkimpolice.nic.in/services.html.

[7] JavaPoint . “DBMS.” Available: https://www.javatpoint.com/.

[8] Sikkim Tenant law Available:http://bareactslive.com/SIK/sik095.htm#0.

[9] W3Schools."W3Schools How To." Available:https://www.w3schools.com/howto/default.asp.

[10] Sikkim tenant law Available: https://www.wikiprocedure.com/index.php/Sikkim_-

_Apply_to_get_Tenant_Verification cite this

44