uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

Hazard Scenario

Potential customers don't like the tool

This would be very sad.

Diagrams

Relationships

Requirements Model
Logical Function Model
Software units
Signals
Global variables
Activation Events
Hardware Model
Testing Model

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 		Potential customers don't like the tool
The type of this object within the uRTE model
Type 		HazardScenario
A descriptive text for this object. Please consider that this field might be used in code and thus must not contain special characters.
Description

This would be very sad.
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 		HazardScenario_93
Each object within the uRTE model has a unique ID, this is the ID for this object
UID 		_oX5WEOc_EeyMHMAOoLxcsQ
The package in which this HazardScenario is included.
Package 		UART
Hazardous Events

Hazardous Events (2)

Hazardous events wich cause this scenario.

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

Requirement Layer

Safetygoals (1)

Safety Goals of the Hazardous Events this Hazard Scenario links to.

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 (10)

(Safety)Requirements of the Safety Goals of the Hazardous Events this Hazard Scenario links to. Directly or through refinement relationships.

(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_110 - Hardware Interfacing

How to read and write data form and to hardware.

 SafetyRequirement_110 Thomas Barth Thu Jun 09 20:50:22 CEST 2022 0.0 Thomas Barth product functional approved System_Function QM derived QM
SafetyRequirement_111 - SignalLayer features

Demonstrate the use of scalers and validators.
Make use of age restrictions, checksums and pointer access.

 SafetyRequirement_111 Thu Jun 09 20:52:41 CEST 2022 0.0 product functional approved System_Function QM derived QM
SafetyRequirement_115 - Protection Sets

Show how protection sets can be used to grant access to hardware.

 SafetyRequirement_115 Fri Jun 10 14:24:52 CEST 2022 0.0 product functional implemented System_Function QM derived QM
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
SafetyRequirement_96 - Inter-task communication

µRTE easily can transmit events and data between tasks

 SafetyRequirement_96 Thomas Barth Wed Jun 08 17:46:14 CEST 2022 0.0 Thomas Barth product functional implemented System_Function QM derived QM
SafetyRequirement_97 - local and global signals

Signals can either be global data objects of local objects on the task stack.
Global signals are the same for everyone while with local signals each task has an own copy which gets synchroized if the signal changes,

 SafetyRequirement_97 Wed Jun 08 17:49:01 CEST 2022 0.0 product non_functional implemented System_Function QM derived QM
SafetyRequirement_98 - Multiple System-States

uRTE allows the definition of multiple system-states where each state has an own data-flow.
For each runnable the system state it shall be active in is configured.
The resulting data-flow can be visualized in Software Model/uRTE/SystemStates

 SafetyRequirement_98 Wed Jun 08 17:52:52 CEST 2022 0.0 product functional implemented System_Function QM derived QM

Functional Layer

Technical Functions (2)

Technical Functions referenced by the (Safety)Requirements associated with the safety goals the hazardous events are related with. Directly or through refinement relationships.

Function LFB Software Hardware Other Software SIL required SIL achieved SIL justification sub Technical Functions Requirements sub Requirements
Blinking LED

An LED shall blink to indicate that the system is alive and responding.
SIL_1 QM
UART

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

Logical Function Blocks (4)

Logical Function Blocks referenced by the above Technical Functions.

Function Type Technical functions
Button

An binary HMI

 Input
Controller

The MCU implementing the logic

 Service
LED

An LED to indicate a binary state

 Output
PC

A PC receiving UART messages

 Monitor

Software Layer

Software units (5)

Sofware units referenced by the (Safety)Requirements associated with the safety goals the hazardous events are related with. Directly or through refinement relationships.

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

Hardware write-Interface towards the LED

 LED
OutDriver 0 0 0
SIL_1 QM - - - - - - - - uRTE_boolean_t 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
 - - - - - - - - -

Signals (4)

Signals referenced by the (Safety)Requirements associated with the safety goals the hazardous events are related with. Directly or through refinement relationships.

Signal Type Storage Runnables OUT Runnables IN Tasks SystemStates Requirements miminum Age maximum Age Checksum Force Sync Inline ISR API effective inline SIL required SIL achieved Initial value (D) Pointer access (D) Datatype (D) Alt-In (D) Alt-Out (D) In-Driver (D) Out-Driver (D) OnData (D) OnError (D) OnTrigger (E)
HWO_UART

Hardware Out interface for UART.
No Signal-Datatype will be defined so that a typedef will be generated into the signal configuration.
Pointer access is granted so signal memory can be used directly by the application.

 Data local in
0 0 false false false false false QM QM true
If not type is defined, a type definition template will be generated into the signal configuration file.
undefined
-
-
button state

A representation of the current button state

 Data local in
0 105 false false false false false SIL_1 QM false false uRTE_boolean_t
-
-
button_cnt

contains the number of seconds, the button has been pressed

 Data global in
Button		 0 202 true false false false false QM QM 0 false button_cnt_t
-
-
button_edge

Fired whenever the button is pressed (but not if it is released)

 Event local in
0 0 false false false false false QM QM - - - - - - - - -

Global Variables (1)

Global referenced by the (Safety)Requirements associated with the safety goals the hazardous events are related with. Directly or through refinement relationships.

Global Variable Container DataType Requirements public (S) InitValue Storage Protection Set (S) SIL required SIL achieved
press_cnt

internal counter for button press duration

 run_readButton uRTE_uint16_t - 0 .button - SIL_1 QM

Activation-Events (1)

Activation Events referenced by the (Safety)Requirements associated with the safety goals the hazardous events are related with. Directly or through refinement relationships.

Event Type Cycle Time (C) Offset (C) Task-Init (S) Requirements Ports Runnables Tasks SystemStates SIL required SIL achieved
Button Timebase

Timebase for button read operations

 CyclicEvent 200 0 - SIL_1 QM

Testing Layer

Tests (1)

Tests referenced by the (Safety)Requirements associated with the safety goals the hazardous events are related with. Directly or through refinement relationships.

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.