Requirements

General

Support for Time-based Architecture		status: valid security: NO safety: ASIL_B
reqtype: Functional satisfies: stkh_req__app_architectures__support_time
The daal framework shall provide Trigger to support a time-based architecture.
feat_req__daal__time_based_arch		Feature Requirement

Lifecycle Interface		status: valid security: NO safety: ASIL_B
reqtype: Functional satisfies: stkh_req__overall_goals__reuse_of_app_soft, stkh_req__execution_model__processes, stkh_req__execution_model__low_power
Lifecycle of executables should use one generic API
feat_req__daal__lifecycle		Feature Requirement

Execution Environments		status: valid security: NO safety: ASIL_B
reqtype: Functional satisfies: stkh_req__functional_req__operating_system
It should be possible to use the framework with all specified os like qnx and linux
feat_req__daal__env		Feature Requirement

Communication		status: valid security: NO safety: ASIL_B
reqtype: Functional satisfies: stkh_req__app_architectures__support_data
The communication layer should use the IPC Framework
feat_req__daal__com		Feature Requirement

Logging		status: valid security: NO safety: ASIL_B
reqtype: Functional satisfies: stkh_req__dev_experience__logging_support
Core Logging API should be used
feat_req__daal__log		Feature Requirement

Trigger		status: valid security: NO safety: ASIL_B
reqtype: Functional satisfies: stkh_req__execution_model__processes
Singe Shot and Cyclic execution should be possible
feat_req__daal__trigger		Feature Requirement

Health & Error Management		status: valid security: NO safety: ASIL_B
reqtype: Functional satisfies: stkh_req__execution_model__processes
Error and Health Management should be availability
feat_req__daal__health_error		Feature Requirement

Open Issues

[Any points that are still being decided/discussed.]

Note

While a CR is in draft, ideas can come up which warrant further discussion. Those ideas should be recorded so people know that they are being thought about but do not have a concrete resolution. This helps make sure all issues required for the CR to be ready for consideration are complete and reduces people duplicating prior discussion.

Footnotes

[A collection of footnotes cited in the CR, and a place to list non-inline hyperlink targets.]