Tool Requirements
Coverage: 0.0% (0 of 22 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 “Received 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.Cover_Received_AoU_Via_Component_Requirement
The CompReq requirement type’s derived_from field (CompReqSourceId) shall accept versioned, typed cross-module TRLC references to AoU records alongside its usual FeatReq/ AssumedSystemReq references. Resolving an AoU reference shall require the defining assumptions_of_use target to be listed directly in the CompReq target’s deps. The dependable_element rule shall convert such references to lobster trace references resolved against the “Received AoUs” tier, so a component requirement can cover a received AoU it handles locally without requiring that AoU to be chain-forwarded.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:165:43
[PARTIAL] TRLC Toolrequirement UseCases.Include_Forwarded_AoUs_In_Traceability
The lobster traceability report of a dependable element shall require every item in its “Received AoUs” tier to be covered by at least one of: a component requirement (via derived_from) or a chain-forwarding entry (via aou_forwarding), so that the existing lobster-ci-report test fails when a received AoU is neither handled nor forwarded.
Traces to:
missing reference to Code
Derived from:
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:183:43
[MISSING] TRLC Toolrequirement UseCases.Lock_File_As_Spec_And_Approval
The tool shall use one YAML lock file as both the declaration of which requirements are claimed to be completely covered and as the committed approval artifact.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:201:43
[MISSING] TRLC Toolrequirement UseCases.Requirement_IDs_From_TRLC
The tool shall extract requirement identifiers automatically from the TrlcProviderInfo provider of the requirements target attribute.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:211:43
[MISSING] TRLC Toolrequirement UseCases.Parse_GWT_Annotations
The tool shall parse GTest XML result files, extracting RecordProperty values for the keys lobster-tracing, given, when, and then on a per-TEST, per-TEST_F, and per-TEST_P basis. A test case without a given, when, or then property shall be included with an empty string for each missing field.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:220:43
[MISSING] TRLC Toolrequirement UseCases.Multi_Requirement_Linking
A test case that carries lobster-tracing values matching more than one requirement identifier shall appear in the lock file entry of every matched requirement.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:232:43
[MISSING] TRLC Toolrequirement UseCases.Lock_File_Content
The lock file shall contain, per requirement: the requirement identifier and an ordered list of linked test cases. Each test case entry shall contain: a uid in the format “//bazel_package/SuiteName:TestName” (package-scoped gtest tag) and the individual given, when, and then strings as separate fields.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:242:43
[MISSING] TRLC Toolrequirement UseCases.Lock_File_Ordering
Test cases within a requirement entry shall be ordered lexicographically by uid to produce a deterministic, diff-friendly lock file.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:255:43
[MISSING] TRLC Toolrequirement UseCases.Update_Command
The .update Bazel run target shall extract requirement identifiers from the TrlcProviderInfo target, parse GTest XML result files for lobster-tracing-linked test cases, build the spec from given/when/then, and overwrite the committed lock file.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:265:43
[MISSING] TRLC Toolrequirement UseCases.Test_Command_Verification
The Bazel test target shall parse GTest XML result files, rebuild the spec for each linked test, and compare uid and spec against the committed lock file, failing if they differ. On failure it shall print a human-readable diff showing which test cases changed and the exact bazel run command needed to refresh the lock file.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:276:43
[MISSING] TRLC Toolrequirement UseCases.LOBSTER_Covered_Attribute
The test target shall emit a lobster-act-trace JSON artifact that marks each linked test case as “ok” when its uid exists in the committed lock file and its spec matches, and “fail” otherwise.
Traces to:
missing reference to Code
Derived from:
missing up reference
Source: bazel/rules/rules_score/docs/requirements/tool_requirements.trlc:288:43