Hi,
for a complete validation of a software, it is mandatory to perform tests. When testing, we differ between two major tasks:
- static code analysis
- dynamic code analysis
For static code analysis, we got the VI Analyzer toolkit. It automates the task of looking into the sources (front panel and block diagram) and compare the current layout against recommended layout (style guide). Additionally, it detects known sources of issues for lack in performance or even crashes and misbehavior during runtime.
So it makes perfect sense, to define requirements that static code analysis has to be performed before proceeding to dynamic (runtime) code analysis.
Yet, VI Analyzer tasks have no option for creating such a link as a field "comment" or "description" is missing for the configuration!
I suggest to add such a field in the cfg-file level (exported VI Analyzer configuration) where we can add strings like [Covers: <req_ID>] as we are used to in LV code.
Norbert