AI-Based Destination Explorer
BSCS FINAL PROJECT
AI BASED DESTINATION EXPLORER
Advisor: Mr. Jawad Hassan
Presented by:
Group ID: S25BS054
Student Reg#
Student Name
L1S22BSCS0088
L1S22BSCS0071
L1F21BSCS0780
ZUMER
ZEBA MUSHTAQ
EISHA ASIF
Faculty of Information Technology
University of Central Punjab
AI BASED DESTINATION
EXPLORER
By
Zumer, Zeba Mushtaq, Eisha Asif
Project submitted to
Faculty of Information Technology,
University of Central Punjab,
Lahore, Pakistan.
in partial fulfillment of the requirements for the degree of
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE
Project Advisor
Manager Projects
Abstract
This project presents a comprehensive web-based system designed to simplify and enhance the
travel planning experience through intelligent recommendations. The primary objective of the
AI-Based Destination Explorer is to address the challenges travelers face when searching for
suitable destinations based on personal preferences, budget, interests, and travel constraints.
Traditional travel platforms often provide generic suggestions and lack personalized guidance,
resulting in inefficient decision-making and user dissatisfaction.
The proposed system enables users to explore travel destinations dynamically by analyzing
their preferences and inputs. An AI-powered recommendation engine generates personalized
destination suggestions, while an integrated chatbot facilitates interactive communication using
natural language. The system also incorporates real-time data through external APIs to provide
relevant and updated information for travel planning.
The project integrates key knowledge areas including full-stack web development, database
management, artificial intelligence, and user-centered UI/UX design. The backend is developed
using Node.js and Express.js with MongoDB for data storage, while the frontend is built using
ReactJS for a responsive and interactive user experience. Machine learning and natural
language processing techniques are utilized to support intelligent recommendations and chatbot
functionality.
The resulting application provides a unified, scalable, and modular platform that automates
destination discovery and personalized travel guidance. This project demonstrates a practical
and extensible solution suitable for real-world travel applications and highlights the effective
use of AI-driven technologies in modern web-based systems.
Page i
University of Central Punjab
Dedication
We, the members of this project group, dedicate our Final Year Project “AI-Based Destination Explorer”
to all those who played a significant role in shaping our academic journey and supporting us throughout
this challenging yet rewarding experience.
First and foremost, we express our deepest gratitude and sincere respect to our esteemed project advisor,
Mr. Jawad Hassan, whose guidance, encouragement, and continuous support were instrumental in the
successful completion of this project. His insightful feedback, technical expertise, and belief in our abilities
motivated us to overcome challenges, refine our ideas, and strive for excellence. His mentorship not only
strengthened our technical skills but also enhanced our confidence and professional growth.
We also dedicate this work to our beloved parents and families, whose unwavering support, patience,
prayers, and sacrifices have been our greatest source of strength. Their constant encouragement and
understanding enabled us to stay focused and determined throughout this journey.
Our heartfelt appreciation goes to our teachers, who equipped us with the knowledge, skills, and critical
thinking abilities required to undertake this project. We are also grateful to our friends and classmates for
their cooperation, constructive feedback, shared learning, and encouragement during stressful moments.
Lastly, we dedicate this project to ourselves — for our perseverance, late nights, problem-solving efforts,
and commitment to learning. This project is not only an academic achievement but also a reflection of our
growth, teamwork, and dedication throughout our undergraduate journey.
Page ii
University of Central Punjab
— Team AI BASED DESTINATION EXPLORER
Acknowledgements
First and foremost, we express our deepest gratitude to Allah Almighty for granting us the
strength, patience, and determination to successfully complete this Final Year Project. Without
His blessings and guidance, this achievement would not have been possible. We would like to
extend our sincere thanks to our respected project advisor, Mr. Jawad Hassan, for his continuous
guidance, valuable insights, and unwavering support throughout the development of this project.
His constructive feedback, technical expertise, and mentorship played a vital role in shaping our
work into a complete and practical system. His encouragement consistently motivated us to
overcome challenges and strive for excellence. We are also thankful to the faculty and staff of
the Department of Computer Science, whose dedication to teaching and academic excellence
laid a strong foundation for the technical and analytical skills applied in this project. Our heartfelt
appreciation goes to our parents and families, whose prayers, patience, and constant motivation
served as our greatest source of strength. Their moral and emotional support enabled us to
remain focused and committed throughout this demanding journey. We would also like to
acknowledge our friends and classmates for their cooperation, constructive suggestions, and
encouragement during the challenging phases of development and documentation. Finally, we
thank each other as team members for the unity, dedication, and perseverance that transformed
this project from an academic requirement into a meaningful journey of learning, growth, and
achievement.
Page iii
University of Central Punjab
List of Figures
Figure 1: Use Case Diagram.........................................................................................................06
Figure 2: ER Diagram ................................................................................................................. 12
Figure 3: Activity Diagram(user)..................................................................................................13
Figure 4: Activity Diagram(Admin) ........................................................................................... 14
Figure 5: Abstract Class Diagram.................................................................................................15
Figure 6: Technical Architecture Diagram...................................................................................19
Figure 7: Sequence Diagram ....................................................................................................... 23
Figure 8: Sequence Diagram ....................................................................................................... 24
Figure 9: DFD Diagram(Level 0)……..........................................................................................25
Figure 10: DFD Diagram(Level 1)................................................................................................26
Figure 11: Swim Lane....................................................................................................................34
Figure 12: Home Page ..................................................................................................................34
Figure 13: Login Page ..................................................................................................................35
Figure 14: Package Display Page ................................................................................................ 35
Figure 15: Booking Page ............................................................................................................. 36
Figure 16: Package Details Page................................................................................................... 36
Figure 17: Map Page .....................................................................................................................37
Figure 18:Taxi Fares Page.............................................................................................................38
Figure 19: Destination Page.......................................................................................................... 39
Figure 20: Pricing Details Page .............................................................................................,......40
Figure 21: Booking Confirmation Page ........................................................................................41
Page iv
AI Based Destination Explorer
List of Tables
Table 1: Use Case 1.......................................................................................................................07
Table 2: Use Case 2......................................................................................................................07
Table 3: Use Case 3.......................................................................................................................08
Table 4: Use Case 4……………...................................................................................................08
Table 5: Use Case 5......................................................................................................................09
Table 6: Use Case 5.......................................................................................................................09
Table 7: Use Case 5.......................................................................................................................10
Table 8: Use Case 5.......................................................................................................................10
Table 9: Use Case 5.......................................................................................................................11
Table 10: Test Case 1…………....................................................................................................43
Table 11: Test Case 2....................................................................................................................43
Table 12: Test Case 3....................................................................................................................44
Table 13: Test Case 4....................................................................................................................45
Table 14: Test Case 5....................................................................................................................45
Table 15: Test Case 6....................................................................................................................46
Table 16: Test Case 7…………....................................................................................................46
Table 17: Test Case 8....................................................................................................................47
Table 18: Test Case 9....................................................................................................................47
Table 19: Test Case 10..................................................................................................................48
Table 20: Test Case 11..................................................................................................................48
Table 21: Test Case 12..................................................................................................................49
Table 22: Test Case 13..................................................................................................................49
Table 23: Test Case 14…………..................................................................................................50
Table 24: Test Case 15..................................................................................................................50
Table 25: Summary of Test Results............................................................................................. 52
Table 26: Project Completion Status/Conclusion.........................................................................53
Table 24: Objective(s)/Target(s) Status........................................................................................54
S25BS054
Library Copy
Page v
AI Based Destination Explorer
Table of Contents
Abstract ........................................................................................................................................... i
Dedication ...................................................................................................................................... ii
Acknowledgements ...................................................................................................................... iii
List of Figures ............................................................................................................................... iv
List of Tables ..................................................................................................................................v
List of Illustrations........................................................................... Error! Bookmark not defined.
Table of Contents ......................................................................................................................... vi
Revision History ......................................................................................................................... viii
Chapter 1. Introduction ...........................................................................................................-
Product (Problem Statement)....................................................................................................... 1
Background.................................................................................................................................. 1
Objective(s)/Aim(s)/Target(s) ..................................................................................................... 1
Scope ........................................................................................................................................... 1
Business Goals............................................................................................................................. 2
Challenges ................................................................................................................................... 2
Learning Outcomes ..................................................................................................................... 2
Nature of End Product ................................................................................................................. 2
Related Work/ Literature Survey/ Literature Review .................................................................. 3
Document Conventions ............................................................................................................... 3
Miscellaneous .............................................................................................................................. 3
Chapter 2.
Overall Description ................................................................................................4
Chapter 3.
System Requirements ............................................................................................6
Chapter 4.
Technical Architecture ........................................................................................18
Chapter 5.
Detailed Design and Implementation .................................................................30
-
Product Features .......................................................................................................................... 4
Functional Description ................................................................................................................ 4
User Classes and Characteristics ................................................................................................. 4
Design and Implementation Constraints...................................................................................... 5
Assumptions and Dependencies .................................................................................................. 5
3.1
Functional Requirements ............................................................................................................. 6
3.1.1 Name of Use-Case 1................................................................................................................ 7
3.1.2 Name of Use-Case 2 (and so on)............................................................................................. 7
3.1.3 Requirements Analysis and Modeling .................................................................................... 9
3.2
Nonfunctional Requirements ................................................................................................... 116
3.2.1 Performance Requirements ................................................................................................. 116
3.2.2 Safety Requirements ........................................................................................................... 116
3.2.3 Security Requirements ........................................................................................................ 116
3.2.4 Additional Software Quality Attributes .............................................................................. 116
3.3
Other Requirements ..................................................................................................................-
Application and Data Architecture ............................................................................................ 20
Component Interactions and Collaborations ............................................................................. 22
Design Reuse and Design Patterns ............................................................................................ 27
Technology Architecture ........................................................................................................... 27
Architecture Evaluation ........................................................................................................... 228
5.1
Component-Component Interface ............................................................................................. 30
5.2
Component-External Entities Interface ..................................................................................... 31
5.3
Component-Human Interface .................................................................................................... 32
5.4
Screenshots/Prototype ............................................................................................................... 33
5.4.1 Workflow .............................................................................................................................. 33
5.4.2 Screens .................................................................................................................................. 35
5.5
Additional Information .............................................................................................................. 44
S25BS054
Library Copy
Page vi
AI Based Destination Explorer
5.6
Other Design Details ................................................................................................................. 44
Chapter 6.
6.1
6.2
Test Specification and Results ............................................................................45
Test Case Specification ............................................................................................................. 45
Summary of Test Results ........................................................................................................... 53
Chapter 7. Project Completion Status/Conclusion ..............................................................54
References .....................................................................................................................................56
Appendix A Glossary ...................................................................................................................58
Appendix B IV & V Report.........................................................................................................61
(Independent verification & validation) ....................................................................................61
Appendix C
Deployment/Installation Guide .......................................................................61
Appendix D
User Manual .....................................................................................................61
S25BS054
Library Copy
Page vii
AI Based Destination Explorer
Revision History
Name
S25BS054
Date
Reason For Changes
Library Copy
Version
Page viii
AI Based Destination Explorer
Chapter 1.
Introduction
1.1 Product (Problem Statement)
This document presents the Library Documentation for the Final Year Project titled “AI-Based
Destination Explorer.”
The purpose of this library documentation is to provide a clear and structured description of the reusable
components, modules, and libraries developed and used in the project. It serves as a reference for
developers, evaluators, and future users who want to understand, maintain, or extend the system.
The AI-Based Destination Explorer is a smart travel recommendation system that helps users discover
travel destinations based on their preferences, budget, interests, and constraints. The system integrates
modern web technologies with artificial intelligence techniques to provide personalized and intelligent
travel suggestions.
1.2 Background
The main purpose of this library documentation is to:
• Explain the internal structure of the project libraries and modules
• Describe how different components interact with each other
• Provide usage guidelines for developers who want to reuse or modify the libraries
• Support future enhancements, maintenance, and scalability of the system
This documentation ensures that the developed libraries are well-organized, understandable, and
reusable, reducing dependency on the original developers.
1.3 Objective(s)/Aim(s)/Target(s)
Travel planning is often time-consuming and complex, especially when users need personalized
recommendations. Existing platforms usually provide generic suggestions and lack intelligent
interaction.
To overcome these limitations, the AI-Based Destination Explorer was developed. The system uses:
• Artificial Intelligence and Natural Language Processing (NLP)
• A recommendation engine based on user preferences
• A chatbot interface for interactive communication
• Web-based frontend and backend technologies
The libraries documented in this chapter play a critical role in enabling these features efficiently and
reliably.
1.4 Scope
This library documentation covers:
• Frontend libraries and reusable UI components
• Backend service modules and APIs
• AI and chatbot-related libraries
• Database interaction and utility modules
• Configuration and integration components
It focuses only on software libraries and reusable modules, not on deployment or user manuals.
S25BS054
Library Copy
Page 1
AI Based Destination Explorer
1.5 Business Goals
The business goals of the AI-Based Destination Explorer are to provide an intelligent and user-friendly
travel planning solution with potential for real-world application. The system aims to enhance user
experience through personalized destination recommendations and AI-based decision support.
Another key goal is to ensure scalability and reusability by developing modular libraries that can be
extended for future features. The project also focuses on cost-effective development using open-source
technologies while maintaining competitiveness through smart recommendation and chatbot features.
Additionally, the system supports future commercialization and data-driven insights for improving travel
services.
1.6 Challenges
During the development of the AI-Based Destination Explorer, several challenges were encountered.
One major challenge was integrating artificial intelligence features, such as the recommendation system
and chatbot, with the web-based frontend and backend. Managing and processing user preferences
accurately also required careful design of data structures and logic.
Another challenge involved handling third-party APIs, including issues related to data consistency,
response time, and dependency management. Ensuring reusability and proper documentation of libraries
while maintaining system performance was also challenging. Additionally, coordinating multiple project
phases and ensuring smooth integration of all modules required effective planning and testing.
1.7 Learning Outcomes
Through the development of the AI-Based Destination Explorer, the project team gained practical
experience in designing and implementing a complete software system. The project enhanced
understanding of modular library design, code reusability, and documentation practices.
Students learned to integrate frontend and backend technologies, work with databases, and apply
artificial intelligence techniques such as recommendation systems and chatbot integration. The project
also improved problem-solving skills, teamwork, version control usage, and the ability to develop
scalable and maintainable software solutions.
1.8 Nature of End Product
The end product of this project is a web-based AI-driven travel recommendation system supported
by well-structured and reusable software libraries. The system provides intelligent destination
suggestions, an interactive chatbot, and a user-friendly interface for travel planning.
From a software perspective, the end product consists of modular frontend and backend libraries, AI
components, and database utilities that can be reused or extended in future projects. The product is
academic in nature with potential for commercial and real-world application.
S25BS054
Library Copy
Page 2
AI Based Destination Explorer
1.9 Related Work/ Literature Survey/ Literature Review
In recent years, the rapid growth of web-based technologies and artificial intelligence has significantly
transformed the travel and tourism industry. Various online travel platforms and recommendation
systems have been developed to assist users in selecting travel destinations, planning trips, and accessing
relevant information. However, many existing systems still lack deep personalization and intelligent
interaction.
Several studies highlight the use of recommendation systems in tourism applications. These systems
commonly apply content-based filtering, collaborative filtering, or hybrid approaches to suggest
destinations based on user preferences and past behavior. While such systems improve user experience,
they often depend on limited user data and provide generic recommendations without contextual
understanding.
Research has also explored the integration of machine learning techniques in travel recommendation
platforms. Machine learning models analyze user interests, travel history, and behavioral patterns to
generate personalized suggestions. Although these approaches enhance accuracy, they require large
datasets and may struggle with new users due to the cold-start problem.
With the advancement of Natural Language Processing (NLP), chatbot-based travel assistants have
gained popularity. Existing travel chatbots provide basic information such as destination details, weather
updates, and booking assistance. However, many chatbots operate on rule-based systems and lack
contextual awareness, limiting their ability to provide meaningful and adaptive responses.
Recent literature emphasizes the importance of AI-driven conversational systems combined with
recommendation engines to create intelligent travel assistants. Hybrid models that integrate NLP-based
chatbots with recommendation systems offer improved interaction and personalization. Despite these
advancements, most platforms still function as separate modules, resulting in fragmented user
experiences.
1.10 Document Conventions
This document follows standard academic and software documentation conventions to ensure clarity and
consistency. Headings and subheadings are numbered for easy reference. Technical terms, module
names, and library names are written in bold when first introduced.
Code snippets, function names, and file names are presented in monospaced font to distinguish them
from normal text. Figures, tables, and diagrams are properly labeled and referenced within the text.
Abbreviations are defined at their first occurrence to avoid ambiguity.
1.11 Miscellaneous
This document may be updated in future to reflect enhancements, bug fixes, or changes in the project
libraries. Any modifications to the libraries or system architecture should be properly documented to
maintain consistency and usability.
All third-party libraries and tools used in the project follow their respective licensing policies. Proper
attribution is maintained where required. Any assumptions or limitations not explicitly stated in this
document are considered outside the scope of this library documentation.
S25BS054
Library Copy
Page 3
AI Based Destination Explorer
Chapter 2.
Overall Description
2.1 Product Features
The AI-Based Destination Explorer provides a set of intelligent features designed to support personalized
travel planning. The system allows users to receive destination recommendations based on their
preferences, budget, interests, and travel constraints.
An interactive chatbot is integrated to assist users through natural language interaction, helping them
explore destinations and obtain relevant travel information. The product also includes a user-friendly
web interface, secure data handling, and real-time data integration through external APIs.
From a technical perspective, the system is built using modular and reusable libraries that support
scalability, maintainability, and future enhancements. These features collectively make the product
efficient, intelligent, and suitable for real-world applications.
2.2 Functional Description
The AI-Based Destination Explorer functions as an intelligent travel planning system that interacts with
users through a web-based interface. Users can register and log in to the system, provide their travel
preferences, and receive personalized destination recommendations generated by the recommendation
engine.
The system processes user inputs and stores relevant data in the database for future analysis and
personalization. The chatbot module enables users to ask questions in natural language and receive
relevant responses related to destinations, travel suggestions, and planning guidance.
Backend services handle data processing, API communication, and business logic, while frontend
components manage user interaction and data presentation. All functionalities are implemented using
modular libraries to ensure reusability, scalability, and ease of maintenance.
2.3 User Classes and Characteristics
The AI-Based Destination Explorer serves multiple user classes with distinct needs. Regular travelers
are the primary users who seek personalized destination recommendations, live maps, and interactive
chatbot support for efficient trip planning. First-time travelers are secondary users who require
guidance, simple navigation, and preference-based suggestions to plan their trips confidently. Travel
enthusiasts or bloggers use the platform for detailed analytics, trending destinations, and content
sharing, while administrators manage backend operations, maintain destination data, and monitor
system performance. The system prioritizes regular and first-time travelers, ensuring that the core
features address their needs effectively, while other user classes support specialized or operational
functionalities.
S25BS054
Library Copy
Page 4
AI Based Destination Explorer
2.4 Design and Implementation Constraints
The development of the AI-Based Destination Explorer is subject to several constraints. The system
must use the MERN stack (MongoDB, ExpressJS, ReactJS, NodeJS) for frontend and backend
development, and Python for AI modules, limiting the choice of technologies. Memory and performance
constraints arise due to real-time map rendering and AI-based recommendation processing. Integration
with external APIs, such as map services or travel data providers, imposes communication protocol and
rate-limiting considerations. Security measures, including user authentication and data privacy, must
follow standard practices to protect personal information. Additionally, the system must adhere to web
design conventions, responsive layouts, and maintainable coding standards, as the client organization
will be responsible for future updates and maintenance.
2.5 Assumptions and Dependencies
The development of the AI-Based Destination Explorer assumes that users will have access to a
stable internet connection and devices capable of running modern web applications. It is also assumed
that third-party APIs, such as mapping services and travel data providers, will be available and reliable
for fetching real-time information. The project depends on the MERN stack (MongoDB, ExpressJS,
ReactJS, NodeJS) for core functionality, and Python libraries for AI-based recommendations. Any
changes or downtime in these technologies or APIs could affect the system’s performance. Additionally,
it is assumed that users will provide accurate preferences and feedback to enable the AI module to
generate meaningful recommendations. Security and privacy practices are dependent on proper
configuration and maintenance by the administrators.
S25BS054
Library Copy
Page 5
AI Based Destination Explorer
Chapter 3.
System Requirements
3.1 Functional Requirements
Use Case Diagram
S25BS054
Library Copy
Page 6
AI Based Destination Explorer
3.1.1 Register Account
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
3
4
Alternate Course of Action
S#
1
2
UC-1
Register Account
To allow a new user to create an account in the system.
High
User must have internet access. System must be operational.
User account is created and stored in the database.
Actor Action
User selects “Register” option
User enters name, email, password
User clicks “Submit”
Actor Action
User enters invalid email format
User enters already registered email
Table 1: UC-1
3.1.2 Login
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
Alternate Course of Action
S#
1
UC-2
Login
To allow registered users to access the system.
High
User must be registered.
User dashboard is displayed.
Actor Action
User enters email and password
User clicks “Login”
Actor Action
User enters incorrect credentials
Table 2 : UC-2
S25BS054
Library Copy
Page 7
AI Based Destination Explorer
3.1.3 Search Destination
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
Alternate Course of Action
S#
1
UC-3
Search Destination
To allow users to search for travel destinations.
High
User must be logged in.
Matching destinations are displayed.
Actor Action
User enters destination name or filters
Actor Action
No matching result found
Table 3 : UC-3
3.1.4 Get AI-Based Recommendation
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
3
Alternate Course of Action
S#
1
UC-4
Get AI-Based Recommendation
To provide personalized destination recommendations using AI.
High
User logged in and preferences selected.
Personalized recommendations displayed.
Actor Action
User selects travel preferences
Actor Action
AI service unavailable
Table 4 : UC-4
S25BS054
Library Copy
Page 8
AI Based Destination Explorer
3.1.5 Generate Itinerary
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
Alternate Course of Action
S#
1
UC-5
Generate Itinerary
To generate a personalized day-wise travel itinerary.
Medium
Destination selected.
Itinerary generated and saved.
Actor Action
User selects travel dates
Actor Action
Invalid date selection
Table 5 : UC-5
3.1.6 View Muslim-Friendly Information
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
Alternate Course of Action
S#
1
UC-6
View Muslim-Friendly Information
To display halal restaurants, mosques, and prayer times.
High
Destination selected.
Muslim-friendly information displayed.
Actor Action
User selects Muslim-friendly tab
Actor Action
API unavailable
Table 6 : UC-6
S25BS054
Library Copy
Page 9
AI Based Destination Explorer
3.1.7 Save Trip
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
Alternate Course of Action
S#
1
UC-7
Save Trip
To allow users to save destinations or itineraries.
Medium
User logged in.
Trip saved in user profile.
Actor Action
User clicks “Save Trip”
Actor Action
User not logged in
Table 7 : UC-7
3.1.8 Submit Feedback
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
3
Alternate Course of Action
S#
1
UC-8
Submit Feedback
To allow users to provide ratings and comments.
Medium
User logged in.
Feedback stored in database.
Actor Action
User selects feedback option
User enters rating and comments
User submits form
Actor Action
Empty submission
Table 8 : UC-8
S25BS054
Library Copy
Page 10
AI Based Destination Explorer
3.1.9 Admin Manage Destinations
Identifier
Use Case Name
Purpose
Priority
Pre-conditions
Post-conditions
Typical Course of Action
S#
1
2
Alternate Course of Action
S#
1
UC-9
Manage Destinations
To allow admin to add, update, or delete destinations.
High
Admin logged in.
Destination database updated.
Actor Action
Admin selects add/update/delete
Admin submits changes
Actor Action
Incomplete data entered
Table 9 : UC-9
S25BS054
Library Copy
Page 11
AI Based Destination Explorer
3.1.10 Requirements Analysis and Modeling
Entity Relationship Diagram:
S25BS054
Library Copy
Page 12
AI Based Destination Explorer
Activity Diagram(User):
S25BS054
Library Copy
Page 13
AI Based Destination Explorer
Activity Diagram(admin):
S25BS054
Library Copy
Page 14
AI Based Destination Explorer
Abstract Class Diagram:
S25BS054
Library Copy
Page 15
AI Based Destination Explorer
3.2 Nonfunctional Requirements
3.2.1 Performance Requirements
The AI Based Destination Explorer system shall provide efficient and responsive performance under
normal operating conditions. The system shall respond to user search queries within three (3) seconds to
ensure smooth interaction. AI-based recommendations shall be generated within five (5) seconds after
the user submits preferences. Database query execution time shall not exceed two (2) seconds for
standard operations. The system shall support at least 500 concurrent users without performance
degradation. Additionally, the system shall maintain 99% uptime availability to ensure continuous access
for users. These performance requirements are defined to provide a seamless user experience and prevent
delays during travel planning activities.
3.2.2 Safety Requirements
The system shall implement safeguards to prevent potential data loss, damage, or misuse. Accidental
deletion of destination data shall be prevented through confirmation prompts for all critical admin actions
such as updating or deleting records. Weekly automated database backups shall be performed to ensure
data recovery in case of system failure. The system shall validate all user inputs to prevent incorrect or
harmful data entry. Furthermore, AI-generated recommendations shall be filtered to ensure that
inappropriate or irrelevant content is not presented to users. These measures aim to protect system
integrity and prevent unintended harm or data loss.
3.2.3 Security Requirements
The system shall ensure the protection of user data and secure access to system functionalities. All users
must authenticate using secure login credentials before accessing protected features. Passwords shall be
encrypted using secure hashing algorithms to prevent unauthorized access. Role-based access control
shall be implemented to distinguish between administrative and regular user permissions. The system
shall operate over HTTPS to secure data transmission. Protection mechanisms against common web
vulnerabilities such as SQL injection, Cross-Site Scripting (XSS), and Cross-Site Request Forgery
(CSRF) shall be implemented. User personal data shall be handled in accordance with recognized data
protection principles such as GDPR guidelines. Additionally, user sessions shall automatically expire
after 15 minutes of inactivity to enhance security.
3.2.4 Additional Software Quality Attributes
The system shall emphasize usability by providing a simple, intuitive, and user-friendly interface. Users
shall be able to access major features within three clicks to ensure ease of navigation. In terms of
reliability, the system failure rate shall not exceed 1% under normal operating conditions.
Maintainability shall be ensured through a modular architecture using React for the frontend and Django
for the backend, along with proper code documentation for future enhancements. The system shall be
portable and accessible across major web browsers including Chrome, Firefox, and Edge, and it shall
feature a responsive design compatible with desktop and mobile devices. Scalability shall be supported
through cloud deployment readiness and a database structure that allows future expansion.
Interoperability shall be achieved by enabling integration with third-party APIs such as Maps, Weather,
and Prayer Time services.
S25BS054
Library Copy
Page 16
AI Based Destination Explorer
3.3 Other Requirements
Database Requirements
The system shall utilize a MySQL relational database management system. The database design shall
follow normalization principles up to Third Normal Form (3NF) to reduce redundancy and ensure data
consistency. A backup and recovery mechanism shall be implemented to safeguard against data loss.
External Interface Requirements
The system shall integrate with external software interfaces including Google Maps API, Weather API,
Prayer Time API, and Hotel or Flight booking APIs to enhance system functionality. The application
shall be compatible with standard hardware devices including desktops, laptops, and mobile devices to
ensure accessibility across multiple platforms.
Legal Requirements
The system shall display a Privacy Policy informing users about data collection and usage practices.
User consent shall be obtained before storing any personal data. The system shall comply with applicable
data protection standards and regulations to ensure lawful processing of user information.
Internationalization Requirements
The system shall initially operate in the English language; however, the architecture shall be designed
to support future multilingual expansion. The system shall also support multiple currencies to
accommodate users from different regions.
Reuse Objectives
The AI recommendation module shall be designed in a reusable manner so that it can be integrated into
future travel-related systems. The backend architecture shall be modular to allow future feature
extensions
and
enhancements
without
major
restructuring.
S25BS054
Library Copy
Page 17
AI Based Destination Explorer
Chapter 4.
Technical Architecture
The AI-Based Destination Explorer is a custom-built, full-stack web application designed for
personalized travel planning, with a focus on Muslim travelers and group coordination. It integrates
multiple subsystems, including booking management, collaborative group planning, faith-friendly travel
tools, and an intelligent Hybrid RAG chatbot. The system supports both online real-time processing
(chatbot queries, group chat, expense tracking) and transactional processing (booking creation, status
updates, payment tracking), along with analytical reporting features for expense breakdowns and travel
statistics.
System Overview
The system is built on a client-server architecture accessible via the Internet, using browser-based
interfaces for end users. The backend is implemented using Node.js with the Express.js framework,
while the frontend uses EJS templating and Bootstrap 5 for responsive UI. The system is hosted on
cloud servers and interacts with external APIs for weather, world time, events, currency conversion, and
OpenStreetMap Overpass data.
Data management is handled via MongoDB, which stores users, bookings, groups, messages, travel
packages, reviews, and taxi fares. Real-time features like group chat, location sharing, and notifications
are powered by Socket.IO. The Hybrid RAG chatbot integrates a retrieval module that searches a
vector database of structured travel and faith-specific content and a generative LLM module that
produces context-aware, personalized responses.
Major Components
1. User Interface (Frontend):
• Browser-based interface accessible on desktop and mobile.
• Provides multi-turn interaction with the Hybrid RAG chatbot, booking management, group
planning, and expense tracking.
• Responsive design using Bootstrap 5 and custom EJS templates.
2. Backend Application Server:
• Node.js + Express.js application handles API requests, user authentication, session
management, and business logic.
• Implements middleware for route protection, error handling, and asynchronous operations.
3. Database Layer:
• MongoDB manages complex data relationships across 9 main schemas: users, bookings,
groups, messages, travel packages, reviews, taxi fares, and chatbot logs.
• Stores structured travel data, user preferences, historical interactions, and transaction records.
4. Hybrid RAG Chatbot Module:
• Retrieval Component: Queries structured datasets, travel policies, and faith-specific content
using semantic similarity search over vector embeddings.
• Generative Component: LLM generates human-like responses grounded in retrieved
context to ensure accuracy.
• Handles context-aware, multi-turn conversations and provides personalized
recommendations.
5. External API Integrations:
• OpenStreetMap Overpass (mosques, halal restaurants)
• Weather APIs
• World Time API
• Currency conversion APIs (PKR, USD, EUR, GBP, others)
• Eventbrite (event discovery)
6. Real-Time Communication Module:
• Socket.IO supports live group chat, location sharing, and instant notifications.
Data Components
The system collects and manages the following data:
User Data: Profiles, authentication credentials, preferences.
Booking Data: Packages selected, travel dates, traveler count, pricing, booking status.
Group Data: Group members, shared itineraries, group expenses.
Travel Information: Destination details, attractions, events, halal food locations, prayer facilities.
S25BS054
Library Copy
Page 18
AI Based Destination Explorer
Chatbot Data: User queries, retrieved documents, conversation context, response logs.
Analytics Data: Expense breakdowns, travel statistics, system notifications.
Processing
Online / Real-time: Chatbot responses, group chat, live location sharing, notifications.
Transactional: Booking creation, status updates, payment tracking.
Analytical: Expense breakdown, per-person cost calculations, historical travel statistics.
Programming Languages & Tools
Backend: Node.js, Express.js
Frontend: EJS, Bootstrap 5, HTML/CSS/JS
Database: MongoDB
Real-Time Communication: Socket.IO
Authentication: Passport.js, JWT tokens
File Uploads: Cloudinary
AI: LLM (for generative chatbot) + Vector database (retrieval module)
Network & Hosting
Accessible over the Internet using standard web browsers.
Hosted on cloud-based servers, ensuring scalability and global availability.
Supports client-server communication, REST APIs, and WebSocket connections.
Design Patterns / Architecture Principles
Layered Architecture: Presentation, Business Logic, Data Access, and AI Modules.
Modular Design: Components (chatbot, booking, group management) are independently deployable
and maintainable.
Hybrid RAG Pattern: Combines retrieval-based and generative AI approaches for accurate,
context-aware responses.
S25BS054
Library Copy
Page 19
AI Based Destination Explorer
4.1 Application and Data Architecture
4.1.1 Frontend (Client-Side)
A browser-based user interface built with EJS templates, Bootstrap 5, and custom CSS.
Handles all user interactions, including browsing travel packages, creating bookings, managing
group travel, and interacting with the chatbot.
Fully responsive across desktop and mobile devices.
Communicates with the backend via REST APIs using Axios and Web Sockets for real-time
features.
Displays dynamic content such as filtered destinations, package details, group itineraries, expense
breakdowns, and chatbot responses.
2.1.2 Backend (Server-Side)
Built with Node.js and Express.js, acting as the core processing unit of the system.
Orchestrates communication between the frontend, database, real-time module, chatbot, and external
APIs.
Handles business logic for:
Booking management (package selection, traveler count, pricing, email notifications).
Group travel collaboration (invite codes, chat, expense tracking).
Faith-friendly travel assistance (mosque and halal restaurant locators, Qiblah direction).
Integrates multiple external APIs (OpenStreetMap Overpass, Weather APIs, World Time API,
Eventbrite) to provide real-time travel intelligence.
Provides secure authentication and authorization using Passport.js (local strategy + JWT tokens)
and session management with MongoDB store.
2.1.3 Hybrid RAG Chatbot
A Hybrid Retrieval-Augmented Generation (RAG) chatbot integrated into the platform.
Retrieval Component: Fetches destination details, Muslim-friendly travel content, travel policies,
and user-specific past interactions from a curated database using vector embeddings and semantic
search.
Generative Component: Uses a Large Language Model (LLM) to generate human-like, contextaware responses grounded in retrieved content.
Provides:
Real-time, personalized travel guidance.
Faith-friendly suggestions (Halal food, prayer times, mosques).
Multi-turn conversation capabilities.
Communicates with the backend via REST APIs and Web Sockets for live queries and responses.
2.1.4 Real-Time Module
Built with Socket.IO for instant updates, including:
Group travel chat.
Location sharing among group members.
Notifications about bookings, itinerary changes, and group activities.
2.1.5 Hosting Environment
Hosted on cloud-based servers for scalability, reliability, and global accessibility.
Backend and databases communicate with the hosting infrastructure securely via REST APIs.
Frontend deployed on static hosts or CDNs, ensuring fast response and low latency.
S25BS054
Library Copy
Page 20
AI Based Destination Explorer
2.1.6 Data Components
Users Database: Stores user profiles, preferences, authentication details, and JWT session tokens.
Bookings Database: Maintains travel bookings with package details, traveler counts, pricing, and
status (pending, confirmed, canceled, completed).
Groups Database: Stores group travel information, member lists, invite codes, group chat messages,
and expense breakdowns.
Travel Packages Database: Contains curated travel packages, including destinations, activities,
durations, and costs.
Chatbot Knowledge Base: Curated and preprocessed datasets including destination info, Muslimfriendly travel content, FAQs, and previous user interactions.
External API Data: Real-time data fetched from OpenStreetMap Overpass, Eventbrite, Weather
APIs, World Time API, and currency conversion APIs.
2.1.7 Data and Request Flow
User → Frontend: Inputs travel preferences, package selection, group invites, and chatbot queries.
Frontend → Backend: Sends inputs via REST API or WebSocket requests for processing.
Backend → Databases: Fetches or updates relevant data (users, bookings, groups, travel packages,
chatbot logs).
Backend → External APIs: Retrieves real-time data for weather, events, locations, and currency
conversions.
Backend → Frontend: Returns processed results for display, including bookings, itinerary details,
group messages, and chatbot responses.
Real-Time Module → Frontend/Backend: Updates multi-user sessions, chat messages, and
location
sharing
instantly.
Decision Tables
Decision Table for Signup
Condition
Rule1
Rule2
Rule3
Rule4
Rule5
Rule6
Rule7
Rule8
Name
✓
✓
✓
✓
✓
Email
✓
✓
✓
✓
✓
Password
✓
✓
✓
✓
✓
✓
Confirm
Password
Contact
Number
Action
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
Sign
Up
Try
Again
Try
Again
Try
Again
Try
Again
Try
Again
Try
Again
Try
Again
Decision Table for Login
S25BS054
Library Copy
Page 21
AI Based Destination Explorer
Condition
Rule1
Rule2
Rule3
Rule4
Rule5
Rule6
Rule7
Rule8
Email
✓
✓
✓
✓
✓
Password
✓
✓
✓
✓
Action
Login
Try
Again
Try
Again
Try
Again
Login
Try
Again
Try
Again
Try
Again
Decision Table for Apply for Destination
Condition
Rule1
Rule2
Rule3
Rule4
Rule5
Rule6
Rule7
Rule8
Logged In
✓
✓
✓
✓
✓
Resume
Uploaded
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
Apply
Try
Again
Try
Again
Try
Again
Try
Again
Try
Again
Try
Again
Apply
Destination
Selected
Action
Decision Table for Posting a Travel Recommendation
Condition
Rule1
Rule2
Rule3
Rule4
Rule5
Rule6
Rule7
Rule8
Logged In (as
Company)
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
Try
Again
Try
Again
Try
Again
Post
Try
Again
Try
Again
Try
Again
Destination
Selected
Description
Provided
Action
S25BS054
Post
Library Copy
Page 22
AI Based Destination Explorer
4.2 Component Interactions and Collaborations
The sequence diagram for the AI-Based Destination Explorer shows the interaction between the user,
frontend, AI recommendation engine, backend, external APIs, and database, starting with the user
entering travel preferences, which the backend processes and sends to the AI engine to generate
personalized travel packages; simultaneously, external APIs provide real-time weather, currency, events,
and faith-friendly location data, which is combined with AI insights, stored in the database, and sent to
the frontend for display, while booking, group planning, authentication, chat, and notifications ensure
seamless coordination for a personalized and efficient travel experience.
Sequence Diagram
S25BS054
Library Copy
Page 23
AI Based Destination Explorer
Sequence Diagram
Sequence Diagram
S25BS054
Library Copy
Page 24
AI Based Destination Explorer
DFD(Data Flow Diagram)
Level 0:
The AI-Based Destination Explorer system interacts with three main external entities:
the User, the Admin, and External APIs. Users input their travel preferences such as
budget, location type, and weather, and the system processes these inputs using an AI
engine to provide personalized travel recommendations. The Admin manages
destination data, user feedback, and alerts via the admin panel. The system also
communicates with external services (like maps, weather, and transport APIs) to
provide real-time information. All data flows through and is stored in internal databases
to support recommendation, itinerary planning, chatbot responses, and feedback
handling.
S25BS054
Library Copy
Page 25
AI Based Destination Explorer
Level 1:
At Level 1, the system is broken into detailed functional processes. Users register or log
in, after which their preferences (like budget, trip type, and weather) are sent to the AI
Recommendation Engine, which processes and returns suggested destinations. Users
can then save favorites, plan itineraries, or coordinate with travel groups. The system
interacts with the Live Map Module and Scraper API to fetch nearby attractions, taxi
fares, and live data. A built-in Chatbot (NLP) assists with queries, while the Hotel &
Emergency Module lists accommodation and contacts. The Admin Panel allows admin
users to manage destinations, view logs, and respond to user feedback. All modules
interact with a central Database for storing and retrieving data.
S25BS054
Library Copy
Page 26
AI Based Destination Explorer
4.3 Design Reuse and Design Patterns
In the development of the AI-Generated Destination Explorer, the following aspects of design reuse and
design patterns have been incorporated:
Design Reuse:
Existing NLP Techniques:
We reused pre-trained NLP models and libraries such as spaCy and NLTK to speed up chatbot
development and ensure accurate interpretation of user input.
Frontend
UI
Components:
Design templates and components from Bootstrap and Material UI were reused to build a responsive and
user-friendly interface quickly.
Database Schema:
Our database structure reuses schemas from similar recommendation systems to efficiently organize user
data, travel preferences, and chat history.
External APIs:
We integrated widely-used APIs like Google Maps, Open Weather Map, and travel data services to
enrich the platform without building every feature from scratch.
Design Pattern:
Model-View-Controller:
We follow the MVC design pattern to separate the frontend (ReactJS), backend logic
(NodeJS/Express), and database operations (MySQL/MongoDB).
Observer Pattern:
This pattern is applied to reflect real-time updates in the UI when recommendations, maps, or
weather data change.
Singleton Pattern:
We use the singleton pattern for managing the AI module instance to avoid multiple model
loads and ensure performance efficiency.
Factory Pattern:
The recommendation engine uses the factory pattern to dynamically generate travel suggestions
based on different user input types and preferences.
4.4 Technology Architecture
The following is the anticipated technology infrastructure required to support the development
and deployment of the AI-Generated Destination Explorer platform:
S25BS054
Library Copy
Page 27
AI Based Destination Explorer
•
•
•
•
•
•
•
•
•
Developing a responsive web application that is compatible with both mobile
and desktop browsers.
Supporting all major mobile browsers above Android v6.0+ and Safari for iOS up
to the latest versions.
Supporting all modern browsers on Windows and macOS, including Chrome, Edge,
Firefox, and Internet Explorer v11+.
The development environment uses the latest stable release Visual Studio Code v1.75+.
The frontend is built using ReactJS version 18+ with HTML5, CSS3, Bootstrap, and
JavaScript.
The backend is developed using NodeJS (v16+) and ExpressJS for server-side logic and
routing.
AI modules are created using Python 3.10+ in Jupyter Notebook, where Natural
Language Processing (NLP) techniques are applied for intelligent travel
recommendations.
The database systems include MySQL for structured data and MongoDB for scalable
and flexible storage needs.
External APIs like Google Maps API and OpenWeatherMap are integrated for realtime location and weather services
4.5 Architecture Evaluation
The infrastructure and technology choices for the AI-Based Destination Explorer were made with a
focus on modularity, scalability, maintainability, and performance. Each selection was carefully
evaluated against alternative technologies to ensure the system meets both functional and non-functional
requirements effectively.
Frontend Choice:
The frontend is built using EJS templates combined with Bootstrap 5 for styling. This choice allows
rapid development of a responsive, lightweight, and fast-loading UI that adapts seamlessly across
desktop and mobile devices. EJS was preferred over frameworks like React or Angular because it
integrates directly with the Node.js backend, reducing complexity for server-side rendering and dynamic
content generation. Bootstrap was chosen for its ready-to-use responsive components, which accelerated
development and ensured a consistent design across pages.
Backend Choice:
The backend uses Node.js with Express.js, providing asynchronous request handling and native
support for real-time communication via Socket.IO. Node.js was selected over alternatives like
Django or Spring Boot due to its non-blocking architecture, which efficiently manages multiple
simultaneous requests—critical for real-time features such as group travel chat and live updates from
external APIs. Express.js simplifies API creation with middleware support and flexible routing, making
it easier to maintain and extend.
S25BS054
Library Copy
Page 28
AI Based Destination Explorer
DatabaseChoice:
MongoDB was chosen for its flexible schema design, which accommodates heterogeneous and
evolving data structures such as user profiles, bookings, travel packages, group data, and chatbot logs.
Unlike SQL databases, MongoDB allows storage of nested objects, arrays, and dynamic fields, which is
essential for handling diverse travel package data, multi-currency expense breakdowns, and vector
embeddings for the Hybrid RAG chatbot. SQL databases were considered but rejected due to rigid
schema requirements and more complex handling of nested and semi-structured data.
HybridRAGChatbot:
The Hybrid RAG chatbot integrates retrieval-based knowledge grounding with generative AI
capabilities, providing faith-conscious, accurate, and context-aware travel guidance. A purely
generative LLM was considered but rejected because of the high risk of hallucinations and inaccurate
responses, which would negatively affect user trust. Retrieval augmentation ensures that responses are
grounded in curated datasets while retaining flexibility and conversational fluency.
Pros of the Selected Infrastructure:
•
•
•
•
•
Modular and maintainable architecture with clear separation of frontend, backend, database, and
AI components.
Scalable design, supporting multi-user real-time collaboration and future feature expansion.
High responsiveness and fast content delivery, enhancing the user experience.
Multi-API integration provides enriched travel intelligence including real-time weather, events,
currency conversions, and halal-friendly services.
Accurate and reliable AI-assisted travel guidance via Hybrid RAG, reducing misinformation
risks.
Cons / Limitations:
•
•
•
System performance is dependent on external API availability (e.g., OpenStreetMap,
Eventbrite).
Chatbot responses require computational resources for vector retrieval and LLM inference.
Current chatbot implementation does not support voice interaction or multilingual queries
(planned for future updates).
Alternatives Considered:
•
•
•
•
Backend: Django and Spring Boot were evaluated but rejected in favor of Node.js for superior
support of real-time features and asynchronous operations.
Database: Traditional SQL databases were considered but lacked flexibility for evolving schema
requirements.
Chatbot: Pure LLM-based chatbot was evaluated but rejected due to hallucination risks; retrieval
augmentation ensures factual accuracy.
Frontend: React or Angular could have been used, but EJS was selected for easier integration
with Node.js and faster server-side rendering
S25BS054
Library Copy
Page 29
AI Based Destination Explorer
Chapter 5.
Detailed Design and Implementation
The AI-Based Destination Explorer system is designed using a modular architecture where each
component performs a specific function but works collectively to provide a smooth user experience. The
frontend, developed in ReactJS, HTML, and CSS, offers an interactive interface for users to log in,
explore destinations, and plan trips. The backend, built with NodeJS and ExpressJS, handles all logic,
API communication, and data management between the user interface, AI model, and MongoDB
database, which stores user details, destinations, preferences, and feedback. The AI recommendation
engine, implemented in Python, analyzes user inputs like budget, location type, and weather to generate
personalized travel suggestions, while the NLP-based chatbot assists users through interactive guidance.
The system also includes a web scraping module to gather live data about hotels, transport, and
attractions, and a Map API for real-time navigation and nearby search. Additionally, the admin panel
allows managing destinations and user feedback. Together, these components ensure an intelligent, userfriendly, and efficient travel planning experience.
5.1 Component-Component Interface
The Component–Component Interface defines how different modules in the AI-Based Destination
Explorer system interact and share data to perform coordinated tasks efficiently. It ensures smooth
communication, data consistency, and modular system operation.
5.1.1.1 Key Interactions:
1. Frontend Backend API:
The frontend (ReactJS) sends user inputs like destination preferences, budget, and weather choice to the
backend (Node.js + Express). The backend processes and returns recommended destinations, maps, and
other dynamic data.
2. Backend Database (MongoDB):
The backend retrieves and stores user profiles, destinations, feedback, and travel plans in the MongoDB
database. This ensures data persistence and quick retrieval.
3. Backend AI Module (Python – NLP & Recommendation):
User data from the backend is sent to the AI module built in Python, which applies NLP for chatbot
responses and machine learning algorithms for destination recommendations.
4. Backend Web Scraping Module:
This interface fetches external data such as taxi fares, famous food spots, and local events from travel
websites and displays it on the user dashboard.
5. Backend Map API / Weather API:
The backend communicates with APIs like Google Maps and OpenWeather to display routes, nearby
hotels, and real-time weather updates.
6. Admin Panel Backend:
The admin interface allows administrators to add, update, or delete destination data, review user
feedback, and manage platform content.
5.1.2 Purpose
This component interface design maintains clear communication channels between modules, improves
data flow, and supports scalability ensuring the entire system works as a single, integrated travel
platform.
S25BS054
Library Copy
Page 30
AI Based Destination Explorer
5.2 Component-External Entities Interface
The Component–External Entities Interface defines how the AI-Based Destination Explorer system
interacts with outside entities such as users, administrators, and third-party services. It ensures smooth
and secure data exchange between the system and its external environment.
5.2.1 Key External Interfaces:
1. User Interface (Frontend):
Acts as the main point of interaction between the user and the system.
Allows users to sign up, log in, explore destinations, plan trips, and access chatbot support.
All user actions are processed through the frontend, which communicates with the backend via secure
APIs.
2. Administrator Interface:
Enables the admin to monitor system activities, manage destinations, handle user feedback, and update
data.
Ensures that only authorized users can access admin functionalities through authentication mechanisms.
3. Map & Weather APIs:
Connects with external APIs such as Google Maps, OpenWeather, or similar services.
Provides live map data, directions, traffic conditions, and real-time weather updates for selected
destinations.
4. Web Scraping Sources:
Interacts with external travel websites to collect and update data such as taxi fares, hotel pricing, tourist
attractions, and local events.
Ensures the user receives up-to-date and accurate travel information.
5. Email/Notification Service:
Used to send registration confirmations, booking alerts, or group invitations to users. Ensures reliable
communication between users and the system.
6. Database Connection:
Although internal, it acts as an interface between system components and stored data (e.g., user profiles,
destinations, feedback).
Handles queries and maintains data consistency during interactions.
S25BS054
Library Copy
Page 31
AI Based Destination Explorer
5.2.2 Purpose
This interface layer ensures that all external entities can communicate efficiently with the system while
maintaining data privacy, real-time access, and system reliability resulting in a seamless experience for
both users and administrators.
5.3 Component-Human Interface
The Component–Human Interface defines how humans mainly users and administrators interact with
the AI-Based Destination Explorer system. It focuses on the design, accessibility, and usability of all
visual and functional elements that allow humans to communicate effectively with the system.
5.3.1 Key-Human Interface
1. User Interface (UI):
Provides a simple, attractive, and user-friendly web interface for travelers.
Allows users to sign up, log in, explore destinations, plan trips, join travel groups, and chat with the AI
assistant.
Built using ReactJS, Bootstrap, and CSS for a responsive and visually engaging experience across
devices.
2. Admin Interface:
A secure dashboard that enables administrators to manage destinations, view user feedback, monitor
logs, and update information.
Designed with easy navigation and clear controls to minimize complexity.
3. Chatbot Interface (AI + NLP):
Allows users to interact with the system in a natural, conversational way.
The chatbot assists with destination recommendations, navigation help, and travel queries using Natural
Language Processing (NLP).
4. Map & Visualization Interface:
Displays interactive maps, live locations, nearby attractions, and real-time weather data using map and
weather APIs.
Provides a visual travel planning experience to make decision-making easier.
5. Feedback & Rating Interface:
Enables users to rate destinations, share reviews, and provide suggestions for improvement. This
interaction helps enhance system accuracy and user satisfaction over time.
5.3.2 Purpose
The Component–Human Interface ensures smooth and intuitive communication between people and the
system. It aims to make the platform easy to use, visually appealing, and responsive enhancing the
overall travel planning experience for both users and administrators.
S25BS054
Library Copy
Page 32
AI Based Destination Explorer
5.4 Screenshots/Prototype
5.4.1 Workflow
5.4.1.1 User:
The user begins by signing up or logging in to the platform.
After successful login, they input travel preferences like budget, location type, and duration.
The user views personalized destination suggestions and can save or plan trips.
They can also create or join a travel group, share their live location, and chat with group members.
Users can check maps, nearby places, and submit feedback on the experience.
5.4.1.2 Operation Provider:
The system authenticates user credentials at login.
After login, it receives user preferences and forwards them to the AI module.
It handles travel group management, location tracking, and coordination features.
Also integrates live maps, hotel data, emergency contacts, and feedback management.
5.4.1.3 Intelligence Provider (AI System):
The AI module processes user inputs using recommendation algorithms.
It scrapes web data for real-time suggestions (taxi fares, events, festivals).
It powers the chatbot for support and translation using NLP.
AI returns curated destinations and updates to the operation provider for user display.
S25BS054
Library Copy
Page 33
AI Based Destination Explorer
S25BS054
Library Copy
Page 34
AI Based Destination Explorer
5.4.2 Screens
S25BS054
Library Copy
Page 35
AI Based Destination Explorer
S25BS054
Library Copy
Page 36
AI Based Destination Explorer
S25BS054
Library Copy
Page 37
AI Based Destination Explorer
S25BS054
Library Copy
Page 38
AI Based Destination Explorer
S25BS054
Library Copy
Page 39
AI Based Destination Explorer
S25BS054
Library Copy
Page 40
AI Based Destination Explorer
S25BS054
Library Copy
Page 41
AI Based Destination Explorer
S25BS054
Library Copy
Page 42
AI Based Destination Explorer
S25BS054
Library Copy
Page 43
AI Based Destination Explorer
5.5 Additional Information
At this stage, the AI-Based Destination Explorer contains a limited set of destinations, travel packages,
datasets, and integrated APIs, as it has been developed as a Final Year Project (FYP). The current
implementation focuses on demonstrating core functionalities such as AI-driven destination
recommendations, Hybrid RAG based chatbot assistance, booking management, group travel planning,
and faith-friendly travel support.
In a fully developed production version, the system can be expanded to include a significantly larger
number of global destinations, real-time airline and hotel inventories, advanced booking and payment
integrations, multilingual support, voice-enabled interaction, and deeper personalization through
enhanced user profiling. Such enhancements would improve scalability, real-world applicability, and
overall user engagement, making the platform suitable for commercial deployment.
5.6 Other Design Details
Model Optimization
The Hybrid RAG based intelligent chatbot is optimized to balance response accuracy and performance.
Prompt control, temperature tuning, and efficient vector retrieval techniques are applied to reduce
unnecessary token usage and response latency. Lightweight embedding models are preferred to ensure
smooth deployment on web servers without excessive computational overhead.
Scalability Considerations
The system is designed with scalability in mind using a modular architecture. Containerization tools
such as Docker can be used to package backend services, while orchestration platforms like Kubernetes
may be employed in a production environment to efficiently manage increased user traffic, chatbot
requests, and real-time API calls.
Ethical and Compliance Details
The platform follows ethical data-handling practices by minimizing the collection of personally
identifiable information. User authentication data is securely stored using password hashing and tokenbased authentication. All communications between frontend and backend are encrypted using HTTPS,
ensuring compliance with general data protection standards and user privacy expectations.
Dataset Details
The chatbot and recommendation system rely on curated and structured datasets, including destination
information, travel guidelines, and faith-friendly travel content. The system is designed to support
continuous dataset updates, allowing new destinations, policies, and travel insights to be added over time
to improve recommendation accuracy and relevance.
Cloud Hosting Dependencies
The application can be hosted on cloud platforms such as AWS, Azure, or Google Cloud, enabling
reliable performance and global accessibility. Scalable cloud resources support real-time chatbot
inference, API integrations (weather, currency, maps), and database operations, ensuring low latency
and high availability across regions.
S25BS054
Library Copy
Page 44
AI Based Destination Explorer
Chapter 6.
Test Specification and Results
6.1 Test Case Specification
Table 6.1: TC-1
Identifier
Related
requirements(s)
Short description
TC-1
Pre-condition(s)
User is on the Sign-Up page
Input data
Name, Email, Password, Confirm Password
Detailed steps
1.
2.
3.
4.
Expected result(s)
Account created and redirected to Login page
Post-condition(s)
User data saved in database
Actual result(s)
Account created successfully
Test Case Result
Pass
User Registration
Verify successful user registration with valid details
Open the website
Click “Sign-Up”
Enter valid details
Click “Register”
Table 6.2: TC-2
Identifier
Related
requirements(s)
Short description
TC-2
Pre-condition(s)
User already registered
Input data
Email, Password
Detailed steps
1.
2.
3.
4.
Expected result(s)
User redirected to Dashboard
Post-condition(s)
Active session created
Actual result(s)
User successfully logged in
Test Case Result
Pass
S25BS054
Login System
Verify login with correct credentials
Open website
Click “Login”
Enter valid email and password
Click “Login”
Library Copy
Page 45
AI Based Destination Explorer
Table 6.3 : TC-3
Identifier
Related
requirements(s)
Short description
TC-3
Pre-condition(s)
User logged in and opened “Explore Destinations”
Input data
Budget, Duration, Location type, Weather
preference
Detailed steps
1. Go to “Explore Destinations”
2. Enter preferences
3. Click “Get Recommendations”
Expected result(s)
AI displays destination suggestions based on input
Post-condition(s)
Recommendations saved temporarily for user
Actual result(s)
Personalized destinations shown successfully
Test Case Result
Pass
AI Recommendation Engine
Verify AI suggestions based on user preferences
Table 6.4: TC-4
Identifier
TC-4
Related requirements(s) Destination Details
Short description
Verify that user can view detailed info
of selected destination
Pre-condition(s)
Destination displayed on recommendation page
Input data
Selected Destination
Detailed steps
1. Click on a destination
2. View full details (location, attractions, etc.)
Expected result(s)
Full destination info displayed
Post-condition(s)
User stays on destination page
Actual result(s)
Details loaded successfully
Test Case Result
Pass
S25BS054
Library Copy
Page 46
AI Based Destination Explorer
Table 6.5: TC-5
Identifier
Related requirements(s)
TC-5
Short description
Verify user can create a trip itinerary
Pre-condition(s)
User logged in
Input data
Trip duration, Budget, Activities
1.
Open “Plan Trip”
2.
Enter trip details
Click “Generate Itinerary”
Detailed steps
Itinerary Planner
Expected result(s)
Itinerary generated successfully
Post-condition(s)
Itinerary saved for the user
Actual result(s)
Itinerary generated and displayed
Test Case Result
Pass
Table 6.6: TC-6
Identifier
Related requirements(s)
TC-6
Short description
Verify that selected destination displays on map
Pre-condition(s)
Destination selected
Input data
Detailed steps
Destination name
1. Click on “View Map”
Map loads with location pin
Expected result(s)
Map shows destination location
Post-condition(s)
Map remains open for navigation
Actual result(s)
Map displayed accurately
Test Case Result
Pass
S25BS054
Live Map Integration
Library Copy
Page 47
AI Based Destination Explorer
Table 6.7: TC-7
Identifier
Related requirements(s)
TC-7
Short description
Verify creation of travel group
Pre-condition(s)
User logged in
Input data
Group name, Invite email
1.
Click “Create Group”
2.
Enter group name
3.
Add members
Save group
Detailed steps
Group Travel Module
Expected result(s)
Group created successfully
Post-condition(s)
Group visible on dashboard
Actual result(s)
Group created
Test Case Result
Pass
Table 6.8: TC-8
Identifier
Related requirements(s)
TC-8
Short description
Verify real-time chat between group members
Pre-condition(s)
Group created and members joined
Input data
Message text
1. Open group chat
2. Send a message
Check message visibility to all members
Detailed steps
Live Chat in Group
Expected result(s)
Message visible instantly to all members
Post-condition(s)
Message saved in group chat history
Actual result(s)
Chat working properly
Test Case Result
Pass
S25BS054
Library Copy
Page 48
AI Based Destination Explorer
Table 6.9: TC-9
Identifier
Related requirements(s)
TC-9
Short description
Verify that travel data (taxi fares, plans)
fetched successfully
Pre-condition(s)
User on Explore Page
Input data
Destination name
1.
Enter destination
2.
Click “Fetch Info”
System retrieves info via scraping
Detailed steps
Web Scraping Module
Expected result(s)
Travel info displayed correctly
Post-condition(s)
Data saved temporarily for user view
Actual result(s)
Data fetched successfully
Test Case Result
Pass
Table 6.10: TC-10
Identifier
Related requirements
(s)
Short description
TC-10
Pre-condition(s)
User selected destination
Input data
Detailed steps
Destination name
1.
Click “Emergency Info”
System loads nearby hotels and contacts
Expected result(s)
Hotels and contacts shown accurately
Post-condition(s)
Data stored for quick re-access
Actual result(s)
Display working fine
Test Case Result
Pass
S25BS054
Hotel & Emergency Module
Verify nearby hotels and emergency contacts display
properly
Library Copy
Page 49
AI Based Destination Explorer
Table 6.11: TC-11
Identifier
Related requirements(s)
TC-11
Short description
Verify chatbot gives proper suggestions
Pre-condition(s)
Chatbot active
Input data
“Suggest best places for 5day trip in Azerbaijan”
1.
Open chatbot
2.
Enter query
Check chatbot response
Chatbot (NLP)
Detailed steps
Expected result(s)
Chatbot gives relevant answer
Post-condition(s)
Chat log saved
Actual result(s)
Chatbot replied correctly
Test Case Result
Pass
Table 6.12: TC-12
Identifier
TC-12
Related requirements(s) Feedback System
Short description
Verify feedback submission works correctly
Pre-condition(s)
User logged in
Input data
Rating, Comment
Detailed steps
1.
2.
3.
Open Feedback Page
Enter feedback
Click “Submit”
Expected result(s)
Feedback saved successfully
Post-condition(s)
Feedback visible in Admin Panel
Actual result(s)
Feedback submitted successfully
Test Case Result
Pass
S25BS054
Library Copy
Page 50
AI Based Destination Explorer
Table 6.13: TC-13
Identifier
TC-13
Related requirements(s) Admin Login
Short description
Verify admin can log in successfully
Pre-condition(s)
Admin credentials exist
Input data
Admin email and password
1.
2.
3.
Detailed steps
Go to Admin Login
Enter credentials
Click “Login”
Expected result(s)
Admin redirected to Admin Dashboard
Post-condition(s)
Admin session created
Actual result(s)
Admin login successful
Test Case Result
Pass
Table 6.14: TC-14
Identifier
Related requirements
TC-14
Manage Destinations (Admin)
Short description
Verify that admin can add, edit, or delete destinations
Pre-condition(s)
Admin logged in
Input data
Destination details
Detailed steps
1.
2.
3.
Open “Manage Destinations”
Add or edit a destination
Save changes
Expected result(s)
Destination list updated successfully
Post-condition(s)
Changes reflected in database
Actual result(s)
Destination updated successfully
Test Case Result
Pass
S25BS054
Library Copy
Page 51
AI Based Destination Explorer
Table 6.15: TC-15
Identifier
TC-15
Related requirements(s) Logout Functionality
Short description
Verify user logout ends the session properly
Pre-condition(s)
User logged in
Input data
—
Detailed steps
1.
2.
Click “Logout” button
Confirm action
Expected result(s)
User redirected to Homepage
Post-condition(s)
Session terminated
Actual result(s)
Logout successful
Test Case Result
Pass
S25BS054
Library Copy
Page 52
AI Based Destination Explorer
6.2 Summary of Test Results
Table 6.2: Summary of All Test Results
Number of Defects
Found
Number of
Defects
corrected so far
Number of
defects still
need to
be corrected
User Registration and A TC-1, TC-2, TC-15
uthentication Module
3
3
0
AI
Recommendation Engine
Module
2
2
0
TC-5
1
1
0
TC-6
1
1
0
2
2
0
1
1
0
1
1
0
Module Name
Itinerary and Trip Plann
er Module
Map Integration Module
Test cases run
TC-4
Group Travel and
Communication Module
TC-7, TC-8
Web Scraping Module
TC-9
Hotel
and Emergency Info
Module
TC-10
Chatbot (NLP) Module
TC-11
1
1
0
Feedback Module
TC-12
1
1
0
Admin Panel Module
TC-13, TC-14
2
2
0
Complete System
TC-1 to TC-15
15
15
0
S25BS054
Library Copy
Page 53
AI Based Destination Explorer
Chapter 7.
Project Completion Status/Conclusion
Table 7.1: Project Completion Status
Module Name
User Authentication &
Authorization Module
Destination Exploration &
Package Generation Module
AI-Based Hybrid RAG
Chatbot Module
Booking Management
System
Group Travel Planning &
Collaboration Module
Faith-Friendly Travel Tools
(Halal Food, Mosques,
Qiblah, Prayer Times)
Real-Time API Integration
(Weather, Currency, Time
Zone, Maps)
Expense Breakdown & Cost
Estimation Module
Email Notification System
Admin Management
Dashboard
Voice-Based Chatbot
Interaction
Complete System
S25BS054
Status
(Complete, Partially Implemented, Not
Implemented)
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Complete
Library Copy
Page 54
AI Based Destination Explorer
Table 7.2: Objective(s)/Target(s) Status
Target/Objective
Status
(Completed,
Partially Completed,
Not Completed)
Reason(s)
Completed
Fully implemented with lifecycle
handling, status tracking, and email
notifications
Objective 2
Group Travel Planning
& Collaboration
Completed
Core functionality implemented;
advanced analytics and moderation
features pending
Objective 3:
Faith-Friendly Travel
Tools
Completed
Fully integrated using APIs and
geographic calculations
Completed
Weather, currency, time zone,
events, and maps successfully
integrated
Completed
Accurate cost calculations
implemented
Completed
Passport.js, JWT, sessions fully
functional
Completed
Mobile-optimized, user-friendly
interface delivered
7
-
0
-
0
-
Objective 1
Booking Management
System
Objective 4:
Real-Time API
Integration
Objective 5:
Intelligent Expense
Breakdown
Objective 6:
Secure Authentication
& Authorization
Objective 7:
Responsive UI/UX
Design
Number of Targets
Completed
Number of Targets
Partially Completed
Number of Targets
Not Completed
S25BS054
Library Copy
Page 55
AI Based Destination Explorer
References
•
Sommerville, I. (2016). Software Engineering (10th ed.). Pearson Education Limited. ISBN:-.
•
Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner's Approach (9th
ed.). McGraw-Hill Education. ISBN:-.
•
Lewis, P., & Gao, D. (2020). "Retrieval-Augmented Generation for Knowledge-Intensive NLP
Tasks." Proceedings of the 34th Conference on Neural Information Processing Systems (NeurIPS
2020), pp-.
•
MongoDB Documentation. (2023). MongoDB Manual (Version 6.0). Retrieved from
https://docs.mongodb.com/manual/
•
Express.js.
•
Node.js Foundation. (2023). Node.js Documentation (Version 18.x). Retrieved from
https://nodejs.org/docs/latest-v18.x/api/
•
Socket.IO. (2023). Socket.IO
https://socket.io/docs/v4/
•
Passport.js. (2023). Passport.js Authentication Middleware Documentation. Retrieved from
https://www.passportjs.org/docs/
•
OpenStreetMap Foundation. (2023). Overpass API Documentation. Retrieved from
https://wiki.openstreetmap.org/wiki/Overpass_API
•
OpenWeatherMap. (2023). Weather API Documentation (Version 2.5). Retrieved from
https://openweathermap.org/api
•
Eventbrite, Inc. (2023). Eventbrite API Documentation (Version 3). Retrieved from
https://www.eventbrite.com/platform/api
•
OpenAI. (2023). OpenAI API Documentation
https://platform.openai.com/docs/guides/embeddings
•
Gao, Y., Xiong, Y., Gao, X., Jia, K., Pan, J., Bi, Y., Dai, Y., Sun, J., & Wang, H. (2023).
"Retrieval-Augmented Generation for Large Language Models: A Survey." arXiv preprint
arXiv:-. Retrieved from https://arxiv.org/abs/-
•
Brown, T. B., Mann, B., Ryder, N., Subbiah, M., Kaplan, J., Dhariwal, P., et al. (2020).
"Language Models are Few-Shot Learners." Advances in Neural Information Processing Systems
33 (NeurIPS 2020), pp-
•
Karpukhin, V., Oguz, B., Min, S., Lewis, P., Wu, L., Edunov, S., Chen, D., & Yih, W. (2020).
"Dense Passage Retrieval for Open-Domain Question Answering." Proceedings of the 2020
Conference on Empirical Methods in Natural Language Processing (EMNLP), pp-.
(2023).
https://expressjs.com/
S25BS054
Express.js
Documentation
Documentation
Library Copy
(Version
(Version
-
4.18).
4.5).
Embeddings.
Retrieved
Retrieved
Retrieved
Page 56
from
from
from
AI Based Destination Explorer
•
Johnson, J., Douze, M., & Jégou, H. (2019). "Billion-scale similarity search with GPUs." IEEE
Transactions on Big Data, 7(3), pp. 535-547. DOI: 10.1109/TBDATA-
•
Cloudinary. (2023). Cloudinary Media Management API Documentation. Retrieved from
https://cloudinary.com/documentation
•
World Time API. (2023).
https://worldtimeapi.org/
•
ExchangeRate-API. (2023). Currency Conversion API Documentation. Retrieved from
https://www.exchangerate-api.com/docs
•
OWASP Foundation. (2023). OWASP Top Ten Web Application Security Risks. Retrieved from
https://owasp.org/www-project-top-ten/
•
JSON Web Token. (2023). JWT.io - Introduction to JSON Web Tokens. Retrieved from
https://jwt.io/introduction
•
Mongoose. (2023). Mongoose ODM Documentation (Version 7.x). Retrieved from
https://mongoosejs.com/docs/
•
Bootstrap Team. (2023). Bootstrap Documentation (Version 5.3). Retrieved from
https://getbootstrap.com/docs/5.3/
•
Nodemailer. (2023). Nodemailer Documentation - Email Sending Library. Retrieved from
https://nodemailer.com/about/
•
Fette, I., & Melnikov, A. (2011). The WebSocket Protocol (RFC 6455). Internet Engineering
Task Force (IETF). Retrieved from https://tools.ietf.org/html/rfc645
•
HalalTrip. (2023). Muslim-Friendly Travel Guide and Resources. Retrieved from
https://www.halaltrip.com/
•
Islamic Tourism Centre (ITC). (2022). Global Muslim Travel Index 2022. MastercardCrescentRating. Retrieved from https://www.crescentrating.com/
•
GitHub. (2023). Git Documentation and Best Practices. Retrieved from https://git-scm.com/doc
•
Mozilla Developer Network (MDN). (2023). Web APIs Documentation. Retrieved from
https://developer.mozilla.org/en-US/docs/Web/API
•
Stack Overflow. (2023). MERN Stack Development Questions and Answers. Retrieved from
https://stackoverflow.com/questions/tagged/mern
S25BS054
World
Time
Library Copy
API
Documentation.
Retrieved
Page 57
from
AI Based Destination Explorer
Appendix A Glossary
A system that uses Artificial Intelligence algorithms to suggest personalized travel destinations
based on user preferences like budget, weather, location, and trip duration.
•
Natural Language Processing (NLP):
A branch of AI that enables the system to understand and respond to user queries in human
language. In this project, NLP powers the chatbot to answer questions about destinations, hotels,
and attractions.
•
Personalized Suggestions:
Recommendations generated by analyzing user preferences, behavior, and input data. For example,
suggesting beaches for someone who prefers coastal destinations.
•
User Preferences:
The individual choices or inputs given by users such as preferred weather, travel duration, activities, and
destination types (mountains, historical, cultural, etc.).
•
Real-Time Data:
Information that is updated instantly — such as live weather, nearby attractions, or maps — to
enhance the accuracy of travel recommendations.
•
Travel Group Management:
A feature that allows users to create or join travel groups, share locations, chat, and coordinate trips
collectively.
•
Emergency Contact Feature:
A safety module providing emergency helplines like police, ambulance, or embassy numbers for
travelers’ security in any location.
•
Web Scraping:
A technique used to collect travel-related data (e.g., popular destinations, restaurants, or
activities) from various websites to update system information dynamically.
•
Weather API:
An external service that provides real-time weather updates for a selected location, used to suggest
destinations suitable for current or upcoming conditions.
•
Map Integration:
The use of mapping tools (like Google Maps API) to display destinations, routes, and nearby
attractions visually on the system interface.
•
User Dashboard:
A personalized panel where users can view their previous searches, saved destinations, and group plans.
•
Admin Panel:
The management interface that allows administrators to add or update destination details,
monitor user activity, and handle feedback.
S25BS054
Library Copy
Page 58
AI Based Destination Explorer
•
Python:
A versatile programming language used for developing the AI module, data analysis, and NLPbased chatbot in this project.
•
Jupyter Notebook:
A tool used during the AI module’s development and testing phases for training, visualization, and
debugging.
•
Node.js:
A backend runtime environment used to handle server-side logic and manage communication
between the frontend and database.
•
Express.js:
A web framework built on Node.js used to design the server APIs for data transfer between
frontend and backend.
•
React.js:
A JavaScript library used for creating the frontend user interface
interactivity, and user-friendly design.
•
ensuring responsiveness,
MongoDB:
A NoSQL database used to store user profiles, preferences, destinations, and chatbot
interactions in structured collections.
•
OpenAI API / NLP Library:
Used for chatbot intelligence to process user queries and respond with contextual travel information.
•
Google Maps API:
Used to display live maps, routes, and destination markers inside the application.
•
WeatherAPI:
A third-party API integrated to provide real-time temperature, humidity, and weather forecast
details for each location.
The user-facing part of the application (built using ReactJS) where travelers interact e.g., searching
destinations, chatting with the AI, or viewing maps.
•
Backend:
The server-side layer (built using NodeJS and ExpressJS) that handles user requests, connects
with the database, and returns responses to the frontend.
•
Database:
The storage system (MongoDB) that keeps records of destinations, user details, feedback, and
chat histories.
•
API (Application Programming Interface):
The communication bridge between the frontend, backend, and third-party services (like
S25BS054
Library Copy
Page 59
AI Based Destination Explorer
weather and map APIs).
•
RESTful API:
The structured form of APIs used in this system to ensure smooth data exchange via HTTP
methods (GET, POST, PUT, DELETE).
•
Authentication:
The security process that verifies user identity before granting access such as when logging into
the platform or joining a travel group.
S25BS054
Library Copy
Page 60
AI Based Destination Explorer
Appendix B IV & V Report
(Independent verification & validation)
IV & V Resource
Name
S#
Signature
Defect Description
Origin Stage
Status
Fix Time
Hours Minutes
1
2
3
…
Table B.2: List of non-trivial defects
Appendix C Deployment/Installation Guide
The AI-Based Destination Explorer is developed as a full-stack web application, therefore no local
installation is required for end users. Once the system is deployed on a live server, users can access the
application directly through a standard web browser using a designated URL https://project-fypfnzt.onrender.com/
The system is hosted on a cloud-based environment and supports access over the Internet, ensuring
availability across different devices such as laptops, tablets, and smartphones. All core functionalities—
including AI-powered destination recommendations, travel package exploration, group travel planning,
booking management, expense tracking, faith-friendly travel tools (mosque
finder, halal food locator, Qiblah direction), real-time API integrations (weather, currency, maps), and
chatbot-based assistance—are accessible through the web interface.
S25BS054
Library Copy
Page 61
AI Based Destination Explorer
Appendix D User Manual
This manual guides users through all features of the AI-Based Destination Explorer platform.
1. User Registration and Login
• Users can create an account by providing basic information such as name, email, and password.
• Existing users can log in using their registered credentials.
• Secure authentication ensures protected access to user data and travel plans.
2. Exploring Destinations
• On the homepage, users can browse popular destinations displayed as cards.
• Each destination card shows:
• Country and city name
• Featured attractions
• Estimated budget range
• Users can click on any destination to view detailed information.
3. AI-Based Travel Package Generation
• Users can generate personalized travel packages by providing preferences such as:
• Budget range
• Travel duration (days/nights)
• Number of travelers
• Preferred destination
• The AI system analyzes these inputs and generates customized travel recommendations.
• An AI chatbot is available to assist users with queries and suggestions.
4. Viewing Travel Package Details
• Each generated package includes:
• Accommodation details
• Transport options
• Estimated costs (hotel, food, transport, attractions, shopping)
• Total and per-person expense breakdown
• Users can view prices in multiple currencies using real-time conversion.
5. Group Travel Planning
• Users can create travel groups for collaborative planning.
• Invite members using:
• Email invitations
• Unique invite codes
• Group members can:
• Share itineraries
• Chat in real time
• Track shared expenses
• Notifications are sent for group activities and updates.
6. Faith-Friendly Travel Features
• The system provides special tools for Muslim travelers, including:
• Mosque finder with nearby and country-wide search
• Qiblah direction calculator
• Halal food restaurant locator
• Faith-conscious hotel suggestions
• Prayer time notifications are available based on user location.
S25BS054
Library Copy
Page 62
AI Based Destination Explorer
7. Booking and Management
•
•
•
•
•
•
•
•
•
•
•
Users can proceed with booking by:
Selecting travel dates
Confirming number of travelers
Reviewing the final cost
A unique booking reference number is generated.
Users receive automated email confirmations.
Booking status can be tracked as:
Pending
Confirmed
Cancelled
Completed
8. Real-Time Information and Assistance
• Users can access:
• Real-time weather forecasts
• Time zone information
• Local events using integrated APIs
• The Hybrid RAG AI chatbot provides instant, accurate, and context-aware responses.
9. Admin Panel (For System Administrators)
• Administrators can securely log in to the admin dashboard.
• The admin panel allows:
• Managing destinations and travel packages
• Monitoring user bookings
• Managing group travel activities
• Viewing system analytics and logs
• Role-based access control ensures secure system operations.
S25BS054
Library Copy
Page 63