My concrete example is the module verification report
Currently the analyzed module can be determined from the id only, or from being in the same repository. While that is theoretically enough for traceability, a more explicit link would help traceability tooling.
Proposal: extend document with a documents or affects or belongs_to links or similar, which would link to the mod in question.
This will also establish a backlink from modules to module verification reports.
Todays workaround is a custom type which has such a link. This allows automated generation of such reports.
My concrete example is the module verification report
Currently the analyzed module can be determined from the id only, or from being in the same repository. While that is theoretically enough for traceability, a more explicit link would help traceability tooling.
Proposal: extend document with a
documentsoraffectsorbelongs_tolinks or similar, which would link to themodin question.This will also establish a backlink from modules to module verification reports.
Todays workaround is a custom type which has such a link. This allows automated generation of such reports.