Table of Contents

Booking Subsystem.................................................................................................................2
1) Stakeholders:..............................................................................................................................2
 2. Brief Use Case Description..............................................................................................................2
2.1 Booking system:...........................................................................................................................2
2.2 Search..........................................................................................................................................4
2.3 Prices vs address..........................................................................................................................5
2.4 Cancellation policy......................................................................................................................6
2.5 Extenuating Circumstance policy...............................................................................................7
2.6 Review..........................................................................................................................................8
3)Class Diagram................................................................................................................................10
Accommodation Subsystem...................................................................................................11
1) Stakeholders.............................................................................................................................11
2) Brief use case description.........................................................................................................11
3) Use case diagrams.....................................................................................................................13
4) Class Diagram...........................................................................................................................14
5) Reflection on the Activities.......................................................................................................15
References............................................................................................................................16

Booking Subsystem
 1) Stakeholders:

The stakeholders associated with the Airbnb are as follows:

 Hosts
 Guests/Users
 Communities
 Employees

Host: Hosts are the one who is renting the accommodation to guests(users). Hosts share the space
with the guests. They are the one to provide the best and quality service to the guest. They are
the internal operational stakeholders but are the external executive stakeholders in the website.
Guest: Guests are the one to check in. Guest can book any types of room, apartment and Host
can add or remove guests form the reservation prior to checking in and we will not be able to
change the guest count once the reservation is started. They are the external operational
stakeholders as they are the one resulting in transaction and the review of the places.
Employees: They are the one who provide service to the guests. Their service determines the
guest to book the hotel or not. They play and important role and are the internal operational
stakeholders.
Community: It is the groups or the members of the guest, host. They are the internal executive
stakeholder as they share their culture and tradition to the guest.
2. Brief Use Case Description
Note: The below use case diagram is the detailed view of how each event works. To make a
wider understanding for the real-world system analyst.
2.1 Booking system:

Actors Use case Description

User, Online Enter Destination These allows user to find the desired destination.
system
User, Online Property available These allows users/guest to see the available
system properties.
User, Online Select property This use case help user to select the property.
System
User, Host, Online Book property Allows user to book the property and give review
System and rating for the property.
User, Host, Online Request to book This allows user to request to book the property
System property
User, Host Make payment Allows users to make payment.
User, Host Confirmation of Confirms the availability of the property.
availability
User, Host Confirmation Confirms for the property
Accommodation Subsystem
1) Stakeholders
There stakeholders of the proposed sub-system will be as follows:

1. Customers – These are internal operational stakeholders, who register themselves in the
system, they could login into the system, manage their account, do the payments, give the
ratings to the facilities used. They also could also hire some services which are available for
the guests to utilize for their luxury or relaxation.
2. Hosts – These are internal executive stakeholders, who work within the system, they will
register as host and they could login and manage their account. They also could hire some
services which are available for the hosts to utilize for their comfort.
3. Families of hosts – These are external stakeholders, who could work from outside the system
on behalf of the host, they will be registered in the system by the host and they could login
and manage the host account or take any urgent decision or fulfil the customer’s genuine
demand in case of emergency or unavailability of the host. They also could hire some
services which are available for the hosts to utilize for their comfort.
4. Suppliers – These are external operational stakeholders, who would provide services to the
hosts/guests or provide services to the hosts/customers from outside the system, they will be
registered in the system by the admin and they will raise the invoice for the provided service
and will get the payment against it, or there could be monthly contract for the same. They
also could hire some services which are available for the hosts to utilize for their comfort.

2) Brief use case description

The brief use case descriptions are as follows.
Sr No Heading Description
1 Use Case name: Add a host
Brief description: System receives host basic requirement details, validates
the entered details and registers the host.
Actors: Host, Admin
2. Use Case name: Add a Customer
Brief description: System receives Customer details, validates the entered
details and registers the Customer.
Actors: Customer, Admin
3 Use Case name: Add a Supplier
 Brief description: System receives Supplier details, validates the entered
details and registers the Supplier.
Actors: Host, Supplier, Admin
4. Use Case name: Add a Service Provider
Brief description: System receives Service Provider details, validates the
entered details and registers the Service Provider.
Actors: Host, Service Provider, Admin
5. Use Case name: Add a Listing
Brief description: Host enters the listing details, System receives
requirement details, validates the entered details and
registers the Listing.
Actors: Host, Admin
6. Use Case name: Add the House Rules
Brief description: Host enters the House rules for the entered listing,
System receives requirement details, validates the entered
details and saves the rules in the system.
Actors: Host, Admin
7. Use Case name: Setup the listing nightly price
Brief description: Host selects the nightly price for the listing, System
receives details, validates the entered details and sets the
nightly price for the listing of the host.
Actors: Host, Admin
8. Use Case name: Add a Book the facility
Brief description: Customer or traveller searches the listing, selects as per
his choice, and submits the enquiry; System receives
requirement details, validates the entered details, and
reserves the listing for the customer. System sends the
reservation details to host for approval.
Actors: Customer, Host, Admin
9. Use Case name: Book any service
Brief description: Host opts to have the services for his listing, System
receives host requirement details, validates the entered
 details and registers the service. System sends the
message to service provider to provide the selected
service.
Actors: Host, Service Provider, Admin
10 Use Case name: Make a payment to service provider for booked service
by host
Brief description: Host utilizes the service from specific service provider,
selects the payment option and makes the payment.
System receives payment details, validates the entered
details and initiates the payment to service provider.
System sends confirmation to service provider.
Actors: Host, Service Provider, Admin