uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

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

Warnings

Testing Warnings (1)

Testing Warnings for SafetyRequirement Multiple System-States
Testing warnings are related to the tests in the testing layer and their depedencies.

(SafetyRequirement_98) Multiple System-States is not referencing a test but all refinements reference a test.

Diagrams

Safety

Required
SIL derivedQM
SIL manualderived
SILQM

Properties

Base
NameMultiple System-States
Type SafetyRequirement
Description

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

User-IDSafetyRequirement_98
UID_DUuBgOdDEeyMHMAOoLxcsQ
Package
Meta-Data
Author
Creation DateWed Jun 08 17:52:52 CEST 2022
Start Date
Deadline
Expense0.0
Responsibe
Categoryproduct
Typefunctional
Statusimplemented
Stereotype
Function TypeSystem_Function
Tests
Associated Implementation

Software units (2)

Software-Components this requirement is mapped to.

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)

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

State-Handler

This requirement references the State-Handler.

(Safety)Requirement dependencies

Refining (Safety)Requirements (1)

(Safety)Requirements this Safety Requirement is refined by.

(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

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

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 this Requirement.

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