CS6P05NI FINAL YEAR PROJECT

Module Code & Module Title

CS6P05NI Final Year Project
Assessment Weightage & Type
40% FYP Final Report Semester
2022 autumn
Project Title: Interim Report
Student Name: Pradip Chapagain
London Met ID: 19031321
College ID: np01cp4a190356
Internal Supervisor: Lekhnath Katuwal
External Supervisor: Ujjwal Subedi
th
Assignment Due Date: 27 Apr
th
Assignment Submission Date: 27 Apr Word
Count (Where Required): 8275
I confirm that I understand my coursework needs to be submitted online via Google Classroom
under the relevant module page before the deadline in order for my assignment to be accepted
and marked. I am fully aware that late submissions will be treated as non-submission and a mark
of zero will be awarded.

Acknowledgement

To begin, I want to express my gratitude to my supervisors, Mr. Ujwal Subedi Sir and Mr.
Lekhnath Katuwal Sir, for their encouragement and motivation in helping me finish the final
report and develop the app. Without their assistance and mentoring, I would not have been able
to complete this report. I'm also grateful to my supervisors for giving me complete freedom to
pursue my research interests and for their unwavering time and support. I was able to research
and write this report much better than expected thanks to consultations and discussions with
supervisors. They also assisted me in gaining a broader perspective. I thank them for giving all
the essential assets for keeping the development of the work smooth. I would also like to thank
Islington College for all the valuable assets and consistent support.
Abstract
This report provides an update on the progress of the final year project, the Room Finder App,
which is based on a mobile app. This is a flutter-based mobile application that allows users to
find the best room for their needs. This app will include features such as pre-room booking,
direct contact between landlord and tenants, and pre-notification of empty rooms so that people
can find a room as soon as possible. It is compatible with all Android devices and will also assist
users by indicating the location of the nearest available room.
This app is simply a method of detecting a rental property or a tenant. The service is available to
both the tenant and the landlord. With the help of this app, users will be able to find all available
rooms to rent with just one click, making it easier for consumers to find rental spaces and
landlords to find the right tenants in the shortest amount of time
Contents
CHAPTER 1: INTRODUCTION
.......................................................................................................................11

1.1 Project Description 1

1.2 Current Scenario 1
1.3 Problem Scenario 2
1.4 Project as a Solution 2
1.5 Aim and Objectives 3
1.5.1 Aim 3
1.5.2 Objective 3
1.6 Structure of the Report 4
1.6.1 Background 4
1.6.2 Development 4
1.6.3 Testing and Analysis 4
1.6.4 Conclusion 4
CHAPTER 2: BACKGROUND 5
2.1 About the End Users 6
2.2 Understanding the Solution 6
2.2.1 Overview of the system 6
2.2.2 Technical terms and definition 6
2.2.2.1 Backend (Node.js) 6
2.2.2.2 Database (MongoDB) 7
2.2.2.3 Frontend (Flutter) 7
2.3 Mobile Application Features 7
2.3.1 Tenants 7
2.3.2 Landlord 8
2.4 Similar Projects 9
2.4.1 Gharbheti Ba 9
2.4.2 Room finder Nepal 10
2.5 Comparisons 11
CHAPTER 3: DEVELOPMENT 12
3.1 Considered Methodologies 13
3.1.1 Rational Unified Process 13
3.1.2 Agile Methodology 13
3.2 Selected Methodology 14
3.2.1 Rational Unified Process 14
3.3 Phases of Methodology 15
3.4 Survey Results 16
3.4.1 Pre- Survey Results 16
3.4.2 Post-Survey Results 19
3.5 Requirement Analysis 22
3.5.1 Planning 22
3.5.1.1. Identification of Interfaces and Constraints 22
3.5.1.2 Review of Project Scope 22
3.5.1.3 Planning the Execution of the Process 23
3.5.2 System Requirement Specifications (SRS) 23
3.5.2.1 Introduction 23
3.5.2.2 Purpose 23
3.5.2.3 Functional Requirements 23
3.5.2.4 Non-Functional Requirements 24
3.5.2.5 Useable Features 24
3.6 Design 25
3.6.1 Use Case Diagram 25
3.6.1.1 Individual Use case diagram 26
3.6.2 Sequence Diagram 30
3.6.2.1 Individual sequence diagram 30
3.6.3 Collaboration diagram 36
3.6.3.1 Collaboration Diagram 36
3.6.3.2 Individual Collaboration Diagram 36
3.6.4 Activity Diagram 40
3.6.4.1 Individual Activity Diagram 40
3.7 Implementation 46
3.7.1 Get Rooms Details 46
3.7.2 Get rooms in certain area define by city 47
3.7.3 Online Payment (khalti integration) 47
3.7.4 Change Password 48
CHAPTER 4: TESTING AND ANALYSIS 49
4.1 Test Plan 50
4.1.1 Unit testing Test plan 50
4.1.1.1 Objectives of testing 50
4.1.1.2 Resources required for testing 50
4.1.1.3 Test Environment 51
4.1.1.4 Unit Test, Test Tasks 51
4.1.2 System testing, Test plan 51
4.1.2.1 Objective of testing 51
4.1.2.2 Resources required for testing 52
4.1.2.3 Test Environment 52
4.2 Unit Testing 53
4.2.1 Register Testing 53
4.2.1.1 Register with Invalid credential 53
4.2.1.2 Register with valid credential 54
4.2.1.3 Invalid Login detail testing 56
4.2.1.4 Valid Login detail testing 57
4.2.1.5 Edit profile testing 59
4.2.1.6 Change password testing 61
4.2.1.7 Add rooms testing 62
4.2.1.8 Shows Added rooms in Home page testing 64
4.2.1.9 Shows Added room details in room detail page testing 65
4.2.1.10 Payment testing 66
CHAPTER 5: CONCLUSION 69
5.1 Legal, Social and Ethical Issues 70
5.1.1 Legal Issue 70
5.1.1.1 The privacy of the users: 70
5.1.1.2 Users data Security 71
5.1.1.3 Protection of intellectual properties: 71
5.1.1.4 Customer protection Laws and Regulations 71
5.1.2 Social Issues 71
5.1.3 Ethical Issues 72
5.1.3.1 Guideline Responsibility 72
5.1.3.2 Non profitable process 72
5.2 Advantages 72
5.3 Limitations 73
5.3.1 Major Services required internet Access 73
5.3.2 Slow performance on old phones 73
5.4 Future Works 73
References 74
Bibliography 74
CHAPTER 8: APPENDIX 75
8.1 Appendix A Pre-Survey 76
8.1.1 Pre-Survey Form 76
8.1.2 Sample of filled Pre-Survey Form 79
6.1.3 Pre–Survey Result 81
8.2 Appendix B: Post-Survey 83
8.2.1 Post – Survey Form 83
8.2.2 Sample of filled post- Survey forms 85
8.2.3 Post survey result 87
8.3 Appendix C: Sample Codes 90
8.3.1 Sample code of the UI 90
8.3.2 Sample Code for the Automations Script 114
8.4 Appendix D: Designs 114
8.4.1 Gantt Chart 114
8.4.2 Work Breakdown Structure 115
8.5 Appendix E: Screenshot of the System 116
8.6 Appendix F: User Feedback 127
8.6.1 User Feedback Form 127
8.6.2 Sample of Filled User Feedback Forms 128
8.7.1 Readings for future work 129
Tables of figures

Figure 1: Review of Gharbheti Ba application .............................................................................................. 9

Figure 2: Review of room finder Nepal application .................................................................................... 10
Figure 3:Pre-survey (i) ................................................................................................................................. 16
Figure 4:Pre-survey (ii) ................................................................................................................................ 17
Figure 5:Pre-survey (iii) ............................................................................................................................... 17
Figure 6: Pre-survey (iv) .............................................................................................................................. 17
Figure 7: Pre-survey (v) ............................................................................................................................... 18
Figure 8: Pre-survey (vi) .............................................................................................................................. 19
Figure 9: Post-survey (i) .............................................................................................................................. 19
Figure 10:Post-survey (ii) ............................................................................................................................ 20
Figure 11:Post-survey (iii) ........................................................................................................................... 20
Figure 12: Post-survey (iv) .......................................................................................................................... 21
Figure 13: Post-survey (v) ........................................................................................................................... 21
Figure 14: Final Use-case Diagram .............................................................................................................. 25
Figure 15: Individual Use Case Registration feature ................................................................................... 26
Figure 16: Individual Use case for Login Feature ........................................................................................ 27
Figure 17: Individual Use case for Tenant Features ................................................................................... 27
Figure 18: Individual Use case for Landlord Features ................................................................................ 28
Figure 19: individual use case for profile and edit profile page ................................................................. 28
Figure 20: Individual Use case for payment ................................................................................................ 29
Figure 21: Individual Use case for Admin Features .................................................................................... 29
Figure 22: Sequence diagram – Login ......................................................................................................... 30
Figure 23: Sequence diagram – Register..................................................................................................... 31
Figure 24: Sequence diagram - Add Rooms ................................................................................................ 32
Figure 25: Sequence diagram - Room booking ........................................................................................... 33
Figure 26: Sequence diagram - Change Password ...................................................................................... 34
Figure 27: Sequence diagram - Payment .................................................................................................... 35
Figure 28: Collaboration – Register ............................................................................................................ 36
Figure 29: Collaboration - Login .................................................................................................................. 37
Figure 30: Collaboration - Add Rooms ........................................................................................................ 37
Figure 31: Collaboration Book rooms ......................................................................................................... 38
Figure 32: Collaboration – Change Password ............................................................................................. 38
Figure 33: Collaboration – Payment ........................................................................................................... 39
Figure 34: Activity diagram - Signup ........................................................................................................... 40
Figure 35: Activity diagram – Login ............................................................................................................. 41
Figure 36: Activity diagram - Add rooms .................................................................................................... 42
Figure 37: Activity diagram- Book room ..................................................................................................... 43
Figure 38: Activity diagram- Change password........................................................................................... 44
Figure 39: Activity diagram - Payment ........................................................................................................ 45
Figure 40: Implementation code (i) ............................................................................................................ 46
Figure 41: Implementation code (ii) ........................................................................................................... 47
Figure 42: Implementation code (iii) .......................................................................................................... 47
Figure 43: Implementation code (iv) .......................................................................................................... 48
Figure 44: Unit test, test environment ....................................................................................................... 51
Figure 45: system test, test environment ................................................................................................... 52
Figure 46: invalid register detail ................................................................................................................. 53
Figure 47: valid register testing .................................................................................................................. 55
Figure 48: unit testing - Invalid login details ............................................................................................... 56
Figure 49: unit -testing login testing with valid details ............................................................................... 58
Figure 50: unit testing-- Edit profile testing ................................................................................................ 59
Figure 51: Unit testing - Edit profile testing ................................................................................................ 60
Figure 52: Unit testing - Change Password ................................................................................................. 61
Figure 53: Unit-Testing- Add rooms testing ................................................................................................ 63
Figure 54: Unit testing - Show added rooms in home screen ..................................................................... 64
Figure 55: Unit Testing - Showing added room Full details ........................................................................ 65
Figure 56: Unit testing - Payment testing ................................................................................................... 68
Figure 57: Appendix A - Pre-survey form 1 ................................................................................................. 77
Figure 58: Appendix A - Pre-survey form 2 ................................................................................................. 77
Figure 59: Appendix A pre- survey form 3 .................................................................................................. 78
Figure 60: Appendix A Filled Pre-survey Form ............................................................................................ 80
Figure 61: Appendix A -pre Survey result ................................................................................................... 82
Figure 62: Appendix B - Post survey form ................................................................................................... 85
Figure 63: Appendix B: Filled Post-Survey form .......................................................................................... 87
Figure 64: Appendix B Post- Survey result .................................................................................................. 89
Figure 65: Gantt chart ............................................................................................................................... 114
Figure 66: Work Breakdown Structure .................................................................................................... 115
Figure 67: Login - UI .................................................................................................................................. 116
Figure 68: Register –UI .............................................................................................................................. 117
Figure 69: Homepage- UI .......................................................................................................................... 118
Figure 70: Add rooms -UI .......................................................................................................................... 120
Figure 71: Room details -UI ....................................................................................................................... 121
Figure 72: Setting page – UI ...................................................................................................................... 122
Figure 73: Profile page UI .......................................................................................................................... 123
Figure 74: Edit Profile UI ........................................................................................................................... 124
Figure 75: Khalti payment Page – UI ......................................................................................................... 125
Figure 76: payment Page -UI ..................................................................................................................... 126
Figure 77: Appendix F - User feedback form ............................................................................................ 127
Figure 78: Appendix F: filled user feedback form ..................................................................................... 128
Tables of Tables
Table 1:Unit Testing resources required for testing
................................................................................... 50
Table 2:unit test, test tasks
.......................................................................................................
.................. 51
Table 3:System testing resources required
................................................................................................ 52
Table 4:Unit testing -Register with Valid Credential
................................................................................... 54
Table 5: unit testing login with invalid detail testing
.................................................................................. 56
Table 6:unit testing - Valid login details testing
.......................................................................................... 57
Table 7: unit testing - edit profile testing
...................................................................................................
59
Table 8:Unit testing - Change password
.....................................................................................................
61
Table 9: Unit testing - Add rooms testing
...................................................................................................
62
Table 10: Unit - Testing Show added room in home page
.......................................................................... 64
Table 11: Unit Testing - Show added room details in room
details page ................................................... 65
Table 12: Unit testing - Payment testing
....................................................................................................
66
Table 13:Unit Testing - Payment testing
.....................................................................................................
67
 CHAPTER 1: INTRODUCTION

CS6P05NI FINAL YEAR PROJECT

1.1 Project Description
This report will provide a detailed overview of a software project called Flutter Android
Application. The software serves as a tool to assist users in finding rental homes or tenants, and
is designed for use by both landlords and tenants. With just one click, users can quickly and
easily identify available rental properties, making it easier for buyers to find suitable properties
and for landlords to find qualified tenants.

Finding office space, rental properties, or apartments can be a challenging task,

particularly for those who do not have the necessary resources or information. In today's
information age, it is essential that everyone has access to the information they need. In
Kathmandu, finding a decent rental home can be particularly challenging. Additionally,
landlords may lose money if their properties remain vacant for extended periods of time. The
aim of this application is to help resolve these issues by providing a platform for tenants and
landlords to interact and find suitable rental solutions.

1.2 Current Scenario

The process of finding a suitable rental property in Kathmandu has proven to be more difficult
than expected, largely due to the city's rapidly growing population. Nepal's population has now
reached 30 million, with around 30% of the country's inhabitants residing in the capital city of
Kathmandu. This high rate of population growth is expected to continue for at least the next five
years, making the search for a quality rental home or apartment in Kathmandu even more
challenging.
1.3 Problem Scenario
With Nepal's population currently at 30 million, finding a quality rental home in Kathmandu has
become a more challenging task than initially anticipated. More than 30% of the country's
population resides in the capital city, exacerbating the issue. Landlords risk losing money if their
properties remain unoccupied for extended periods of time. A significant number of Kathmandu
residents, almost 60%, are dissatisfied with their housing conditions, with issues ranging from
lack of amenities like parking, water, or inadequate room size and quantity, to poor property
locations or excessive rent demands from landlords.

Due to busy work schedules, most Kathmandu residents have limited time to search for suitable
rental properties. As a result, finding an available property quickly that meets their needs is a
significant challenge. Many vacant properties in the city go unnoticed because few people have
the time or resources to search door-to-door. Additionally, landlords may experience financial
losses during the time it takes to find a tenant, particularly if it takes several months.

1.4 Project as a Solution

This software project is designed to address the issues previously mentioned. By enabling users
to locate available rental spaces with just one click, this Android application aims to simplify the
process of finding suitable rental properties for tenants while also assisting landlords in finding
qualified tenants quickly.

This application is solely intended to serve as a resource for tenants seeking rental
homes, and it is open to both tenants and landlords. One of the most significant advantages of
using this application is the time saved, which is beneficial for both parties. The app facilitates
communication between landlords and tenants, providing a solution to the issue at hand.
The application is particularly beneficial for students in Kathmandu, as they make up a
significant proportion of the tenant population. With the help of this app, students will no longer
have to spend time searching for accommodations, streamlining the rental property search
process for them.
1.5 Aim and Objectives

1.5.1 Aim
The primary objective of this project is to create a reliable and user-friendly Android application
that will assist customers in finding affordable rental accommodations that meet their specific
requirements.

1.5.2 Objective
The objectives of this project can be summarized as follows:

1. To improve the process of searching for rental accommodations so that users can find
available rooms quickly and easily.

2. To assist users in finding the rental property that best meets their needs and preferences.
3. To provide landlords with an efficient platform for finding suitable tenants and filling
vacant rental properties
1.6 Structure of the Report
1.6.1 Background

The background section of the report provides details about the target audience for the project,
including any relevant technical terminology associated with the project and the proposed
solution.

1.6.2 Development

This chapter delves into the various stages involved in the development of the project. It includes
an overview of the different methodologies that were considered, the selection process for the
chosen methodology, an analysis of the selected methodology, requirements analysis, design, and
development implementation. Additionally, the chapter provides a detailed examination of the
results from pre- and post-project surveys.
1.6.3 Testing and Analysis
The Testing and Analysis phase encompasses the test strategies and test cases that were
employed during the project. Two types of testing scenarios, namely unit tests and machine tests,
were utilized. Additionally, the chapter provides an in-depth analysis of critical aspects of the
project.

1.6.4 Conclusion
This chapter contains information pertaining to the assumptions made in the report, an analysis
of the implications of the project, and suggestions for potential future improvements.
 CHAPTER 2: BACKGROUND

2.1 About the End Users

The objective of this project is to develop a reliable Android application that helps users find
suitable and affordable rental accommodations. The application is designed to be used by both
tenants searching for a room and landlords providing a room. By utilizing this application, users
can save time and reduce travel costs associated with physical agents. The service is open to both
landlords and tenants and facilitates communication between them.
2.2 Understanding the Solution
2.2.1 Overview of the system
This initiative aims to address the challenge of finding suitable rental properties in Kathmandu
due to the city's growing population. The Android application developed under this project will
simplify the process of locating rental spaces for customers and enable landlords to find suitable
tenants quickly. With just one click, users can access all available rooms for rent through this
application. However, it should be noted that this application is intended solely as a resource to
assist tenants in finding rental homes.

2.2.2 Technical terms and definition

2.2.2.1 Backend (Node.js)

Node.js is a server-side open source framework that allows JavaScript code execution. It is
commonly used for real-time applications such as chat, news feeds, and web push notifications
due to its ability to maintain a constant connection from the browser to the server. Node.js
operates asynchronously and is event-driven, processing incoming requests in a continuous event
stack and sending small requests one after the other without waiting for responses. MongoDB is
an open-source document database with a flexible schema that utilizes a horizontal scale-out
design. Unlike traditional relational databases, MongoDB stores data in collections and
documents, which are made up of key-value pairs. This NoSQL database is capable of handling
large volumes of data and has a sizable global development community.

2.2.2.3 Frontend (Flutter)

Flutter is a lightweight and speedy framework created using the Dart programming language.
Unlike other frameworks, Flutter generates the user interface directly in the canvas of the
operating system instead of utilizing a native framework (2022,TutorialsPoint).

2.3 Mobile Application Features

Flutter is a cross-platform app development framework that allows developers to create apps for
both iOS and Android platforms. Using Flutter, you have created a room locator application that
caters to two different types of users: tenants and landlords. Some of the key features of this
mobile application are as follows:
2.3.1 Tenants
• Tenant registration feature is available.
• Login and password reset feature is provided for tenants.
• Tenants can view the location of available rooms and contact landlords directly via
contact numbers.

• The app allows tenants to view their own profile.

• Editing of tenant profile is possible.
• Tenants can find and book rooms easily and even cancel their booking in case of personal
issues.

2.3.2 Landlord
• Landlords can register for the system.
• Landlords can log in to the system and reset their password if needed.
• Landlords can add photos of their rooms.
• Landlords must add details about their rooms, such as the price, location, and contact
information.

• Landlords can view their own profile.

• Landlords can edit their profile.
2.4 Similar Projects
2.4.1 Gharbheti Ba

Figure 1: Review of Gharbheti Ba application

Gharbheti Ba is an Android application that serves as a platform for tenants and landlords to find
rental spaces and renters. Landlords can effortlessly add their properties or rooms, while
customers can use the app to browse for available rental spaces. The app enables landlords to
find suitable renters for their properties.

2.4.2 Room finder Nepal

 Figure 2: Review of room finder Nepal application

The Room Finder is an Android application that connects tenants and landlords looking for
rental spaces. Users can easily add their properties or rooms and search for the best matches.
This platform helps tenants find the perfect rental space and landlords find the most suitable
tenants quickly and efficiently.

2.5 Comparisons
Room Finder Nepal is an application designed to assist individuals in finding rental properties or
renters, with the service being accessible to both tenants and landlords. This app is primarily
intended for valley residents and can be utilized for various purposes such as renting a room for
living or official purposes, as well as renting out a property. By utilizing this application, users
can easily find available rooms to rent with just one click, saving time for both landlords and
renters.

The app includes a search bar feature that enables users to filter search results by location, and
an advanced booking system that allows users to make advance or full payments for bookings.
The main goal of this application is to provide a solution to the problem of finding a rental
property or renter, and to save time for all parties involved. Landlords can benefit from a
consistent source of income, while tenants can find suitable rental spaces in the shortest amount
of time possible.
 CHAPTER 3: DEVELOPMENT

3.1 Considered Methodologies

3.1.1 Rational Unified Process
The Rational Unified Process (RUP) is an agile software development methodology that divides
the project life cycle into four phases. All six core development disciplines, namely business
modeling, requirements, analysis and design, implementation, testing, and deployment, are
practiced in each phase. However, certain processes are more critical and time-consuming at
each stage. For instance, business modeling is generally conducted in the early stages of
development, such as inception and elaboration (Study.com, 2022). To move on to the next
phase of the project, each of the four stages must achieve a primary objective.

Reason for Considering:

• Improves feature accuracy.

• Widely recognized as the standard software development method in the industry.
• Produces precise outcome features through feature-driven methodology.
3.1.2 Agile Methodology
The Agile methodology is a project management approach that breaks down a project into
stages, requiring constant collaboration with stakeholders and continuous improvement at each
step. Teams follow a process of planning, executing, and evaluating throughout the work.
Reason for Considering:

1. Reduces technical debt

2. Results in higher quality production
3. Enables predictable delivery dates
4. Improves stakeholder engagement

3.2 Selected Methodology

3.2.1 Rational Unified Process
The Rational Unified Process (RUP) is an agile software development methodology that divides
the project life cycle into four distinct phases. The six core development disciplines, including
business modeling, requirements, analysis and design, implementation, testing, and deployment,
are practiced at each stage. However, certain processes are given more emphasis and require
more time during each phase. For example, business modeling is typically done during the early
stages of development, such as inception and elaboration. Before the project can proceed to the
next phase, each of the four stages has a primary objective that must be achieved.

Reason for Selecting

1. Provides detailed understanding of the project structure

2. Enables accurate tracking of project progress and estimation of completion time within
the given deadline
3. Ensures that important project development phases such as inception and elaboration,
research, resource work, prototype and UI designs are not missed
4. Focuses on collecting and improving resources during project development rather than
solely focusing on development and deployment

3.3 Phases of Methodology

The Rational Unified Process (RUP) is a software development methodology that involves four
major phases.

• The first phase is Inception, where the project is defined, and the initial scope and
feasibility are determined.

• The second phase is Elaboration, where research, analysis, and design are conducted to
determine the project's specific requirements and scope.

• The third phase is Construction, where the actual development and implementation of the
software takes place.

• The final phase is Transition, where the software is deployed, tested, and delivered to the
end-users.

The Rational Unified Process (RUP) consists of four major phases with specific objectives to be
achieved in each phase. They are:

Inception Phase: During this phase, the project requirements and goals are gathered, and a
project plan is created. The plan includes features, risk assessment, resource scheduling, cost and
time estimation, and the creation of a prototype.

Elaboration Phase: This phase is focused on analyzing the problem, researching system features,
and evaluating similar systems. The system architecture is designed and the project plan is
refined based on the research findings.

Construction Phase: In this phase, the system is developed using Node.js as a backend and
Flutter for the frontend. The project plan is optimized with the acquired resources, and testing
and prototyping are also carried out.

Transition Phase: In the final phase, beta testing is performed, user feedback is collected, and the
system documentation is improved. Any necessary improvements to the system are made based
on the feedback received.

3.4 Survey Results

3.4.1 Pre- Survey Results

A comprehensive survey of professionals and consumers, primarily end-users, was conducted

during the early stages of the project's development. The survey aimed to understand the
project's demand, required features, and real-time evaluation from industry experts.

Figure 3:Pre-survey (i)

Figure 4:Pre-survey (ii)

Figure 5:Pre-survey (iii)

Figure 6: Pre-survey (iv)

Figure 7: Pre-survey (v)

Figure 8: Pre-survey (vi)

3.4.2 Post-Survey Results

Ensuring customer satisfaction is crucial in the development of any system. Meeting the user's
functional and non-functional requirements, as well as creating good resources for the customer,
are key factors in achieving this. In order to gather information about the system's potential
benefits, drawbacks, and future add-ons, a post-survey was conducted. The survey was
distributed among IT students and the general public. The project team will rely heavily on
community feedback and surveys for all future work.
 Figure 9: Post-survey (i)

Figure 10:Post-survey (ii)

Figure 11:Post-survey (iii)

 Figure 12: Post-survey (iv)

Figure 13: Post-survey (v)

3.5 Requirement Analysis

Requirements analysis, also called requirements engineering, is a crucial and collaborative
process that involves the integration of technical expertise in software, hardware, and human
factors, along with interpersonal skills. Its main objective is to identify and document the needs
and expectations of a new product. To achieve this, continuous communication with the
product's stakeholders and end-users is required in order to clarify expectations, address
conflicts, and capture all of the product's essential requirements (simplilearn, 2022).

To achieve a shared understanding of the final product's vision with customers, businesses must
engage in a challenging task. This involves a collaborative effort among key stakeholders,
software developers, end-users, and customer managers to perform a business requirements
analysis. The goal of this analysis is to determine what the product should accomplish, establish
expectations, resolve conflicts, and document all key requirements. This process is carried out at
the beginning of a project to ensure that the final product meets all specifications (simplilearn,
2022).
3.5.1 Planning
The planning phase is a critical organizational process where project priorities are determined,
and a comprehensive proposal is developed. The following are the main tasks involved in the
planning process:
3.5.1.1. Identification of Interfaces and Constraints
1. The system requires a significant amount of carefully curated training data.
2. Administrator privileges are necessary for users to utilize the system.
3. Manual configuration is needed for IP addresses, protocols, email addresses, and
passwords.
4. Ethical and legal considerations must be taken into account.
3.5.1.2 Review of Project Scope
1. The aim of this project is to enhance the room search process to facilitate faster and more
efficient room finding for the user.
2. Timeframe and user validation of the system are the key constraints affecting the project.
3. The RUP methodology is being utilized for this project.
3.5.1.3 Planning the Execution of the Process

1. To create an effective collection tool in this process, the primary requirements include an
online mass survey and supervisor feedback.

2. Beta users' feedback, gathered through post-survey analysis, is an essential part of this
process. It helps to identify potential benefits and drawbacks of the system, as well as
possible add-ons.

3. The creation of a useful questionnaire is a critical part of the study initialization,

requiring a separate process dedicated solely to this task.

3.5.2 System Requirement Specifications (SRS)

3.5.2.1 Introduction
The System Requirements Specification (SRS) is a collection of documents that outlines the
features and behaviors of a software application or system. The main purpose of the SRS is to
describe the intended functionality of the system in order to meet the needs of the customer and
its users. The SRS typically includes various elements, such as functional requirements, non-
functional requirements, constraints, and performance requirements. By defining these elements,
the SRS provides a clear understanding of the system's scope and expectations, which can be
used as a reference throughout the development process (inflectra, 2022).

3.5.2.2 Purpose
The purpose of creating a System Requirements Specification (SRS) document is to provide
detailed information about the various functionalities of Nep Room's system that are necessary
for the proper functioning of its features, and to ensure that they meet the needs and expectations
of its end-users.

3.5.2.3 Functional Requirements

Functional requirements are the specific behaviors and functions that a system must exhibit. In
the case of this app, the functional requirements include:

1. Login and registration functionality

2. Ability to post details about available rooms
3. Capability to upload pictures of rooms while posting
4. Ability for users to search and view available rooms based on their preferences
5. Direct contact feature for users to communicate with landlords.
3.5.2.4 Non-Functional Requirements
Non-functional requirements define the quality attributes and characteristics of a software
system, including aspects such as security, usability, and portability. In the case of this system,
the following non-functional requirements are essential:

1. Ensuring the safety and security of user data

2. Providing accurate and detailed information about available rooms
3. Enabling users to easily access and read room descriptions.
3.5.2.5 Useable Features
The system offers a number of user-friendly features, including:

1. A simple and straightforward login interface for users.

2. A search function that allows users to find rooms in specific locations.
3. A contact number for the landlord is provided on the room details page, enabling tenants
to directly reach out to the property owner.
3.6 Design
3.6.1 Use Case Diagram

Figure 14: Final Use-case Diagram

3.6.1.1 Individual Use case diagram

1. Registration features individual Use Case diagram

Figure 15: Individual Use Case Registration feature

2. Login features individual Use Case diagram

 Figure 16: Individual Use case for Login Feature

3. Tenant feature individual Use case diagram

Figure 17: Individual Use case for Tenant Features

4. Landlord feature individual Use case diagram

Figure 18: Individual Use case for Landlord

Features

5. Landlord and tenant feature individual Use case diagram

 Figure 19: individual use case for profile and edit profile
page

6. Landlord and tenant payment feature individual Use case diagram

Figure 20:
Individual Use case for payment
7. Admin feature individual Use case diagram
 Figure 21: Individual Use case for Admin Features

3.6.2 Sequence Diagram

3.6.2.1 Individual sequence diagram
1. Individual sequence diagram for login

Figure 22: Sequence diagram – Login

This diagram illustrates the Login activity flow. Initially, the user inputs their credentials into the
Login user interface (UI). The Login UI then interacts with the backend functionality to
authenticate the user's details and validate them. Based on the validation results, the backend
returns a response to the Login UI. The flow of events is depicted using lifelines, which are
shown as vertical lines originating from the user and the backend elements.

2. Individual Sequence diagram for register

 Figure 23: Sequence diagram – Register

This sequence diagram illustrates the flow of the Register User activity. Initially, the user inputs
their information in the Register UI, which then communicates with the backend functionality to
validate the data. Based on the validation results, a response is returned. The lifeline is
represented by the vertical column underneath the user and each element involved in the process.

3. Individual Sequence diagram for Add rooms

Figure 24: Sequence diagram - Add Rooms

This sequence diagram illustrates how the Add Rooms activity flows. The user enters details
about the room, such as the number of rooms, preferences, BHK, and price, into the Add Rooms
UI. The UI then communicates with the backend functionality to validate the information and
provide a response. The lifeline is indicated by the column below the user and elements.

CS6P05NI FINAL YEAR PROJECT

4 l Sequence diagram for booking rooms

Figure 25: Sequence diagram - Room booking

This diagram illustrates the sequence of the room booking activity. When the user clicks on the
"Book" option on the room details page, the Room Details UI communicates with the backend
functionality to validate the booking request. Based on the validation results, a response is
generated and returned. The lifeline is represented by the vertical column under the user and the
respective system elements involved in the process.

5 l Sequence diagram for change password

 Figure 26: Sequence diagram - Change Password

This diagram depicts the flow of the Change Password activity. The user first navigates to the
Change Password UI and inputs the old and new passwords. The Change Password UI then
communicates with the backend functionality, checks the validation, and returns a response
based on the results. The lifeline is determined by the column below the user and element.

6 l Sequence diagram for Payment

 Figure 27: Sequence diagram - Payment

3.6.3 Collaboration diagram

A Collaboration diagram is a UML diagram used to depict the interactions and relationships
among software objects. The key components of the Collaboration diagram include:

• Objects: Represented by rectangular boxes with the name of the object written inside.
Objects are named according to the naming convention of the class they belong to.

• Actors: Represented by human figures and are included in the diagram to show the
involvement of external entities in the system. Actors have a name and role in the
diagram.

• Links: The solid line that connects two elements is known as the link. Links indicate
where messages can be sent.

• Messages: Represented by solid lines with arrows indicating the direction of

communication. Messages carry information from one object to another.

3.6.3.1 Collaboration Diagram

3.6.3.2 Individual Collaboration Diagram
1. Sign Up Collaboration diagram

Figure 28: Collaboration – Register

2. Login Collaboration diagram

Figure 29: Collaboration - Login

3. Add Rooms Collaboration diagram

Figure 30: Collaboration - Add Rooms

4. Book rooms Collaboration diagram

Figure 31: Collaboration Book rooms

5. Change Password Collaboration diagram

 Figure 32: Collaboration – Change Password

6. Payment Collaboration diagram

Figure 33: Collaboration – Payment

3.6.4 Activity Diagram

3.6.4.1 Individual Activity Diagram
1. Sign up Activity Diagram
 Figure 34: Activity diagram - Signup

2. Login Activity Diagram

 Figure 35: Activity diagram – Login

3. Add Rooms Activity Diagram

 Figure 36: Activity diagram - Add rooms

4. Add Rooms Activity Diagram

 Figure 37: Activity diagram- Book room

5. Change Password Activity Diagram

 Figure 38: Activity diagram- Change password

4. Payment Activity Diagram

 Figure 39: Activity diagram - Payment

3.7 Implementation
3.7.1 Get Rooms Details

Figure 40: Implementation code (i)

3.7.2 Get rooms in certain area define by city

Figure 41: Implementation code (ii)

3.7.3 Online Payment (khalti integration)

Figure 42: Implementation code (iii)

3.7.4 Change Password

 Figure 43: Implementation code (iv)

CHAPTER 4: TESTING AND ANALYSIS

The purpose of testing this system is not limited to detecting and explaining the importance of
bugs. It is aimed at reducing risks by proactively identifying and assisting in the resolution of
issues that can have a significant impact on the software user.
4.1 Test Plan
The purpose of the test plan is to define the scope, approach, resources, and schedule of all
testing activities for the project. The plan specifies the items and features to be tested, as well as
the types of testing to be conducted. The project will involve two types of testing:
1. Unit testing: This testing technique focuses on verifying individual modules to identify any
bugs or issues, typically conducted by the developer.
2. System testing: This testing is based on black-box testing, evaluating the complete system
to ensure that it meets the functional and non-functional requirements.
4.1.1 Unit testing Test plan
4.1.1.1 Objectives of testing
The objective of testing is to ensure that the features and modules of the project are
functioning properly. The purpose is to identify and fix any bugs or issues before integrating
the modules into the system, so that there are no problems when the software is used in the
real world.
4.1.1.2 Resources required for testing

Resources Description
Server Need a database server which is installed with mongo dB server
Android Mobile At least one android phone or android e
mulator which has higher version than oreo

Network Connection to the internet

Table 1:Unit Testing resources required for testing

4.1.1.3 Test Environment
A mobile phone with internet connectivity is required to access a system's middleware,
such as an API management system, and another middleware called Docker, to connect to
the database.

Figure 44: Unit test, test environment

4.1.1.4 Unit Test, Test Tasks

Test No Test case Description

1. Wrong login details testing Testing the user with wrong
details.
2. Valid login testing Testing when user logs in with
valid details
3. Registration with valid details Testing when user register with
testing valid details
Table 2:unit test, test tasks

4.1.2 System testing, Test plan

4.1.2.1 Objective of testing
The aim of this testing is to evaluate the system from the end user's perspective, ensuring that the
application has the required functionalities and features that meet the user's needs.

4.1.2.2 Resources required for testing

Resources Description
Server Need a database server which is installed with mongo dB server

Android Mobile At least one android phone which has higher version than oreo

Network Connection to the internet

Table 3:System testing resources required

4.1.2.3 Test Environment

A mobile device with internet connectivity is required, along with middleware components such
as an API management system and Docker for database access.
 Figure 45: system test, test environment

4.2 Unit Testing

4.2.1 Register Testing
No pre case required
S.N Test Case Expected Result Actual Result Status
1 User input valid name, email, User can register data Pass
password, contact, gender in database and can
and date of birth login User is able to register
data in database and
can
login
2 User leaves all field empty Popup error message Pass
Error message should is shown for all the
be displayed to warn fields that are empty
user to fill which field is
empty

2 User leaves any one field Pass

empty out of four fields User cannot register User is not registered
and error message is at all and cannot login.
displayed Popup

message is displayed
for only the empty
field
3 User cannot register User cannot register Pass
User inputs password less with password less than and pop is shown to
than 6 characters and 6 characters warn the user
doesn’t contain a special
character
4 User input the same email User cannot register Pass
and tries to register with same email User cannot register
with the same email.
Duplicate email
cannot be entered
Logging In User:
Pre-Case: User must have registered an account
S.N Test Case Expected Result Actual Result Status
1 User is able to login Pass
User login with the valid User must be allowed
email and password to login
2 Invalid email or password is Pass
provided User cannot login with User is not able to
invalid user email or login with invalid
password email and password.
3 User login with empty fields Pass
User cannot login and User is not able to
error message is login and a pop up is
displayed displayed to the user
Editing Profile
Pre-Case: User must be logged in
S.N Test Case Expected Result Actual Result Status
1 Updating the profile of the Pass
user with valid values The user must be able The user can edit the
to edit the profile profile and the new
name, email and data are stored in the
avatar database.
2 Updating the profile of the Pass
user with invalid / empty The user cannot edit The user is not able
values his/her profile and an to edit his/her profile
error message should and and error
be displayed message is displayed
Updating Password
Pre-Case: User must be logged in
S.N Test Case Expected Result Actual Result Status
1 User provides empty The user is not able Pass
values for updating The user should not to update password
password be able to update and an error
password and an error message is displayed
message should be
displayed

2 User provides invalid The user is not able Pass

values for updating The user should not to update password
password be able to update and an error
password and an error message is displayed
message should be
displayed
3 User provides valid values Pass
for updating password The user must be able The user is able to
to update their update their
password password
Posting Rent Floors
Pre-Case: User must be logged in
S.N Test Case Expected Result Actual Result Status

1 Posting rent floors with Pass

invalid details User shouldn’t be able User is not able to
to post rent floor and post rent floor and an
an error message error message is
should be displayed displayed
2 Posting rent floors with Pass
empty details User shouldn’t be able User is not able to
to post rent floor and post rent floor and an
an error message error message is
should be displayed displayed
3 Posting rent floors with valid User should be able to User is able to post Pass
details post rent floor rent floor

Managing Rent floors

Pre-case: User must be logged in
S.N Test Case Expected Result Actual Result Status
1 Updating rent floor with User is not able to Pass
invalid/empty values User should not be update the rent floor
able to update the rent and an error
floor and an error message is displayed
message should be
displayed
2 Pass
Updating rent floor with valid User should be able to User is able to update
values update the rent floor the rent floor
3 Deleting the rent floor Pass
User should be able to User is able to delete
delete the particular the particular rent
rent floor floor

4 Changing availability status Pass

of rent floor User should be able to User is able to
change the availability change the
status of particular rent availability status of
floor particular rent floor
Adding frequently asked questions
Pre-case: User must be logged in
S.N Test Case Expected Result Actual Result Status

1 Posting FAQs with invalid Pass

details User shouldn’t be able User is not able to
to post FAQs and an post FAQs and an
error message should error message is
be displayed displayed
2 Posting FAQs with empty Pass
details User shouldn’t be able User is not able to
to post FAQs and an post FAQs and an
error message should error message is
be displayed displayed
3 Pass
Posting FAQs with valid User should be able to User is able to post
details post FAQs FAQs

View Rent floor details

Pre-case: User must be logged in
S.N Test Case Expected Result Actual Result Status
1 View rent floor details Pass
User must be able to User is able to view
view details of the details of the rental
rental spaces spaces
2 User must be able to User is able to view Pass
View availability status of
rent floor view availability status availability status of
of rent floor rent floor
3 View FAQs of the rental Pass
space User must be able to User is able to view
view the FAQs of the FAQs of the rental
rental space space

4 Contact the landlord Pass

User must be able to User is able to
contact the landlord via contact the landlord
phone, message and via phone message
email and email
Searching for rent floors
Pre-case: User must be logged in
S.N Test Case Expected Result Actual Result Status
1 Searching for rent floors via Pass
address keyword User must be to User is able to search
search for rent floors for rent floors via
via address keywords address keywords
and available rent and available rent
floors should be floors are displayed
displayed displayed
2 Searching for rent floors via User must be to Pass
cities
search for rent floors User is able to search
via cities namely : for rent floors via
Kathmandu, cities namely:
Bhaktapur, Lalitpur and Kathmandu,
available rent floors Bhaktapur, Lalitpur
should be displayed and available rent
floors are displayed
displayed
3 Pass
Searching for rent floors via User must be able to User is able to
Google Maps browse for rent floors browse for rent floors

via Google maps and

via Google maps and the available rent
the available rent floors are displayed
floors should be on Google maps
displayed on Google
maps

Making payments for rent floors

Pre-case: User must be logged in
S.N Test Case Expected Result Actual Result Status
1 Make payments without User is not able to Pass
invalid Khalti details User should not be able proceed to make
to proceed to make payments and a
payments and and message is displayed
message should be
displayed

2 Make payments with valid Pass

User should be able to User is able to make
Khalti details make payment for the payment for the rent
rent floor floor
Logging out
Pre-case: User must be logged in
S.N Test Case Expected Result Actual Result Status

1 Logging out of system Pass

User must be able to User is able to log out
log out of the system of the system
CHAPTER 5: CONCLUSION
The Nep Room application is designed to help users find rental properties or tenants through an
intuitive interface. Developed with Flutter for the frontend and Node.js for the backend, the
application incorporates all the necessary functional, non-functional, and usable requirements.

During the development of this project, valuable experience was gained in working with Flutter,
Node.js, and Dart programming, which will prove useful in future projects. Time management
was also an important consideration during the project, with meticulous planning ensuring that
the project was completed on schedule.

The Rational Unified Process (RUP) was used as the software development methodology, which
proved to be effective in successfully completing the project. Overall, the Nep Room application
represents a significant achievement in software development, providing an intuitive and
effective solution for users seeking rental properties or tenants.

5.1 Legal, Social and Ethical Issues

5.1.1 Legal Issue
Legal issues pertain to matters that are governed by the laws of a country, and violating these
laws may result in legal action, the decision of which is determined by the court of justice. When
developing the project, potential legal issues that may affect the user were taken into
consideration. These include:
5.1.1.1 The privacy of the users:
User privacy is a major legal concern for many applications today, as misuse of user data can
lead to legal action. Therefore, when developing the project, legal issues were taken into
consideration, including the importance of protecting user privacy. The application's Privacy
Policy was provided to the user, outlining the types of data that would be collected and how it
would be used to enhance the user's experience. Only users who agreed to the Privacy Policy and
Terms and Conditions were granted access to the application. Additionally, the content posted on
the event page is reviewed by staff, and any content that violates the community guidelines is
promptly removed.
5.1.1.2 Users data Security
The application collects and stores information related to tenants and landlords in a secure and
confidential manner. Users' data can be utilized for more integrative services. Personal
information such as phone numbers, email addresses, and names are also included in the app.
Additionally, the application displays visual data of the landlords, such as their property listings,
which enables tenants to contact them directly via phone number if they are interested in a
particular property.

5.1.1.3 Protection of intellectual properties:

The Nep Room application is a new and unique room finding application in Nepal. The
development of the application followed all laws and regulations regarding intellectual property,
ensuring that no violations occurred. The application's design is entirely original and was not
copied from any other sources, ensuring its uniqueness and compliance with legal requirements.

5.1.1.4 Customer protection Laws and Regulations

During the development of this application, the team took into account the Customer Protection
Act of Nepal to ensure that the customers were protected. The application was designed in a way
that ensures that user data is protected and privacy is maintained. Additionally, the team also
considered the regulations set forth by the Computer Association of Nepal to ensure compliance
with industry standards.

5.1.2 Social Issues

“Social issues refer to concerns or problems that impact individuals or communities within a
given society.”
This project does not appear to raise any social concerns or contribute to any discriminatory
practices. The project is designed to assist the public in finding rental properties, and it is
accessible to people from all walks of life. The application does not discriminate on the basis of
race or any other personal characteristic. Additionally, since the application is beneficial to both
landlords and tenants, it is not expected to have any negative effects on society.

5.1.3 Ethical Issues

"Ethical issues involve questions about the morality and principles underlying a particular
action or decision, and whether it aligns with accepted standards of right and wrong."
5.1.3.1 Guideline Responsibility
The company is responsible for ensuring that the user and building details recorded in the system
are not misused. The staff members are not authorized to remove any content or block any user
from using the application, unless there has been a violation of the community guidelines.

5.1.3.2 Non profitable process

The application is designed to not generate profit from any actions taken within the system, and
there are measures in place to prevent black market activities. The main purpose of the
application is to make it easy for tenants to find rooms without any complications.

5.2 Advantages
Some benefits of using this application include:

• The system is user-friendly and easy to set up. It does not require complex configurations
or updates.
• The application helps renters find rental properties and landlords find suitable tenants
quickly and efficiently.
• The application focuses on solving a problem and saves time for both renters and
landlords.

5.3 Limitations
In addition to its benefits, this application also has some limitations that may be addressed in the
future. These limitations are as follows:
5.3.1 Major Services required internet Access
The primary limitation of this application is its dependence on internet connectivity. The
majority of the application's services, such as adding buildings, viewing room status, logging in,
and registering, require internet access. This means that the user cannot access these services
without an internet connection. However, this limitation is common among many modern
applications and is expected to improve as technology advances.
5.3.2 Slow performance on old phones
Older phones may have hardware and software limitations that could affect their performance
when using the application, making it less accessible to a wider audience. Users with older
versions of Android or iOS may encounter issues such as slow data loading, system
communication failure, and animation failure, limiting their ability to use the application
effectively.

5.4 Future Works

The current project outlined in the proposal has been completed successfully according to user
feedback and responses, with many users expressing satisfaction with the system and its real-
time assistance. However, there are several future tasks that will be undertaken to improve the
application's user-friendliness, including:

• The addition of a chat feature to facilitate interaction between tenants and landlords.
• The creation of a webpage to promote and support the application.
• The inclusion of additional features and improvements to the application's design to make
it more attractive and user-friendly.
• The implementation of AI-based recommendation systems to enhance the user experience.
References
Chauhan, H., Gupta, D., Gupta, S. and Verma, V., 2019. On rent—an android mobile
application. Journal of Computational and Theoretical Nanoscience, 16(10), pp.4400-4405.
Voumick, D., Deb, P., Sutradhar, S. and Khan, M.M., 2021. Development of Online Based Smart
House Renting Web Application. Journal of Software Engineering and Applications, 14(7),
pp.312-328.
Karki, J., Matthewman, S. and Grayman, J.H., 2022. Nayã Ghar (A new house): examining post-
earthquake housing reconstruction issues in Nepal. International Journal of Disaster Risk
Reduction, 78, p.103116.
Sawant, A.A., Bari, P.H. and Chawan, P.M., 2012. Software testing techniques and
strategies. International Journal of Engineering Research and Applications (IJERA), 2(3),
pp.980-986.
Anwar, A., 2014. A review of rup (rational unified process). International Journal of Software
Engineering (IJSE), 5(2), pp.12-19.
Lin, Y.L. and Lee, T.J., 2009. The impacts of the online reservation system in London city
hotels. Journal of Hospitality Marketing & Management, 19(1), pp.82-96.
Thapa, D., Budhathoki, N.R. and Munkvold, B.E., 2017. Analyzing crisis response through
actor-network theory: The case of Kathmandu living labs. Communications of the Association
for Information Systems, 41(1), p.19.
Mishra, A.K. and Shah, S.K., 2018. Estimating housing unit for low income group of people in
Kathmandu, Nepal. Nolegein Journal of Operafions Research & Management, 1(2), pp.16-27.
Shrestha, R., 2016. Business plan: student housing in Kirtipur, Nepal.
Gyaba, R.K., 2010. Tax System in Nepal (Contribution of Corporate Tax on Income
Tax) (Doctoral dissertation, Faculty of Management).

CHAPTER 8: APPENDIX
8.1 Appendix A Pre-Survey
8.1.1 Pre-Survey Form

Figure 57: Appendix A - Pre-survey form 1

Figure 58: Appendix A - Pre-survey form 2
 Figure 59: Appendix A pre- survey form 3

8.1.2 Sample of filled Pre-Survey Form

 Figure 60: Appendix A Filled Pre-survey Form

6.1.3 Pre–Survey Result

 Figure 61: Appendix A -pre Survey result
8.2 Appendix B: Post-Survey
8.2.1 Post – Survey Form
 Figure 62: Appendix B - Post survey form

8.2.2 Sample of filled post- Survey forms

 Figure 63: Appendix B: Filled Post-Survey form

8.2.3 Post survey result

Figure 64: Appendix B Post- Survey result
8.3 Appendix C: Sample Codes
8.3.1 Sample code of the UI
1. Add room UI code
2. Home page UI
3. Room details
4. Khalti Payment page
8.3.2 Sample Code for the Automations Script

8.4 Appendix D: Designs

8.4.1 Gantt Chart
A Gantt chart is a useful tool for project management, particularly for complex tasks. It
displays timelines and tasks in a horizontal bar chart that shows start and finish dates,
dependencies, scheduling, and deadlines. It also allows for tracking the progress of each
stage of the project, identifying task owners, and ensuring that the project remains on
schedule. Gantt charts are particularly helpful for large teams with multiple stakeholders
involved, as they provide a clear overview of the project's progress and help to ensure that
everyone stays on track.

Figure 65: Gantt chart

8.4.2 Work Breakdown Structure

A Work Breakdown Structure (WBS) is a project management technique that can
simplify the management of complex, multi-step projects. This technique involves
breaking down a large project into smaller, more manageable components, which can
be used to plan, execute, and monitor project progress.
The WBS enables project managers to assign specific roles and responsibilities to
team members more easily. By dividing the project into smaller tasks, different team
members can work on different aspects of the project simultaneously, resulting in
increased team productivity and a simplified project management process. By tracking
progress at each stage of the project, managing costs, and making informed decisions,
project managers can stay on track and adapt to any required changes.
The primary goal of a WBS is to make complex projects more manageable by
breaking them down into smaller, more attainable tasks. This technique typically starts
with the project's overall objective and successively breaks it down into smaller, more
specific sub-tasks until each task is small enough to be easily managed by an
individual or team. The WBS ensures that all project requirements are identified,
estimated, and tracked, and that all project deliverables are delivered on time, within
budget, and to the required quality standards.

Overall, the WBS is an essential tool for effective project management, providing
project managers with a clear and structured approach to managing complex projects.
The WBS improves communication between team members, enhances project
transparency, and enables project managers to make informed decisions throughout
the project's life cycle.
The WBS is not only useful for project managers but also for team members. By
breaking down the project into smaller tasks, each team member has a clear
understanding of what they need to do and how their contribution fits into the bigger
picture. This helps to ensure that everyone is on the same page and working towards
the same goal.
The WBS can also help to identify potential risks and challenges before they become
problems. By breaking down the project into smaller tasks, project managers can
identify potential roadblocks and address them before they become critical. This
proactive approach can save time, money, and resources in the long run.

Another benefit of using a WBS is that it allows project managers to prioritize tasks
based on their importance and urgency. This helps to ensure that critical tasks are
completed on time, and the project stays on track. By having a clear understanding of
the project's priorities, project managers can make informed decisions about resource
allocation and ensure that everyone is working towards the same goals.

The WBS is also a useful tool for managing project budgets. By breaking down the
project into smaller tasks, project managers can estimate the costs associated with
each task and allocate resources accordingly. This helps to ensure that the project stays
within budget and that resources are used efficiently.

In conclusion, the WBS is a powerful tool for managing complex projects. By

breaking down the project into smaller, more manageable tasks, project managers can
ensure that the project stays on track, and all team members are working towards the
same goal. The WBS can also help to identify potential risks and challenges, prioritize
tasks, and manage project budgets. Overall, the WBS is an essential tool for effective
project management and can be used in a variety of industries and settings.
 Figure 66: Work Breakdown Structure

8.5 Appendix E: Screenshot of the System

Figure 67: Login - UI

Figure 68: Register –UI
Figure 69: Homepage- UI
Figure 70: Add rooms -UI
Figure 71: Room details -UI
Figure 73: Profile page UI
Figure 74: Edit Profile UI
Figure 75: Khalti payment Page – UI
 Figure 76: payment Page -UI
8.6 Appendix F: User Feedback
8.6.1 User Feedback Form
 Figure 77: Appendix F - User feedback form

8.6.2 Sample of Filled User Feedback Forms

Figure 78: Appendix F: filled user feedback form

8.7.1 Readings for future work

The proposed project has been completed and has received positive feedback from users.
However, to continue delivering high-quality service to tenants and landlords, there are several
areas in which the application can be improved. These improvements will enhance the
application's user-friendliness and efficiency, improving the overall user experience.
One area that will be addressed is the addition of a chat feature that will facilitate interaction
between tenants and landlords. This feature will allow users to communicate with each other in
real-time, enabling tenants to ask landlords questions, report issues, and receive prompt
feedback. The chat feature will also allow landlords to keep in touch with their tenants, making it
easier to resolve issues and provide timely assistance. The chat feature will be a valuable
addition to the application, making it more interactive and user-friendly.
Another area of improvement is the creation of a webpage for the application. The webpage will
serve as an extension of the application, providing users with more information about the
service, its features, and how to use it. The webpage will be designed to be user-friendly and will
provide a seamless transition between the application and the webpage. The webpage will also
be optimized for search engines, making it easier for users to find the application online.
In addition to the above improvements, the application will also undergo changes to include
additional features and a more attractive design. These improvements will enhance the
application's overall usability, making it more appealing to users. The new features will be
designed to provide a better user experience, making it easier for users to find what they need
and use the application. The improved design will also make the application more visually
appealing, making it more engaging and interesting to use.
Finally, the application will be improved by implementing AI for recommendations. This will be
a major change to the application, providing users with personalized recommendations based on
their preferences and usage history. The AI-powered recommendation engine will analyze user
data to provide relevant recommendations, making it easier for users to find what they need
quickly. This feature will also improve user engagement, encouraging users to explore more of
what the application has to offer.

In conclusion, the proposed project has received positive feedback, but there are still areas in
which the application can be improved. The addition of a chat feature, a webpage, and the
implementation of AI for recommendations will enhance the application's user-friendliness and
efficiency, providing users with an improved overall experience. These improvements will
ensure that the application continues to meet the needs of tenants and landlords, providing them
with a valuable service that is both user-friendly and efficient.