Chapter 1

Introduction
1.1 Background
Housing is one of the most fundamental needs for individuals and families. It provides shelter, security,
and a sense of belonging. As urbanization continues to rise globally, more people are moving to cities in
search of better job opportunities, education, and an improved quality of life. In this context, the
demand for housing, especially rental properties has increased significantly.

The history of the home rental system can be traced back to the feudal system and the medieval period:

~ Feudal system

Under the feudal system, land was repeatedly sublet between lords, barons, and tenants. In 1290, two
statutes banned subinfeudation, which outlawed this practice.

~ Medieval period

Royal families in the medieval period distributed their wealth to friends by signing away titles and deeds
to lands. The holders of these lands would collect rent from the peasants who lived there.The landlord-
tenant relationship that is familiar today was established in the 16th century. A landowner would build a
property and charge inhabitants a set fee to live there.

Traditionally, finding a rental property has involved time-consuming processes. Prospective tenants
often rely on word-of-mouth referrals, local advertisements, or real estate agents to find suitable
accommodations. These methods can be inefficient, communication issues,financial management
difficulties and security risks leading to frustration for both renters and landlords. Renters may struggle
to find properties that meet their needs, while landlords may find it challenging to reach a broad
audience.

Currently most of the Ethiopian parts and regions has no automated home renting system for renters.
Since the country is wide and it is harder to find houses for renting in such wide country.The System
feature includes displaying posted houses with their properties, give service forrenters.Who are going
to rent the house, display withdrawal form for renters who want to leavethe house, allow admin to
post houses and so many features are included. In general ourobjective is to design and implement an
easy to use system .

1.2 Purpose of the Systen

The purposes of a Home Rental Management System (HRMS) database are multifaceted, aiming to
streamline and improve various aspects of the rental process. Here's a list of its key purposes:
• Efficient Tenant Management: The system should allow for easy storage and retrieval of tenant
information (contact details, lease agreements, payment history, etc.), reducing administrative
overhead.

• Streamlined Property Management: Organize and track information about rental properties (address,
features, availability, rent amount, photos, etc.), simplifying property listings and searches.

• Automated Rent Collection: Facilitate online rent payments, automate reminders, and generate
detailed payment records, reducing late payments and improving cash flow.

• Effective Maintenance Tracking: Enable tenants to submit maintenance requests through the system,
allowing landlords to track and manage repairs efficiently.

• Improved Communication: Provide a platform for communication between landlords and tenants,
reducing misunderstandings and improving tenant relations.

• Financial Reporting and Analysis: Generate comprehensive financial reports (income, expenses,
profitability), aiding in better financial decision-making.

• Enhanced Security: Secure storage of sensitive information (tenant data, financial records, lease
agreements) to protect against loss or unauthorized access.

• Reduced Administrative Costs: Automate many manual tasks, freeing up time and reducing the need
for administrative staff.

• Increased Efficiency: Streamline the entire rental process from listing a property to collecting rent and
handling maintenance requests.

• Better Decision-Making: Data-driven insights from the system can improve decision-making related to
pricing, property investment, and tenant selection.

• Improved Tenant Satisfaction: Providing a user-friendly system for rent payments and communication
can lead to greater tenant satisfaction.

1.3 Scope of the System

The main scope of this project is to develop online house rental system for most parts of Ethiopian.

Scope of project will be performing as:-

~ The system allows admin to post the house and properties

~The system allows user to manage their own account and allows Admin to manage all

users account.

~The system allows house owner ,Adminto update the house information
~ The system allows renters to send request to theAdmin.

~ The system allowsAdmin to send response to the renter.

~ Make the system more secured by creating login account for all renter, house owners, and

Admin.

~ The system allows to house owner, Admin and renters to view houses and their

information

~The system allowsAdmin to view renters’ requests

~The system allows renter to send withdrawal request.

1.4 Objectives of the System

The objectives of a home rental management system database project should be specific, measurable,
achievable, relevant, and time-bound (SMART). Here's a detailed description encompassing several key
objectives:

~ Automate Rental Processes: The primary objective is to automate key aspects of the rental process,
such as tenant onboarding, rent collection, lease management, and maintenance requests. This
automation should significantly reduce manual effort, minimize human errors, and save time for
property managers.

~ Improve Data Management and Accuracy: The system should provide a centralized, secure database
for storing all rental-related information, ensuring data accuracy, consistency, and easy accessibility. This
includes tenant details, property information, lease agreements, payment records, and maintenance
histories. This objective aims to eliminate data redundancy and inconsistencies often found in manual
systems.

~ Enhance Communication and Collaboration: The system should facilitate seamless communication
between landlords/property managers and tenants. This might involve features such as online
messaging, maintenance request submission, and automated notifications (e.g., rent due reminders).
Improved communication will enhance tenant satisfaction and reduce conflicts.

~ Streamline Financial Management: The system should automate financial processes, such as rent
collection, payment tracking, and the generation of financial reports. This will improve cash

flow management, reduce late payments, and provide landlords with valuable financial insights. Specific
features could include online payment gateways, automated invoicing, and customizable reporting
dashboards.
~ Enhance Security and Data Protection: The system should prioritize the security and privacy of
sensitive data, including tenant personal information and financial records. This objective requires
implementing appropriate security measures (e.g., access control, data encryption, regular backups).

~ Improve Reporting and Analytics: The system should generate various reports and analytics to aid
decision-making. This might include reports on occupancy rates, rental income, expenses, tenant
turnover, and property performance. These reports should help landlords make informed decisions
regarding pricing, investments, and property management strategies.

~ Increase Efficiency and Productivity: Overall, the system should enhance the efficiency and
productivity of the rental management process. By automating tasks and streamlining workflows, the
system should free up time for property managers to focus on other critical aspects of their busines.

1.5 Methodology
Creating a home rental management system involves various components, including database design,
user interface, and business logic. Below is a detailed description of the methodology you might follow
for developing such a system.

Requirements Gathering

Stakeholder Interviews

• Conduct interviews with potential users (landlords, tenants, property managers) to understand their
needs and pain points.

Use Cases

• Define specific use cases for the system, such as:

• Listing properties

• Searching for rentals

• Managing tenant applications

• Processing payments

• Generating reports

System Design

1 Architecture Design

Define the high-level structure of the system.

• Architecture Style: Choose an architecture style (e.g., client-server, microservices, or monolithic). For a
home rental management system, a microservices architecture might be suitable for scalability.

2 Database Design

Design a robust database schema that supports the application’s functionality.

Entity-Relationship Diagram (ERD)

~ Create an ERD to visualize the relationships between different entities in the system.

Common entities may include:

~ Users (Landlords, Tenants, )

~ Properties (Details like address, price, type)

~ Leases (Start date, end date, status)

~ Payments (Amount, date, method)

~ Maintenance Requests (Description, status)

~ Tentantin(moveindate)

~ Tentantout(moveoutdate)

Database Schema

• Based on the ERD, design the database schema. Define tables, fields, data types, and

constraeints.

Normalization

Apply normalization techniques to eliminate redundancy and ensure data integrity. This involves
organizing data into tables and defining primary and foreign keys.

Development

Build the application based on the defined requirements and designs.

• Agile Methodology: Utilize an Agile approach to allow for iterative development, enabling teams to
adapt to changes in requirements quickly.

• Modular Development: Break down the system into manageable modules (e.g., user management,
property listings, payment processing) to facilitate parallel development.
• Version Control: Implement Git for source code management to track changes and collaborate
effectively among team members.

Testing

Ensure the application functions correctly and meets quality standards.

• Unit Testing: Conduct unit tests on individual components to verify their correctness.

• Integration Testing: Test interactions between different modules to ensure they work together
seamlessly.

• User Acceptance Testing (UAT): Engage end-users in testing to validate that the system meets their
needs and expectations before going live.

• Performance Testing: Assess the system's performance under various loads to ensure it can handle
expected traffic without degradation.

Deployment

Release the application into a production environment.

• Continuous Integration/Continuous Deployment (CI/CD): Set up a CI/CD pipeline to automate the

build, testing, and deployment processes, ensuring that new features and fixes can be deployed quickly
and reliably.

• Environment Setup: Prepare staging and production environments that mirror each other to minimize
issues during deployment.

• Rollback Plan: Establish a rollback plan to revert to a previous version if critical issues arise after
deployment.

Training and Documentation

Equip users and stakeholders with the knowledge to effectively use the system.

• User Training: Conduct training sessions for landlords, tenants, and property managers to familiarize
them with the system's functionalities.

• Documentation: Create comprehensive documentation, including:

• User manuals detailing how to navigate and use the system.

• Technical documentation for developers outlining the architecture, APIs, and database schema.

• Maintenance guides for IT staff regarding system upkeep and troubleshooting.

▎ Maintenance and Support

Ensure the system remains operational and evolves with user needs.

• Regular Updates: Schedule periodic updates to address bugs, security vulnerabilities, and feature
requests based on user feedback.

• Support System: Establish a support ticketing system for users to report issues or request assistance,
ensuring timely responses.

• Monitoring Tools: Implement monitoring solutions to track system performance and detect anomalies
proactively, allowing for quick resolutions.

Chapter 2
The Existing System
2.1 Overview
The existing home rental management system typically consists of various components and processes
that manage the relationship between landlords, tenants, and the properties being rented.

User Roles

• Landlords: Property owners who list their properties for rent. They manage property details, set rental
prices, and communicate with potential tenants.

• Tenants: Individuals looking for rental properties. They search for available listings, apply for rentals,
and manage their lease agreements.

Key Features of the Existing System

• Property Listings: Landlords can create and manage listings that include property descriptions, photos,
rental prices, and availability.

• Search Functionality: Tenants can search for properties based on various criteria such as location, price
range, number of bedrooms, and amenities.

• Application Process: Tenants can submit applications for rental properties, which may include
background checks, credit checks, and references.

• Lease Management: The system tracks lease agreements, including start and end dates, rental
payments, and any applicable terms and conditions.

• Payment Processing: Some systems may include features for online payment processing, allowing
tenants to pay rent electronically.
• Maintenance Requests: Tenants can submit maintenance requests for issues that need attention
within the rental property.

Benefits

~ Easy Property Listings: Landlords can quickly list their properties with details and photos, making it
easier for tenants to find what they’re looking for.

~ Improved Communication: The system often provides a centralized platform for landlords and tenants
to communicate, reducing confusion and missed messages.

~ Time-Saving Automation: Many tasks can be automated, such as sending reminders for rent due
dates, which saves time for both landlords and tenants.

~ Online Payments: Many systems allow tenants to pay rent online, making it convenient and reducing
the chances of late payments.

~ Convenient Search Options: Tenants can search for rental properties based on their preferences, such
as location, price, and size, saving time and effort.

2.2 Problems in The Existing System

The existing home rental management systems face a variety of challenges that can hinder their
effectiveness and user satisfaction. Below are some of the key problems associated with these systems.

~ Inefficient Property Listings:

• Difficulty in updating property information leads to outdated listings.

• Lack of standardized formats for listings can confuse tenants.

~ Limited Search Functionality:

• Tenants may struggle to find properties that meet their specific criteria due to inadequate filtering
options.

• Search results may not prioritize relevance, leading to frustration.

~ Cumbersome Application Process:

• Manual application processes can lead to delays and lost applications.

• Lack of automated background checks increases the risk of tenant issues.

~ Poor Lease Management:

• Difficulty in tracking lease terms, renewal dates, and compliance can lead to legal issues.
 • Manual storage of lease agreements increases the risk of loss or mismanagement.

~ Inconvenient Payment Methods:

• Limited payment options can inconvenience tenants and lead to late payments.

• Lack of automated reminders for rent due dates can result in missed payments.

~ Ineffective Maintenance Request Handling:

• Maintenance requests may get lost or delayed without a proper tracking system.

• Tenants may have no visibility into the status of their requests, causing dissatisfaction.

~ Communication Barriers:

• Lack of a centralized communication platform can lead to misunderstandings between

landlords and tenants.

• Important messages may be missed or overlooked due to reliance on email or phone calls.

~ Data Management Issues:

• Inadequate organization of tenant and property data can lead to inefficiencies and errors.

• Difficulty in generating reports for financial analysis and decision-making.

~ Scalability Challenges:

• Existing systems may not scale well with an increasing number of properties or tenants, leading to
performance issues.

• Difficulty in integrating with other tools or platforms (e.g., accounting software).

~ Security Concerns:

• Sensitive tenant information may not be adequately protected, leading to potential data

breaches.

• Lack of access controls can result in unauthorized access to confidential information.

2.3 New opportunities

The problems identified in existing home rental management systems present a significant opportunity
for the development of a new database project that can streamline processes, improve user
experiences, and enhance overall efficiency. Below are some detailed opportunities for innovation and
improvement in a home rental management system:
~ Up-to-Date Property Listings:

• Real-Time Updates: Allow landlords to instantly update property information and sync with other
listing sites.

• Consistent Formats: Use a standard template for listings to make it easy for tenants to compare
properties.

~ Better Search Features:

• Advanced Filters: Let tenants search using detailed criteria like price, number of bedrooms, and pet
policies.

• Smart Recommendations: Use machine learning to show properties based on what users like and
search for.

~ Simplified Application Process:

• Easy Online Applications: Create a user-friendly online form that lets tenants fill out applications
quickly and upload documents.

• Quick Background Checks: Integrate services that automatically check tenant backgrounds to speed
up approvals.

~ Effective Lease Management:

• Digital Lease Storage: Store leases securely online for easy access and management.

• Renewal Alerts: Send reminders to landlords and tenants about upcoming lease renewals.

~ Flexible Payment Options:

• Multiple Payment Methods: Allow tenants to pay rent using various options like credit cards,

bank transfers, or mobile payments.

• Payment Reminders: Send automated reminders to help tenants remember when rent is due.

~ Streamlined Maintenance Requests:

• Maintenance Portal: Provide a dedicated space for tenants to submit and track maintenance

requests.

• Performance Tracking: Give landlords tools to monitor how quickly maintenance issues are resolved.

~ Centralized Communication:

• In-App Messaging: Include a messaging feature for easy communication between landlords
 and tenants.

• Notification Alerts: Notify users about important messages or updates regarding their

properties.

~ Organized Data Management:

• Central Database: Create a single database to keep all tenant and property information organized
and accessible.

• Easy Reporting Tools: Allow landlords to generate reports on finances and occupancy rates easily.

~ Scalable System Design:

• Cloud-Based Solutions: Use cloud technology so the system can grow with more properties and
tenants without slowing down.

• API Integration: Design the system to connect with other software tools for better functionality.

~ Strong Security Measures:

• Data Protection: Use encryption to keep tenant information safe from unauthorized access.

This streamlined approach highlights the key opportunities for innovation in a home rental management
system, making it easier to understand and implement.

2.4 Functional Requirements

When developing a home rental management system it is essential to define the functional
requirements that out line the specific behaviours and functionalities the system must

~ User management support:

• Landlords and Tenants: Allow users to register and log in securely.

• Role-Based Access: Different access levels for landlords and tenants.

~ Property Management:

• Add/Edit/Delete Properties: Landlords can manage their property listings.

• Property Details: Include features like price, location, size, amenities, and photos.

~ Application Management:

• Online Applications: Tenants can submit rental applications online.

• Application Status Tracking: Tenants can check the status of their applications.
~ Lease Management:

• Digital Lease Creation: Generate lease agreements based on tenant information.

• Renewal Notifications: Send alerts for upcoming lease expirations.

~ Payment Processing:

• Rent Payment Options: Allow tenants to pay rent online via various methods (credit card,

bank transfer).

• Payment History: Tenants can view their payment history and upcoming dues.

~ Maintenance Requests:

• Submit Requests: Tenants can report maintenance issues through the system.

• Track Status: Both tenants and landlords can track the status of maintenance requests.

~ Communication Tools:

• In-App Messaging: Enable direct communication between landlords and tenants.

• Notifications: Notify users about important updates (e.g., new messages, payment reminders).

2.5 Non Functional Requirements

Non functional requirements define the quiality attributes, system performance and constraints of a
system rather than specific behaviors

~ Performance:

• Response Time: The system should respond to user queries within 2 seconds under norma

load conditions.

• Transaction Processing: Rent payment transactions must be processed within 5 seconds to

ensure a smooth user experience.

~ Usability:

• User Interface: The system should have an intuitive and user-friendly interface, allowing users to
navigate easily without extensive training.

• Help and Support: Provide accessible help documentation and customer support options for users
encountering issues.
~ Maintainability:

• Code Modularity: The system should be designed with modular components to facilitate easier
updates and maintenance.

• Documentation: Comprehensive technical documentation should be provided for future developers

and maintainers.

~ Security:

• Data Protection: User data must be encrypted both in transit and at rest to protect sensitive
information.

• Access Control: Implement role-based access control (RBAC) to restrict access to sensitive features
based on.

~ Budget Constraints:

• Development Budget: The project must adhere to a predefined budget limit for development,
testing, and deployment phases.

Chapter 3
The Proposed System
3.1 Overview
The proposed Home Rental Management System is designed to simplify the process of renting homes
for both landlords and tenants. This system will provide a user-friendly platform where users can
manage properties, track rental payments, and communicate effectively.The system aims to improve the
efficiency,reduce errors and enhanced customers satisfaction by providing the centralized platforms.

3.2 Features of the proposed System

~ Rental Management:

• Rental Applications: Tenants can submit applications through the system, which are stored in the
database for landlords to review. This feature streamlines the application process and allows landlords
to track multiple applications simultaneously.

• Application Tracking: The status of each application can be updated in real-time, providing
transparency for both parties and improving communication
~ User Management:

• Registration and Profiles: The system allows for the creation of distinct user profiles for landlords and
tenants. Each profile stores relevant information such as personal details, rental history, and
preferences. This is crucial for maintaining a well-organized database that can easily retrieve user-
specific data.

• Role-Based Access Control: Different access levels can be implemented to ensure that landlords and
tenants can only access information pertinent to their roles, enhancing data security and integrity.

~ Property Management:

• Property Listings: Landlords can input property details (e.g., location, price, size, amenities) into the
database. This feature enables easy searching and filtering for tenants, facilitating quick access to
relevant listings.

• Data Validation: The system can enforce validation rules to ensure that all property information
entered is accurate and complete, reducing data entry errors.

~ Payment Management:

• Online Rent Payments: The HRMS facilitates secure online payment processing, allowing tenants to
pay rent directly through the platform. Payment details are recorded in the database, providing an
accurate financial history.

• Payment History and Reporting: Landlords can access reports on rental income and payment
statuses, which helps in financial planning and management. This data can also be used for generating
financial statements or tax documentation.

~ Maintenance Management:

• Maintenance Requests: Tenants can submit requests for repairs or maintenance through the system.
These requests are stored in the database and can be tracked by landlords, ensuring timely responses.

• Status Updates: The system allows landlords to update the status of maintenance requests, keeping
tenants informed and enhancing satisfaction

3.3 Feasibility Analysis

The purpose of the feasibility analysis is to evaluate the practicality and viability of a proposed project,
in this case, a home rental management system. It aims to determine whether the project is technically,
economically, legally, and operationally feasible, helping stakeholders make informed decisions about
whether to proceed with the development.
~ Technical Feasibility

- Technology Requirements: Assess the technology stack (e.g., programming languages,

frameworks, database management systems) to ensure compatibility with existing systems.

- Technical Skills: Evaluate if the team has the necessary skills or if training is required.

- Infrastructure: Determine whether existing hardware and software resources are adequate.

~ Legal Feasibility

- Compliance: Ensure the system complies with relevant laws and regulations (e.g., data

protection laws like GDPR, housing regulations).

- Contracts: Assess any legal agreements required with third-party services (e.g., payment

processors)

~ Operational Feasibility

- User Acceptance: Evaluate whether potential users (landlords, tenants) will accept and use

the system.

- Training Needs: Identify any training requirements for users and support staff.

- Support and Maintenance: Plan for ongoing support and maintenance operations.

~ Economic Feasibility

- Cost-Benefit Analysis:

- Development Costs: Estimate costs for development, including:

- Salaries for developers, designers, and project managers.

- Software licenses and tools.

- Hardware costs (if applicable).

- Operational Costs: Recurring costs such as hosting, maintenance, and support.

~ Budget Analysis

- Estimated Costs: Break down the budget into categories, such as:

- Personnel Costs: Salaries for developers, designers, and project managers.

 - Software and Tools: Costs for development tools, licenses, and subscriptions.

- Infrastructure Costs: Costs for servers, hosting, and maintenance.

- Marketing and User Acquisition: Costs for promoting the system to potential users.

~ Schedule Analysis

- The developmenet for home rental management system may vary depending on the project scope
and available resourse.A typical development might involve the following Phases of development.

~ Requirements gathering and analysis: 2-4 weeks

System design: 3-5 weeks

implementation and implementation : 4-8 weeks

testing and debugging: 2-5 weeks

deployment and training: 1-2 weeks

Chapter 4
Database Design
4.1 Conceptual Database of the new System
The conceptual database design serves as a high-level blueprint for the data structure of the home
rental management system. It outlines the key entities, their attributes, and the relationships between
them without getting into the technical details of how the data will be stored in a database. This design
helps in understanding the overall data requirements of the system and guides the subsequent stages of
database design.

4.1.1 Entities identification and description

In a Home Rental Management System entities represent the key objects or concepts that the system
manages. Here's a detailed descripition of the essential entities, along with considerations for a
construction design:

The core Entities that are the fundamentals building blocks of the Home rental management system
database

~ Tenant: Represents an individual or group renting a property. This entity is central to the system, and
all other entities are related to it directly or indirectly.
~ Property: Represents a rental property (house, apartment, etc.). This includes details like address,
features, rent amount, and availability status.

~ Lease: Represents a rental agreement between a tenant and a landlord. This entity is crucial for
tracking rental terms, duration, and payment schedules.

~ Payment: Records a payment made by a tenant towards their rent. This entity tracks payment details
such as date, amount, and payment method.

~ Landlord: Represents the individual or company managing the properties. This entity is responsible
for creating and managing properties and lease agreements.

~ Maintenance Request: Records a request for repairs or maintenance at a rental property. This entity
tracks the request's status, description, and assignment to a contractor (if applicable).

~ TenantIn: This entity records the move-in event for a tenant at a specific property. It provides a
precise timestamp for the start of a tenancy.

~ TenantOut: This entity records the move-out event for a tenant at a specific property. It provides a
precise timestamp for the end of a tenancy.

4.1.2 Entity Attributes identification and description

~ Tentant
*tenantID (Integer, Primary Key): Unique identifier for each tenant.

* firstName (String):

* lastName (String): Tenant's last name.

* email (String): Tenant's email address.

* phoneNumber (String):

* registrationdate(date):

* propertyID(intger,Foreign key referencing property):ID of the property.

* requestID(integer,Foreign key referencing MaintenanceRequest):ID of the maintenanceRequest.

~ Landlord
* LandlordID (Integer, Primary Key)

* LandlordfirstName (String)

* LandlordlastName (String)
 * phoneNumber (String)

* email (String)

* leaseID(integer.Foreign key referencing Lease):ID of the lease.

* propertyID(integer,Foreign key referencing property):ID of the property.

~ MaintenanceRequest:
* requestID (Integer, Primary Key): Unique identifier for each maintenance request.

* propertyID (Integer, Foreign Key referencing Property): ID of the property.

* requestDate (Date): Date the request was submitted.

* descriptionissue(String): Description of the maintenance issue.

* status (String):

* resolvedDate (Date):

~ Payment:
* paymentID (Integer, Primary Key): Unique identifier for each payment.

* leaseID (Integer, Foreign Key referencing Lease): ID of the lease.

* paymentDate (Date): Date of the payment.

*payment amount (Decimal): Amount of the payment.

* paymentMethod (String): Method of payment (e.g., check, online).

~ Lease:
* leaseID (Integer, Primary Key): Unique identifier for each lease agreement.

* tenantID (Integer, Foreign Key referencing Tenant): ID of the tenant.

* propertyID (Integer, Foreign Key referencing Property): ID of the rented property.

* startDate (Date): Lease start date.

* endDate (Date): Lease end date.

* rentAmount (Decimal): Monthly rent amount.

* leaseStatus (String): Status of the lease (e.g., active, terminated).

 * paymentschedule (date):the schedule of paying the payment

* registrationdate(date): the tentant registration data

~ Property:
* propertyID (Integer, Primary Key): Unique identifier for each property.

* subcity (string): subcity where the property is located.

* city (String): City where the property is located.

* state (String): State where the property is located.

* rentAmount (Decimal): Monthly rent amount.

* bedrooms (Integer): Number of bedrooms.

* bathrooms (Integer): Number of bathrooms.

* propertytype(string):(house,apartment....)

* descriptionofproperty(String): Description of the property's features.

* status (boolean): Indicates if the property is currently available.

* TentantID (Integer, Foreign Key referencing Tentant): ID of the tentant.

~ TenantIn:
* tenantInID (Integer, Primary Key): Unique identifier for each move-in record.

* leaseID (Integer, Foreign Key referencing Lease): ID of the associated lease.

* moveInDate (Date): The date the tenant moved into the property. This is essential.

* initialRentAmount (Decimal): The rent amount at the start of the lease.

* registrationdate(date):the tentant registration date

~ Tenantout:
* tenantOutID (Integer, Primary Key): Unique identifier for each move-out record.

* leaseID (Integer, Foreign Key referencing Lease): ID of the associated lease.

* moveOutDate (Date): The date the tenant moved out of the property. This is essential.

* finalRentAmount (Decimal): Rent due for final month of the lease..

* moveOutReason (String): Reason for moving out.

* registrationdate (date):

4.1.3 Relationship identification and description

* Tenant — Lease: A Tenant has one or more Leases. A Lease belongs to one Tenant. (One-to-many
relationship)

* landlord -- property: A landlord ownerd many property.so one-to-many relatioshiP

* landlord--lease: A landlord has many lease.so the relationship is one-to-many.

* Property — Lease: A Property has one or more Leases. A Lease is for one Property. (One-to-many
relationship)

* Lease — Payment: A Lease has one or more Payments. A Payment is for one Lease. (One-to-many
relationship)

• Property — MaintenanceRequest: A Property receives one or more MaintenanceRequests. A

MaintenanceRequest is for one Property. (One-to-many relationship)

* Tenant — MaintenanceRequest: A Tenant submits one or more MaintenanceRequests. A

MaintenanceRequest is submitted by one Tenant (can be NULL if the manager submits the request).
(One-to-many relationship)

* Lease — TenantIn: One-to-one. Each lease has exactly one TenantIn record (when the tenant moves
in).

* Lease — TenantOut: One-to-one. Each lease has exactly one TenantOut record (when the tenant
moves out).

* tentant - property :one -to-many.Each tentant renting many property.