issue_2501_created_missing_drafts by attifunel · Pull Request #2600 · eclipse-score/score

attifunel · 2026-02-13T11:15:35Z

Creates the documents in the safety plan which previously been "Link to WP" and their according status in "automated"
Use the folder structure as in the templates from the process_description. Missing templates for platform levels, are created from the ones from module level.

Resolves: #2501

github-actions · 2026-02-13T11:15:48Z

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

a-zw · 2026-02-17T12:54:05Z

docs/safety/fdr_reports_safety_analyses_DFA.rst

+
+**Checklist**
+
+Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular.


/home/runner/work/score/score/docs/safety/fdr_reports_safety_analyses_DFA.rst:38: WARNING: undefined label: 'review_concept' [ref.ref] /home/runner/work/score/score/docs/safety/fdr_reports_safety_analyses_DFA.rst:58: WARNING: undefined label: 'doc__platform_dfa' [ref.ref] /home/runner/work/score/score/docs/safety/fdr_reports_safety_package.rst:41: WARNING: undefined label: 'doc_concept__wp_inspections' [ref.ref] /home/runner/work/score/score/docs/safety/fdr_reports_safety_platform_safety_plan.rst:40: WARNING: undefined label: 'doc_concept__wp_inspections' [ref.ref]

Only Sphinx-Needs links work across repos but not labels.

a-zw · 2026-02-17T12:56:05Z

docs/safety/fdr_reports_safety_analyses_DFA.rst

+        -
+      * - REQ_01_02
+        - Are the templates for DFA and/or FMEA used?
+        - See :ref:`doc__platform_dfa` 


Suggested change

- See :ref:`doc__platform_dfa`

- See :need:`doc__platform_dfa`

This should work.

github-actions · 2026-02-17T14:12:25Z

The created documentation from the pull request is available at: docu-html

masc2023

All documents seems to be templates, Templates should be in process_description, Template Folder not in SCORE repo

masc2023 · 2026-02-18T06:16:26Z

docs/platform_management_plan/verification_report/platform_ver_report.rst

+**2. DFA Report**
+       - List of the performed component DFA, pass/fail with open mitigations
+
+**3. Safety Analysis Report**


FMEA Report, as Safety Analysis in our context is superset including DFA and FMEA

It is already split in DFA and next subchapter Safety Analysis (i.e. FMEAs). I'd keep this structure because they're actually two analyses of very different type

Compare here, should follow up definition, safety analysis is used as superset including DFA, therefore I woul propose, mention DFA and FMEA or only the superset term
https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/safety_analysis_concept.html

Looking at here Platform FMEA is not planned https://eclipse-score.github.io/process_description//main/process_areas/safety_analysis/safety_analysis_workproducts.html#wp__platform_dfa

the verification report used a template that is not compliant to https://eclipse-score.github.io/process_description//main/process_areas/verification/verification_workproducts.html#wp__verification_platform_ver_report. I will rewrite it accordingly, thanks for the notification

docs/platform_management_plan/verification_report/platform_ver_report.rst

masc2023 · 2026-02-18T06:23:24Z

docs/platform_management_plan/verification_report/platform_ver_report.rst

+   :status: draft
+   :safety: ASIL_B
+   :security: NO
+   :realizes: wp__verification_module_ver_report


it it the platform verification report, so is these really realizing module verification report? I would assume each module has its own verification report and these is only the platform report

I agree, I will check

fixed thanks

masc2023 · 2026-02-18T06:28:48Z

docs/platform_management_plan/verification_report/platform_ver_report.rst

+   :safety: ASIL_B
+   :security: NO
+   :realizes: wp__verification_module_ver_report
+   :tags: template


If this is a template, why is it in SCORE, Templates should be part of process_description Template Folder?

Sorry I will fix it

attifunel · 2026-02-18T08:15:37Z

All documents seems to be templates, Templates should be in process_description, Template Folder not in SCORE repo

They are not templates, but drafts. The explanatory content from the template is kept to help filling the content accordingly.

docs/platform_management_plan/verification_report/platform_ver_report.rst

masc2023 · 2026-02-18T08:21:43Z

docs/platform_management_plan/verification_report/platform_ver_report.rst

+**2. DFA Report**
+       - List of the performed component DFA, pass/fail with open mitigations
+
+**3. Safety Analysis Report**


Compare here, should follow up definition, safety analysis is used as superset including DFA, therefore I woul propose, mention DFA and FMEA or only the superset term
https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/safety_analysis_concept.html

masc2023 · 2026-02-18T08:22:31Z

docs/platform_management_plan/verification_report/platform_ver_report.rst

+   :safety: ASIL_B
+   :security: NO
+   :realizes: wp__verification_module_ver_report
+   :tags: template


IF it not template, then remove the tag template her and everywhere

masc2023 · 2026-02-18T17:24:14Z

docs/safety/fdr_reports_safety_analyses_DFA.rst

+   # *******************************************************************************
+
+
+Safety Analysis Checklist


Why is this not called like safety package: Safety Plan Formal Review Report -> Safety Analysis Formal Review Report, realizing anyway this work product?

masc2023 · 2026-02-18T17:24:48Z

docs/safety/fdr_reports_safety_package.rst

+Safety Package Formal Review Report
+===================================
+
+.. note:: Document header


remove note here

masc2023 · 2026-02-18T17:25:03Z

docs/safety/fdr_reports_safety_platform_safety_plan.rst

+Safety Plan Formal Review Report
+================================
+
+.. note:: Document header


remove note here

masc2023 · 2026-02-18T17:26:15Z

docs/safety/platform_safety_manual.rst

+Safety Manual
+=============
+
+.. note:: Document header


remove note here

masc2023 · 2026-02-18T17:27:19Z

docs/safety/platform_safety_manual.rst

+Assumed Platform Safety Requirements
+------------------------------------
+| For the S-CORE Platformhe following safety related stakeholder requirements are assumed to define the top level functionality (purpose) of the S-CORE Platform. I.e. from these all the feature and component requirements implemented are derived.
+| <List here all the stakeholder requirements, with safety not equal to QM, the module's components requirements are derived from.>


May easier to read, if you put this kind of actions List here.. in Bold or Note or Attention, that the user can replace this later or remove it, while this is not any more a template

Done thanks

masc2023 · 2026-02-18T17:28:34Z

docs/safety/platform_safety_manual.rst

+Assumptions on the Environment
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+| Generally the assumption of the project platform SEooC is that it is integrated in a safe system, i.e. the POSIX OS it runs on is qualified and also the HW related failures are taken into account by the system integrator, if not otherwise stated in the module's safety concept.
+| <List here all the OS calls the project platform expects to be safe.>


same here, list is already there

masc2023 · 2026-02-18T17:30:40Z

docs/index.rst

      requirements/index
      modules/index
      contribute/index
+      safety/index


may move safety behind PMP

masc2023 · 2026-02-18T17:32:02Z

docs/platform_management_plan/verification_report/platform_ver_report.rst

+Verification Report
+===================
+
+.. note:: Document header


remove the note

masc2023 · 2026-02-18T17:32:38Z

docs/safety/platform_ver_report.rst

+     (can be several levels), passed/failed and completeness verdict, including normal
+     operation and failure reactions
+   - The list of requirements may also contain other verification methods like "Analysis"
+   - Formal evidence about the performed DFA


Platform DFA, other DFAs are part of Safety Analsis

masc2023 · 2026-02-18T17:32:53Z

docs/safety/platform_ver_report.rst

+     operation and failure reactions
+   - The list of requirements may also contain other verification methods like "Analysis"
+   - Formal evidence about the performed DFA
+   - Formal evidence about the performed Safety Analyses (if planned)


Why is planned?

It's not too clear to me if we plan or not a Platform FMEA. They are not in the Safety Plan

aschemmel-tech · 2026-02-19T14:58:50Z

The proper way of linking a PR to an issue is to put the number in the Commit message (but not in the headlines):
Resolves: #2501

aschemmel-tech

See inline comments

aschemmel-tech · 2026-02-19T15:18:06Z

docs/safety/platform_ver_report.rst

Why was the template not used?

aschemmel-tech · 2026-02-19T15:20:01Z

docs/safety/platform_ver_report.rst

I would not see this as part of the PMP as it is not about planning. Part of Release? Safety?

I can move it to safety

aschemmel-tech · 2026-02-19T15:25:22Z

docs/safety/index.rst

+Safety specific documentation for Platform is listed here
+
+.. toctree::
+


please do not show the content of the documents. I think you need the sphinx instruction :maxdepth: 1 for this.

aschemmel-tech · 2026-02-19T15:26:56Z

docs/index.rst

      requirements/index
      modules/index
      contribute/index
+      safety/index


Shall we call this "dependability" instead "safety" and add also the security documents in the future?

My suggestion is to keep safety separated from security

issue_2501_createx_missing_drafts

4e27895

attifunel changed the title ~~issue_2501_createx_missing_drafts~~ issue_2501_created_missing_drafts Feb 13, 2026

issue2501_fixed wrong links

1a30be4

a-zw reviewed Feb 17, 2026

View reviewed changes

attifunel added 3 commits February 17, 2026 14:13

issue2501 fixed link errors as per suggestions

e8eb38a

issue 2501: fixed last residual link errors

e3a9174

issue 2501 trying fixing errors link

e30633b

pahmann marked this pull request as ready for review February 17, 2026 14:50

pahmann requested review from PandaeDo, aschemmel-tech, masc2023 and pahmann as code owners February 17, 2026 14:50

masc2023 requested changes Feb 18, 2026

View reviewed changes

attifunel added 2 commits February 18, 2026 09:21

2501 attifunel fixed wrong req. link

0fbb3d1

2501 attifunel fixed wrong tag

850bf14

masc2023 requested changes Feb 18, 2026

View reviewed changes

attifunel added 2 commits February 18, 2026 09:29

2501 attifunel fixed wrroenous template flags

f0658f6

2501 attifunel corrected platform ver. report template

664879b

attifunel marked this pull request as draft February 18, 2026 08:51

attifunel marked this pull request as ready for review February 18, 2026 13:53

issue 2501 attifunel somex fixes

94db119

masc2023 reviewed Feb 18, 2026

View reviewed changes

docs/index.rst

requirements/index

modules/index

contribute/index

safety/index

Copy link

Contributor

masc2023 Feb 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may move safety behind PMP

masc2023 reviewed Feb 18, 2026

View reviewed changes

aschemmel-tech requested changes Feb 19, 2026

View reviewed changes

attifunel added 7 commits February 19, 2026 16:58

issue 2501 fixed review comments

7cc7537

issue 5201 attifunel changes from review

f2663ee

issue 2501 fixed further review comments

cc5a119

issue 2501 attifunel fixing build errors

1aa48be

issue 2501 trying again to solve conflicts...

413b19d

issue 2501 fixed titles

6003b4d

issue 2501 titles fixes

1a2b7ff


		Checklist

		Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular.

	- See :ref:`doc__platform_dfa`
	- See :need:`doc__platform_dfa`

		# *******************************************************************************


		Safety Analysis Checklist

		Safety specific documentation for Platform is listed here

		.. toctree::

Comments

Conversation

attifunel commented Feb 13, 2026 • edited by pahmann Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 13, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Feb 17, 2026

Uh oh!

masc2023 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

attifunel commented Feb 18, 2026

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

masc2023 Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aschemmel-tech commented Feb 19, 2026

Uh oh!

attifunel commented Feb 13, 2026 •

edited by pahmann

Loading

masc2023 Feb 18, 2026 •

edited

Loading