My Project
My Project
A PROJECT REPORT
Submitted to
Department of Computer Application
Divya Gyan College
Kamaladi mod, Kathmandu, Nepal
Submitted by:
Santosh Kumar Mahato (Exam Roll No :75120141)
Supervisor’s Recommendation
I hereby recommend that this project prepared under my supervision by Mr. SANTOSH
KUMAR MAHATO (Exam roll no:75102141) entitled “House Rental Management
System” in partial fulfillment of requirements of Bachelor in Computer Application 4th
Semester (Project I) for the degree of Bachelor in Computer Application is
recommended for the final evaluation.
…………………
SIGNATURE
Mr. Shirish Timilshina
SUPERVISOR
Department of IT
Divya Gyan College
Kamaladi Mod, Kathmandu
Tribhuvan University
Faculty of Humanities and Social Sciences
Divya Gyan College
LETTER OF APPROVAL
This is to certify that this project prepared by Mr. SANTOSH KUMAR MAHATO
(Exam roll no:75102141) entitled “House Rental Management System” in partial
fulfillment of the requirements for the degree of Bachelor in Computer Application has
been evaluated. In our opinion it is satisfactory in the scope and quality as a project for
the required degree.
Rental house management has become an important factor in modern society, hence the
need to have a rental house management system. If you are a stranger in some city and
want to rent a house, then it is difficult to find a suitable house in time. This is the main
motivation behind the Online House Rental Management System project development. In
our project we have three stakeholders (Admin who controls everything, Owner who
owns a property, and a renter). The website has three different panels for them. If any
issue happens with the website a user can contact the admin using the Contact us form.
And admin will get all the users‟ messages in admin panel. Admin has some more power
like to delete a profile in case something goes wrong. The renters have a renter panel
where renter can browse all the posts, can bookmark a rent post if the renter likes and can
communicate with the owners. Also, this website has a house owner panel where an
owner can post their property details. The owner can update and delete a post if he
wishes.
ii. The current system does not allow customers to rent a house without physical contact
with the house owner.
2. To manage all the information about house, rent and booking and house status and
it helps to users to search home on rent.
Time-consuming training: It may take a lot of time to train tenants or agents to use the
system effectively.
Dependency on cash payments: for rent can lead to security risks, limited financial
transparency, miscounting, lack of a paper trail, and potential for human error.
Built as a web application using Microsoft Visual Studio, a Microsoft SQL database, and
incorporating technologies such as PHP, jQuery, JavaScript, CSS, and this system stands
at the forefront of technological advancement. Its highly configurable nature empowers
administrators to tailor the appearance and access privileges of users according to specific
requirements. Successfully addressing the limitations of antiquated manual systems, the
Smart House Rental Management System not only meets current needs but also
anticipates future demands with upcoming enhancements including features for online
communication and expedited payment processing, ensuring continued relevance and
efficiency in the dynamic realm of property management. [3]
Chapter 3: System Analysis and Design
3.1 System Analysis:
The system analysis of the system is done by conducting requirement analysis, feasibility
analysis, data modeling and process modeling as follows:
Actors: Represented by stick figures in the diagram. They are external entities that
interact with the system. Examples include a customer, an administrator, or another
system.
Use cases: Represented by oval shapes in the diagram. They are the actions or functions
that the system can perform. Examples include placing an order, viewing a report, or
resetting a password.
System boundary: Represented by a rectangle that encloses the use cases and actors. It
defines the scope of the system and separates it from the outside world.
Relationships: Represented by lines connecting the actors and use cases. The lines
indicate how the actors and use cases interact with each other.
There are two types of relationships:
o Association: A line connecting an actor to a use case, representing that the actor
performs the use case.
o Include: A dashed line connecting one use case to another, representing that the first use
case includes the functionality of the second use case. Use case diagrams are a useful tool
for capturing the functional requirements of a system, and can be used during the
planning, analysis, and design phases of a project. They can help identify the specific
actions or functions that a system must perform, and the actors that will interact with the
system. They can also provide a clear and concise view of the system's functionality,
making it easier for developers, stakeholders, and users to understand and communicate
about the system's requirements. Page | 23 In this system, there are two actors where one
is internal agent, and another is external agent. The internal agent is the system owner
while the external agent is the tenant.
Figure:3.1 user case diagram of house rental management system
3.1.1.2 Non-Functional Requirements:
Performance Requirement:
The user shall be able to login into the system.
Usability Requirement:
The user shall be able to use the system in easy manner.
Availability Requirement:
The system is available 100% for the user and is used 24hrs a day and
365 days a year.
The system shall be operational 24hrs a day and 7 days a week.
Environmental Requirement:
The system shall require a localhost server, database server and a web
browser to run successfully.
Compatibility Requirement:
The system shall be compatible across all platforms under required
environment.
Security Requirement:
The user password shall be in encrypted format in the database.
Every user shall have a unique Session while logging into the system.
Analysis
Design
Implementation
Testing
Documentation
Review
Chapter 4 :Design
Software design is the process of defining the architecture, components,
interfaces, and other characteristics of a software system. It is the process of creating a
plan or blueprint that describes how the software will meet the needs of its users, and how
the different components of the software will work together. The goal of software design
is to produce a representation of the software that can be used to guide its construction,
testing, and maintenance.
There are many different approaches to software design, each with their own
strengths and weaknesses. Some of the more popular approaches include:
waterfall design, which emphasizes on requirement are first fixed The specific approach
and techniques used will depend on the requirements of the software and the goals of the
project.
High level design
ER diagram
Schema diagram
References