Feature Requirements#

[Your Feature Name] Requirements
status: draft
security: NO
safety: ASIL_B
tags: template, feature_name

Attention

The above directive must be updated according to your Feature.

  • Modify Your Feature Name to be your Feature Name

  • Modify id to be your Feature Name in upper snake case preceded by doc__ and followed by _requirements

  • Adjust status to be valid

  • Adjust safety and tags according to your needs

<Headlines (for the list of requirements if structuring is needed)>#

Some Title
status: invalid
security: NO
safety: ASIL_B

The Feature shall do xyz to the user to bring him to this condition at this time.

Note: (optional, not to be verified)

Some Other Title
status: invalid
security: NO
safety: ASIL_B
tags: feature_name
reqtype: Process

The Feature User shall do xyz to use the feature safely.

Attention

The above directives must be updated according to your feature requirements.

  • Replace the example content by the real content for your first requirement (according to Requirements Guideline (gd_guidl__req_engineering))

  • Set belongs_to with a link to feature ID

  • Set reqtype with a link to the right value (<Functional|Interface|Process|Non-Functional>)

  • Set satisfies with a link to the right stakeholder requirement

  • Adjust safety and security to the right value (ASIL B/QM; YES/NO)

  • Add other needed requirements for your feature

  • Adjust valid_from and valid_until to the right version numbers

  • Set status to valid and start the review/merge process