F7.3.6 Create File for use in Prosecution

Header Image
Project:
F7.3.6 Create File for use in Prosecution : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:38
Modified: 23.12.2021 10:11:33
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to send the file containing all the elements necessary for the prosecution of the violator to the most appropriate Law Enforcement Agency.<br/>(2) As part of the process of preparing the file, the ability to check that the violation is not the result of an instruction that has been given to and acknowledged by a Driver and to abandon the prosecution process if it was.<br/>(3) The ability to also send the resulting file, plus all the elements received, to the functionality that stores violation notifications.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» psle_request_violation_history_for_prosecution
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tlea-psle_prosecution_file
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_prosecution_file
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_check_insructions_recieved
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_User_Need» 3.1.0.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_violation_characteristics
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» psle_violation_history_for_prosecution
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_check_instructions_results
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.1.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.7.7
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) receive all the elements related to the violation in the first trigger input data flow;<br/>(b) select the Law Enforcement Agency(ies) concerned by the violation from the data received in (a);<br/>(c) if necessary extract information on previous offences from the store of Violations Data, receiving the data in the first other input data flow;<br/>(d) send a data flow to check that the detected violation is not the result of instructions sent to Drivers, and abandon the creation of the prosecution file at this point if the response is that it is;<br/>(e) fill the prosecution file using to the format required by the Law Enforcement Agency identified in (b);<br/>(f) send the prosecution file to the Law Enforcement Agency using the third trigger output data flow;<br/>(g) send the prosecution file and all the associated elements to the Violation Function, using the second trigger output data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0