F6.5.9 Make Trip Bookings and Payments

Header Image
Project:
F6.5.9 Make Trip Bookings and Payments : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:37
Modified: 08.09.2021 14:47:26
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(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.<br/>(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.<br/>(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.<br/>(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.<br/>(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.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» ptja_full_trip_description_with_bookings
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tfc-trip_planning_service_payment_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Functional_Area» F6. Provide Traveller Journey Assistance
FRAME_Functional_Area «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_request_trip_planning_payment
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F6.5 Prepare Trip Plan
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tfc-request_payment_for_trip_planning
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_booking_mishap
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_advanced_payment_needed
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 6.2.3.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.1.3.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.1.3.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.4.1.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_booking_approved
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ffc-payment_for_trip_planning_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_cancel_bookings_for_trip
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.1.3.6
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_full_trip_description_for_bookings
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_trip_planning_payment
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.2.3.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ffc-trip_planning_service_payment_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.2.3.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.4.1.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.2.3.3
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.2.3.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) continuously monitor for receipt of the full trip description data flow from the Provide Traveller Trip Planning Interface function;<br/>(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;<br/>(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;<br/>(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;<br/>(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;<br/>(f) as a result of (e), continuously monitor for receipt of the payment for trip planning response data flow from the financial clearinghouse;<br/>(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;<br/>(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;<br/>(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;<br/>(j) as a result of (i) continuously monitor for receipt of the booking approval data flow from the Provide Traveller Trip Planning Interface function;<br/>(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;<br/>(l) as a result of (k), continuously monitor for receipt of the trip planning service payment response data flow from the financial clearinghouse;<br/>(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;<br/>(n) as a result of (m), continuously monitor for receipt of the revised booking choices data flow and repeat (i) to (l);<br/>(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;<br/>(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.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0