Is there a product that can pull requirements from DOORS into TestStand so they do not have to be entered twice?

[Witoka]

Export requirements from DOORS into TestStand and not allow requirement changes in TestStand.  All editing should be done in DOORS and then exported into TestStand.  Is there an application that can link the two together to meet that request?

[~jiggawax~]

I thought this was built on DOORS but I could be wrong. http://zone.ni.com/devzone/cda/tut/p/id/8330   

I've not heard of an automated process that does this.

[AllenP]

Requirements Gateway talks between DOORS (and several other requirements management products) and TestStand (and several other NI products).

[RayFarmer]

There isn't a product that is commercially available that will do this that I know of.

NI Gateway doesn't do this, all it does is place traceable references inside documents, Test Sequence, Code that is linked to a requiremnts which could be in DOORS. This you have to do manually in NI Gateway. NI Gateway can also create the basic frame of a the Test Sequence or Code module but it can not build you whole test sequence or code.

You could have all sorts of information in DOORS that could be extracted out by some tool so as to create test sequences / sequences but to create code modules as well is asking a lot.

One way would be to have a set of pre-defined code modules or custom steps already built that your tool could ues ( a bit like the example in TestStand which can build a test sequence from information from an INI file an run that test sequence after it has been created).

As to not allowing changes in TestStand, probably the only ways there are to not supply a Sequence Editor and to password protect your sequence files and remove diagrams from LabVIEW VI's or package your code module into say  a DLL's.

[Norbert_B · Accepted solution]

As already said, there is no tool available which does what you want. The reason for this is, that managing requirements with DOORS has a standardized interface, but the description for each test is custom, so transition for test description -> test routine is always custom as well.

Nevertheless, you can create such a tool (or let some partner develope one).

I have to be honest with you: Creating such tool requires good knowledge of DOORS (or NI Requirement Gateway if you use this to extract requirements), TestStand API and a programming language. I suggest the following procedure:

1. Extract the requirements from DOORS (e.g. using NIRG) and create some file based description for the requirements. I would use XML.

2. Create a Sequence File Translator for TestStand. This loads your interims XML file and creates a TS Sequencefile. You will want to define step types (including code modules) to ease transistion. Creating step types and Sequence File Translator requires good knowledge of TS.

3. Create an UI for TS giving the user the ability to "simply export test routines from DOORS to TS". This would incorporate step 1 and 2 into an application for the enduser.

Please note that esp. the second part of step 2 shows why NI does not provide an off-the-shelf product for this approach.

hope this helps,

Norbert

[AmitKaria2k]

NI Requirement Gateway can be used in your scenario. Checkout the following link:

https://www.ni.com/en-us/shop/product/requirements-gateway.html