F6.3.12 Manage Revised Trip Plan Creation for Traveller

Header Image
Project:
F6.3.12 Manage Revised Trip Plan Creation for Traveller : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:37
Modified: 08.09.2021 14:47:25
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to manage the production of revised trip plans whenever a change becomes necessary to the trip plan that is currently being implemented.<br/>(2) The ability to request changes to the trip plan either because it is not providing the best possible trip for the Traveller, or because the Traveller requests the change.<br/>(3) Once the request has been received, the ability to send it to the Trip Planning functionality for the creation of a new trip plan that starts from the last known location of the Traveller.<br/>(4) When the revised trip plan is received, the ability to use the Provide Traveller Trip Interface Function to establish that either the Traveller accepts the revised trip plan, or wishes to have further changes made.<br/>(5) Once the revised trip plan has been accepted, the ability to send it to the Manage Store of Trip Plan Data Function and to inform the Implement Trip Plan and Track Traveller Function that a revised trip plan is about to be provided.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_High_Level_Function» F6.3 Support Trip
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_trip_plan_changes_for_traveller
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_revised_trip_plan_after_traveller_approval
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_revised_trip_plan_requirements
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_imlpement_updated_trip_plan
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 7.6.2.15
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_trip_plan_changes_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_revise_trip_plan_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_revised_trip_plan_for_approval
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_trip_plan_changes_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) continuously monitor for receipt of the revise implementing trip plan request and trip plan changes request data flows;<br/>(b) then the first data flow is received in (a), convert its contents into a request for a change to the trip plan and send it to the Trip Planning functionality in the trip plan update from traveller data flow;<br/>(c) as a result of (b) continuously monitor for receipt of the revised trip plan data flow;<br/>(d) when the data flow in (c) is received, send the details of the changes to the Provide Traveller Trip Interface function in the trip plan changes for traveller data flow;<br/>(e) as a result of (d) continuously monitor for receipt of the trip plan changes response data flow;<br/>(f) when the data flow in (e) is received, check its contents and if the changes have been accepted, send the trip plan update data flow to the Private Trip Plan management functionality and also send the implement updated trip plan data flow to the Implement Plan and Track Traveller function;<br/>(g) if the response in (f) is a rejection, revise the trip plan requirements in accordance with the contents of the data flow and send them to the Trip Planning functionality in the trip plan update from traveller data flow;<br/>(h) repeat (c) to (g) until acceptance;<br/>(i) if the second data flow is received in (a) convert its contents into a request for a change to the trip plan and send it to the Trip Planning functionality in the trip plan update from traveller data flow;<br/>(j) repeat (c) to (i) until acceptance.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0