0% found this document useful (0 votes)
28 views9 pages

131 Dbms PBL Report

This document proposes developing a home rent database management system to address challenges in efficiently managing rental properties. It involves creating a centralized database to store property, tenant, and financial transaction data, as well as modules for communication, payment processing, and maintenance tracking. An entity-relationship diagram is presented showing tables for tenants, properties, payments, contracts, tenant move-ins and outs with defining attributes and relationships. The methodology involves designing the database structure using SQL to form relations between tables and allow querying and updating records.

Uploaded by

Ritiesh Bhatia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views9 pages

131 Dbms PBL Report

This document proposes developing a home rent database management system to address challenges in efficiently managing rental properties. It involves creating a centralized database to store property, tenant, and financial transaction data, as well as modules for communication, payment processing, and maintenance tracking. An entity-relationship diagram is presented showing tables for tenants, properties, payments, contracts, tenant move-ins and outs with defining attributes and relationships. The methodology involves designing the database structure using SQL to form relations between tables and allow querying and updating records.

Uploaded by

Ritiesh Bhatia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

TITLE:

HOME RENT DATABASE


MANAGEMENT SYSTEM

PROBLEM STATEMENT :
In the dynamic landscape of real estate, managing rental properties efficiently is crucial
for both property owners and tenants.
Challenges:

Data Discrepancies:

● Property details, tenant information, and financial records are often


scattered across various sources.Difficulty in maintaining an updated
database due to manual entry and lack of a centralized system.
Communication Gap:
● Lack of a structured communication channel between landlords, tenants,
and property managers.
● Important notifications, rent reminders, and maintenance requests may
get lost or delayed.
Payment Processing:
● Inefficient handling of rent payments, security deposits, and other
financial transactions.Difficulty in tracking payment history and generating
financial reports for property owners.
Maintenance Tracking:
● Challenges in tracking and scheduling property maintenance tasks.Lack of
a systematic approach to handling repair requests and keeping records of
maintenance history.
Security and Privacy Concerns:
● Potential risks of data breaches and unauthorized access to sensitive
information.

Objective:
● Centralized Database:
● Develop a centralized database to store and manage comprehensive
information about properties, tenants, and financial transactions.
Communication Module:
● Implement a robust communication module to facilitate seamless
interaction between landlords, tenants, and property managers.
Payment Integration:
● Integrate a secure payment processing system to handle rent payments,
security deposits, and other financial transactions.
Maintenance Tracking System & Security Measures:
● Design a module for tracking and scheduling property maintenance tasks,
including repair requests and maintenance history.
Security Measures:
● Implement security measures to protect sensitive data, ensure user
privacy, and comply with data protection regulations.

Scope of Project:
Property and Tenant Information Management:
● Property Listings: Create a centralized repository for property details, including
addresses, features, rental terms, and availability status.
● Tenant Profiles: Manage comprehensive tenant profiles, including contact
information, lease agreements, payment history, and application details.
Property and Tenant Information Management:
● Property Listings: Create a centralized repository for property details, including
addresses, features, rental terms, and availability status.
● Tenant Profiles: Manage comprehensive tenant profiles, including contact
information, lease agreements, payment history, and application details.
Communication and Maintenance Handling:
● Communication Platform: Build a communication module to facilitate
interactions between landlords, property managers, and tenants. This includes
announcements, notices, and messaging features.

METHODOLOGY:
System Design:
Create a basic design for the database and system architecture using Entity-
Relationship diagram.
Development:
● Set up the database structure and create tables for properties, tenants, and
financial transactions(relational model).
Testing:
● Objective: Ensure that the system functions as intended and identify and rectify
any bugs or issues

ENTITY- RELATIONSHIP DIAGRAM:


ENTITIES:

Tenant:
● Attributes: TenantID (Primary Key), FirstName, LastName, ContactInfo
House:
● Attributes: HouseID (Primary Key), Address, Features, AvailabilityStatus
Payment:
● Attributes: PaymentID (Primary Key), Amount, PaymentDate
Contract:
● Attributes: ContractID (Primary Key), LeaseStartDate, LeaseEndDate
Tenant-In:
● Attributes: TenantInID (Primary Key), HouseID (Foreign Key), TenantID
(Foreign Key), ContractID (Foreign Key)
Tenant-Out:
● Attributes: TenantOutID (Primary Key), TenantInID (Foreign Key),
MoveOutDate

RELATIONSHIPS:

House-Tenant Relationship:
● One House can be rented by Many Tenants (One-to-Many).
● A tenant can rent multiple houses over time.
Payment-Contract Relationship:
● One Payment is associated with One Contract (One-to-One).
● Each payment corresponds to a specific lease contract.
Contract-TenantIn Relationship:
● One Contract is associated with One Tenant-In (One-to-One).
● Represents the initiation of a lease contract with a specific tenant.
TenantIn-TenantOut Relationship:
● One Tenant-In is associated with One Tenant-Out (One-to-One).
● Represents the exit of a tenant from a house associated with a specific
entry.
● .

Entities with Total Participation:


Tenant: Every tenant must be associated with a house. (Total Participation on
the Tenant side)
House: Every house must be associated with at least one tenant. (Total
Participation on the House side)
Contract:Participates totally in the "Contract-TenantIn Relationship." Every
contract must be associated with a Tenant-In entry, and each Tenant-In entry
must be associated with a contract. (Total Participation on the Contract side)
Tenant-In:Every Tenant-In entry must be associated with a Tenant-Out exit, and
each Tenant-Out exit must be associated with a Tenant-In entry. (Total
Participation on both sides)

Entities with Partial Participation:


Tenant-Out:Participates partially in the "TenantIn-TenantOut Relationship." A
Tenant-Out exit might not be associated with any Tenant-In entry if a tenant
moves out without a specific entry (Partial Participation on the Tenant-Out side).
Payment:Participates partially in the "Payment-Contract Relationship." A payment
might not be associated with any contract if it's not related to a specific lease
agreement (Partial Participation on the Payment side).
RELATIONAL MODEL:

FORMATION OF DATABASE AND RELATIONS USING


SQL:
TENANT TABLE:

HOUSE TABLE:

PAYEMENT:

CONTRACT:
TenantIn

TenantOut

CONTACT:

USER:

DISPLAY TABLE USING SELECT STATEMENT:


BIBLIOGRAPHY AND REFERENCES:
1.Fundamentals of database systems(Ramez Elmsari,Shamkant B.Navathe)

2. Database System Concepts (Avi Silberschatz · Henry F.Korth · S. Sudarshan)

3.geeks for geeks for sql learning

4.W3Schools. SQL Tutorial. https://www.w3schools.com/sql/

● A beginner-friendly resource for learning SQL, essential for database


management.

5https://www.scribd.com/document/428244636/House-Rental-Management-System-
Report-1-pdf

6.https://www.ijsrp.org/research-paper-1114/ijsrp-p35101.pdf

You might also like