Since the above mentioned idea came from me, I will elaborate a little bit on the approach.
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. That means there shall be no "global" database of available requirement string identifiers planned to be read by the Doxygen tool directly.
Each position on the list of requirement string identifiers shall be an URL with title req-string-id
and href pointing to a generated subpage. A subpage shall contain req-string-id
, calculated req-string-id-header
, req-string-id-body
, req-string-id-url
information strings, and list of URLs to locations (lines or blocks) within a source code where the actual @req{}
happened. Locations should include code snipp