Kavre Guide Website Use Case Descriptions

Your Name
January 8, 2025

1 Use Case Descriptions

1.1 Use Case: Register (Tourist)
1.2 Use Case: Login (Tourist)
1.3 Use Case: Search Guides
1.4 Use Case: Book Guide (Tourist)
1.5 Use Case: Send Message (Tourist)
1.6 Use Case: View Bookings (Tourist)
1.7 Use Case: Edit Booking (Tourist)
1.8 Use Case: Delete Booking (Tourist)
1.9 Use Case: Contact Admin (Tourist)
1.10 Use Case: Register (Guide)
1.11 Use Case: Login (Guide)
1.12 Use Case: Update Profile (Guide)
1.13 Use Case: Manage Availability (Guide)
1.14 Use Case: Reply Message (Guide)
1.15 Use Case: View Bookings (Guide)
1.16 Use Case: Edit Booking Status (Guide)
1.17 Use Case: Manage Destination (Admin)
1.18 Use Case: Manage Users (Admin)
1.19 Use Case: Monitor Communication(Admin)

1
Field Description
Title Register (Tourist)
Primary
Tourist
Actor
Pre-
User is on the registration page.
condition
Post- User account created and logged
condition into the system.

1. User provides personal

details (first name, last
name, username, email,
password).
Success
2. System verifies data.
Flow
3. Creates new user account.

4. Logs the user into the sys-

tem.

1. User submits form with

missing fields: system alerts
required fields.

2. User tries to register with

taken username: system
alerts username taken.
Exception
Flow 3. User tries to register with
taken email id: system
alerts email id taken.

4. Passwords do not match:

system alerts password not
matched.

Extends None
Includes None

2
Field Description
Title Login (Tourist)
Primary
Tourist
Actor
Pre-
User is on the login page.
condition
Post-
User is logged into the system.
condition

1. User provides username and

password in login page.

2. System validates provided

credentials against stored
Success
records.
Flow
3. User authenticated.

4. System Logs user into the

system.

1. User submits with empty

fields: system prompts for
required fields.
Exception
Flow 2. Invalid user-
name/password: prompts
error message invalid cre-
dentials

Extends None
Includes None

3
Field Description
Title Search Guides
Primary
Tourist
Actor
Pre-
Tourist is logged in.
condition
Post- System displays a list of available
condition tour guides.

1. Tourist accesses the search

page.

2. System retrieves a list of

Success guides from the database
Flow based on search filter.

3. System displays the filtered

list of guides.

1. No guide found as per filter

Exception criteria: system prompts no
Flow guide found.

Extends None
Includes None

4
Field Description
Title Book Guide (Tourist)
Primary
Tourist
Actor
Pre- Tourist is logged in, on tour guide
condition details page.
Post- Booking request is sent and cre-
condition ated for user.

1. Tourist provides name,

email, preferred date, party
size, and message.

2. System validates data and

checks if Guide is available
Success
on preferred date.
Flow
3. System stores the provided
booking info.

4. Booking success message is

displayed.

1. User submits booking re-

quest with missing fields,
shows error.

2. User submits without

accepting terms, system
prompts for terms.
Exception
Flow 3. User provides booking date
in past, prompts to select a
valid date.

4. Selected guide is not avail-

able, prompts to select
available guide.

Extends None
Includes None

5
Field Description
Title Send Message (Tourist)
Primary
Tourist
Actor
Pre-
Tourist is logged in.
condition
Post-
Message is sent to the tour guide.
condition

1. Tourist composes a message

for the tour guide.

2. System stores the message

Success in database.
Flow
3. Message sent to guide.

4. Success message displayed

to tourist.

1. User submits without mes-

Exception sage, shows required mes-
Flow sage.

Extends None
Includes None

6
Field Description
Title View Bookings (Tourist)
Primary
Tourist
Actor
Pre-
Tourist is logged in.
condition
Post- System displays a list of bookings
condition for tourist.

1. Tourist access his dash-

board.

2. System retrieves the list of

Success the bookings for the tourist
Flow from database.

3. System displays the list of

bookings.

Exception 1. No booking found. Prompt

Flow ”No bookings yet”.

Extends None
Includes None

7
Field Description
Title Edit Booking (Tourist)
Primary
Tourist
Actor
Pre- Tourist is logged in and is viewing
condition a list of bookings.
Post-
Booking details are updated.
condition

1. Tourist selects a booking he

wants to edit.

2. System displays the details

of the selected booking.
Success
Flow 3. Tourist updates the desired
field.

4. System stores the updated

booking.

1. User submits with empty

fields: system prompts for
required fields.
Exception
Flow 2. User provides booking date
in past, prompts to select a
valid date.

Extends None
Includes None

8
Field Description
Title Delete Booking (Tourist)
Primary
Tourist
Actor
Pre- Tourist is logged in, viewing a list
condition of bookings.
Post- Selected booking is deleted from
condition the system.

1. Tourist selects a booking he

wants to delete.
Success 2. System prompts to confirm.
Flow
3. System deletes selected
booking if confirmed.

1. User cancels the delete op-

Exception eration. system retains the
Flow booking.

Extends None
Includes None

9
Field Description
Title Contact Us (Tourist)
Primary
Tourist
Actor
Pre-
User is on the contact us page.
condition
Post- Contact request is submitted to
condition the system.

1. User provides name, email,

subject, and message.

2. System validates the data.

Success
Flow 3. System stores the contact
info.

4. Success message is dis-

played to the user.

Exception 1. User submits with empty

Flow fields, prompts to fill out.

Extends None
Includes None

10
Field Description
Title Register (Guide)
Primary
Tour Guide
Actor
Pre- User is on the guide registration
condition page.
Post- Guide account created and logged
condition into the system.

1. Guide provides personal

and professional details on
the register page.
Success 2. System verifies data.
Flow
3. Creates new guide account.

4. Log the user into the sys-

tem.

1. User submits form with

missing fields: system alerts
required fields.

2. User tries to register with

taken user name: system
alerts user name taken.
Exception
Flow 3. User tries to register with
taken email id: system
alerts user email id taken.

4. Passwords do not match:

system alerts password not
matched.

Extends None
Includes None

11
Field Description
Title Login (Guide)
Primary
Tour Guide
Actor
Pre-
User is on the guide login page.
condition
Post-
Guide is logged into the system.
condition

1. User provides username and

password in login page.

2. System validates provided

credentials against stored
Success
records.
Flow
3. User authenticated.

4. System Logs user into the

system.

1. User submits with empty

fields: system prompts for
required fields.
Exception
Flow 2. Invalid user-
name/password: prompts
error message invalid cre-
dentials

Extends None
Includes None

12
Field Description
Title Update Profile (Guide)
Primary
Tour Guide
Actor
Pre-
Tour guide is logged in.
condition
Post-
Tour guide profile is updated.
condition

1. Tour guide accesses the up-

date profile page.

2. Tour guide updates his pro-

file details.
Success
Flow 3. System saves the updated
data.

4. Success message is dis-

played.

Exception 1. User submits with empty

Flow fields, prompts to fill out.

Extends None
Includes None

13
Field Description
Title Manage Availability (Guide)
Primary
Tour Guide
Actor
Pre-
Tour Guide is logged in.
condition
Post-
Guide availability updated.
condition

1. Guide selects a start date

and end date for the avail-
ability period.

2. System validates the dates.

Success
Flow 3. Availability data stored and
updated.

4. Success message is dis-

played.

1. User submits without dates,

prompts to input required.
Exception
Flow 2. End date provided prior to
start date, prompts an er-
ror.

Extends None
Includes None

14
Field Description
Title Reply Message (Guide)
Primary
Tour Guide
Actor
Pre- Tour Guide is logged in and has
condition received a message.
Post-
Reply message is sent to tourist.
condition

1. Tour Guide selects to reply

the message.

2. System displays the mes-

sage from tourist.

3. Guide composes a reply

Success message for the tourist.
Flow
4. System stores the message
in the database.

5. Message sent to tourist.

6. Success message is dis-

played.

1. User submits without mes-

Exception sage, prompts for required
Flow message.

Extends None
Includes None

15
Field Description
Title View Bookings (Guide)
Primary
Tour Guide
Actor
Pre-
Tour Guide is logged in.
condition
Post- System displays the list of book-
condition ings for the tour guide.

1. Guide access dashboard.

2. System retrieves the list of

Success bookings assigned to guide
Flow from database.

3. Display the list of bookings

with tourist information.

Exception 1. No booking found. Prompt

Flow ”No bookings yet”.

Extends None
Includes None

16
Field Description
Title Edit Booking Status (Guide)
Primary
Tour Guide
Actor
Pre- Tour Guide is logged in and view-
condition ing a list of bookings.
Post-
Booking status is updated.
condition

1. Tour guide selects a book-

ing that he wants to edit the
status of.

2. System displays the book-

ing details with current sta-
Success tus.
Flow
3. Tour guide updates the sta-
tus of the booking (Con-
firm/Reject/Cancel)

4. System stores the updated

status

Exception 1. Status is already updated,

Flow prompts an error.

Extends None
Includes None

17
Field Description
Title Manage Destination (Admin)
Primary
Admin
Actor
Pre-
Admin is logged in.
condition
Post- Admin is able to manage all the
condition destinations.

1. Admin selects to add new,

edit or delete destination.

2. System displays the form

to add or edit or select to
Success delete.
Flow
3. Admin proceeds with the
desired operation.

4. Destination details is man-

aged as per selection.

1. Form is submitted with

Exception empty fields: prompt for re-
Flow quired fields.

Extends None
Includes None

18
Field Description
Title Manage Users (Admin)
Primary
Admin
Actor
Pre-
Admin is logged in.
condition
Post- Admin is able to manage all the
condition system users.

1. Admin selects to add, edit

or delete user.

2. System displays the form to

add/edit or select user for
Success
deletion.
Flow
3. Admin proceeds with de-
sired operation.

4. System users are managed.

1. Form is submitted with

Exception empty fields, prompts for
Flow required fields

Extends None
Includes None

19
Field Description
Use Case Monitor Communication (Ad-
Name min)
Primary
Admin
Actor
Pre- The Admin is logged in and has
condition access to the system’s dashboard.
Admin can view or intervene in
Post-
messages exchanged between the
condition
Tourist and the Guide, if needed.

1. Admin accesses the ”Com-

munication Logs” section of
the dashboard.

2. System retrieves and dis-

plays a list of commu-
nication threads between
Normal Tourists and Guides.
Flow
3. Admin selects a specific
thread to view its details.

4. Admin reviews messages

exchanged and optionally
takes action (e.g., flag,
archive, or delete).

1. No communication records
found: system displays
”No communication records
available.”
Exception
Flow 2. Admin attempts to access
restricted data: system de-
nies access and logs the
event.

Retrieve Communication
Includes
Records.
Extends None.

20