Dire Dawa University Institute of Technology (DDUIOT)

School of Electrical and Computer Engineering

Computer Engineering chair
Title: - Guest House Renting system (GHRS)
FINAL THESIS PROJECT

By: -
1. Mahlet Wondesen [DDU1103620]
2. Zebiba Essa [DDU1103809]
3. Robel Muluwork [DDU1103628]
4. Daniel Amare [DDU1103536]

Adviser: Mr. Haftu M.

Senior project Submitted to the School of Electrical and Computer Engineering at Dire Dawa
University Institute of Technology – Dire Dawa University in Partial Fulfillment of the Requirements
for the Degree of Bachelor of Science in Electrical Engineering.

17/June/ 2023 GC

DIRE DAWA, ETHIOPIA

 Declaration
We, the undersigned, declare that this project is our own original work, has not been presented for a degree
in this or any other universities, and all sources of materials used for the project have been fully
acknowledged.

_______________________ ____________________________

Student Name Signature

_______________________ ____________________________

Student Name Signature

_______________________ ____________________________

Student Name Signature

_______________________ ____________________________

Student Name Signature

_______________________ ____________________________

Student Name Signature

_______________________ ____________________________

Student Name Signature

This Project has been submitted for examination with my approval as a university advisor.
_____________________ _____________________

Project Advisor Signature

I
 Approval by Board of Examiners

_______________________ ____________________________

Chairperson Signature

_______________________ ____________________________

Project advisor Signature

_______________________ ____________________________

Project Examiner 1 Signature

_______________________ ____________________________

Project Examiner 2 Signature

_______________________ ____________________________

Project Examiner 3 Signature

_______________________ ____________________________

Project Examiner 4 Signature

II
 Acknowledgment
We would like to express our sincere gratitude to all those who have contributed to the successful
completion of our final thesis project. Firstly, we would like to thank our advisor, Mr. Haftu
Meresa, for his invaluable guidance, support, and encouragement throughout the entire duration
of this project. His expertise and insights have been instrumental in shaping the direction and focus
of our research. We would also like to extend our appreciation to the faculty members of electrical
and computer engineering, computer stream, who have provided us with a solid academic
foundation and equipped us with the necessary skills and knowledge to undertake this project. We
are deeply grateful to our friends and families for their unwavering support, understanding, and
encouragement. Their love and encouragement have kept us motivated and focused during the
challenging times of this project.

Finally, we would like to thank all the participants who generously gave their time and effort in
participating in this study. Their contributions have been essential in achieving the objectives of
this research. Once again, thank you to everyone who has played a significant role in making this
project a success.

III
 Abstract
This project focuses on the development of a software system designed to facilitate the rental
process of guest houses. The objective is to create a user-friendly platform that enables guests to
easily find and rent various types of accommodations, including private rooms, shared rooms, and
entire houses. The system incorporates a comprehensive database to store guest and property
information, as well as an intuitive interface for guests to access and interact with the platform.
The software system offers a range of features to enhance the rental experience. Guests can browse
through available properties, view detailed descriptions, check availability and make reservations.

Furthermore, the system provides convenience and efficiency for property owners. They can
manage their properties and reservations effectively through the centralized database, enabling
them to update property details, monitor availability, and keep track of reservations. The successful
implementation of this project brings numerous benefits. Guests can easily find and rent guest
houses for their desired duration, streamlining the reservation process and eliminating the need for
manual arrangements. Property owners experience improved property management and customer
satisfaction, as the system simplifies the process of managing properties and reservations.

In conclusion, the guest house renting software development system project aims to create a user-
friendly platform that simplifies the rental process for both guests and property owners. By
incorporating a comprehensive database, intuitive interface, and secure payment gateway, the
system enhances convenience, efficiency, and reliability.

IV
 List of Abbreviations and Symbols
DDU Dire Dawa University

HTML Hyper Text Markup Language

CSS Cascade Style Sheet

JS JavaScript

GH Guest house

GHRS Guest house renting system

MERN Mongo, express, react and node js

PC Personal Computer

UI User Interface
UX User experience
INSA Information Network Security Administration

CSV Comma separated values

JSON JavaScript object notation

JWT Json web token

V
 List of Figures
Figure 1 Procedures followed to complet this project --------------------------------------------------- 8
Figure 2 Use case model of the project ------------------------------------------------------------------- 14
Figure 3 Sequence diagram of registration --------------------------------------------------------------- 26
Figure 4 Sequence diagram of login ----------------------------------------------------------------------- 26
Figure 5 Sequence diagram for admin -------------------------------------------------------------------- 27
Figure 6 Sequence diagram for editor --------------------------------------------------------------------- 27
Figure 7 Activity diagram for admin ---------------------------------------------------------------------- 28
Figure 8 Analysis class diagram --------------------------------------------------------------------------- 29
Figure 9 System decomposition diagram ----------------------------------------------------------------- 31
Figure 10 Deployment diagram of the system ----------------------------------------------------------- 32
Figure 11 User modal database of the system ------------------------------------------------------------ 33
Figure 12 Guest modal database of the system ---------------------------------------------------------- 33
Figure 13 User registration form of the system ---------------------------------------------------------- 34
Figure 14 Login form of the system ----------------------------------------------------------------------- 35
Figure 15 Home page of the system ----------------------------------------------------------------------- 35
Figure 16 Guest house view page of the system --------------------------------------------------------- 36
Figure 17 A singe guest house detile page ---------------------------------------------------------------- 36
Figure 18 GH uploading stepper form (step 2)----------------------------------------------------------- 37
Figure 19 GH uploading stepper form image uploding section --------------------------------------- 37
Figure 20 Dashbored main page in dark mode ----------------------------------------------------------- 38
Figure 21 Dashbored main page in light mode----------------------------------------------------------- 38
Figure 22 Manage users page of the system -------------------------------------------------------------- 39
Figure 23 GH management page of the system ---------------------------------------------------------- 39

VI
 List of Tables
Table 1 Register use case description --------------------------------------------------------------------- 15
Table 2 Login use case description ------------------------------------------------------------------------ 16
Table 3 Update profile use case ---------------------------------------------------------------------------- 17
Table 4 Upload guest house use case ---------------------------------------------------------------------- 18
Table 5 Edit guest house data use case -------------------------------------------------------------------- 19
Table 6 Delete guest house use case description--------------------------------------------------------- 20
Table 7 View guest house details use case description ------------------------------------------------- 21
Table 8 Edit user role description -------------------------------------------------------------------------- 22
Table 9 Activate users use case description -------------------------------------------------------------- 23
Table 10 View clustered guest house use case description --------------------------------------------- 24
Table 11 View generated reports in different forms use case ------------------------------------------ 25

VII
Table of Contents
Declaration ....................................................................................................................................... I
Approval by Board of Examiners ................................................................................................... II
Acknowledgment .......................................................................................................................... III
Abstract ......................................................................................................................................... IV
List of Abbreviations and Symbols................................................................................................ V
List of Figures ............................................................................................................................... VI
List of Tables ............................................................................................................................... VII
CHAPTER ONE ............................................................................................................................. 1
Introduction ..................................................................................................................................... 1
1.1 Statement of Problem ............................................................................................................ 2
1.2 Objectives ............................................................................................................................. 3
1.2.1 General Objective .......................................................................................................... 3
1.2.2 Specific Objectives ........................................................................................................ 3
1.3 Significance of the project .................................................................................................... 3
1.4 Scope of the Project .............................................................................................................. 4
1.5 Feasibility study .................................................................................................................... 4
1.5.1 Technical feasibility ....................................................................................................... 4
1.5.2 Economic feasibility ...................................................................................................... 4
1.5.3 Operational feasibility.................................................................................................... 5
CHAPTER TWO ............................................................................................................................ 6
Literature Review............................................................................................................................ 6
CHAPTER THREE ........................................................................................................................ 8
Methodology ................................................................................................................................... 8
Introduction ................................................................................................................................. 8
3.1 Project Methodology............................................................................................................. 8
3.2 System Development ............................................................................................................ 9
3.3 Developing Tools .................................................................................................................. 9
3.4 Requirement Specification .................................................................................................. 10
3.4.1 Functional Requirement ............................................................................................... 10
3.4.2 Non-Functional Requirements ..................................................................................... 11

VIII
 3.5 System Analysis .................................................................................................................. 12
3.5.1 Actor Identification ...................................................................................................... 12
3.5.2 Use Case Identification ................................................................................................ 13
3.5.3 Use Case Documentation ............................................................................................. 15
3.5.4 Sequence Diagram ....................................................................................................... 25
3.5.5 Activity Diagram ......................................................................................................... 28
3.5.6 Analysis of class diagram ............................................................................................ 28
3.6 System Design ................................................................................................................ 30
3.6.1 Design Goals ................................................................................................................ 30
3.6.2 System Decomposition ................................................................................................ 30
3.6.3 Deployment Modeling ................................................................................................. 31
3.6.4 Database Design........................................................................................................... 33
CHAPTER FOUR ......................................................................................................................... 34
Result and Discussion ................................................................................................................... 34
4.1 Result .................................................................................................................................. 34
4.2 Discussion ........................................................................................................................... 40
CHAPTER FIVE .......................................................................................................................... 41
Conclusion and Recommendation ................................................................................................ 41
5.1 Conclusion .......................................................................................................................... 41
5.2 Recommendation ................................................................................................................ 42
References ..................................................................................................................................... 43

IX
 CHAPTER ONE

Introduction
In recent years, the hospitality and tourism industry has experienced a significant growth due to
the increased demand for vacation rental properties. The emergence of online booking systems
and vacation rental platforms has made it easier for guests to search and book their
accommodations. One such system is a guest house renting system project that allows guests to
book and manage their guest house reservations.

The main objective of a guest house renting system is to provide a platform for the rental of
accommodation facilities such as guest houses, bed and breakfast, and vacation homes. These
systems enable guests to browse various listings of properties that are available for rent, view
photos and descriptions of the properties and make online reservations. The guest house renting
system provides an efficient way of managing reservations, tracking guests’ information, and
conducting transactions securely.

One of the primary advantages of a guest house renting system is the convenience it offers to
guests. The system eliminates the need for guests to search for accommodation manually, contact
multiple property owners, and make reservations through emails or phone calls. Instead, guests
can search for the available properties on the platform, compare prices, and book their stay online.
Additionally, guests can manage their reservations, view past reservations, and track payment
transactions from one platform.

Another advantage of a guest house renting system is its ability to enable property owners to
manage their properties efficiently. The platform offers property owners a centralized system for
managing their property listings, updating their availability, setting up pricing structures, and
communicating with their guests. Property owners can also monitor their booking history, track
revenue, and receive payment directly from the platform.

One of the significant limitations of guest house renting systems is the competition in the market.
There are already established vacation rental platforms such as Airbnb, VRBO, and HomeAway
that have a large customer base. These platforms have already set high standards for customer
experience, and it may be challenging for new platforms to compete with them.

1
Another challenge of guest house renting systems is the potential for fraudulent activities or fake
listings. To counter this, guest house renting systems need to have robust verification processes
for both property owners and guests. These processes could include identity verification such as
driver's license, passport, or government-issued ID, as well as payment verification processes.

In conclusion, a guest house renting system is an efficient platform for booking and managing
vacation rental properties. The platforms provide guests with the convenience of booking their
stays online and managing their reservations, while property owners have a centralized system for
managing their properties. Nevertheless, there are challenges that guest house renting systems face,
including competition in the market and potential for fraudulent activities. The guest house renting
system project has the potential to address these challenges by incorporating robust verification
processes, providing unique value propositions, and improving the overall guest experience. The
platform will provide a more efficient and effective way for administrators to manage the users
and guest houses by providing admin dashboard.

1.1 Statement of Problem

some of the problems in not having computerized guest house renting system are:

➢ Lack of computerized system Currently most guest house owners use the manual system
in recording and maintaining their property and customers data
➢ Data security is not assured in a manual way, data is recorded on books/papers which may
easily get damaged leading to loss of data.
➢ Limited Accessibility: Accessing the guest house renting system can be challenging,
especially for users with limited technical knowledge. The system may not be versatile
enough to be compatible with different devices and browsers, limiting its accessibility.
➢ Inaccurate and Unreliable Information: The current guest house renting system may
contain inaccurate and unreliable information that does not represent a fair description of
the rooms or amenities available in the guest house. This can lead to customer
dissatisfaction and a decline in customer loyalty.
➢ Poor Communication and Coordination: Communication and coordination between guest
house owners and management and potential customers is often inadequate, resulting in
possible booking conflicts and a negative experience for guests.

2
1.2 Objectives
1.2.1 General Objective
The general objective of the project is to build guest house renting system.

1.2.2 Specific Objectives

The Specific objectives of the project are:

➢ Gathering required information for the proposed system.

➢ Specifying functional and non-functional requirements of the proposed System
➢ To design and implement the user interface of the system
➢ Deployment of a database for the proposed system
➢ Testing and validating the proposed system

1.3 Significance of the project

The guest house renting system is significant for various reasons:

➢ Optimizes space utilization: Guest house renting system helps in optimizing the
utilization of space. Homeowners can make use of empty spaces in their homes to provide
a temporary stay for guests.
➢ Additional income: Renting out a guest house can provide an additional source of income.
This income can be used to maintain the guest house, pay bills or even save for other
investments.
➢ Better customer service: By renting out a guest house, you are providing guests with
better customer service as compared to staying in a hotel. Guests can experience the
comfort of a home and feel more welcomed.
➢ Flexibility: The guest house renting system offers more flexibility as guests can book the
guest house for a shorter or longer period, as per their requirement.
➢ Cost savings: The cost of renting a guest house is generally lower than staying in a hotel.
Guests can save money and still enjoy the comforts of home.
➢ Tourism promotion: Guest houses can help in promoting tourism in the local area.
Visitors who stay in guest houses are more likely to explore the local attractions and spend
money in the local economy.

3
 ➢ Social interaction: Staying in a guest house offers guests the opportunity to interact with
the hosts and learn more about the local culture and way of life. This can enhance the
guest's overall experience.

1.4 Scope of the Project

The aim of this project is to develop a guest house renting by which it will be used by users who
will rent their gust house will add their guest house to this platform and tenants or users who need
this guest house will see the guest house detailed information and be able to rent guest house from
anywhere they are.

1.5 Feasibility study

Feasibility is the measure of how beneficial or practical the development of an information system
will be in an organization. For the project we have done the feasibility study and our project is
feasible in almost all aspects. The following sub chapters have a brief review of each aspects of
feasibility study.

1.5.1 Technical feasibility

Technical feasibility assessment is focused on gaining an understanding of the present technical
resources of the organization and their applicability to the expected needs of the proposed system.
We are fully confident that the system we develop is fully attainable by existing technology. The
system will also be portable in different platforms as long as the platform can use internet. It is
fully mobile responsive.

1.5.2 Economic feasibility

Economic feasibility is used to determine the positive economic benefits to the organization
provided by the proposed system.

Some benefits provided by the system are:

➢ Small response time and many services

➢ Easy and fast file management
➢ Reduce cost for manual data management (Reduced expenses)

4
1.5.3 Operational feasibility
Operational feasibility is a measure of how well a proposed system solves the problem based on
including the requirement of the user, and then it can handle problems in an appropriate manner.
When the system is applied in to operation, we are fully confident that the system will be
operationally feasible because as we developed a system that is easy to use and maintain. With a
little training anyone will be able to understand and will be able to cope with the system easily.

5
 CHAPTER TWO

Literature Review

The main aim of this review section is to find the best solutions by considering the errors and
imperfection of the system proposed by authors and also to give the solutions provided by other
authors.

Airbnb has gained significant popularity over the last decade as a novel platform for property
owners to list and rent their properties to travelers. This new housing system has supplemented the
traditional hotel industry by providing a more personalized and affordable accommodation option
for people traveling for business or leisure.

Several studies have been conducted to examine various aspects of the Airbnb model, including
its impact on the traditional hotel industry, the behavior of hosts and guests, and its impact on local
communities. For instance, Guttentag (2015) examined the impact of Airbnb on hotel industry by
analyzing the transaction volume data of several leading cities in the United States. [1] The study
concluded that Airbnb has negatively impacted the hotel industry, with tourism revenue decreasing
due to the lower prices offered by Airbnb listings. Additionally, other studies have also examined
the behavior of hosts and guests by conducting surveys and interviews, which have highlighted
that social networking is a crucial element in the Airbnb's growth.

Another important aspect of Airbnb is its popularity in the light of the COVID-19 pandemic. Many
people who had planned to travel to big cities have opted to stay in local guest houses through
Airbnb listings in small towns, which have seen a surge in popularity. For instance, a study by
Greene et al. (2020) revealed that Airbnb rentals in rural areas in the US saw an increase in demand,
unlike urban areas with a decline in bookings [2].

However, although the Airbnb model has received much attention for its disruptive ability to
innovate and dominate its market, there are also concerns related to the negative impacts of this
platform on local communities. For instance, community leaders in several destinations have cited
the negative impact that Airbnb rentals have on local housing markets, which lead to housing
shortages and higher rents due to Airbnb activity. A study by Oskam and Boswijk (2016) found

6
that the effects of Airbnb may differ based on the characteristics of the local housing market, but
concluded that a balance between rental housing availability and sustainable use of retail and
commercial apartments should be pursued. [3]

In conclusion, this literature review highlights the complex and multidimensional nature of the
Airbnb model, with its impact ranging from positive to negative while providing affordable and
personalized accommodation to travelers. Nonetheless, the platform needs regulations to mitigate
the negative impacts and ensure protection to the local housing market. This platform has potential
and continues to play an essential role in providing a unique and affordable accommodation
experience to travelers.

7
 CHAPTER THREE

Methodology
Introduction
In this chapter we will make a detail analysis of the project starting from project methodology,
system design, requirements analysis, and there will be diagrams that will be used to depict the
overall system functionalities. These include the use case diagram, sequence diagram and others.
There will also be description of the functional and non-functional requirements of our system
later in this chapter. Now let us start by project methodology.

3.1 Project Methodology

The proposed guest house renting system (GHRS) is implemented based on the following criteria.

Data gathering procedures

We have gathered information both orally and in written documents as described below

➢ Document analysis: We researched over several documents to gather information, related

literatures, studies, other facts and books that could help in pursuing the project.
➢ Interview: We asked a few questions about the problems encountered in the existing
system

Figure 1 Procedures followed to complet this project

8
3.2 System Development
In this project we planned to design and develop the platform using the MERN stack, which is a
full stack JavaScript framework which are react as frontend, node js and express as server side for
the business logics mongo DB as a data base for the back end and material UI as CSS framework
and leaflet for the map.

3.3 Developing Tools

The developing tools and equipment’s that are used in this project are listed below:

Hardware equipment

➢ Personal computer
Software equipment

➢ Programming language: JavaScript

➢ Code editor: visual studio code
➢ Packages: leaflet, supercluster, mongoose, recharts, react-date picker,
➢ Operating system: window 10
➢ Frame works: MERN
➢ Front end: React, Material UI
➢ State management: redux-toolkit
➢ Server side: node js, express
➢ Database: mongo dB

we have developed this system using MERN stack which is full stack JavaScript framework that
includes the following frameworks and libraries.

MongoDB: - is a document database designed for ease of application development and scaling
which enables you to store and query your data by Modeling your data, connect to MongoDB and
insert, query, update, or delete documents.

Express: - is a minimal and flexible Node.js web application framework that provides a robust set
of features for web and mobile applications.

9
React: - React is an open-source front-end JavaScript library that is used for building user
interfaces, especially for single-page applications. It is used for handling view layer for web and
mobile apps. React was created by Jordan Walke, a software engineer working for Facebook.
React was first deployed on Facebook's News Feed in 2011 and on Instagram in 2012.

Node js: - is an open-source, cross-platform JavaScript runtime environment. It is used for server-
side programming, and primarily deployed for non-blocking, event-driven servers, such as
traditional web sites and back-end API services, but was originally designed with real-time, push-
based architectures in mind.

3.4 Requirement Specification

Our software specification document satisfies the following: -

➢ It specifies the external system behaviors.

➢ It specifies constraints on the implementation.
➢ It serves as reference tool for system maintainers.
➢ It characterizes acceptable response to undesired events.

3.4.1 Functional Requirement

Functional requirement is a description of the service that the software must offer. It describes a
software system or its component. A function is an input to the software system, its behavior, and
outputs. Functional requirements for the crime analysis and management system have been
identified to make sure that the functionalities and functional aspects of the system. They are listed
below: -

➢ Store guest house data and reports

➢ Registration: The system allows the users to register in the system.
➢ Login: The system allows the authenticated users to login to the system.
➢ Manage users: The system enables the Administrator to view, activate and suspend
accounts.
➢ Provide sort and filter tool: The system provides a sort and filter tool to access easily and
efficiently.
➢ Upload data: The system allows the users and admin to upload guest houses to the system.
➢ Update data: The system allows the users and admin to update the guest houses data.

10
 ➢ View detail: The system allows the users and the admin to view file detail that are in the
unloaded guest houses data.
➢ Generate report: The system allows to generate reports from the database.
➢ Cluster data: The system clusters the data according to the location uploaded guest
houses.
➢ Dashboard: The System provides users and admin to access the dashboard.

3.4.2 Non-Functional Requirements

Non-functional requirements of the proposed system focus on the quality that the system behaves,
the teams aim to increase the quality of the system to fulfill the functional requirements of the
system.

Performance

The system is designed to provide fast and steady response times (Quality of Service). The
maximum user response time should be less than 5 seconds and the average response time should
be less than 5 seconds for the next screen to appear or for the existing screen to refresh for the
submission of data.

Reliability

The system is designed to handle invalid inputs and displays an error message to users since
Reliability is one feature of the system that significantly validates user inputs.

Availability

The system is available 24 hours a day and 7 days a week with the existence of an internet
connection and other requirements.

Security

The user who has a valid email and password and who is activated by the admin only can utilize
the system based on their roles. All passwords of the users and admin are encrypted, the user and
admin have to have access token which will expire every 1 hour. Also, route guard is implemented
so as all the routes are accessed by the required authorization level.

11
Maintainability

The system is designed to be maintained easily without spending much time and cost. It has to be
handling both server and client-side errors, bugs, failures and alerts that suits user easily
understand the cause of errors (wrong form fill errors), validation errors, and other bugs.

Portability

The system is designed to support the latest window operating system and another familiar
operating system. Its platform-independent.

Responsiveness

The system is designed to be full responsive in all device, it’s fully mobile, desktop and other
devices responsive.

3.5 System Analysis

It is a process of collecting and interpreting facts, identifying the problems, and decomposition of
a system into its components. System analysis is conducted for the purpose of studying a system
or its parts in order to identify its objectives. It is a problem-solving technique that improves the
system and ensures that all the components of the system work efficiently to accomplish their
purpose. [4] In the following sections we tried to illustrate the system analysis of our crime analysis
for prediction and management project.

Use Case:

Modeling in the use case modeling stage of the analysis phase we first identified the actors, and
then identified the use cases. After these we tried to see the use case diagram of our system and
the use case description of each use case are also included

3.5.1 Actor Identification

In the use cases an actor interacts with the system to perform a piece of meaningful work that helps
them to achieve a goal and has access to define their overall role in the system and the scope of
their action. Depending on the above explanation actors in this system are the following:

➢ Basic: a basic user of the system who visits the system look full information of the uploaded
guest houses choose the desired one and rent by having an account.

12
 ➢ Editor: an editor user of the system is the one how has an editor account, has the guest
house to rent and upload to the system.
➢ Administrator: an actor who is responsible for controlling the overall system

3.5.2 Use Case Identification

Each Use Case describes the functionality that are built in our system, which can include another
Use Case’s functionality or extend another Use Case with its own behavior. The most important
and basic use cases of this system are the following:

➢ Register: anyone how needs to use the system has to register to access the basic system
functionalities.
➢ Login: Before performing the basic system functionalities or administrative tasks a user
has to log into the system.
➢ Update profile: is an authenticated users’ task which enables them to update their profile
by updating their user name and profile pictures of the system.
➢ Upload guest house: is an authenticated editors and admins task which enables only the
authenticated editors and admins to upload a guest house to the system.
➢ Edit guest house data: is an authenticated editors and admins task which enables only
the authenticated editors and admins to edit the guest house data in the system.
➢ Delete guest house: is an authenticated admins task which enables only the authenticated
to delete guest house from the system.
➢ View guest house detail: is an authenticated editor, basic and admins task which enables
only the authenticated editors, basic and admins to view details of the uploaded guest house
in the system.
➢ Edit user role: is an administrative task which enables the admin to edit the basic’s and
editor’s role to basic, editor or admin of the system.
➢ Activate users: is an administrative task which enables the admin to activate the editor’s
and basic users’ in order to access basic system functionalities in the system.
➢ Suspend users: is an administrative task which enables the admin to suspend users (editors
and basic) of the system if needed by deactivating them to be suspended from the system.
➢ View clustered guest houses: enables the system clusters the guest houses according to
their location and enables the users to view.

13
 ➢ View generated reports in different forms: enables the system generate reports in
different forms which are easy to analyze the data according to the guest house present in
the system enables the users to view in their dashboard.
➢ Logout: After performing the basic functionalities as editor, administrator or basic users
the actor’s logout of the system.

Based on the above identified use cases and actors the use case diagram for Guest House Renting
System is displayed as follows:

Figure 2Use case model of the project

14
3.5.3 Use Case Documentation
Based on the earlier use case diagram and the identifications made we now will proceed to use
case description part. In this sub section each use case will be described and clarified thoroughly.

Use case Name Register

Use case Id UC01

Actor(s) Administrator, Editor and Basic

Description Required for registering the users to the system.

Flow of action Actor Action System responds

Step 1: user wants to register Step 3: The system

displays the registration
Step 2: Select the register link
form.
Step 4: Fills registration form Step 6: Validates the input
data in the form.
Step 5: Submits the form
Step 7: Notifies about the
status of registration
(success or failure).

Step 8: Use case ends.

Alternate course of The system alerts an error input message
action (If the registration
➢ The system redirects the customer to step 4 to fill
form is not filled
registration form
correctly)
➢ Use case ends

Precondition The one to be register have to fulfill registration form requirements.

Post condition The registered user now has to contact the admin to be activated and
log into the system
Table 1 Register use case description

15
Use case Name Login

Use case Id UC02

Actor(s) Administrator, Editor and Basic

Description Required to authenticate the users (admin, basic and editor) of the
system.
Flow of action Actor Action System responds

Step 1: Basic, editor or admin Step 3: The system displays the

wants to login login form.

Step 2: Select the login link Step 6: Validates email and

password
Step 4: Fills login
Step 7: The system redirects to
form (email and password) the appropriate page
Step 8: Use case ends.
Step 5: Submits the form

Alternate course of action The system alerts appropriate error message

(If the email and password is
➢ The system redirects the user to step 4 to fill email and
incorrect)
password
➢ Use case ends
Precondition First the admin or the user must be registered and must be activated.

Post condition The authenticated user will be redirected to the appropriate page

Table 2 Login use case description

Use case Name Update profile

Use case Id UC03

16
Actor(s) Administrator, Editor and Basic

Description Required to enable the users and admin to manage their profile in
the system.
Flow of action Actor Action System responds

Step 1: Admin, editor and Step 3: The system displays the

basic wants to update their profile form.
profile Step 6: Validates username and

Step 2: Select the profile link profile picture

Step 7: The system redirects to

Step 4: Fills profile
the appropriate page
form (username) and select Step 8: Use case ends.
picture from their file

Step 5: Submits the form

Alternate course of action The system alerts appropriate error message

(If the username is less than
➢ The system redirects the user to step 4 to fill the profile
3 char and can’t load profile
form
picture)
➢ Use case ends

Precondition First the admin or the user must be login to the system.

Post condition The authenticated user will be redirected to the appropriate page

Table 3 Update profile use case

Use case Name Upload guest house

Use case Id UC04

17
Actor(s) Administrator and Editor

Description Required to upload guest house in the system

Flow of action Actor Action System responds

Step 1: The administer or editors Step 3: The system displays

wants to guest house data to the the stepper form.
system. Step 6: Validates the stepper
Step 2: Select the add link in form
home page bottom nav. Step 7: The system notifies

Step 4: Fills and complete the about the status of uploading

guest house to the editor or
stepper form
admin.
Step 5: Submits the form
Step 8: Use case ends.

Alternate course of action The system displays the error message.

(If filling the add new guest
➢ The system redirects the administrator or editor to step
house stepper form is
4 to fill the add guest house form
incorrect)
➢ Use case ends

Precondition First the Administrator or the editor must login to the system.

Post condition New guest house uploaded to the system.

Table 4 Upload guest house use case

Use case Name Edit guest house data

Use case Id UC05

Actor(s) Administer and editors

18
Description Required to edit uploaded guest house data in the system

Flow of action Actor Action System responds

Step 1: The administer and editor Step 3: The system displays

wants to edit uploaded guest the edit crime data form.
house in the system. Step 6: Validates the edit
Step 2: Select the edit link in guest house form
dashboard page respective to the Step 7: The system notifies
to be edited. about the status of editing

Step 4: Fills the edit guest house guest house data to the user or
stepper form admin.

Step 8: Use case ends.

Step 5: Submits the form

Alternate course of action The system displays the error message.

(If filling the edit uploaded
➢ The system redirects the administrator or editors to
guest house data form is
step 4 to fill the edit uploaded guest house data form
incorrect)
➢ Use case ends

Precondition First the Administrator or the editor must login to the system.

Post condition Existing guest house data edited in the system.

Table 5 Edit guest house data use case

Use case Name Delete guest house

Use case Id UC06

Actor(s) Administer and editor

Description Required to delete uploaded guest house from the system

19
Flow of action Actor Action System responds

Step 1: The administer and editor Step 3: The system displays

wants to delete specific guest the delete guest house data
house from the system form.

Step 2: Select the delete icon in Step 6: Validates the delete

dashboard page respective to the guest house data form
to be deleted. Step 7: The system notifies

Step 4: Fills the delete guest about the status of deleting

house data form guest house to the editor or
admin
Step 5: Submits the form
Step 8: Use case ends.

Alternate course of action The system displays the error message.

(If filling the delete guest
➢ The system redirects the administrator or the editor to
house data form is incorrect)
step 4 to fill the delete guest house data form
➢ Use case ends
Precondition First the Administrator or editor must login

Post condition The specified guest house record deleted from the system.
Table 6 Delete guest house use case description

Use case Name View guest house details

Use case Id UC07

Actor(s) Administer, Basic and editor

Description Required to view details of uploaded guest house in the system

20
Flow of action Actor Action System responds

Step 1: The administer, basic and Step 3: The system displays

editor wants to view specific guest the view guest house data.
house from the system Step 4: Use case ends.
Step 2: Select the view icon in
dashboard page respective to the
to be viewed.

Alternate course of action The system displays the error message.

(If guest house data couldn’t
➢ The system alerts error message to the administrator,
be fetched)
editor or basic users.
➢ Use case ends
Precondition First the Administrator or editor must login

Post condition The specified guest house record deleted from the system.
Table 7 View guest house details use case description

Use case Name Edit user role

Use case Id UC08

Actor(s) Administer

Description Required to edit user’s role in the system

21
Flow of action Actor Action System responds

Step 1: The administer wants to Step 3: The system displays

edit user’s role in the system. the edit role dropdown options

Step 2: Select the role link in users with the basic and admin role.
page respective to the user to be Step 6: Validates the edit role
edited. option.

Step 4: Select the appropriate role Step 7: The system notifies

for the user from the dropdown. about the status of editing
users’ role to the admin.
Step 5: Click save icon of the user
Step 8: Use case ends.
record.

Alternate course of action The system displays the error message.

(If unable to edit existing
➢ The system redirects the administrator to step 4 to
users’ role)
select users role dropdown.
➢ Use case ends
Precondition First the Administrator must login to the system.

Post condition Existing user’s role edited in the system.

Table 8 Edit user role description

Use case Name Activate users

Use case Id UC09

Actor(s) Administer

Description Required to activate users in the system to be able to login to the

system.

22
Flow of action Actor Action System responds

Step 1: The administer wants to Step 3: The system displays

activate users in the system. the check box.

Step 2: Select the active option in Step 6: Validates the edit role
users page respective to the user to option.
be activated. Step 7: The system notifies

Step 4: Click the check box to about the status of activating

activate the user. user to the admin.

Step 8: Use case ends.

Step 5: Click save icon of the user
record.

Alternate course of action The system displays the error message.

(If unable to activate existing
➢ The system redirects the administrator to step 4 to click
user)
the check box.
➢ Use case ends
Precondition First the Administrator must login to the system.

Post condition Existing user activated in the system.

Table 9 Activate users use case description

Use case Name View clustered guest house

Use case Id UC10

Actor(s) Administer, Editor and Basic

Description Required to view clustered uploaded guest house data by location

in the system to be able to choose the guest house locations easily.

23
Flow of action Actor Action System responds

Step 1: The administer or user Step 3: The system displays

wants to see the clustered guest the map which has clustered
house data in the system. uploaded guest house data

Step 2: Select the map link in the present in the system.

home page bottom nav options. Step 4: The system notifies
about the status of getting
Step 5: Click + and – signs to
clustered uploaded guest
zoom in and out.
house data to the admin editor
or basic users.

Step 6: Use case ends.

Alternate course of action The system displays the error message.

(If unable to display clustered
➢ The system alerts the basic, editor or admin.
uploaded guest house data)
➢ Use case ends

Precondition First the Admin, basic or basic user must open the system.

Post condition Existing view clustered guest house data in the system.
Table 10 View clustered guest house use case description

Use case Name View generated reports in different forms

Use case Id UC11

Actor(s) Administer, Basic and Editors

Description Required to view generated graphical reports in different forms

uploaded guest house efficiently.

24
 Flow of action Actor Action System responds

Step 1: The administer, basic or Step 3: The system displays

editor wants to see the generated the appropriate pages with
reports in different forms in the respective to the basic, editors
system. or admins option.

Step 2: Select the dashboard link Step 4: The system notifies

in the home page. about the status of getting
appropriate page to the admin
Step 5: view the pages and use
or users.
available options provided in the
pages like sort filter export. Step 6: Use case ends.

Alternate course of action The system displays the error message.

(If unable to display system
➢ The system alerts the user or admin.
generated reports)
➢ Use case ends

Precondition First the Administrator, editor or basic users must login to the
system.
Post condition Existing View generated reports in different forms of the guest
house in the system.
Table 11 View generated reports in different forms use case

3.5.4 Sequence Diagram

UML Sequence diagram showing the sequence of interactions among objects and used to
represent or model the flow of messages, events and actions between the objects or components of
a system. In our system the sequence diagrams that we identified and presented are sequence
diagram for registration, login, administrator and editors.

25
Figure 3 Sequence diagram of registration

Figure 4 Sequence diagram of login

26
Figure 5 Sequence diagram for admin

Figure 6 Sequence diagram for editor

27
3.5.5 Activity Diagram
In our Guest House Renting System (GHRS) activity diagram we identified is activity diagram for
the admin. It contains the activities what an admin of the system perform throughout his active
session is displayed in the following activity diagram.

Figure 7 Activity diagram for admin

3.5.6 Analysis of class diagram

Class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, operations (or
methods), and the relationships among objects. In this class diagram the team members try to
describe the types of object in the system and the various kinds of static relationships that exist
among them as well as depicted the detailed understanding of problem domain of the system.
28
These Class diagrams are developed based on the functional requirement. [4] The next diagram is
the class diagram of our guest house renting system which includes the discussed class diagram
points above

Figure 8 Analysis class diagram

29
3.6 System Design
System design is the transformation of the analysis model into a system design model. The
purpose of designing is to show the direction, how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. In this section we
will see the design goals, system decomposition, deployment diagram and database design.

3.6.1 Design Goals

The following are the design goals considered when we develop guest house renting system.

➢ Security: The system authenticates users by using email and password and JWT access
token also the system is secured by using encryption type md5.
➢ Performance: Since the system is web based the deliver response time of the system
should be very fast. It performs in a very satisfying speed.
➢ Availability: This system allows all the authenticated users to access the system
everywhere and anywhere with internet access its 24/7 available over the internet.
➢ Error handling: This system allows preventing or eliminating of error by displaying nice
alert message or the system warns the users who make errors.

3.6.2 System Decomposition

The Crime Analysis and Management System is decomposed into the following sub systems:

➢ Guest house management sub system: - is one of the subsystems in which the
administrator and authenticated editors will perform add, edit, delete view details of a
guest house in the system.
➢ User management sub system: - is one of the subsystems in which the administrator will
perform activation, role edit and view the users of the system.
➢ Update profile sub system: - is one of the subsystems in which the administrator and the
users will update their profile by updating their user name and profile picture.
➢ Cluster guest house sub system: - is one of the subsystems which enables to analyze the
guest house data in the form of clustered by location map.
➢ Generate overview report sub system: - is one of the sub systems which generates the
overview of the guest house data in a graph which makes it easy to analyze and manage
the system.

30
 ➢ Generate pie chart report sub system: - is one of the sub systems which generates the
pie chart report of the of the guest house data in the system which makes it easy to analyze
and manage the system.
➢ Filter and sort sub system: - is one of the subsystems which enables to filter and sort the
represented guest house which is implemented by server pagination and which makes it
easy to analyze and manage the system.
➢ Theme sub system: - is one of the subsystems which enables the users of the system to
change the theme of their dashboard theme as they prefer it to be it has light and dark
mode.

Figure 9 System decomposition diagram

3.6.3 Deployment Modeling

When the system will be deployed, it will be deployed as three tier architecture. At the front end
(client side) there will be the administrator and the users presented the user interface. At the

31
middleware tier (app server) there are a lot of capabilities and business logics provided by the
system all goes in this tier. Finally, at the back end (database) side there will be security
mechanisms in addition to database management system. The following deployment diagram
clearly shows the above description.

Figure 10 Deployment diagram of the system

32
3.6.4 Database Design
In the Crime Analysis and Management System project we used mongodb which is NoSQL
database and from that we used document database which stores data in documents similar to
JSON objects. Each document contains pairs of fields and values. The values can typically be a
variety of types including strings, numbers, Booleans, arrays and even objects.

Figure 11 User modal database of the system

Figure 12 Guest modal database of the system

33
 CHAPTER FOUR

Result and Discussion

4.1 Result
Our system has been tested in order to measure its usability, where the system was tested by
operating on Internet Explorer, Google Chrome and Mozilla Firefox with the local host server.
The aim of the project is to measure the user satisfaction about the proposed system and prove its
usability. The results obtained shows a high percentage of its usability, useful and achieved the
main project target. Also, the user interface prototype of the System is displayed in the following
figures.

Figure 13 User registration form of the system

34
Figure 14 Login form of the system

Figure 15 Home page of the system

35
Figure 16 Guest house view page of the system

Figure 17 A singe guest house detile page

36
 Figure 18 GH uploading stepper form (step 2)

Figure 19 GH uploading stepper form image uploding section

37
Figure 20 Dashbored main page in dark mode

Figure 21 Dashbored main page light mode

38
 Figure 22 Manage users page of the system

Figure 23 GH management page of the system

39
4.2 Discussion
This paper highlights the best practices in building and designing a Guest House Renting System.
In this work, we designed and implemented our project using MERN stack which stands for
mongodb for database as backend node js and express for the server-side business logics and react
for frontend presentation of the application. Along with Material UI, Material UI icons for the user
interface design, leaflet map, super cluster for clustering the guest house rechart for the graph we
used, react data grid for the data grids we used and some other packages. In our system, the UML
offered several diagrams to enable the new functions to be updated and added easily such as use
case, sequence and class diagrams, and user interfaces.

The developed Guest House Renting System will help users who will rent their gust house will
add their guest house to this platform and tenants or users who need this guest house will see the
guest house detailed information and be able to rent guest house from anywhere they are. Along
with the tools that have been used based on the analysis and implementation environment, our
system offered excellent advantages for the support of system development.

40
 CHAPTER FIVE

Conclusion and Recommendation

5.1 Conclusion
In conclusion, the guest house renting system project has successfully achieved its objective of
providing a user-friendly platform for guests to easily rent a variety of guest houses. By developing
a comprehensive database to store guest and property information and creating an intuitive
interface, the system enables guests to browse available properties, view descriptions, check
availability, make reservations, and securely pay for their stays.

For guests, the system provides an easy and convenient way to find and rent various types of
accommodations, ensuring a seamless reservation process. They can browse through available
properties, access detailed descriptions, check availability, make reservations, and securely
complete payment transactions. This eliminates the need for manual arrangements and streamlines
the entire rental process.

Property owners also benefit significantly from the system. They can efficiently manage their
properties and reservations through the centralized database, enabling them to update property
details, monitor availability, and keep track of reservations. This leads to improved property
management and increased customer satisfaction.

By implementing this project, guests can now effortlessly find and rent guest houses for their
desired duration, whether they prefer private rooms, shared rooms, or entire houses. The system
simplifies the reservation process, eliminating the need for time-consuming manual arrangements.
Property owners also benefit from this system as they can efficiently manage their properties and
reservations. The centralized database allows them to easily update property details, track
availability, and monitor reservations, leading to improved property management and customer
satisfaction.

In summary, the guest house renting system project successfully fulfills its purpose of providing
a seamless and efficient platform for guests to rent guest houses. The system's user-friendly
interface, and comprehensive database contribute to a convenient and reliable rental experience
for both guests and property owners.

41
5.2 Recommendation
According to scope of the project the team develops web-based application. The system may have
limitation but in the future the team believes that this system should be fully operational by adding
some functionality that are not included in the proposed system. The team also wants to
recommend this project can be expanded and more automated with additional functionalities by
integrating with many new technologies. Generally, the team recommends being included the
following functionality:

➢ Proper transaction getaway

➢ More advanced UI/UX

42
 References
[1] Guttentag, D. (2015). Airbnb: disruptive innovation and the rise of an informal tourism
accommodation sector. Current Issues in Tourism, 18(12), 1192-1217.

[2] Greene, R. A., Kilgore, M. A., & Osman, A. (2020). The impacts of COVID-19 on rural
tourism: A study on Airbnb bookings in the United States. Journal of Rural Studies, 80, 228-231.

[3] Oskam, J., & Boswijk, A. (2016). Airbnb: The future of networked hospitality businesses.
Journal of Tourism Futures, 2(1), 22-42.

[4] Modern system analysis and design third edition by JEFFERY A. HOFFER, JOEY F.
GEORGE, and JOSEPH S. VALACLCH (for the analysis and design class diagram detail
operation, attribute, inheritance and association.) on December 26/04/2010 EC and On January
1/05/2010 EC.

43
44