F7.3.5 Sort Violation Notifications

Frame Repository / Frame Functional View / Functionality / Functional Area F7 - Provide Support for Law Enforcement / F7 Provide Support for Law Enforcement / F7.3 Process Violation Notifications / F7.3.5 Sort Violation Notifications

Project:

F7.3 Process Violation Notifications

F7.3.5 Sort Violation Notifications : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:38
Modified:	08.09.2021 14:47:43

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{40851971-A935-4f69-B668-62412F36BC19}
Appears In:	Functional Tree of Area F7 Provide Support for Law Enforcement, DFD F7.3 Process Violation Notifications

This Function shall be capable of providing the following facilities: (1) The ability to carry out the classification of the violation notifications received from the functionality in other Functional Areas or directly from the Detect Violation Function. (2) If the violator's identity is not included in the notification, the ability to send the data that is available to the Identify Violator Function for it to be retrieved. (3) The ability to carry out the classification according to different criteria: level of seriousness, field (road, financial, commercial) and repeat offence. (4) Once the classification has been completed, the ability to send it together with all the other information about the violation to the Create File for use in Prosecution Function.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» psle_request_violation_classification FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_inter-urban_violator_ID FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violation_notification_for_storage FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_urban_violator_ID FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violator_data_for_image_analysis FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F7.3 Process Violation Notifications FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violation_characteristics FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Functional_Area» F7 Provide Support for Law Enforcement FRAME_Functional_Area «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_request_violation_history_for_notification FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.1.7.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violation_type_from_violator_determination FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.psle_illegal_carpark_space_occupancy FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pscs.psle_bus_lane_violation FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violator_ID_from_violator_determination FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 3.1.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.psle_inter-urban_violating_vehicle_identity FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.18 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violation_history_for_notification FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violation_type_from_compliance_check FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.psle_vehicle_entering_inter-urban_zone FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_classification_of_violation FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.psle_inter-urban_vehicle_identity_error FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violation_type_from_image_analysis FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pscs.psle_sensitive_area_entrance_violation FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.psle_urban_vehicle_identity_error FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psle_violator_ID FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.psle_urban_violating_vehicle_identity FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pepf.psle_incorrect_payment_notification FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 3.1.1.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pepf.psle_access_violation_notification FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.psle_vehicle_entering_urban_zone 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 any violation notification sent by the other functionality;<br/>(b) when any of the data flows in (a) is received, process it and extract the violator ID;<br/>(c) if the violator ID is not in the notification received in (b), extract any elements useful for this identification, and send them to the Identify Violator Function, using the violator data for image_analysis data flow;<br/>(d) await receipt of the data resulting from (c) which will arrive in the violation type from image analysis data flow;<br/>(e) note that the data flow in (d) will be accompanied by the violation type from compliance check data flow;<br/>(f) send a request to the Manage Rules Function for classification and rules for the violation in the request violation classification data flow;<br/>(g) as a result of the request in (f) continuously monitor of the receipt of the classification of violation data flow;<br/>(h) send a request to the Store Violations Function to search in the store of Violations Data to see if the violator has already committed other similar offences before using the data flow;<br/>(i) continuously monitor for the receipt of the results of the search in data flow;<br/>(j) dispatch the notifications according to the format of the violation in the first trigger output data flow to the Create File for use in Prosecution Function;<br/>(k) send all the data about the violation to the Violation Function, using the second trigger output data flow;<br/>(l) where the Driver and/or Vehicle ID is known, send the data to the Manage Traffic Area, using the appropriate of the first and second trigger output data flows, depending on whether the violation was committed in the inter-urban or urban road network.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0