F3.1.4.7 Provide Operator interface for Car Park Management

Header Image
Project:
F3.1.4.7 Provide Operator interface for Car Park Management : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:28
Modified: 08.09.2021 11:24:31
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) A HMI through which the Parking Operator can manage one or a number of car parks.<br/>(2) The HMI shall enable the Parking Operator to set up data about car parks that is loaded into the store of Car Park Data, to provide output of the current static data and to provide output of the current car park data (occupancy and/or number of spaces).<br/>(3) The HMI shall also enable the Parking Operator to override the current status so that for example, a car park can be set to "CLOSED" regardless of how many of its spaces are not being used.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» to.po-carpark_payment_records
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.po-carpark_current_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F3.1.4 Provide Management of Car Parks
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.po-carpark_status_overrride_response
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_override_carpark_status
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_carpark_output_settings
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.po-carpark_static_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_load_carpark_static_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_request_carpark_payment_records
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» fo.po-carpark_payment_record_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_carpark_status_change
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.po-carpark_static_data_inputs
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.po-carpark_status_override
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_read_carpark_static_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.po-carpark_static_data_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_requested_carpark_payment_records
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.po-carpark_current_data_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.po-carpark_output_settings
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) when any of the input data flows are received from the Parking Operator, process them and send the appropriate output data flows to either obtain the requested data or take the requested action;<br/>(b) when any of the data flows containing the responses to the output data flows in (a) are received, output the data they contain using the Parking Operator output data flows.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0