uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

Technical Function

UART

If the button is pressed, UART messages indicating the press duration are sent.

Warnings

Safety (1)

Safety Warnings for TechnicalFunction UART.
Safety warnings are related to the Requirements Layer, especially the SIL

UART has a SIL required of SIL_1 but a SIL achieved of QM. This is caused by the following referenced implementation units: USART (QM), ButtonRead (QM), UART out (QM), run_UART_send (QM), run_UART_wakeUp (QM), run_readButton (QM)

Diagrams

Relationships

Requirements Model
Logical Function Model
Software Model
Hardware Model

Safety

Required
The highest SIL derived from SafetyRequirements.
SIL derived 		SIL_1
This attribute allows to overwrite the derived SIL level. The result is the SIL effective attribute.
SIL manual 		derived
The reason why the derived SIL is ignored and an explicit SIL is set.
reason
The SIL required for this implementation unit is defined by the derived SIL but can be overwritten by "SIL manual".
SIL required 		SIL_1
Achieved
Calculated from referenced implementation units.
SIL achieved 		QM
A justification why a certain SIL was achieved.
justification

Properties

Base
The name of this object. Certain classes of objects require this field to be unique. Please consider that this field might be used in code and thus must not contain special characters.
Name 		UART
The type of this object within the uRTE model
Type 		TechnicalFunction
A descriptive text for this object. Please consider that this field might be used in code and thus must not contain special characters.
Description

If the button is pressed, UART messages indicating the press duration are sent.
A user defined ID which can be freely chosen. Please consider that this field might be used in code and thus must not contain special characters.
User-ID 		TechnicalFunction_85
Each object within the uRTE model has a unique ID, this is the ID for this object
UID 		_nLRL4Oc0EeyMHMAOoLxcsQ
References

Software units (5)

Sofware units this technical function is associated with.

Unit Parent Function calls other Software Elements Technical Functions Requirements Type Tasks WCET Stack ROM Globals ProtectionSets SIL required SIL achieved sub Technical Functions (R) sub Requirements (R) Has a return value (R) SystemStates (R) Ingoing Trigger Ports (R) Outgoing Trigger Ports (R) Ingoing Data Ports (R) Outgoing Data Ports (R) Signals (D) Runnables (D) DataType (D) Is Synchronous (D) Hardware (D) Ports (G) Callers (F) Return Type (F) Parameters (F)
ButtonRead

Reads the current button state from hardware

 Button
InDriver 0 0 0
SIL_1 QM - - - - - - - - uRTE_boolean_t true - - - -
UART out

writes Data to the UART module.
No DataType is chosen, so that a typedef file will be generated.

 UART
OutDriver 0 0 0
SIL_1 QM - - - - - - - - None true - - - -
run_UART_send

Sends UART messages periodically via the UART signal

 UART
Runnable 0 0 0
SIL_1 QM
true
  • Runnable_run_UART_send_TPortIN_1
  • Runnable_run_UART_send_DPortIN_1
  • Runnable_run_UART_send_DPortIN_2
  • Runnable_run_UART_send_UART_OUT
 - - - - - - - - -
run_UART_wakeUp

Runnable to switch into the UART state if there is an event in the Blink State.
This runnable does not use hardware signals but accesses hardware directly and is therefore associated with
an protection set grandting access to hardware.

 UART
Runnable 0 0 0
SIL_1 QM
true
  • Runnable_run_UART_WakeUP
- - - - - - - - -
run_readButton

Acquires the button state periodically and provides button signals

 Button
Runnable 0 0 0
SIL_1 QM false
  • Runnable_run_readButton_Tick
  • Runnable_run_readButton_Edge_OUT
  • run_readButton_HW_IN
  • Runnable_run_readButton_Button_OUT
  • Runnable_run_readButton_button_pressed_cnt
 - - - - - - - - -

Hardware Components (1)

Hardware Components this technical function is associated with.

Component Type Start End SIL required SIL achieved Sub-Components Technical Functions sub Technical Functions Requirements sub Requirements
USART

UART module connected to pin TX/RX PA2/PA3 at 115200 8N1

 Periphery USART2_BASE USART3_BASE - 1 SIL_1 QM

Functional Layer

Logical Function Blocks (3)

Logical Function Blocks which which are associated with this Technical Function.

Function Type Technical functions
Button

An binary HMI

 Input
Controller

The MCU implementing the logic

 Service
PC

A PC receiving UART messages

 Monitor

Requirement Layer

Hazard Scenarios (1)

Hazard Scenarios for associated Hazardous Events.

Hazard Scenario Parent Hazard Events
Potential customers don't like the tool

This would be very sad.

Hazardous Events (2)

Hazardous Events for associated Safety Goals.

Hazardous Event Parent Probability Controllability Effect SIL Safety-Goals
Complexity

The user might think µRTE is hard to use.

 QM
Unknown features

The customer might not see the full spectrum of features µRTE comes with.

 QM

Safetygoals (1)

Safety Goals linking to the Requirements.

Safety Goal Parent Function Type SIL derived SIL manual SIL required Safe State Safety Requirements
Show most important features in an lightweight demo

An small demo model with the most important features shall show the most important features of µRTE.

 System_Function QM derived QM Show slides

(Safety)Requirements (4)

(Safety)Requirements referencing to this technical function.

(Safety)Requirement Parent User-ID Author Creation Date Start Date Deadline Expense Responsibe Category Type Status Justification Function Type SIL derived SIL manual SIL required Tests Technical Functions Software Other SW Hardware Signals Global variables Activation events Use-Cases User-Stories Refining Conflicting refined by conflicted by
Requirement_95 - UART

When the button is pressed, the system-state shall change from Blink into UART mode.
The start of UART mode shall be signaled via UART.
As long as the button is pressed, UART strings with the time in seconds the Button was pressed shall be send with the frequency with which the button pressed signal is updated.

 Requirement_95 Thomas Barth Wed Jun 08 17:56:19 CEST 2022 0.0 Thomas Barth product functional implemented - - - -
SafetyRequirement_93 - Runnable activation by signal events

Runnables can be activated by signal (onData/onError) events.

 SafetyRequirement_93 Thomas Barth Wed Jun 08 17:34:15 CEST 2022 0.0 Thomas Barth product functional implemented System_Function QM derived QM
SafetyRequirement_94 - Global variables

Global variables can store data for Runnables and other Software Functions.
The memory protection will automatically be generated.
The actual declaration is implemented as user-code to allow the use of non-trivial datatypes and operations.

 SafetyRequirement_94 Thomas Barth Wed Jun 08 17:34:15 CEST 2022 0.0 Thomas Barth product functional implemented System_Function QM derived QM
SafetyRequirement_95 - Runnable activation by cyclic events

Runnables can be activated by cyclic events.

 SafetyRequirement_95 Thomas Barth Wed Jun 08 17:34:15 CEST 2022 0.0 Thomas Barth product functional implemented System_Function QM SIL_1 SIL_1

Software Layer

Tasks (2)

Tasks in which software units are executed.

Task Core SIL Priority Software States Signals Init Hardware OutputSections Own TimeBase Stack
Button

Task responsible for reading the button state

 Arm® Cortex®-M4 SIL_1 6 - false .rtos.task.Button
UART

Task responsible for sending out UART protocolls

 Arm® Cortex®-M4 SIL_1 5 - false .rtos.task.UART

Testing Layer

Tests (1)

Tests derived from referencing requirements.

Test User-ID Group Priority Status Procedure and Input-Data Expected Results gen Name gen Props SIL Requirements Technical-Functions Software-Units Signals Global variables Activation-Events Hardware-Components
(Test_134) UART functional/system test

Tests the UART functionality at the system level

 Test_134 0 approved Regular power-on with a terminal connected to UART. The Button is pressed for 10 seconds. The string '--- UART WakeUp ----' is send whenever the button is pressed, followed by 'Button pressed for %d seconds.' messages, where '%d' represents the integer number of seconds the button already has been pressed.