Requirements#
[Your Component Name] Requirements
|
status: draft
security: YES
safety: ASIL_B
|
||||
Attention
The above directive must be updated according to your Component.
Modify
Your Component Nameto be your Component NameModify
idto be your Component Name in upper snake case preceded bydoc__and followed by_requirementsAdjust
statusto bevalidAdjust
safety,securityandtagsaccording to your needs
<Headlines (for the list of requirements if structuring is needed)>#
Component Requirements#
Some Title
|
status: valid
security: YES
safety: ASIL_B
|
||||
The Component shall do xyz to another component to bring it to this condition at this time Note: (optional, not to be verified) |
|||||
Attention
The above directive must be updated according to your component requirements.
Replace the example content by the real content for your first requirement
Set
derived_fromwith links to Feature requirementsSet
satisfied_bywith a link to the right Component idSet
safetyandsecurityto the right valueSet the status to valid and start the review/merge process
Add other needed requirements for your component
Assumption of Use Requirements#
Next Title
|
status: valid
security: YES
safety: ASIL_B
|
||||
The Component User shall do xyz to use the component safely/securely |
|||||
Environmental Requirements#
Another Title
|
status: invalid
security: YES
safety: ASIL_B
|
||||
The Component shall only be used in a xyz environment to ensure its proper functioning. |
|||||
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
safetyandsecurityto the right value (ASIL B/QM; YES/NO)Set
reqtypewith a link to the right value (<Functional|Interface|Process|Non-Functional>)Add other needed requirements for your feature
Set
statustovalidand start the review/merge process
Requirements checklist#
See following requirements inspection checklist for verification of the requirements.