Stakeholder Requirements

Platform Requirements		status: draft security: YES safety: ASIL_B
tags: template, platform realizes: wp__requirements_feat
doc__platform_name_requirements		Generic Document

Attention

The above directive must be updated.

• Adjust status to valid

• Adjust safety, security 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: <The rationale provides the reason that the requirement is needed.> reqtype: Functional valid_from: v0.0.1 valid_until: v1.0.1 satisfied by: feat_req__feature_name__some_title
The platform shall …
stkh_req__requirements__template		Stakeholder Requirement

Some Other Title		status: invalid security: YES safety: ASIL_B
tags: platform reqtype: Interface
The Platform User shall do xyz to use the platform safely.
aou_req__platform__some_other_title		Assumption of Use Requirement

Attention

The above directives must be updated according to platform requirements.

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

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

• Set valid_from and valid_until to the right milestones

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

• Provide the appropriate rationale

• Adjust valid_from and valid_until to the right version numbers

• Add other needed requirements for the platform

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