F4.6.1 Provide Vehicle Sharer Interface

Frame Repository / Frame Functional View / Functionality / Functional Area F4 - Manage Public Transport Operations / F4. Manage Public Transport Operations / F4.6 Provide Facilities for Vehicle Sharing / F4.6.1 Provide Vehicle Sharer Interface

Project:

F4.6 Provide Facilities for Vehicle Sharing

F4.6.1 Provide Vehicle Sharer Interface : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:31
Modified:	08.09.2021 11:24:41

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{03E45E36-BEAB-4729-B2FB-DCA15B1A6590}
Appears In:	DFD F4.6 Provide Facilities for Vehicle Sharing, Functional Tree of Area F4 Manage Public Transport Operations

This Function shall be capable of providing the following facilities: (1) A HMI through which the Vehicle Sharer can register or de-register to be included in vehicle sharing travel plans. (2) The HMI shall also enable the Vehicle Sharer to take part in plans that they propose, or are proposed by other Vehicle Sharers. (3) The ability through the HMI for Vehicle Sharers to accept or reject any proposed travel plan to be shared with other Vehicle Sharers and to request and view only those travel plans in which they are active participants. (4) The HMI shall also be capable of operating in a variety of locations and if necessary provide controlled access for registered Vehicle Sharers.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_request_current_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_vehicle_sharer_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.vs-proposed_travel_plan 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» mpto_travel_plan_rejected FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_travel_plan_accepted FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.vs-current_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F4.6 Provide Facilities for Vehicle Sharing FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_vehicle_sharer_travel_needs FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_proposed_travel_plan FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_current_travel_plan FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» flds-vehicle_sharer_location FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-request_current_travel_plan FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.3.0.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.3.0.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-personal_details FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-accept_travel_plan FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.3.0.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-deregistration FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.0.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-travel_needs 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 the receipt of the travel needs data flow from the Vehicle Sharer;<br/>(b) when the data flow in (a) is received, check to see of the personal details of the Vehicle Sharer are available (i.e. the Vehicle Sharer has previously registered by providing their details) and if not, wait for receipt of the personal details data flow from the Vehicle Sharer;<br/>(c) when (b) has been completed, send the Vehicle Sharer travel needs data flow to the Create Travel Plans for Vehicle Sharing function;<br/>(d) when in (b) the personal details for the Vehicle Sharer are received, send them to the Manage Vehicle Sharing Information function in the vehicle sharer details data flow;<br/>(e) as a result of (c) continuously monitor for receipt of the proposed travel plan from the Create Travel Plans for Vehicle Sharing function;<br/>(f) when the data flow in (e) is received, send its contents to the Vehicle Sharer in the proposed travel plan data flow;<br/>(g) as a result of (f) await arrive of the accept travel plan data flow from the Vehicle Sharer;<br/>(h) if the data flow in (g) contains a negative response send the travel plan rejected data flow to the Create Travel Plans for Vehicle Sharing function and include the reasons for rejection that have been provided by the Vehicle Sharer;<br/>(i) if the data flow in (g) contains a positive response send the travel plan accepted data flow to the Create Travel Plans for Vehicle Sharing function;<br/>(j) if the personal details data flow is received from the Vehicle Sharer, send the data it contains to the Manage Vehicle Sharing Information function in the vehicle sharer details data flow;<br/>(k) if the de-registration data flow is received from the Vehicle Sharer, send a delete indication to the Manage Vehicle Sharing Information function in the vehicle sharer details data flow;<br/>(l) continuously monitor for receipt of the vehicle sharer location data flow and when it is received, use its contents in the above request for a travel plan.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0