Audit not started: Specification of the technical safety requirements

[aschemmel-tech]

check if the stakeholder requirements are defined to be our assumed TSR. If yes then check if all the questions/topics from the exida audit report list can be answered

[aschemmel-tech]

Stakeholder requirements are described as aTSR in https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/requirements_concept.html#stakeholder-requirements and also in https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/requirements_workproducts.html#wp__requirements_stkh.

[aschemmel-tech]

Questions:

• Are there assumptions of Use? (in TSR) - no, not on stakeholder level, but will be added to care for general topics relevant for all SW-platform users (this could be for example a requirement not to use exceptions in application development or to perform all the verification steps like running a static analysis tool on the SW-platform which cannot be done by S-CORE due to organizational topics), the main AoU appear during break down and implementation of the requirments on feature and component level based on the safety analysis on these levels. (see [Platform AoUs] Define basic SW-Platform AoUs score#1566)
• Is there a guideline for creating requirements for safety mechanisms? - there is a req guideline, no seperate guideline for safety mechanisms - will mark safety mechanisms defined in stakeholder requirements by tags. See Stakeholder requirements: Align wording and add safety mechanisms tag score#1883
• What is the safe state?
• How long are we allowed to take from detection to safe state?

[aschemmel-tech]

Discussed two "safe state" questions in https://github.com/orgs/eclipse-score/discussions/407#discussioncomment-14573537
Created eclipse-score/score#1882 to cover the two "safe state" questions.