Use Cases
=========

**Coverage:** 43.8% (7 of 16 items OK)

.. _lobster-item-3946d6859e7b08de155fa8242d00dca1fcf26a01:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Verify\_Architecture\_Conformance
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:68:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L68>`__

.. _lobster-item-4579e1519cd395a734f5e93b02f7148ebf352466:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Trace\_Failure\_Modes\_To\_Interfaces
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:87:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L87>`__

.. _lobster-item-9392f557673c87f4d3533c01aeeffaf39bac575e:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Aggregate\_Safety\_Analysis\_Report
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:96:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L96>`__

.. _lobster-item-a6461294825ddc7fc5cdc1e1011d3d340f7173cd:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Enforce\_Certified\_Scope\_And\_Integrity
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:106:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L106>`__

.. _lobster-item-18a8783ced685e2b017d8352760280039e33387b:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Author\_Requirements\_In\_Rst\_Or\_Trlc
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:116:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L116>`__

.. _lobster-item-ae7e63b8cd467312470575bdc970159ba753a746:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Verify\_Unit\_Tests\_Pass
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:126:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L126>`__

.. _lobster-item-c28b5d4714ef3419f75201156010298489ff22b9:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Merge\_Cross\_Module\_Documentation
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:135:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L135>`__

.. _lobster-item-0178ede123bb22180565193660812ffe55d4e878:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Validate\_Architecture\_Specification\_Documents
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:156:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L156>`__

.. _lobster-item-09ff16403e494b9cc92a7d0c503b9f0d2e6a548b:

.. dropdown:: [MISSING] TRLC Usecase UseCases.Validate\_Unit\_Specification\_Documents
   :open:
   :class-title: sd-bg-danger sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   .. card::
      :class-card: lobster-issue-card

      * missing reference to Potential Errors

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:166:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L166>`__

.. _lobster-item-5bf01423d1d7ec424f75a8f52b286c3bf9e51f24:

.. dropdown:: [OK] TRLC Usecase UseCases.Build\_Traceable\_Documentation
   :class-title: sd-bg-success sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   * :ref:`UseCases.Missing\_Requirement\_In\_Output <lobster-item-513ab6aaff6aa3ab495c8007ef045aa47b9b3c8c>`
   * :ref:`UseCases.Broken\_Cross\_Reference <lobster-item-7ced35da8f7cd8140cb2772ba5ec95ef08ed8097>`

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:19:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L19>`__

.. _lobster-item-f834194333ad628849b71e9d604bb30dfb5b145c:

.. dropdown:: [OK] TRLC Usecase UseCases.Validate\_Requirement\_Chains
   :class-title: sd-bg-success sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   * :ref:`UseCases.Broken\_Cross\_Reference <lobster-item-7ced35da8f7cd8140cb2772ba5ec95ef08ed8097>`
   * :ref:`UseCases.Undetected\_Missing\_Traceability <lobster-item-8678328713fd839c86743dab0ef6d2dce2d24554>`
   * :ref:`UseCases.Incorrect\_Provider\_Chain <lobster-item-a5ad25025aa0de256a2a9ca702af7ac5d1566b00>`

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:29:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L29>`__

.. _lobster-item-265868cb6b0ede376eae2aee867df97ecf6dfe9a:

.. dropdown:: [OK] TRLC Usecase UseCases.Render\_Safety\_Analyses
   :class-title: sd-bg-success sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   * :ref:`UseCases.Missing\_Failure\_Mode\_In\_Render <lobster-item-0ea377ceb997572e4699ddf21c406295870469d4>`

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:39:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L39>`__

.. _lobster-item-da6f8db567d860ce010c454046551ab29d0cb9bb:

.. dropdown:: [OK] TRLC Usecase UseCases.Assemble\_Dependable\_Element
   :class-title: sd-bg-success sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   * :ref:`UseCases.Incorrect\_Provider\_Chain <lobster-item-a5ad25025aa0de256a2a9ca702af7ac5d1566b00>`
   * :ref:`UseCases.Missing\_Failure\_Mode\_In\_Render <lobster-item-0ea377ceb997572e4699ddf21c406295870469d4>`
   * :ref:`UseCases.Silent\_Diagram\_Parse\_Failure <lobster-item-40e89cc7b9b5484db47595fbc2bc6bdd0e0670dc>`

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:49:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L49>`__

.. _lobster-item-b8b0170d611a7c1ad38b646be9c84537c209fed0:

.. dropdown:: [OK] TRLC Usecase UseCases.Parse\_Architectural\_Diagrams
   :class-title: sd-bg-success sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   * :ref:`UseCases.Silent\_Diagram\_Parse\_Failure <lobster-item-40e89cc7b9b5484db47595fbc2bc6bdd0e0670dc>`

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:59:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L59>`__

.. _lobster-item-23df4d1efff6944e78ae37380bfa4d84d42d23bd:

.. dropdown:: [OK] TRLC Usecase UseCases.Gate\_Traceability\_At\_Test\_Time
   :class-title: sd-bg-success sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   * :ref:`UseCases.AoU\_Silently\_Dropped <lobster-item-8e1731daac058e1c027aceaf7961ddec068708a4>`

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:78:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L78>`__

.. _lobster-item-101773ba44552347386d09e29933907d90195a47:

.. dropdown:: [OK] TRLC Usecase UseCases.Forward\_AoU\_To\_Dependees
   :class-title: sd-bg-success sd-text-white

   .. pull-quote::

      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.

   .. raw:: html

      <hr>

   **Traces to:**

   * :ref:`UseCases.AoU\_Silently\_Dropped <lobster-item-8e1731daac058e1c027aceaf7961ddec068708a4>`
   * :ref:`UseCases.Invalid\_Forwarding\_YAML\_Accepted <lobster-item-542ad2e8b8d798aea0954d942233ef68af9ab2c1>`

   .. raw:: html

      <hr>

   **Source:** `bazel/rules/rules\_score/docs/requirements/use\_cases.trlc:145:31 <../../../../../../../bazel/rules/rules_score/docs/requirements/use_cases.trlc#L145>`__