uRTEDemo_03_Nucleo-F446RE_SystemStates_10_Model

Requirement - Requirement_32

LED Blink

In order to indicate that uRTE is up and running, an LED shall blink (toggle its binary state) with an frequency of 1/100ms.

Diagrams

Relationships

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
LED Blink
The type of this object within the uRTE model
Type
Requirement
A descriptive text for this object. Please consider that this field might be used in code and thus must not contain special characters.
Description

In order to indicate that uRTE is up and running, an LED shall blink (toggle its binary state) with an frequency of 1/100ms.

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
Requirement_32
Each object within the uRTE model has a unique ID, this is the ID for this object
UID
_zp2koOZREeyZ2OzYlvU4PA
The package in which this Requirement is included.
Package
Meta-Data
The author of this requirement.
Author
Thomas Barth
The date this requirement was created.
Creation Date
Tue Jun 07 13:05:57 CEST 2022
The date when the implementation of the requirement statrs.
Start Date
The deadline until this requirement has to be achieved.
Deadline
The expenses of this requirement.
Expense
0.0
Who is responsible for this requirement.
Responsibe
Thomas Barth
The category of this requirement.
Category
product
The type of this requirement.
Type
functional
The status of this requirement.
Status
implemented
The purpose of the justification is to provide rationale for the requirement status and the like.
Justification
Tests

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

The LED has to blink with a frequency of 1/100ms.

Test_132 0 implemented Regular power-on without user-input A blinking LED
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

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

SIL_1 QM

Software units (1)

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)

Controls the LED signal and thus the LED

LED
Runnable 0 0 0
SIL_1 QM false
  • Runnable_00_blink_Tick
  • Runnable_blink_Button_IN
  • Runnable_00_blink_OUT
- - - - - - - - -

Activation-Events (1)

Activation events this requirement is mapped to

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

The timebase for the LED logic. Has an bit of offset to make sure it comes after the button has been read (button value is polled).

CyclicEvent 100 2 -
  • Runnable_00_blink_Tick in run_LED
SIL_1 QM

Requirement Layer

All refined (Safety)Requirements (1)

All (Safety)Requirements this Requirement is refining.

(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

The LED on the Nucelo Board shall act as an simple demo.

Requirement_94 Thomas Barth Wed Jun 08 17:23:11 CEST 2022 0.0 Thomas Barth product non_functional implemented - - - -

Refined (Safety)Requirements (1)

(Safety)Requirements directly refined by this Requirement.

(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

The LED on the Nucelo Board shall act as an simple demo.

Requirement_94 Thomas Barth Wed Jun 08 17:23:11 CEST 2022 0.0 Thomas Barth product non_functional implemented - - - -

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

An binary HMI

Input

The MCU implementing the logic

Service

An LED to indicate a binary state

Output