Crypto Requirements#

Crypto Requirements		status: draft security: YES safety: ASIL_B
tags: crypto version: 1 realizes: wp__requirements_comp

doc__crypto_requirements		Generic Document

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

Functional Requirements#

.. comp_req:: Some Title
   :id: comp_req__crypto__func_req_example
   :reqtype: Process
   :security: YES
   :safety: ASIL_B
   :derived_from:
   :status: valid
   :satisfied_by: comp__crypto

   The Component shall do xyz to another component to bring it to this condition at this time

   Note: (optional, not to be verified)

Assumption of Use Requirements#

Crypto AoU Requirement Example		status: valid security: YES safety: ASIL_B
tags: crypto reqtype: Process version: 1
The Component User shall do xyz to use the component safely/securely
aou_req__crypto_aou__next_title		Assumption of Use Requirement

Environmental Requirements#

Crypto Environmental Requirement Example		status: invalid security: YES safety: ASIL_B
tags: environment, crypto reqtype: Process version: 1
The Component shall only be used in a xyz environment to ensure its proper functioning.
aou_req__crypto__crypto_env_req_ex		Assumption of Use Requirement

Hints#

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 gd_guidl__req_engineering)
Set safety and security to the right value (ASIL B/QM; YES/NO)
Set reqtype with a link to the right value (<Functional|Interface|Process|Non-Functional>)
Add other needed requirements for your feature
Set status to valid and start the review/merge process