F4.6.3 Manage Vehicle Sharing Information

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.3 Manage Vehicle Sharing Information

Project:

F4.6 Provide Facilities for Vehicle Sharing

F4.6.3 Manage Vehicle Sharing Information : 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:	Updae after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{77F474EF-B1AA-4def-BDBF-F826363D1E8C}
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) The ability to manage the store of Vehicle Sharing Data which contains data about Car Sharers and their travel plans. (2) As one part of the management activity, it shall be possible for a Vehicle Sharers to register to take part in shared travel by providing sufficient data about the trips that they wish to make and their willingness to share their own Vehicle, or share Vehicles belonging to other Vehicle Sharers. (3) Another part of the management activity shall enable a record to be kept of the currently accepted travel plans for use in new travel plans, or for retrieval by the Vehicle Sharers involved in them. (4) A further part of the management activity shall control access to the store of Vehicle Sharing Data so that Vehicle Sharers may only see the travel plans in which they are active participants. (5) The store of information about each Vehicle Sharer must conform to the requirements of the relevant European Data Protection laws and any local variations that may have been introduced. (6) If notice of a Vehicle Sharer de-registering is received from the Vehicle Sharer interface functionality, details of the affected travel plans shall be sent back to that functionality for output to the other Vehicle Sharers who are involved in them.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Functional_Area» F4. Manage Public Transport Operations FRAME_Functional_Area «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_travel_plans FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_load_vehicle_sharing_data 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_requested_current_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_read_vehicle_sharing_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.3.0.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_existing_travel_plans FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_accepted_travel_plan FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_vehicle_sharer_details FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_current_travel_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 the receipt of the Vehicle Sharer details, request current travel plan, request existing travel plans and accepted travel plan data flows;<br/>(b) when as a result of (a) the vehicle sharer details data flow is received, securely store its contents in the store of Vehicle Sharing Information Data through the load vehicle sharing data flow, using this process as a means of registering the Vehicle Sharer;<br/>(c) when as a result of (a) the request current travel plan data flow is received, only collect the travel plan(s) for the registered Vehicle Sharer that made the request from the store of Vehicle Sharing Information Data through the read vehicle sharing data flow and send that to the Provide Vehicle Sharer Interface function in the requested current travel plan data flow;<br/>(d) when as a result of (a) the request existing travel plans data flow is received, send collect all the existing travel plans from the store of Vehicle Sharing Information Data through the read vehicle sharing data flow and send them to the Create Travel Plans for Vehicle Sharing function using the requested travel plans data flow;<br/>(e) when as a result of (a) the accepted travel plan data flow is received, securely store its contents in the store of Vehicle Sharing Information Data through the load vehicle sharing data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0