Overview

This Function shall be capable of providing the following facilities:

(1) The ability to make any bookings for services that are needed as part of a trip, or to make payment for the use of the actual trip planning service itself.
(2) For bookings of services that are needed as part of a trip, the ability to select the best choice of services to be booked based on what they provide and the price to be paid, i.e. obtain the best value for money.
(3) If the best choice cannot be used, the ability to suggest possible alternatives to the Traveller by sending their details to the Provide Traveller Trip Planning interface.
(4) The ability to initiate any necessary payment action by sending the details to the Financial Clearinghouse for processing and waiting for receipt of confirmation that payment has successfully been made.
(5) The ability to cancel all of the bookings made for a previous trip and send a confirmation message to the Provide Traveller Trip Planning interface when a "cancel bookings" request is received.

Functional Requirements

(a) continuously monitor for receipt of the full trip description data flow from the Provide Traveller Trip Planning Interface function;
(b) when the data flow in (a) is received, check its contents to see if any payment for the actual trip planning service is needed;
(c) if the answer to the question in (b) is yes, request payment from the traveller by sending the request trip planning payment data flow to the Provide Traveller Trip Planning Interface function;
(d) as a result of (c) continuously monitor for the receipt of the trip planning payment data flow from the Provide Traveller Trip Planning Interface function;
(e) when the data flow in (d) is received, check for payment information and if found, send this to the financial clearinghouse in the trip planning payment request data flow;
(f) as a result of (e), continuously monitor for receipt of the payment for trip planning response data flow from the financial clearinghouse;
(g) when the data flow in (f) is received, check to see if it was successful and if not, send the booking mishap data flow to the Provide Traveller Trip Planning Interface function and repeat (c) to (f), or if this is for the third time, delete the trip plan, and send a message to the Provide Traveller Trip Planning Interface function that the trip plan has been deleted in the request trip planning payment data flow;
(h) if in (e) a negative response is received, delete the trip plan, and send a message to the Provide Traveller Trip Planning Interface function that the trip plan has been deleted in the request trip planning payment data flow;
(i) if in (b) no trip planning payment is needed, then send details of the advanced payment(s) that are needed for the trip plan to the Provide Traveller Trip Planning Interface function in the advanced payment needed for trip plan data flow;
(j) as a result of (i) continuously monitor for receipt of the booking approval data flow from the Provide Traveller Trip Planning Interface function;
(k) when the data flow in (j) is received, check for payment information and if found, send this to the financial clearinghouse in the trip planning service payment request data flow
(l) as a result of (k), continuously monitor for receipt of the trip planning service payment response data flow from the financial clearinghouse
(m) when the data flow in (f) is received, check to see if it was successful and if not, send the booking mishap data flow to the Provide Traveller Trip Planning Interface function;
(n) as a result of (m), continuously monitor for receipt of the revised booking choices data flow and repeat (i) to (l);
(o) if in (k) a negative response is received, delete the trip plan, and send a message to the Provide Traveller Trip Planning Interface function that the trip plan has been deleted in the request trip planning payment data flow;
(p) if the cancel bookings for trip data flow is received, repeat (m) and (n) and send a cancel booking instruction to the financial clearinghouse in the request payment for trip planning data flow.

Diagrams

Parent Higher Level Function

• 6.5 Prepare Trip Plan

Input logical dataflows

• ffc-payment_for_trip_planning_response
• ffc-trip_planning_service_payment_response
• ptja_booking_approved
• ptja_cancel_bookings_for_trip
• ptja_full_trip_description_for_bookings
• ptja_trip_planning_payment

Output logical dataflows

• ptja_advanced_payment_needed
• ptja_booking_mishap
• ptja_full_trip_description_with_bookings
• ptja_request_trip_planning_payment
• tfc-request_payment_for_trip_planning
• tfc-trip_planning_service_payment_request

User needs