Feb 13, 2013 · I use a custom Doxygen tag to track requirement implementations in my software source code, like so : The @req tag is defined in my doxygen.conf file: This works, Doxygen generates a list of requirements for each method/class/file.

Jun 5, 2013 · I already know that I can set up Doxygen to write undocumented elements as warnings into a log file, but to fully evaluate the documentation coverage from that, I'd need to write my own warning log parser.

May 19, 2020 · The goal is to generate, through the Doxygen tool source code extension, an index page, and accompanied set of pages of documentation. An index page shall contain a list of all the requirement strings (i.e. identifiers) where each one such string shall be referenced in the parsed source code through the designed @req{<req-string-id>} command.

Jun 11, 2013 · Now I'm trying to use doxygen also for "requirement coverage". I mean: I have a set of requirements and I would like to trace them back to Java / C modules and function implementing them.

Jul 8, 2018 · We use the API documentation as the main interface to trace implementation back to documented features. This is done using custom doxygen tags that reference requirements maintained somewhere else in a requirement catalogue.

First, run doxygen with XML output on your project, Coverxygen will read generated file and produce an lcov compatible output. Finally, run lcov or genhtml to produce the coverage output. Alternatively, Coverxygen can also calculate the coverage and print a summary table when given the option --format summary .

doxy-coverage is a source code documentation coverage measurement tool. Its primary use case is to gate on the percentage of API and structures documented on software projects. First, Doxygen must be run on your project's source code to generate some XML documentation files. Doxy-coverage consumes those files and reports the documentation coverage.

Sep 14, 2007 · In general, I think this could create: 1) Hyperlinks to source requirements in a page 2) Pages of requirements analysis, specifically: Trace matrix, Code that has no requirements, Code that has no output, etc. I'm still working out how to interface with requirements databases / where the requirements would be stored.

Jul 29, 2020 · take a look at reqflow that create traceability matrix. I'm using that to trace the requirements to the code and requirements to the test cases. http://goeb.github.io/reqflow/#example-of-report. It can be configured with regexp to …

Nov 14, 2022 · Requirement traceability is required to answer two fundamental questions: are we building the right product? Are we building the product correctly? Code documentation can embed requirement identifiers that enable forward and backward tracing to code.