F3.2.10 Manage Store of Incident Data

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.2 Manage Incidents / F3.2.10 Manage Store of Incident Data

Project:

F3.2 Manage Incidents

F3.2.10 Manage Store of Incident Data : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

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

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{6DBA7FEF-A37F-413d-B627-1C8C5CD54C63}
Appears In:	DFD F3.2 Manage Incidents, Functional Tree of F3.2 Manage Incidents

This Function shall be capable of providing the following facilities: (1) The ability to take responsibility for the management of data about incidents and the production of statistical reports. (2) The ability to receive data about reported incidents and updates to that data from other functionality and incident data from other entities outside the System. (3) The ability to load all the data that is received into the store of Incident Data. (4) The ability to retrieve data from the store of Incident Data for assessment, when requested by other functionality in the System. (5) When a request is received from the functionality providing the HMI for the Road Network Operator, the ability to retrieve the data from the store of Incident Data and produce the required incident statistics reports.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt_load_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_statistics_response FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F3.2 Manage Incidents FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_data_for_assessment FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_requested_incident_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.2.2.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.11 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_read_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_updated_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 9.5.6.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.43 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_request_for_stored_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_new_incident_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_incident_statistics_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_request_incident_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 the first trigger input data flow is received, the data that it contains shall be loaded into the store of Incident Data;<br/>(b) when the second trigger input data flow arrives, if the request is for incident data the required data shall be obtained from the store of Incident Data;<br/>(c) as a result of (b) the data shall be sent to the Operator interface Function in the first trigger output data flow;<br/>(d) if the second trigger input data flow in (b) contains revised incident data, the data in the store of Incident Data shall be updated;<br/>(e) if the second trigger input data flow in (b) requests a report, the required data shall be retrieved from the store of Incident Data;<br/>(f) the data produced in (e) shall be processed into statistical form, and sent to the Operator interface Function in the first trigger output data flow;<br/>(g) when the third trigger input data flow is received, the data it contains shall be loaded into the store of Incident Data;<br/>(h) when the fourth trigger input data flow is received, the data about current and future incidents from the store of Incident Data shall be retrieved;<br/>(i) the data retrieved in (f) shall be sent to the assessment Function in the second trigger output data flow;<br/>(j) when the fifth trigger input data flow is received, the data it contains shall be loaded into the store of Incident Data;<br/>(k) loading and obtaining data from the store of Incident Data shall use the other output and input data flows respectively;<br/>(l) of the above, the activities in (h) and (a) shall take absolute priority over all other activities within the Function;<br/>(m) the integrity and contents of the store of Incident Data shall be maintained and managed to make most efficient use of the space available whilst optimising data access time.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0