Templates#

Feature Requirements Template
status: valid

See Some Title (feat_req__feature_name__some_title)

Component Requirements Template
status: valid

See Some Title (comp_req__component_name__some_title)

Process Requirements Template
status: valid
tags: requirements_engineering, requirements_engineering
.. gd_req:: <Title>
   :id: gd_req__<process>__<Title>
   :satisfies: <link to guidance id>
   :complies: <link to standard requirement>
   :status: <valid|invalid>
Tool Requirements Template
status: valid
tags: requirements_engineering, requirements_engineering
.. tool_req:: <Title>
   :id: tool_req__<tool>__<Title>
   :security: <YES|NO>
   :safety: <QM|ASIL_B>
   :satisfies: <link to process req id>
   :status: <valid|invalid>
   :implemented: <YES|PARTIAL|NO>
Requirement Formulation Template
status: valid

Requirements shall be specified according to the following schema:

<The SW Platform|Feature|Component> shall <main verb> <object> <parameter> <temporal/logical conjunction>

<Note: (optional, not to be verified)>

Table 37 Sentence Table#

Addressee of the requirement (subject)

shall

main verb

object of the requirement

parameter of the requirement

temporal/logical conjunction

The development object (who/what)

shall

do something

for whom or what

which target value/condition

when, under which conditions

Example 1: The component

shall

detect

if a key-value pair got corrupted

and set its status to INVALID

during every restart of the SW platform.

Example 2: The software platform

shall

enable

users

to ensure the compatibility of application software

across vehicle variants and vehicle software releases.

Example 3: The linter-tool

shall

check

correctness of .rst files format

upon each commit.

Note

Of the last three columns of the above sentence template table, filling one is mandatory the others are optional.