28 - Flight Booking System
28 - Flight Booking System
28 - Flight Booking System
This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information.
The document and product are protected by copyright and distributed under licenses restricting their use, copying, distribution,
or transmittal in any form without prior written authorization of Pegasystems Inc.
This document is current as of the date of publication only. Changes in the document may be made from time to time at the
discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This
document does not imply any commitment to offer or deliver the products or services provided. This document may include
references to Pegasystems product features that have not been licensed by your company. If you have questions about
whether a particular capability is included in your installation, please consult your Pegasystems service Consultant.
PegaRULES, Process Commander, SmartBPM® and the Pegasystems logo are trademarks or registered trademarks of
Pegasystems Inc. All other product names, logos and symbols may be registered trademarks of their respective owners.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical
errors. This document or Help System could contain technical inaccuracies or typographical errors. Changes are periodically
added to the information herein. Pegasystems Inc. may make improvements and/or changes in the information described
herein at any time.
Contents
1. Flight Ticket Booking System..............................................................................................6Hrs
1. Flight Ticket Booking System - 12 Hours
Use case ID UC-28 Version 1.0
Use Case Name Flight Ticket Booking System
Platform Details Pega 8.4 Time for completion 6 Hrs
Created By: Nikhila V Last Updated By Kiran
Date Created Last Revision Date: 20th April, 2022
Concepts Covered 1. Case Design (Primary & Alternate stages)
2. Routing – Worklist
3. Multistep form
4. Create PDF
5. Data Transform
6. Correspondence
7. Views
8. Validation
9. Child Cases
10. Delegation
Description AirZ company want to develop application for online flight booking for the customers. In this
use case in order to book the flights tickets online the user can call to CSR(Customer
Support Representative) or login as guest to book tickets by entering the booking details,
customer Details and do the payment. On completion of the payment customer will receive
the ticket details through an email.
Another way is that customer can call to CSR for new registration and can complete the
booking process Or customer can also book tickets through the existing account details.
When customer calls to the CSR for booking the tickets, if he/she is an existing customer
they will be asked to provide customer Id. Based on the customer id they will be able to
book the ticket. In the booking process, customer name will be on the booking page where
in all the ticket booking details need to be provided and has to be confirmed. Upon
confirmation the payment sub case will be initiated. On completion of the ticket booking, a
Booking ID will be generated. Booking ID (first 3 letters of First Name and 4 digits of random
number) along with the booking details will be sent to the customer through an email.
If the customer is new, then CSR will be asked to provide the customer Details. Upon
confirmation of the details the customer will be registered successfully and will be
generated with Customer ID. Customer ID will be sent to the customer through an email.
Then will proceed with the booking process. When the customer login he/she can book
ticket by providing the booking details. On completing the booking details the customer can
go to the payment subcase and can complete the payment. On completion of payment,
booking ID will be generated. Flight ticket along with the booking id and booking details will
be sent to the customers.
Customers can also cancel the tickets by launching the cancellation case type. In
cancellation, it will ask the user to provide the Booking id. Based on the id provided booking
details will be fetched and customer will be asked to confirm cancellation, Upon
confirmation, booking cancellation mail will be sent to the customer. Customer can book
tickets by calling to CSR. CSR can book, cancel and view the history of the tickets by
specifying the customer ID given by the customer. Admin add, delete and update the flights.
Actors 1. Admin
2. CSR
3. User
Trigger 1. Case is instantiated when a Customer start searching for Flights for ticket Booking.
Preconditions 1. User can be logged in with pre created operator ids.
2. Sample data: as provided in the table below
3.The ‘Date of Travel’ should be pre-populated with the current date and time
4. Initially the ‘Return Date’ field should NOT appear on the screen; it should appear
only when the ‘Two Way’ selected for ‘Flight Booking’
5. ‘Button’ format should match exactly as shown in the UI mock-up
6. Date fields should match the format shown in UI mock-up
7. ‘Special Note’ should NOT appear initially, it is required field only when the ‘Special
instructions for the staff in flight’ check box selected
Post conditions 1. All fields are mandatory; System should not allow to submit the form if any of the
field is not provided with value.
2. Once user submits the form, all the values should be persisted into ‘Booking’ data
type, it is not worktable, client want to save into Data Type and as local data
storage.
Normal Flow 1. User first selects the options to login as a guest user, existing user or new user.
2. When user selects the existing user he/she will be promoted to specify the
customer id and then he/she will selects the value for ‘Flight Booking’ field (can be
‘One Way’ or ‘Two Way’); if ‘Two way’ selected ‘Return Date’ field should appear.
3. Then selects the ‘Departure City’, next selects the ‘Destination City’; Please note,
the city selected in ‘Destination City’ drop down should not be same as in
‘Departure City’ drop down. For Example; if Departure City is ‘Hyderabad’ then
Destination city cannot be ‘Hyderabad’
4. Next goes to select ‘Date of Travel’ and ‘Return Date’; ‘Return Date’ should always
greater than the ‘Date of Travel’
5. On Selecting the dates, Departure and destination city he/she will select the
submission for flight search and it will display the list of flights available
6. Now he/she will be selecting one flight from the available list and will specify the
Number of adults, infants (below 2 years) and children (2-12 years), he/she will
select the Travel class (Business, Economy, premium Economy).
7. Next they will be provided with an option for extra baggage chargers which they can
opt.
8. On submitting the Details payment sub case will be initiated where he/she will be
completing the payment. In the payment subcase he/she can opt for payment
modes credit card, debit card, net banking, and UPI options and can complete the
payment.
9. On completing the payment he/she will be receiving the Booking confirmation mail
along with the Booking ID
Alternative flow N/A
UI Mock up
Hyderabad
Bangalore
Chennai
Delhi
Below table list the Flight Details. In the user interface screen of flight search, the below details
from the table should be appearing as a list.