Anegm/per fmea json

[ANegm-ETAS]

1- Use needimport to import FMEA needs elements in the form of a json file.
2- use needtable to render the needs element in a table format for better readability

Build is failing pending patch to docs-as-code
eclipse-score/docs-as-code#516

[github-actions]

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

[masc2023]

Needs discussion, put on agenda here https://github.com/orgs/eclipse-score/discussions/407#discussioncomment-16514494

[github-actions]

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

[aschemmel-tech]

What is the reasoning behind this? Work products shall be documented as sphinx needs elements. If you want a table view this can be done by a needtable.

[ANegm-ETAS]

What is the reasoning behind this? Work products shall be documented as sphinx needs elements. If you want a table view this can be done by a needtable.

Yeah that's true we can achieve the table presentation using needtable, but the intention is to make updating the FMEA more user friendly by enabling the team to use any xml editing tool like excel instead of dealing with RST formatting.

[masc2023]

What is the reasoning behind this? Work products shall be documented as sphinx needs elements. If you want a table view this can be done by a needtable.

Yeah that's true we can achieve the table presentation using needtable, but the intention is to make updating the FMEA more user friendly by enabling the team to use any xml editing tool like excel instead of dealing with RST formatting.

So need to check, if this is still following this stakeholder requirement, https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#stkh_req__requirements__as_code

[ANegm-ETAS]

What is the reasoning behind this? Work products shall be documented as sphinx needs elements. If you want a table view this can be done by a needtable.

Yeah that's true we can achieve the table presentation using needtable, but the intention is to make updating the FMEA more user friendly by enabling the team to use any xml editing tool like excel instead of dealing with RST formatting.

So need to check, if this is still following this stakeholder requirement, https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#stkh_req__requirements__as_code

I don't see why it wouldn't be following the stakeholder requirement a sphinx extension is still documented as (Docs-as-code).

[masc2023]

What is the reasoning behind this? Work products shall be documented as sphinx needs elements. If you want a table view this can be done by a needtable.

Yeah that's true we can achieve the table presentation using needtable, but the intention is to make updating the FMEA more user friendly by enabling the team to use any xml editing tool like excel instead of dealing with RST formatting.

So need to check, if this is still following this stakeholder requirement, https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#stkh_req__requirements__as_code

I don't see why it wouldn't be following the stakeholder requirement a sphinx extension is still documented as (Docs-as-code).

I am refering to the note: rationale: In this project no external tool or service is used. Therefore as-code is the selected option.
Xml for me would not be really doc as code, especially if I need an editor or excel

[ANegm-ETAS]

What is the reasoning behind this? Work products shall be documented as sphinx needs elements. If you want a table view this can be done by a needtable.

Yeah that's true we can achieve the table presentation using needtable, but the intention is to make updating the FMEA more user friendly by enabling the team to use any xml editing tool like excel instead of dealing with RST formatting.

So need to check, if this is still following this stakeholder requirement, https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#stkh_req__requirements__as_code

I don't see why it wouldn't be following the stakeholder requirement a sphinx extension is still documented as (Docs-as-code).

I am refering to the note: rationale: In this project no external tool or service is used. Therefore as-code is the selected option. Xml for me would not be really doc as code, especially if I need an editor or excel

I see what you mean, I'd argue that XML is just a data vehicle and you don't strictly need a specialized tool to edit it, also it's already in use in the project for tests reporting