131 Dbms PBL Report
131 Dbms PBL Report
PROBLEM STATEMENT :
In the dynamic landscape of real estate, managing rental properties efficiently is crucial
for both property owners and tenants.
Challenges:
Data Discrepancies:
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
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.
● .
HOUSE TABLE:
PAYEMENT:
CONTRACT:
TenantIn
TenantOut
CONTACT:
USER:
5https://www.scribd.com/document/428244636/House-Rental-Management-System-
Report-1-pdf
6.https://www.ijsrp.org/research-paper-1114/ijsrp-p35101.pdf