F4.2.7 Manage PT Route Data Store

Frame Repository / Frame Functional View / Functionality / Functional Area F4 - Manage Public Transport Operations / F4. Manage Public Transport Operations / F4.2 Plan PT Service / F4.2.7 Manage PT Route Data Store

Project:

F4.2 Plan PT Service

F4.2.7 Manage PT Route Data Store : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:32
Modified:	08.09.2021 11:24:40

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{4CB95CAB-929A-4f84-B636-86164AAC1B70}
Appears In:	Functional Tree of Area F4 Manage Public Transport Operations, DFD F4.2 Plan PT Service

This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to manage the store of PT Route Static Data, loading it with data provided by other functionality comprising data about the road network served by the PT operation and strategies that have been devised for its management. <br/>(2) The ability to provide data from the store for use in PT service schedule preparation, plus for use at PT stops, by Travellers preparing trip plans and in reports produced by other functionality at the request of the PT Operator.<br/>

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_load_static_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_route_data_for_planning FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F4.2 Plan PT Service FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_route_static_data_for_stops 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_route_static_data_for_travellers FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_route_static_data_for_reports FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 10.4.2.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_urban_road_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.4.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.0.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_read_static_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_current_static_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_route_static_data_updates FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.4.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_inter-urban_road_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) when either of the data flows containing urban road data or inter-urban road data is received, the data that it contains shall be loaded into the store of PT Route Static Data;<br/>(b) when the route static data updates data flow is received, the data that it contains shall also be loaded into the store of PT Route Static Data;<br/>(c) if the data flow containing a request for the current static data is received, the required data shall be obtained from the store of PT Route Static Data;<br/>(d) when all the data in (c) has been obtained, it shall be sent to the Provide PT Operator Interface to PT Schedule Plans function in the route static data for reports data flow;<br/>(e) every time the data flows in (a) or (b) are received, the data that they contain shall be sent to the Plan New Service Schedule function in the route data for planning data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0