F8.4.2 Manage Freight Transport Execution Plan Store

Frame Repository / Frame Functional View / Functionality / Functional Area F8 - Manage Freight and Fleet Operations / F8. Manage Freight and Fleet Operations / F8.4 Manage FTEP Preparation / F8.4.2 Manage Freight Transport Execution Plan Store

Project:

F8.4 Manage FTEP Preparation

F8.4.2 Manage Freight Transport Execution Plan Store : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	16.08.2021 16:55:36
Modified:	20.12.2021 15:10:05

Project:
Author:	Richard
Version:	1.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{C9CF0B31-8844-4a24-A819-7403DB01B47A}
Appears In:	Functional Tree of Functional Area F8 Manage Freight and Fleet Operations, DFD F8.4 Manage FTEP Preparation

This Function shall be capable of providing the following facilities: (1) Manage the store of previously prepared Freight Transport Execution Plans. (2) Update the store in (1) as and when new Plans are created and approved by other functionality in the Manage Freight and Fleet Operations Functional Area. (3) Provide approved Plans for implementation by other functionality in the Manage Freight and Fleet Operations Functional Area. (4) Respond to requests by providing details of previously prepared Freight Transport Execution Plans.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_High_Level_Function» F8.4 Manage FTEP Preparation FRAME_High_Level_Function «component of»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_requested_existing_FTEP_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_User_Need» 9.11.2.7 FRAME_User_Need «belongsto»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_existing_FTEP_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_FTOM_FTEP_data_response FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_User_Need» 9.11.1.3 FRAME_User_Need «belongsto»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_load_FTEP_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_User_Need» 9.11.1.1 FRAME_User_Need «belongsto»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_requested_FTEP_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mffo_request_existing_FTEP FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_request_FTEP_details FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_FTOM_FTEP_data_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_for_store FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_read_FTEP_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_request_existing_FTEP_details FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Fuctional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously monitor for receipt of the FTEP data request data flow from the Provide FTOM Interface function;<br/>(b) when the data flow in (a) is received, extract the requested FTEP data from the store and return it to the Provide FTOM Interface function in the data flow requested FTEP data;<br/>(c) continuously monitor for receipt of the existing FTEP data flow from the Provide FTU Interface function;<br/>(d) when the data flow in (c) is received, extract the requested FTEP data from the store and return it to the FTU Interface function in the existing FTEP data data flow;<br/>(e) continuously monitor for the request FTEP details data flow from the Implement FTEP function;<br/>(f) when the data flow in (e) is received extract the FTEP data from the store and return it to the Implement FTEP function in the requested FTEP details data flow;<br/>(g) continuously monitor for receipt of the new FTEP for store data flow and when received, load the content into the store creating a new FTEP entry in the process;<br/>(h) continuously monitor for receipt of the request existing FTEP details data flow from the Prepare FTEP function;<br/>(i) when the data flow in (e) is received extract the FTEP data from the store and return it to the Prepare FTEP function in the requested existing FTEP details data flow;<br/>(j) always ensure that there is no conflict between the data flows that load data for a new FTEP into the Data Store and the data flows that read data for an existing FTEP from the Data Store. <br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0