Tool Requirements
Coverage: 0.0% (0 of 12 items OK)
[PARTIAL] TRLC Toolrequirement UseCases.Render_All_TRLC_Records
The trlc_rst renderer shall produce an RST output that contains every requirement record present in the input TRLC source files.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:21:43
[PARTIAL] TRLC Toolrequirement UseCases.Resolve_Derived_From_References
The rendered RST output shall contain working cross-references for all derived_from fields, linking child requirements to their parent requirements.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:31:43
[PARTIAL] TRLC Toolrequirement UseCases.Validate_Traceability_Completeness
The build shall fail when a component requirement does not have a derived_from reference to at least one feature requirement, unless the requirement is explicitly marked as component-internal.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:46:43
[PARTIAL] TRLC Toolrequirement UseCases.Emit_Correct_Provider_Info
The score_requirements_rule shall emit a TrlcProviderInfo provider containing all own TRLC source files, the specification RSL files, and all transitive dependency TRLC files.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:57:43
[PARTIAL] TRLC Toolrequirement UseCases.Emit_Sphinx_Sources
The score_requirements_rule shall emit a SphinxSourcesInfo provider containing the rendered RST file and all transitive Sphinx source dependencies.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:68:43
[PARTIAL] TRLC Toolrequirement UseCases.Render_All_Failure_Modes
The FMEA rule shall render every FailureMode record from the input TRLC sources into the documentation output.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:83:43
[PARTIAL] TRLC Toolrequirement UseCases.Reject_Invalid_PlantUML
The PlantUML parser shall exit with a non-zero return code when the input diagram contains syntactical errors, preventing silent production of incorrect output.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:97:43
[PARTIAL] TRLC Toolrequirement UseCases.Extract_Lobster_From_Requirements
The requirements rule shall extract a lobster traceability file from all TRLC requirement records using the configured lobster extraction schema.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:113:43
[PARTIAL] TRLC Toolrequirement UseCases.Forward_Own_AoUs_To_Dependees
The dependable_element rule shall automatically include lobster traceability entries for all assumptions of use defined by its direct dependencies in the dependee’s traceability report as a “Forwarded AoUs” tier.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:128:43
[PARTIAL] TRLC Toolrequirement UseCases.Chain_Forward_Received_AoUs
The dependable_element rule shall support an aou_forwarding attribute pointing to a YAML file that selects which received AoUs are forwarded further to elements that depend on this element. Each entry in the YAML shall require a mandatory justification field.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:140:43
[PARTIAL] TRLC Toolrequirement UseCases.Reject_Unknown_AoU_In_Forwarding_YAML
The AoU forwarding tool shall exit with a non-zero return code when the forwarding YAML references an AoU identifier that does not exist in the set of received AoUs, preventing silent misconfiguration.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:153:43
[PARTIAL] TRLC Toolrequirement UseCases.Include_Forwarded_AoUs_In_Traceability
The lobster traceability report of a dependee shall include forwarded AoUs as traceable items so that the existing lobster-ci-report test fails when forwarded AoUs are not handled (linked to a requirement, test, or justification).
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:165:43