F4.7.1 Provide On- Demand Service Traveller Interface

Header Image
Project:
F4.7.1 Provide On- Demand Service Traveller Interface : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:33
Modified: 08.09.2021 11:24:41
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) A HMI through which Pre-Trip Travellers can request an On-Demand Service for some or their entire proposed journey.<br/>(2) The HMI shall enable the Traveller to provide information about the proposed journey, such as origin, destination, required times of departure and arrival, plus any other relevant information, e.g. disabled, elderly, luggage and young children.<br/>(3) Once the Traveller has accepted the proposed service, the HMI shall also enable payment to be requested and only confirm acceptance once payment has been completed.<br/>(4) A separate interface through which payments can be transacted in a safe and secure way.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mpto_demand_service_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F4.7 Provide On-demand Services
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tt.ptt-proposed_demand_service
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Functional_Area» F4. Manage Public Transport Operations
FRAME_Functional_Area «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tfc-demand_service_payment
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_demand_service_payment_successful
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tt.ptt-demand_service
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 10.2.0.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 10.2.0.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ft.ptt-make_demand_service_payment
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ft.ptt-request_demand_service
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ft.ptt-confirm_demand_service
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ffc-demand_service_payment_confirmed
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 10.2.1.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 10.2.0.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 10.2.1.9
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_demand_service_confirmed
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_proposed_demand_service
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) when the request demand service data flow is received from the Traveller, check that all the required input data is present and sent to the Plan Demand Service function;<br/>(b) following (a) when the proposed demand service data flow is received, output the proposed service data flow to the Traveller, including details of any payments that are required;<br/>(c) following (b), when details of how any payment is to be made are provided by the Traveller, send this information via secure link to the Financial Clearinghouse;<br/>(d) following (d), when confirmation of successful payment is received from the Financial Clearinghouse, send the payment made message to the Plan Demand Service function;<br/>(e) when the demand service confirmed message is received, send details of the service to the Traveller.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0