F5.14.1 Provide Driver Interface for Trip Planning

Frame Repository / Frame Functional View / Functionality / Functional Area F5 - Provide Support for Host Vehicle Systems / F5. Provide Support for Host Vehicle Services / F5.14 Provide In-vehicle Trip Planning & Implementation / F5.14.1 Provide Driver Interface for Trip Planning

Project:

F5.14 Provide In-vehicle Trip Planning & Implementation

F5.14.1 Provide Driver Interface for Trip Planning : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:34
Modified:	08.09.2021 14:47:00

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{31A36D82-88DF-43bb-9D3A-BF5F2B9FECEF}
Appears In:	SSTP Function Allocation, High Level Function Information Service, DFD F5.14 Provide In-vehicle Trip Planning & Implementation, Functional Tree of Area F5 Provide Support for Host Vehicle Services

This Function shall be capable of providing the following facilities: (1) A HMI through which the Driver can create, initiate and modify Vehicle Trip Plans. (2) The HMI shall enable the Driver to provide data from which new Trip Plans can be created, draft Trip Plans modified, created Trip Plans accepted and implementing Trip Plans changed. (3) The HMI shall enable the Driver to initiate the implementation of a previously created Trip Plan.

Associations To
Associations From
Requirements
Advanced
Other Links

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» td.tpd-modified_vehicle_trip_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_accept_revised_vehicle_trip_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_implement_vehicle_trip_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F5.14 Provide In-vehicle Trip Planning & Implementation FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_trip_plan_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_trip_plan_acceptance FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» td.tpd-draft_vehicle_trip_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» fd.tpd-modified_vehicle_trip_plan_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.19 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_trip_plan_draft FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd.tpd-vehicle_trip_plan_accepted FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd.tpd-implement_vehicle_trip_plan FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd.tpd-vehicle_trip_plan_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd.tpd-modify_current_vehicle_trip_plan FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs_revised_vehicle_trip_plan_for_driver FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.22 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.15 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd.tpd-accept_revised_vehicle_trip_plan 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 from the Driver of the data flow containing vehicle trip plan data or the implement vehicle trip plan data flow;<br/>(b) when first the data flow in (a) is received, send the data about the vehicle trip plan that is to be created to the Create and Revise Vehicle Trip Plan function in the data flow containing vehicle trip plan data;<br/>(c) as a result of (b) continuously monitor for receipt of the vehicle trip plan draft data flow;<br/>(d) when the data flow in (c) arrives, re-format its contents if required and output them to the Driver in the draft vehicle trip plan data flow;<br/>(e) as a result of (d), continuously monitor for receipt of either the modified vehicle trip plan data or vehicle trip plan accepted data flows;<br/>(f) when the first data flow in (e) is received, use its contents to repeat (b) to (d);<br/>(g) when the second data flow in (e) is received, send the acceptance to the Prepare and Revise Trip Plans function in the vehicle trip plan acceptance data flow;<br/>(h) when the second data flow in (a) is received, send the details of the vehicle trip plan that is to be implemented to the Implement Vehicle Trip Plan and Track Vehicle function in the implement vehicle trip plan data flow;<br/>(i) as a result of (h) continuously monitor for receipt of the revised vehicle trip plan for driver data flow;<br/>(j) when the data flow in (i) is received, re-format its contents if required and output them to the Driver in the modified vehicle trip plan data flow;<br/>(k) as a result of (j) continuously monitor for the receipt of either the modify current vehicle trip plan or accept revised vehicle trip plan data flows;<br/>(l) when the first data flow in (k) is received, put its contents into the data flow containing vehicle trip plan data and send it to the Create and Revised Vehicle Trip Plan function;<br/>(m) as a result of (l) repeat (i) to (k);<br/>(n) when the second data flow in (k) is received, send the acceptance to the Prepare and Revise Trip Plans function in the accept revised vehicle trip plan data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0

Object	Type	Connection	Direction	Notes
Service Provider Main Application	Object	Usage	From
SSTPIS End User Application	Object	Usage	From