New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generation of traceability matrices #964
Comments
Interrest in matrices generated with export --formats rst |
Adding input from one user on this traceability matrices topic. The context of the following considerations is the DO-178C aviation standard. Input from a userTrace has the following objectives:
A system is usually composed of several functions: 1 sdoc file per function. Functions are allocated to several software/ hardware components through a system design document, which also allocates design assurance level to these components. A software component is specified with HLR (high level requirements), then software design specifies software architecture and low level requirements.
In addition to these objectives, there is some industrial/economic will to optimise change request management. Technical consideration: All artefacts shall remain readable/modifiable during more than 50 years (ex: https://fr.m.wikipedia.org/wiki/Sud-Aviation_SA330_Puma). That's why the artefact data format shall be text or pdf. A trace matrix is a 2 column table: 1/ SYS-REQ,HLR Until today, the relationship between the applicant and the certification authority is based on the sharing of the pdf artefacts, plus some on site audit of the source code and test case. This is not convenient for engineers to use pdf on every day job, and it is also not convenient for the authority to navigate across tens of pdf. Matrices are a way to identify uncovered items in a twinkling of an eye, and to navigate in pdf. They are the entry point to conduct an audit. But there might be other clever ways to comply to the objectives I first described. |
This ticket will probably not be worked before 2023-Q2, so here are only initial thoughts only:
strictdoc.toml
or dynamically in the UI.The text was updated successfully, but these errors were encountered: