A

SOFTWARE REQUIREMENT SPECIFICATION ON

HOUSE BUYING/RENTING WEB

APPLICATION

UNDER

NON-SYLLABUS PROJECT

Submitted To: Submitted By:

Mr. Madhav Sharma Anurag Dadhich (PIET22CS025)
Assistant Professor Anshul Panchal(PIET22CS024)

DEPARTMENT OF COMPUTER ENGINEERING

POORNIMA GROUP OF INSTITUTIONS, JAIPUR
(Academic Year 2022-23) (Odd)

1
 DECLARATION

I hereby declare that the Non-syllabus Project report entitled “HOUSE

BUYING/RENTING WEBPAGE" was carried out and written by me under the
guidance of Mr. Madhav Sharma, Assistant Professor, Department of Computer
Engineering, Poornima Institute of Engineering & Technology, Jaipur. This work has
not been previously formed the basis for the award of any degree or diploma or
certificate nor has been submitted elsewhere for the award of any degree or
diploma.

Place: Jaipur Anurag Dadhich (PIET22CS025)

Date: 11.12.2023 Anshul Panchal (PIET22CS024)

2
 Table of Contents

Chapter 1 Introduction 4
1.1 Objective of Project
1.2 Project Scope
1.3 Types of users
Functional Requirements
Chapter 2 Overall Description 4
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 User Documentation
Chapter 3 External Interface Requirements 5
3.1 User Interface
3.2 Hardware Interface
3.3 Software Interface
3.4 Communication Interface
Chapter 4 System Features 6
4.1 Activity Diagram
4.2 Use-Case Diagram
4.3 Data Flow Diagram
4.4 Class Diagram
4.5 E-R Diagram
4.6 Project Snapshots
Chapter 5 Non-Functional Requirements 13
5.1 Performance
5.2 Reliability
5.3 Security
5.4 Usability and scalability
5.5 Compatibility and maintenance
5.6 Back up and recovery
Chapter 6 Conclusion 14

3
 Chapter 1
Introduction of project

1.1 Objective of Project

To create a user-friendly, easily accessible and suitable website for buying/checking out houses rate and availability
according to requirements or user for purchasing or for rentals.

1.2 Project Scope

The project scope for a house buying/renting web application involves the development of an online platform that
enables users to search, explore, and potentially transact properties for purchase or rent. The application will include
user-friendly features such as advanced search functionalities, property listings with detailed information, high-
quality images, and interactive maps for location visualization. Users will be able to set preferences, filter results
based on criteria like location and budget, and, if purchasing is involved, register for an account. The platform aims
to provide a seamless and secure experience for users looking to find their ideal home or property, enhancing their
ability to make informed decisions in the real estate market.

1.3 Type of users

The primary audience for a house buying/renting web application includes individuals and families actively
searching for residential properties(fully furnished/ semi-furnished). This diverse audience may consist of
prospective homebuyers looking for a permanent residence, renters seeking temporary accommodation, real estate
investors exploring investment opportunities, and anyone interested in the housing market. The application caters to a
broad spectrum of users with varying needs related to property acquisition or rental, providing a convenient online
platform for their real estate endeavors.

Chapter 2
Overall description

2.1 Project perspective

The House Buying/Renting Web Page is designed in order to provide the best of available properties they could buy
with the best of deals. This website has a creative and user-friendly interface. Buyers will approach the page and look
for the required property. Before confirming the purchase, buyer need to register with valid credentials. And the
payment mode is secured.

2.2 Project functions

The House Buying/Renting Web Page made for users who are willing to buy or renting a house property in
correspondence with their requirements. Buyers can find best deals through this website. A login process is made
essential in order to buy from this website. This website provides the details like location of property, selling price of
property as well some pictures for viewing the property. The contact details are shared at the time of confirming the
purchase and registration as well as verification also need to be done.

2.3 User Classes and Characteristics

This project works well with the integration of buyer, tech experts and the property dealers. Property dealers will
update on the available properties while technical experts will manage the website and that property is accessible to
the fellow buyers.

2.4 Operating Environment

This web application can run on desktops, laptops and different mobile displays. It requires internet connectivity for
APIs to work, browse the site, for registering and for payment as well. It is compatible with various operating
systems.

2.5 Design and Implementation Constraints

4
  Limited Interactivity: Without a back-end, interactions with the server and dynamic data handling are restricted.
 Transaction Handling: Handling financial transactions securely on the client-side poses significant security risks.
Implementing payment gateways and processing transactions typically requires server-side processing for
security reasons.
 Dependency on external APIs: Any disrupts or changes in the these APIs can directly impact the functionality of
the webpage.
2.6 User Documentation
User documentation is crucial to help users navigate the platform effectively.
An introduction about the webpage is being displayed and how it is used. The user registration is explained and it is
required for buying the property.

Chapter 3
External Interface Requirements

3.1 User Interface

The user interface (UI) in the external interface requirements of a house buying/renting web application involves the
design and functionality that users interact with. It encompasses the layout, navigation, search features, property
listings, interactive maps, and user account management. The UI should be intuitive, visually appealing, and
responsive, ensuring an optimal user experience across devices. External interface requirements also include
seamless integration with external services, such as mapping APIs for location visualization and possibly third-party
real estate databases for property information. The goal is to provide users with a user-friendly and efficient interface
to search, explore, and potentially transact properties for buying or renting.

3.2 Hardware Interface

In the external interface requirements of a house buying/renting web application, the hardware interface specifies the
necessary hardware components and configurations needed to run the application effectively. This generally includes
requirements for user devices such as computers, laptops, tablets, and smartphones with internet connectivity. The
web application should be compatible with common web browsers (e.g., Chrome, Firefox, Safari) and responsive to
different screen sizes. Additionally, any specific hardware requirements for servers or hosting platforms, if
applicable, should be outlined to ensure the optimal performance and scalability of the application.

3.3 Software Interface

In the external interface requirements of a house buying/renting web application, the software interface outlines the
compatibility and integration aspects with external software components. This includes specifying the supported web
browsers (e.g., Chrome, Firefox, Safari), operating systems (e.g., Windows, macOS, Android, iOS), and any
additional software dependencies required for the application to function seamlessly. Furthermore, it may detail
integration points with external services or APIs, such as mapping services for location visualization, real estate
databases for property information, or payment gateways for transaction processing. The goal is to ensure a smooth
interaction between the web application and the software environments in which it operates.

3.4 Communication Interface

In the external interface requirements of a house buying/renting web application, the communication interface
specifies how the application interacts with external systems and services. This includes detailing the protocols and
methods used for data exchange between the web application and any third-party services it integrates with, such as
real estate databases, mapping APIs, or payment gateways. Additionally, it may outline security measures,
authentication mechanisms, and data encryption protocols to ensure secure communication between the web
application and external entities. The communication interface aims to establish seamless and secure interactions for
the effective functioning of the house buying/renting web application.

5
 Chapter 4
System Features

A house buying/renting web application incorporates a range of essential features to facilitate a seamless user experience.
Users can efficiently search for properties based on specific criteria such as location and budget, with advanced filtering
options for precision. Detailed property listings showcase relevant information, including high-quality images, property
descriptions, and pricing details. The platform ensures user engagement through registration and authentication processes,
allowing individuals to save searches, favorite properties, and interact with property owners or agents. The inclusion of
interactive maps aids in visualizing property locations and evaluating surrounding amenities. Responsive design
guarantees accessibility across various devices, while security measures protect user data and transactions. Additional
features encompass user account management, transaction processing, feedback mechanisms, notifications, and
accessible help and support resources. Together, these system features create a robust and user-friendly environment for
individuals navigating the process of buying or renting a property.

4.1 Activity Diagram

Activity Diagram

4.2 Use-Case Diagram

6
 Use-Case Diagram

4.3 Data Flow Diagram

7
4.4 Class Diagram

4.5 E-R Diagram

8
4.6 Project Snapshots

Home Page

Sign-up and Login Page

9
Code –

10
11
12
 Chapter 5
Non-Functional requirements

Non-functional requirements for a house buying/renting web application define the qualities and characteristics that are
not directly related to specific functionalities but are critical for the overall performance, usability, and reliability of the
system. Here are some non-functional requirements for such an application:

13
5.1 Performance
- Response Time: The system should provide quick response times for search queries, property listings, and other
interactions.
- Scalability: The application should scale effectively to handle an increasing number of users and property listings.

5.2 Reliability:
- Availability: The web application should be available and accessible to users with minimal downtime.
- Fault Tolerance: The system should be designed to handle and recover gracefully from errors or failures.

5.3 Security:
- Data Encryption: All sensitive user data, including login credentials and personal information, should be encrypted
for security.
- Authentication and Authorization: Robust authentication mechanisms and access control should be in place to ensure
secure user interactions.

5.4 Usability and Scalability:

- User Interface (UI) Consistency: The UI should provide a consistent and intuitive experience across different pages
and functionalities.
- Accessibility: The application should adhere to accessibility standards to accommodate users with disabilities.
- Database Scalability: The database infrastructure should be scalable to accommodate a growing number of property
listings and user data.
- Load Balancing: Load balancing mechanisms should distribute incoming traffic efficiently to maintain system
performance.

5.5 Compatibility and maintenance:

- Cross-Browser Compatibility: The application should be compatible with major web browsers (e.g., Chrome, Firefox,
Safari).
- Device Compatibility: The website should be responsive and function well on various devices, including desktops,
tablets, and smartphones.
- Code Maintainability: The codebase should be well-organized, documented, and modular to facilitate future updates
and maintenance.
- Scalable Architecture: The system architecture should be designed for scalability and ease of future enhancements.

5.6 Backup and Recovery:

- Data Backup: Regularly back up critical data to prevent data loss in case of unexpected events.
- Disaster Recovery Plan: Have a well-defined plan for recovering the system in the event of a disaster or system
failure.
These non-functional requirements play a crucial role in shaping the overall quality and effectiveness of a house
buying/renting web application. They ensure that the application not only meets functional needs but also delivers a
secure, reliable, and efficient user experience.

Chapter 6
Conclusion

In conclusion, a house buying and renting web application serves as a dynamic and user-centric platform designed to
streamline the process of property acquisition and rental. By offering a range of features, including advanced search
functionalities, detailed property listings, interactive maps, and user account management, the application aims to provide
a comprehensive and personalized experience for users. The responsive design ensures accessibility across various
devices, while robust security measures safeguard user data and transactions. Non-functional requirements, such as
performance, reliability, scalability, and compliance with privacy regulations, contribute to the overall success and
sustainability of the application. In essence, the house buying and renting web application seeks to empower users in
making informed real estate decisions while prioritizing usability, security, and efficiency throughout the user journey.
14