Component Time Daemon Requirements#

Time Daemon Requirements		status: draft security: YES safety: ASIL_B
tags: time_daemon, time, time_daemon version: 1 realizes: wp__requirements_comp

doc__time_daemon_requirements		Generic Document

Note

Work in progress: structure, titles, and needs IDs only. Content and req/comp/feat traceability links to follow in later PRs.

Attention

The above directive must be updated according to your Component.

Adjust status to be valid
Adjust safety, security and tags according to your needs

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

Functional Requirements#

.. comp_req:: Some Title
   :id: comp_req__time_daemon__some_title
   :reqtype: Process
   :security: YES
   :safety: ASIL_B
   :derived_from: feat_req__example_feature__example_req
   :status: invalid
   :version: 1
   :satisfied_by: comp__time_daemon

   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_from with links to Feature requirements
Set satisfied_by 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: time, time_daemon reqtype: Process version: 1
The Component User shall do xyz to use the component safely/securely
aou_req__time_daemon__next_title		Assumption of Use Requirement

Environmental Requirements#

Another Title		status: invalid security: YES safety: ASIL_B
tags: environment, time, time_daemon reqtype: Process version: 1
The Component shall only be used in a xyz environment to ensure its proper functioning.
aou_req__time_daemon__another		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