Audit preparation: Requirement Engineering

[aschemmel-tech]

"not started" topics:

• Specification of the technical safety requirements (AoU): check description of Stakeholder Req (= assumed TSR according to https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/requirements_concept.html#stakeholder-requirements) against exida list (questions) see e.g. https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#stkh_req__dependability__safe_state or https://eclipse-score.github.io/score/main/requirements/platform_assumptions/index.html#aou_req__platform__flow_monitoring
• Safety mechanisms: Undo Tailoring and add SM to assumed TSR, check against exida list - see REQ_09_01 in https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/guidance/requirements_inspection_checklist.html, plus text on stakeholder requirements in https://eclipse-score.github.io/score/main/platform_management_plan/safety_management.html#tailoring, examples: https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#safety-mechanisms
• HSI: HSI is a work product, but it is not covered by process, so process needs update or tailoring out - tailored out: see point on std_wp__iso26262__software_652 in https://eclipse-score.github.io/score/main/platform_management_plan/safety_management.html#tailoring

Actions and Deviations:

• Action_8: Tool is not yet implemented to create the hash attribute. - ticket see eclipse-score/score/#197 - was supposed to support impact analysis, manual work around
• Action_9: Requirements related to tools need to be audited. - see process: https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/guidance/requirements_templates.html#gd_temp__req_tool_req example: https://eclipse-score.github.io/docs-as-code/main/internals/requirements/requirements.html#tool_req__docs_common_attr_id
• Action_10: AoU (Assumption of Use) requirements need to be audited. - example: (baselibs: https://eclipse-score.github.io/score/main/modules/baselibs/json/docs/requirements/index.html#aou-requirements, persistency: https://eclipse-score.github.io/score/main/features/persistency/requirements/index.html#aou-requirements, communication: https://eclipse-score.github.io/score/main/modules/communication/docs/requirements/aou_req.html
• Action_11: The AoUs shall be automatically populated into the Safety Manuals. - see process: https://eclipse-score.github.io/process_description/main/folder_templates/modules/module_name/docs/manual/safety_manual.html#assumptions-on-the-user example: https://eclipse-score.github.io/score/main/modules/feo/docs/manual/safety_manual.html#assumptions-on-the-user
• Action_45: ASIL D shall be removed from the requirements process description. - see https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/guidance/requirements_process_reqs.html#gd_req__req_attr_safety and https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/requirements_concept.html#attributes-of-the-requirements
• Deviation_14: The definition of the participants of the inspection reviews needs to be done. Several roles shall be defined for the inspectors. At least the content responsible and the verification responsible shall be defined for the requirements. Other review properties might be done automatically. see process https://eclipse-score.github.io/process_description/main/folder_templates/modules/module_name/component_name/docs/requirements/chklst_req_inspection.html - see example https://eclipse-score.github.io/score/main/modules/baselibs/result/docs/requirements/chklst_req_inspection.html (and in github to show participants: https://github.com/eclipse-score/score/blob/main/docs/modules/baselibs/result/docs/requirements/chklst_req_inspection.rst)
• Action_46: The Configuration Management of the requirements needs to be audited. Baselines of a complete set of requirements shall be described, not only the version management of single requirements. - The release process and the Branching concept for release candidates are not yet described. The above action remains. - still see https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/requirements_concept.html#sets-of-requirements-baselines and https://eclipse-score.github.io/process_description/main/process_areas/release_management/release_concept.html, example: https://github.com/eclipse-score/score/blob/v0.5.0/docs/requirements/stakeholder/index.rst for v0.5.0 requirements baseline (corresponding to v0.5.0 release https://github.com/eclipse-score/score/releases/tag/v0.5.0).