Requirements

Use Cases

UseCases.Build_Traceable_Documentation

As a safety engineer I want to build HTML documentation from requirements, architecture diagrams, and safety analyses so that all artefacts are rendered in a single navigable document with cross-references and traceability information.

UseCases.Validate_Requirement_Chains

As a requirements engineer I want the build system to validate that all component requirements trace back to feature requirements and all feature requirements trace back to assumed system requirements so that incomplete traceability is detected early.

UseCases.Render_Safety_Analyses

As a safety engineer I want FMEA failure modes and control measures to be rendered into the documentation automatically so that the safety analysis artefacts are always up to date with the source TRLC definitions.

UseCases.Assemble_Dependable_Element

As a project lead I want to assemble a dependable element (SEooC) from its components, requirements, architectural design and safety analyses so that the complete safety case is represented as a single auditable artefact.

UseCases.Parse_Architectural_Diagrams

As a software architect I want PlantUML component and sequence diagrams to be parsed and verified during the build so that architectural design errors are caught before integration.

UseCases.Verify_Architecture_Conformance

As a software architect I want the implemented component and unit structure to be checked against the static architecture diagrams during the build so that the delivered code does not drift away from the documented architecture.

UseCases.Gate_Traceability_At_Test_Time

As a safety engineer I want a test that fails when the traceability chain of a dependable element is incomplete so that an element with unsatisfied traceability links cannot be released.

UseCases.Trace_Failure_Modes_To_Interfaces

As a safety engineer I want failure modes to be traceable to the public interface elements of the architecture so that every failure mode is allocated to a concrete part of the design.

UseCases.Aggregate_Safety_Analysis_Report

As a safety engineer I want failure modes, control measures and fault-tree root causes to be aggregated into a single traceability report so that the completeness of the safety analysis can be assessed in one place.

UseCases.Enforce_Certified_Scope_And_Integrity

As a project lead I want the build to fail when a dependable element pulls in implementation targets outside its certified scope or depends on an element of lower integrity level so that certification boundaries are enforced automatically.

UseCases.Author_Requirements_In_Rst_Or_Trlc

As a requirements engineer I want to author requirements either as RST directives or as TRLC records so that existing RST requirement sources can be integrated into the traceability chain without manual rewriting.

UseCases.Verify_Unit_Tests_Pass

As a software developer I want unit test results to be captured and fed into the traceability report so that requirements are only considered verified when their tests actually pass.

UseCases.Merge_Cross_Module_Documentation

As a documentation author I want the HTML documentation of dependent modules to be merged into a single navigable site with working cross-references so that a dependable element and its sub-elements are read as one document.

UseCases.Forward_AoU_To_Dependees

As a system integrator I want assumptions of use defined by a dependable element to be automatically forwarded to the elements that depend on it so that the integrating project is made aware of all conditions it must satisfy — including those originating from transitive dependencies.

UseCases.Validate_Architecture_Specification_Documents

As a software architect I want the build to verify that architectural specification documents (component and sequence diagrams) are consistent with the implemented Bazel structure so that specification drift is detected automatically during the build.

UseCases.Validate_Unit_Specification_Documents

As a software developer I want the build to verify that unit design class and sequence diagrams are consistent with the corresponding implementation artefacts so that unit-level design drift is detected automatically during the build.

UseCases.Declare_Complete_Coverage

As a safety engineer I want to declare that a set of requirements is completely covered by automated test cases so that the coverage claim is explicit, auditable, and version-controlled.

UseCases.Detect_Specification_Drift

In the CI pipeline I want to detect automatically when a test’s given/when/then specification or formal test specification has changed without re-approval so that stale coverage claims are caught before release.

UseCases.Formal_Test_Specification

As a test engineer I want to specify a complex test case in a formal test specification document (test goal, test focus, test steps) instead of a given/when/then description, so that multi-step and higher-order tests are specified completely and the specification is part of the reviewed coverage claim.

UseCases.Detect_Coverage_Set_Changes

In the CI pipeline I want to detect when a test case is added to or removed from the set of tests linked to a requirement so that undeclared coverage changes cannot pass silently.

UseCases.Generate_Covered_Traceability_Artifact

As a project integrator I want the tool to emit a LOBSTER-compatible artifact that marks each linked test case as covered or not so that complete requirement coverage is visible in the LOBSTER dashboard.

UseCases.Semi_Automated_Lock_Update

As an engineer I want a single bazel run command that reads requirement identifiers from the TRLC requirements target, discovers all linked test cases in the GTest XML results, and rewrites the lock file, so that I only need to review the diff before committing my approval.