Using Requirements Gateway with LabVIEW classes

[Thoric]

Does anyone know how to get the NI Requirements Gateway to read coverage information from the documentation contained in a LabVIEW class (.lvclass)?

Requirements Gateway appears to load the documentation content fine from VIs, controls, .llb, .lvlib, .lvproj etc, but not .lvclass? My LabVIEW keeps crashing out when I try to point Requirements Gateway at a project with .lvclass files!

If this can't be done then is there a neat way to add requirements coverage information (you know, the "Covers: ID" field) into the class properties, or something near the class maybe, that Requirements Gateway can read?

[Manooch_H · Accepted solution]

Thoric -

I believe Requirements Gateway should be able to trace coverages from LabVIEW Classes as long as the classes are added to a LabVIEW Project and Requirements Gateway is configured to look at the LabVIEW Project. Here's a very primitive example that I pieced together from files in the Requirements Gateway and LabVIEW Example directories.

Hope this helps.

[Thoric]

Hi Manooch,

Thank you for your prompt reply. The example you attached, with a little alteration to include the coverage ID tag in the class documentation field, does precisely what I need, thank you. The snapshot below shows the LabVIEW class satisfying requirement 2:

However, this doesn't work in my project. I have similar content, and when I ask Requirements Gateway to analyse the project it shows nothing and then LabVIEW crashes! I'll have to try stripping my project down to the bare bones to find the problematic element. I hate it when this happens....

[Thoric]

I've just spotted an message area in Requirements Gateway which reports the following after attempting to analyse the LabVIEW project:

Document 'LabVIEW Project    LabVIEW'.
Document 'D:\temp\Simulation\simulation_classes_test.lvproj' type is 'LabVIEW'.
Error: COM error (The remote procedure call failed.

 'Run')
Error: Conversion problem  (file 'D:\temp\Simulation\simulation_classes_test.lvproj')

Does this mean anything to anyone?

[Thoric]

OK, so I rebuilt my test project from the ground up, using the same content (classes, VIs etc.), but in a new LabVIEW Project. Now it works.

Luckily this has only been a test project, a little experiment to help me learn about adopting Requirements Gateway for requirements tracking in LVOOP. If it had been a real (substantial) project, it wouldn't have been so easy to rebuild the whole project from scratch. Very worrying.

[Manooch_H]

Thoric -

If you had a copy of your files that are reproducing this error, you could provide us with the files and we can investigate the error in an effort to fix it in the next version of Requirements Gateway.

[Thoric]

Hi Manooch,

I'll create a Service Request with local Technical Support and link to this thread.

[Manooch_H]

Thoric -

I directly support Requirements Gateway, so if you would prefer not to post your code to this forum thread, I can ask the forum administrator for your email information and contact you directly.

[Thoric]

Hi Manooch,

Feel free to do that if you wish. I'll expect an email from you later