Add failure mode attributes

[ANegm-ETAS]

📌 Description

Add additional optional attributes to FMEA/DFA

Updating the process template
eclipse-score/process_description#669

🚨 Impact Analysis

• This change does not violate any tool requirements and is covered by existing tool requirements
• This change does not violate any design decisions
• Otherwise I have created a ticket for new tool qualification

✅ Checklist

• Added/updated documentation for new or changed features
• Added/updated tests to cover the changes
• Followed project coding standards and guidelines

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: e151e154-36e0-4d29-a007-27040ae43a2c
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
WARNING: Target pattern parsing failed.
ERROR: Skipping '//src:license-check': no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
Analyzing: 0 targets (1 packages loaded)
ERROR: no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
INFO: Elapsed time: 5.528s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[github-actions]

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

[FScholPer]

eAny process requirements?! They should be linked e.g. 🆔 gd_req__saf_attr_safety_relevant

[ANegm-ETAS]

eAny process requirements?! They should be linked e.g. 🆔 gd_req__saf_attr_safety_relevant

process requirement PR is not merged yet will link them once they're merged

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.

[MaximilianSoerenPollak]

@ANegm-ETAS Is this still relevant or can we close this PR?

[ANegm-ETAS]

eAny process requirements?! They should be linked e.g. 🆔 gd_req__saf_attr_safety_relevant

linking to process requirements added