Time Assumption of Use Requirements		status: draft security: NO safety: ASIL_B
version: 1 realizes: wp__requirements_feat_aou
doc__feature_time_aou_reqs		Generic Document

Time Feature Assumption of Use Requirements

Vehicle time value integrity		status: valid security: NO safety: ASIL_B
reqtype: Non-Functional version: 1
The integrity of the vehicle time value is not guaranteed by score::time alone. If the system using score::time has the safety goal to treat the vehicle time as ASIL-B data, the system integrator shall establish end-to-end integrity by suitable measures, e.g.: integrity protection along the time-distribution chain (grand master, intermediate masters, time-aware bridges/switches), and/or a receiver-side qualification/monitoring mechanism that evaluates the qualifiers provided by score::time (see Vehicle Time base time poin... (feat_req__time__vehicle_time_time_pt_qual), Vehicle Time base accuracy ... (feat_req__time__vehicle_time_acc_qual_api)) and reacts per the project safety concept. Note 1: score::time provides the qualifier/detection hooks; the concrete integrity mechanism, its redundancy, the safety reaction and the end-to-end safety argument are project-specific and outside the scope of the score::time SEooC. Note 2: If this assumption is not fulfilled, the vehicle time value integrity falls back to QM and must be marked accordingly in the project documentation.
aou_req__feature_time__veh_time_integrity		Assumption of Use Requirement

Vehicle time integrity result reflected in qualifier		status: valid security: NO safety: ASIL_B
reqtype: Non-Functional version: 1
Where the integrity check for the vehicle time is realized as a score::time extension, the system integrator shall ensure its result is reflected in the time point qualifier (see Vehicle Time base time poin... (feat_req__time__vehicle_time_time_pt_qual)).
aou_req__feature_time__veh_time_qual_reflect		Assumption of Use Requirement