F6.5.8 Enable Final Approval of Trip Plan : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created:
24.10.2019 12:49:42
Modified:
08.09.2021 14:47:26
Project:
Author:
Update after transfer
Version:
5.0
Phase:
1.0
Status:
Proposed
Complexity:
Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:
{C9B427C7-4C4F-4385-A282-F2850E00E673}
Appears In:
This Function shall capable of providing the following facilities:<br/><br/>(1) The ability to enable the Pre-Trip Traveller to give final approval to the trip plan that has just been prepared.<br/>(2) The ability to provide the Pre-Trip Traveller with the trip itinerary encompassing travel modes, schedules, bookings, payments made and further information coming out of the Trip Planning functionality.<br/>(3) If so desired by the Pre-Trip Traveller, the ability to include any maps for road trips or route descriptions, as well as safety advice concerning all conditions that are likely to be encountered by following the route that have been produced as part of the trip planning process.<br/>(4) The ability for the Pre-Trip Traveller to give final approval to the trip plan after which it will be sent to the Manage Store of Trip Plan Data for implementation when so requested by the Pre-Trip Traveller.<br/>(5) The ability for the Pre-Trip Traveller to cancel the trip at this stage, in which case a "cancel bookings" command shall be sent to the Make Bookings and Payments for Trip Function and the trip planning process will be implemented again from the beginning.<br/>
(a) continuously monitor for the receipt of the full trip description no bookings and full trip description with bookings data flows;<br/>(b) when either of the data flows in (a) is received, put the trip plan details into the itinerary initial data flow and send it to the Pre-Trip Traveller;<br/>(c) continuously monitor for receipt of the final approval data flow from the Pre-Trip Traveller;<br/>(d) when the data flow in (c) is received, check to see if the Pre-Trip Traveller has given final approval;<br/>(e) if the approval has been received in (d), send all of the trip plan data to the Manage Store of Trip Plan Data function in the trip plan ready for implementation data flow;<br/>(f) if a rejection has been received in (d), send the trip plan rejected data flow to the Provide Traveller with Trip Planning Interface function so that the trip plan can be deleted and the trip planning process re-initiated, plus the cancel bookings for trip data flow to the Make Bookings and Payments for Trip function so that all bookings can be cancelled.<br/>
