uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

Safety-Requirement - SafetyRequirement_93

Runnable activation by signal events

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

Warnings

Testing Warnings (1)

Testing Warnings for SafetyRequirement Runnable activation by signal events
Testing warnings are related to the tests in the testing layer and their depedencies.

(SafetyRequirement_93) Runnable activation by signal events is not referencing a test but all refinements reference a test.

Diagrams

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

Safety

Required
SIL derivedQM
SIL manualderived
SILQM

Properties

Base
NameRunnable activation by signal events
Type SafetyRequirement
Description

Runnables can be activated by signal (onData/onError) events.
User-IDSafetyRequirement_93
UID_dBzLEOdAEeyMHMAOoLxcsQ
Package
Meta-Data
AuthorThomas Barth
Creation DateWed Jun 08 17:34:15 CEST 2022
Start Date
Deadline
Expense0.0
ResponsibeThomas Barth
Categoryproduct
Typefunctional
Statusimplemented
Stereotype
Function TypeSystem_Function
Tests
Associated Implementation

Technical Functions (1)

Technical functions this requirement is mapped to

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

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

Signals (1)

Signals this requirement is mapped to

Signal Type Storage Runnables OUT Runnables IN Tasks SystemStates Requirements miminum Age maximum Age Checksum Force Sync Inline ISR API effective inline SIL req SIL ach 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)
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
-
-
(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
(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 - - - -

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

Safety Goal Parent Function Type SIL derived SIL manual SIL effective 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

Functional Layer

Logical Function Blocks (3)

Logical Function Blocks which map to a technical function which is directly linked by this Safety Requirement.

Function Type Technical functions
Button

An binary HMI

 Input
Controller

The MCU implementing the logic

 Service
PC

A PC receiving UART messages

 Monitor