uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

Logical Function Block

PC

A PC receiving UART messages

Diagrams

Safety

Required
SIL SIL_1
mixed SILs QM, SIL_1

Properties

Base
NamePC
Type LogicalFunctionBlock
Description

A PC receiving UART messages

User-IDLogicalFunctionBlock_84
UID_jc3ngOc0EeyMHMAOoLxcsQ
Stereotype
Type Monitor
References

Technical Functions (1)

System functionalities (technical functions) this logical function block is associated with.

Function LFB Software Hardware Technical Functions sub Technical Functions Requirements sub Requirements

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

Ports
Port Flow
PC_UART_IN (LogicalFunctionPort_88)
  • UART (LogicalFunctionFlow_86)

Functional Layer

Logical Function Blocks (2)

Logical Function Blocks which which are associated with the Technical Functions.

Function Type Technical functions

An binary HMI

Input

The MCU implementing the logic

Service

Requirement Layer

Hazard Scenarios (1)

Hazard Scenarios for associated Hazardous Events.

Hazard Scenario Parent Hazard Events

This would be very sad.

Hazardous Events (2)

Hazardous Events for associated Safety Goals.

Hazardous Event Parent Probability Controllability Effect SIL Safety-Goals

The user might think µRTE is hard to use.

QM

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 effective Safe State Safety Requirements

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 linking to the Technical Functions.

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

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

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

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

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 - - - -

Software Layer

Software units (5)

Sofware units the associated technical functions are associated with. See associated tasks for more software dependencies.

Unit Parent Function calls Technical Functions Requirements Type Tasks WCET Stack ROM Globals ProtectionSets SIL req SIL ach 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)

Reads the current button state from hardware

Button
InDriver 0 0 0
QM QM - - - - - - - - uRTE_boolean_t true - - - -

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

UART
OutDriver 0 0 0
- QM - - - - - - - - None true - - - -

Sends UART messages periodically via the UART signal

UART
Runnable 0 0 0
QM 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
- - - - - - - - -

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
QM QM
true
  • Runnable_run_UART_WakeUP
- - - - - - - - -

Acquires the button state periodically and provides button signals

Button
Runnable 0 0 0
QM 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 Layer

Hardware Components (1)

Hardware Components the associated technical functions are associated with. See associated tasks for more hardware dependencies.

Component Type Start End SIL req SIL ach Sub-Components Technical Functions sub Technical Functions Requirements sub Requirements

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

Periphery USART2_BASE USART3_BASE - 1 - QM