Requirements

[Your Component Name] Requirements		status: draft security: YES safety: ASIL_B
tags: template, component_name realizes: wp__requirements_comp
doc__component_name_requirements		Generic Document

Attention

The above directive must be updated according to your Component.

• Modify Your Component Name to be your Component Name

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

• Adjust status to be valid

• Adjust safety, security and tags according to your needs

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

Component Requirements

Some Title		status: invalid security: YES safety: ASIL_B
tags: component_name reqtype: Process satisfies: feat_req__feature_name__some_title belongs to: comp__component_name_template fulfilled by: comp_arc_sta__component_name__static_view, comp_arc_dyn__component_name__dynamic_view, comp_arc_sta__component_name__2
The Component shall do xyz to another component to bring it to this condition at this time Note: (optional, not to be verified)
comp_req__component_name__some_title		Component Requirement

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 satistifes with links to Feature requirements

• Set belongs_to with a link to the right Component id

• Set safety and security to the right value

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

• Add other needed requirements for your component

Assumption of Use Requirements

Next Title		status: invalid security: YES safety: ASIL_B
tags: component_name reqtype: Process
The Component User shall do xyz to use the component safely/securely
aou_req__component_name__next_title		Assumption of Use Requirement

Environmental Requirements

Another Title		status: invalid security: YES safety: ASIL_B
tags: environment, component_name reqtype: Process
The Component shall only be used in a xyz environment to ensure its proper functioning.
aou_req__component_name__another_title		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 Requirements Guideline (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