Low Level Function
7.1.2 Check Compliance
Overview
This Function shall be capable of providing the following facilities:
(1) The ability to check the compliance of the recorded images with the established rules both in real-time and/or off-line.
(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.
(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.
(4) The ability to use information sent by functionality in the Manage Freight and Fleet Operations Area.
(5) The ability to apply the rules more or less strictly according to guidelines sent by functionality in the Manage Traffic Function Area.
(6) Upon detection of a fraud, the ability to send the associated elements to the Process Fraud Notifications Function.
Functional Requirements
(a) when the first trigger input data flow is received, analyse the measure to detect obvious frauds, using the guidelines received in the third and fourth other input data flows
(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
(c) when the data has been received in (b) receive the characteristics of the vehicle and its cargo from the Manage Freight and Fleet Operations Area, using the first and second other input data flows
(d) 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
(e) wait for the return of the vehicle ID in the second trigger input data flow
(f) extract from the store of Rules Data the corresponding authorised values for the measured parameter, using the fifth other input data flow
(g) compare the values, and if discrepancy less than that allowed by the guidelines take no further action
(h) if discrepancy greater than that allowed by the guidelines, send the violator ID and other fraud elements to the Process Fraud Notification Function using the second and third trigger output data flows.
Diagrams
Parent Higher Level Function
Input logical dataflows
Output logical dataflows
User needs
Number | Description |
| The system shall enforce the traffic laws and regulations of the region automatically (where possible). |
| The system shall be able to collect the evidence of a violation of the traffic laws and regulations in a manner suitable to justify the application of a legal punishment |
| The system shall be able to provide support for the enforcement of safe behaviour and vehicle priorities. |