Requirements

[Your Feature Name] Requirements		status: draft security: NO safety: ASIL_B
tags: template, feature_name realizes: wp__requirements_feat
doc__feature_name_requirements		Generic Document

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)>

Template		status: invalid security: YES safety: ASIL_B
rationale: Exists just for the template example reqtype: Non-Functional satisfied by: feat_req__feature_name__some_title
The platform shall …
stkh_req__requirements__template		Stakeholder Requirement

Attention

The above stakeholder requirement must be removed, it just serves as a link target for this template.

Some Title		status: invalid security: YES safety: ASIL_B
tags: feature_name reqtype: Process satisfies: stkh_req__requirements__template satisfied by: comp_req__component_name__some_title fulfilled by: feat_arc_sta__feature_name__static_view, feat_arc_dyn__feature_name__dynamic_view
The Feature shall do xyz to the user to bring him to this condition at this time Note: (optional, not to be verified)
feat_req__feature_name__some_title		Feature Requirement

Some Other Title		status: invalid security: YES safety: ASIL_B
tags: feature_name reqtype: Process
The Feature User shall do xyz to use the feature safely
aou_req__feature_name__some_other_title		Assumption of Use Requirement

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 the status to valid and start the review/merge process

• Add other needed requirements for your feature