Requirements
Tool Requirements
Requirements Rendering
- UseCases.Render_All_TRLC_Records
- Description:
The trlc_rst renderer shall produce an RST output that contains
every requirement record present in the input TRLC source files.
- UseCases.Resolve_Derived_From_References
- Description:
The rendered RST output shall contain working cross-references
for all derived_from fields, linking child requirements to their parent requirements.
Requirement Validation
- UseCases.Validate_Traceability_Completeness
- Description:
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.
- UseCases.Emit_Correct_Provider_Info
- Description:
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.
- UseCases.Emit_Sphinx_Sources
- Description:
The score_requirements_rule shall emit a SphinxSourcesInfo
provider containing the rendered RST file and all transitive Sphinx source dependencies.
Safety Analysis Rendering
- UseCases.Render_All_Failure_Modes
- Description:
The FMEA rule shall render every FailureMode record from the
input TRLC sources into the documentation output.
Architecture Parsing
- UseCases.Reject_Invalid_PlantUML
- Description:
The PlantUML parser shall exit with a non-zero return code when
the input diagram contains syntactical errors, preventing silent production of incorrect output.
Lobster Traceability
- UseCases.Extract_Lobster_From_Requirements
- Description:
The requirements rule shall extract a lobster traceability file
from all TRLC requirement records using the configured lobster extraction schema.
AoU Forwarding
- UseCases.Forward_Own_AoUs_To_Dependees
- Description:
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.
- UseCases.Chain_Forward_Received_AoUs
- Description:
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.
- UseCases.Reject_Unknown_AoU_In_Forwarding_YAML
- Description:
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.
- UseCases.Include_Forwarded_AoUs_In_Traceability
- Description:
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).