F7.1.2 Check Compliance

Header Image
Project:
F7.1.2 Check Compliance : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:38
Modified: 23.12.2021 10:09:56
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to check the compliance of the recorded images with the established rules both in real-time and/or off-line.<br/>(2) For Vehicles that can be identified, the ability to extract from the store of User's Registration Data the information needed to check that the user is allowed to behave as in the recorded image.<br/>(3) For Vehicles that cannot be identified, the ability to request it from the Identify Violator Function, sending it an image of the violator extracted from the response.<br/>(4) The ability to apply the rules more or less strictly according to guidelines sent by functionality in the Manage Traffic Function Area.<br/>(5) Upon detection of a violation, the ability to send the associated elements to the Process Violation Notifications Function.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» psle_violation_type_from_compliance_check
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_user_clearance_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F7.1 Detect Violation
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_user_image
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_violator_ID
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psel_reqest_relevant_rules
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:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» psle_requested_relevant_rules
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_vehicle_ID_for_detection
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.0.3
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_measure
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.0.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_rules_read
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.psle_urban_enforcement_compliance_guidelines
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_user_clearance_read
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.0.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.psle_inter-urban_enforcement_guidelines_CC
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, analyse the measure to detect obvious violations, using the guidelines received in the third and fourth other input data flows;<br/>(b) if the Vehicle ID is available, extract from the store of User Registration Data the clearance of the vehicle using the fifth other input data flow;<br/>(c) if the Vehicle ID cannot be determined in (b), use the first trigger output data flow to send the relevant image to the Identify Violator Function to get the ID;<br/>(d) wait for the return of the Vehicle ID in the second trigger input data flow;<br/>(e) extract from the store of Rules Data the corresponding authorised values for the measured parameter, using the fifth other input data flow;<br/>(f) compare the values, and if discrepancy less than that allowed by the guidelines take no further action;<br/>(g) if discrepancy greater than that allowed by the guidelines, send the violator ID and other violation elements to the Process Violation Notification Function using the second and third trigger output data flows.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0