+Requirement Model
- +Blinking LED
- +UART
+Logical Function Model
- Controller
- LED
- PC
- Button
- Blinking LED
- UART
+Software Model
- +Software
  - +Button
    - ButtonRead
    - +run_readButton
      - press_cnt
  - +LED
    - drv_LED
    - run_LED
  - +UART
- +RTE
  - +Activation Engine
    - Button Timebase
    - LED timebase
  - +Signal Layer
    - HWI LED
    - HWI_Button
    - button state
    - button_edge
    - button_cnt
    - HWO_UART
    - +Signal-Pools
      - Button
  - +System States
    - Blink
    - UART
    - +State-Handler
- +RTOS
  - Button
  - LED
  - UART
- +Linkage
  - +Output-Sections
  - +Protection-Sets
    - BaseProtection
    - UART
- +DataTypes
+Hardware Model
- +Nucelo-F446RE
  - +STM32F446RE
    - Arm® Cortex®-M4
    - main
    - +GPIO
      - PA5
      - PC13-TAMPER-RTC
    - USART
  - Button
  - LED
+Testing Model
- +Item Tests
  - (Test_128) Smoke-Test
- +Functional Tests
  - +Blinking LED
    - (Test_132) Regular blink
    - (Test_133) LED permanent ON
  - +UART
    - (Test_134) UART functional/system test

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

Diagrams

Relationships

Requirements Model

Logical Function Model

Software units

Signals

Global variables

Activation Events

Hardware Model

Testing Model

Properties

Base

Name

UART

Type

Requirement

Description

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.

User-ID

Requirement_95

UID

_iIAIgOdDEeyMHMAOoLxcsQ

Package

UART

Meta-Data

Author

Thomas Barth

Creation Date

Wed Jun 08 17:56:19 CEST 2022

Start Date

Deadline

Expense

0.0

Responsibe

Thomas Barth

Tests (1)

References to the tests for this requirement

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	Functional Tests UART	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.				Requirement_95 - UART	UART	run_UART_send run_UART_wakeUp

Directly associated Implementation

Technical Functions (1)

Technical functions this requirement is mapped to

Function	LFB	Software	Hardware	Other Software	SIL required	SIL achieved	SIL justification	sub Technical Functions	Requirements	sub Requirements
UART If the button is pressed, UART messages indicating the press duration are sent.	Button Controller PC	run_UART_send UART out run_UART_wakeUp run_readButton ButtonRead	USART		SIL_1	QM		Blinking LED UART	Requirement_95 - UART SafetyRequirement_93 - Runnable activation by signal events Requirement_95 - UART SafetyRequirement_94 - Global variables Requirement_95 - UART SafetyRequirement_95 - Runnable activation by cyclic events Requirement_95 - UART	Requirement_95 - UART SafetyRequirement_110 - Hardware Interfacing SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_115 - Protection Sets Requirement_95 - UART SafetyRequirement_94 - Global variables Requirement_95 - UART SafetyRequirement_98 - Multiple System-States Requirement_95 - UART

Software units (2)

Software-Components this requirement is mapped to.

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)
run_UART_send Sends UART messages periodically via the UART signal	UART			UART	Requirement_95 - UART SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_98 - Multiple System-States Requirement_95 - UART	Runnable	UART	0	0	0			SIL_1	QM	UART		true	UART	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			UART	Requirement_95 - UART SafetyRequirement_115 - Protection Sets Requirement_95 - UART SafetyRequirement_98 - Multiple System-States Requirement_95 - UART	Runnable	UART	0	0	0		UART	SIL_1	QM			true	Blink	Runnable_run_UART_WakeUP				-	-	-	-	-	-	-	-	-

Requirement Layer

Hazard Scenarios (1)

Hazard Scenarios for all Hazardous Events of refined requirements.

Hazard Scenario	Parent	Hazard Events
Potential customers don't like the tool This would be very sad.	UART	Complexity Unknown features

Hazardous Events (2)

Hazardous Events for all Safety Goals of refined requirements.

Hazardous Event	Parent	Probability	Controllability	Effect	SIL	Safety-Goals
Complexity The user might think µRTE is hard to use.	UART				QM	Show most important features in an lightweight demo
Unknown features The customer might not see the full spectrum of features µRTE comes with.	UART				QM	Show most important features in an lightweight demo

Safetygoals (1)

Safety Goals linking to requirements this requirement is refining.

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.	UART	System_Function	QM	derived	QM	Show slides	SafetyRequirement_94 - Global variables Requirement_95 - UART SafetyRequirement_110 - Hardware Interfacing SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_96 - Inter-task communication SafetyRequirement_97 - local and global signals Requirement_95 - UART SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_98 - Multiple System-States Requirement_95 - UART SafetyRequirement_115 - Protection Sets Requirement_95 - UART SafetyRequirement_95 - Runnable activation by cyclic events Requirement_95 - UART SafetyRequirement_93 - Runnable activation by signal events Requirement_95 - UART

All refined (Safety)Requirements (9)

All (Safety)Requirements this Requirement is refining.

(Safety)Requirement	Parent	User-ID	Author	Creation Date	Responsibe	Category	Type	Status	Function Type	SIL derived	SIL manual	SIL required	Technical Functions	Software	Signals	Global variables	Activation events	Refining	refined by
SafetyRequirement_110 - Hardware Interfacing How to read and write data form and to hardware.	UART	SafetyRequirement_110	Thomas Barth	Thu Jun 09 20:50:22 CEST 2022	Thomas Barth	product	functional	approved	System_Function	QM	derived	QM		ButtonRead drv_LED				SafetyRequirement_111 - SignalLayer features Requirement_95 - UART
SafetyRequirement_111 - SignalLayer features Demonstrate the use of scalers and validators. Make use of age restrictions, checksums and pointer access.	UART	SafetyRequirement_111		Thu Jun 09 20:52:41 CEST 2022		product	functional	approved	System_Function	QM	derived	QM		run_UART_send	HWO_UART button_cnt			Requirement_95 - UART	SafetyRequirement_110 - Hardware Interfacing SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_96 - Inter-task communication SafetyRequirement_97 - local and global signals Requirement_95 - UART SafetyRequirement_111 - SignalLayer features Requirement_95 - UART
SafetyRequirement_115 - Protection Sets Show how protection sets can be used to grant access to hardware.	UART	SafetyRequirement_115		Fri Jun 10 14:24:52 CEST 2022		product	functional	implemented	System_Function	QM	derived	QM		run_UART_wakeUp				Requirement_95 - UART
SafetyRequirement_93 - Runnable activation by signal events Runnables can be activated by signal (onData/onError) events.	UART	SafetyRequirement_93	Thomas Barth	Wed Jun 08 17:34:15 CEST 2022	Thomas Barth	product	functional	implemented	System_Function	QM	derived	QM	UART		button state			Requirement_95 - UART
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.	UART	SafetyRequirement_94	Thomas Barth	Wed Jun 08 17:34:15 CEST 2022	Thomas Barth	product	functional	implemented	System_Function	QM	derived	QM	UART	run_readButton		press_cnt		Requirement_95 - UART
SafetyRequirement_95 - Runnable activation by cyclic events Runnables can be activated by cyclic events.	UART	SafetyRequirement_95	Thomas Barth	Wed Jun 08 17:34:15 CEST 2022	Thomas Barth	product	functional	implemented	System_Function	QM	SIL_1	SIL_1	Blinking LED UART		button state		Button Timebase	Requirement_95 - UART
SafetyRequirement_96 - Inter-task communication µRTE easily can transmit events and data between tasks	UART	SafetyRequirement_96	Thomas Barth	Wed Jun 08 17:46:14 CEST 2022	Thomas Barth	product	functional	implemented	System_Function	QM	derived	QM			button state button_cnt button_edge			SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_97 - local and global signals Requirement_95 - UART
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,	UART	SafetyRequirement_97		Wed Jun 08 17:49:01 CEST 2022		product	non_functional	implemented	System_Function	QM	derived	QM			button state button_cnt			Requirement_95 - UART	SafetyRequirement_96 - Inter-task communication SafetyRequirement_97 - local and global signals Requirement_95 - UART SafetyRequirement_111 - SignalLayer features Requirement_95 - UART
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	UART	SafetyRequirement_98		Wed Jun 08 17:52:52 CEST 2022		product	functional	implemented	System_Function	QM	derived	QM		run_UART_send run_UART_wakeUp State-Handler				Requirement_95 - UART

Refined (Safety)Requirements (7)

(Safety)Requirements directly refined by this Requirement.

(Safety)Requirement	Parent	User-ID	Author	Creation Date	Responsibe	Category	Type	Status	Function Type	SIL derived	SIL manual	SIL required	Technical Functions	Software	Signals	Global variables	Activation events	Refining	refined by
SafetyRequirement_111 - SignalLayer features Demonstrate the use of scalers and validators. Make use of age restrictions, checksums and pointer access.	UART	SafetyRequirement_111		Thu Jun 09 20:52:41 CEST 2022		product	functional	approved	System_Function	QM	derived	QM		run_UART_send	HWO_UART button_cnt			Requirement_95 - UART	SafetyRequirement_110 - Hardware Interfacing SafetyRequirement_111 - SignalLayer features Requirement_95 - UART SafetyRequirement_96 - Inter-task communication SafetyRequirement_97 - local and global signals Requirement_95 - UART SafetyRequirement_111 - SignalLayer features Requirement_95 - UART
SafetyRequirement_115 - Protection Sets Show how protection sets can be used to grant access to hardware.	UART	SafetyRequirement_115		Fri Jun 10 14:24:52 CEST 2022		product	functional	implemented	System_Function	QM	derived	QM		run_UART_wakeUp				Requirement_95 - UART
SafetyRequirement_93 - Runnable activation by signal events Runnables can be activated by signal (onData/onError) events.	UART	SafetyRequirement_93	Thomas Barth	Wed Jun 08 17:34:15 CEST 2022	Thomas Barth	product	functional	implemented	System_Function	QM	derived	QM	UART		button state			Requirement_95 - UART
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.	UART	SafetyRequirement_94	Thomas Barth	Wed Jun 08 17:34:15 CEST 2022	Thomas Barth	product	functional	implemented	System_Function	QM	derived	QM	UART	run_readButton		press_cnt		Requirement_95 - UART
SafetyRequirement_95 - Runnable activation by cyclic events Runnables can be activated by cyclic events.	UART	SafetyRequirement_95	Thomas Barth	Wed Jun 08 17:34:15 CEST 2022	Thomas Barth	product	functional	implemented	System_Function	QM	SIL_1	SIL_1	Blinking LED UART		button state		Button Timebase	Requirement_95 - UART
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,	UART	SafetyRequirement_97		Wed Jun 08 17:49:01 CEST 2022		product	non_functional	implemented	System_Function	QM	derived	QM			button state button_cnt			Requirement_95 - UART	SafetyRequirement_96 - Inter-task communication SafetyRequirement_97 - local and global signals Requirement_95 - UART SafetyRequirement_111 - SignalLayer features Requirement_95 - UART
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	UART	SafetyRequirement_98		Wed Jun 08 17:52:52 CEST 2022		product	functional	implemented	System_Function	QM	derived	QM		run_UART_send run_UART_wakeUp State-Handler				Requirement_95 - UART

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	Blinking LED UART
Controller The MCU implementing the logic	Service	Blinking LED UART
PC A PC receiving UART messages	Monitor	UART