Tool Qualification Report Example#
This page demonstrates the machine-readable model used for a Docs-as-Code tool qualification report. The content is based on the published S-CORE Doc-as-Code Tool Verification Report.
The evaluation considers build and CI behavior, pull-request review, and
derived views. A malfunction is represented as a nested Need below the use case
where it occurs. Its safety_measure is intentionally free text. Generated
testcase Needs can link back to a malfunction through the existing verification
links.
Docs-as-Code Tool Qualification
|
status: evaluated
|
||||
This report evaluates the Docs-as-Code toolchain as a qualified tool for producing and verifying safety-relevant documentation. |
|||||
Automatically generated overview starts here.
Tool qualification matrix#
The following table summarizes the tool use cases and their identified malfunctions. Each malfunction is nested below its use case and links to the requirements it violates.
Malfunction identification |
Use case description |
Malfunction |
Impact on safety? |
Safety measure available? |
Detection sufficient? |
Additional safety measure required? |
Confidence |
|---|---|---|---|---|---|---|---|
Listing assumptions of use (tool_malfunction__docs_as_code__aou_listing) |
Build and CI behavior |
A missing or incorrect assumption of use can lead to an incomplete safety argument. |
YES |
YES |
NO |
YES |
LOW |
Requirements coverage stati... (tool_malfunction__docs_as_code__coverage) |
Build and CI behavior |
A defect in the statistics calculation can produce an incorrect coverage result while leaving the build green. |
YES |
YES |
NO |
YES |
LOW |
Safety-critical linking enf... (tool_malfunction__docs_as_code__safety_links) |
Build and CI behavior |
A silent false negative could allow an unsafe derivation or other invalid safety-critical link to pass the build. |
YES |
YES |
NO |
YES |
LOW |
Document metamodel enforcement (tool_malfunction__docs_as_code__metamodel) |
Build and CI behavior |
A silent false negative can result from a permissive regular expression or a defect in a metamodel check. |
YES |
YES |
NO |
YES |
LOW |
Build and CI behavior |
The safety case may incorrectly conclude that a requirement is tested if a testcase link is missing or points to the wrong need. |
YES |
YES |
NO |
YES |
LOW |
|
Test reference check (tool_malfunction__docs_as_code__test_refs) |
Build and CI behavior |
A missing or outdated requirement reference can invalidate the test evidence without causing a CI failure. |
YES |
YES |
NO |
YES |
LOW |
Architecture visualization (tool_malfunction__docs_as_code__arch_view) |
Derived views |
An incorrect visualization can misrepresent the architecture. The result is detected by inspecting the derived view. |
YES |
YES |
YES |
NO |
HIGH |
Derived views |
A generated backlink can be missing or point to the wrong Need. |
NO |
YES |
NO |
YES |
LOW |
|
Documentation generation (tool_malfunction__docs_as_code__generation) |
Derived views |
The generated HTML can be incomplete, outdated, or rendered incorrectly. The issue is detected by inspecting the derived view. |
NO |
YES |
YES |
NO |
HIGH |
Traceability evidence#
The evidence below keeps requirement violations, safety measures and generated testcase links visible without hiding them in the summary table.
Build and CI behavior
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The repository contents are the source of truth and gated CI evaluates the generated documentation and traceability data.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Derived views
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Derived views are generated from the machine-readable Need model and are not the source of truth.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||