F3.1.1.5.8 Detect Urban Traffic Violations

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.1 Provide Traffic Control / F3.1.1 Provide Urban Traffic Management / F3.1.1.5 Provide Urban Traffic Management Facilities / F3.1.1.5.8 Detect Urban Traffic Violations

Project:

F3.1.1.5 Provide Urban Traffic Management Facilities

F3.1.1.5.8 Detect Urban Traffic Violations : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:25
Modified:	08.09.2021 11:24:28

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{FA01231C-66D0-44d8-8651-06D7A0A53169}
Appears In:	DFD F3.1.1.5 Provide Urban Traffic Management Facilities, Functional Tree of F3.1.1 Provide Traffic Control

This Function shall be capable of providing the following facilities: (1) The ability to detect violations of urban traffic management commands and report them to the law enforcement functionality. (2) The ability to only report a violation when it is detected that a vehicle does not follow the current urban traffic commands. (3) The ability for details of these commands to be provided by the urban traffic management functionality.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt.psle_urban_violating_vehicle_identity FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F3.1.1.5 Provide Urban Traffic Management Facilities FRAME_High_Level_Function «Componentof»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.4.1.28 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.10.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_c&i_device_status FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_device_s&g_status FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ftrfc-urban_vehicle_identity_for_violations FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.11.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_speed_value FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.1.22 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.7.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_l&s_device_status FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_lane_status 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 second or third trigger input data flows are received, the internal data describing the permitted vehicle movements within the urban road network shall be updated;<br/>(b) the first trigger input data flow shall be continuously monitored and converted into vehicle presence and speed data;<br/>(c) the positions of vehicles produced by (b) shall be compared against that required by (a);<br/>(d) if a vehicle is found in an illegal position by (c), details of the vehicle, the time, date. place and nature of the violation shall be sent to functionality in the Provide Support for Law Enforcement Area using the trigger output data flow;<br/>(e) when the fourth trigger input data flow is received, the internal data describing the permitted vehicle speed shall be updated;<br/>(f) if the vehicle speed obtained from (b) exceeds that specified in (e), details of the vehicle, the time, date. place plus allowed and actual speeds shall be sent to functionality in the Provide Support for Law Enforcement Area using the trigger output data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0