RIF - data exchange between DOORS and other tools supporting RIF/ReqIF

So far we have tested exchanging RIF data between DOORS 9.3.0.6 and two other commonly-used requirements management tools - without success.

DOORS 9.3 to another DOORS 9.3 works fine but that is hardly the point of adopting a standard which was created for use between tools and not within the same tool. The whole point of RIF/ReqIF is to support data exchange between DIFFERENT tools supporting the extended XML standard.

Specifically and with highest priority we need to exchange data with a supplier who is using Polarion. Polarion has implemented RIF 1.1a and DOORS seem to have implemented RIF 1.0. Even this small difference seems to make data exchange impossible. DOORS runs the RIF import without errors but no data is imported, though we can see a lot of data in the rif source file. Again, and similarly with DOORS, Polarion to Polarion works fine.

Has anyone successfully exchanged data between DOORS and other RIF-supporting tools (i.e.: NOT only between DOORS databases)? It would be good if anyone had done this successfully with DOORS<-->Polarion.

TIA.
BillTidy - Tue May 15 11:51:59 EDT 2012

Re: RIF - data exchange between DOORS and other tools supporting RIF/ReqIF
BillTidy - Mon May 21 04:21:04 EDT 2012

Well, as I suspected, not looking very hopeful that anyone is using RIF/ReqIF as it was designed.

We're still pursuing this, so I will update if I have something new.
Meanwhile, if anyone does have anything, please post here.
Thanks.

Re: RIF - data exchange between DOORS and other tools supporting RIF/ReqIF
SystemAdmin - Thu Nov 29 05:13:12 EST 2012

We have been implementing an ReqIF support for one of our tools and tested the round-tripping scenario against the 9.4.0 version of DOORS, which shall support ReqIF 1.0.1.

We noticed that the DOORS implementation of ReqIF does not fully comply to the ReqIF Specification. Before one can import a ReqIF-File exported from DOORS, one has to do some adjustments to the file with regard to DOORS specific information stored in the file, which are not compatible to the standard. In other word, one has to adjust the file in a manner, that makes it compatible to the standard. Only then such a file can be imported.
It also concerns the import of a ReqIF-File generated in another tool to DOORS.

Re: RIF - data exchange between DOORS and other tools supporting RIF/ReqIF
BillTidy - Mon Dec 10 10:21:38 EST 2012

SystemAdmin - Thu Nov 29 05:13:12 EST 2012
We have been implementing an ReqIF support for one of our tools and tested the round-tripping scenario against the 9.4.0 version of DOORS, which shall support ReqIF 1.0.1.

We noticed that the DOORS implementation of ReqIF does not fully comply to the ReqIF Specification. Before one can import a ReqIF-File exported from DOORS, one has to do some adjustments to the file with regard to DOORS specific information stored in the file, which are not compatible to the standard. In other word, one has to adjust the file in a manner, that makes it compatible to the standard. Only then such a file can be imported.
It also concerns the import of a ReqIF-File generated in another tool to DOORS.

Thanks for your reply. What is the tool you have developed the ReqIF interface for?
Yes, you're correct that DOORS seems to have its own flavour of ReqIF - hardly the sense of having an industry 'standard' data format.

We dropped the whole ReqIF idea since it never seems to have got off the ground with tool vendors and developed a standardized csv import/export script in DXL which is configurable, so we do not have to change it for any application - csv has its limitations but at least it works.

Re: RIF - data exchange between DOORS and other tools supporting RIF/ReqIF
meirajl - Thu Apr 21 03:35:38 EDT 2016

Hello,

    I am facing some issues when importing a reqif packages (exported from Polarion) into DOORS.

I have two reqif packages exported from Polarion. The first one is the full package and the second one is an update of the first one.

When, for the first time, I import the first reqIf package into DOORS 9.5 version, it seems to work fine. DOORS creates a ReqIf definition (ReqDef A) and also the module (Module A) contained in the reqIf package.

Now when I import the second reqIf package (which is an update of the first one), I expect DOORS to use the same reqIf definition (in my case ReqDef A) so that the Module A is updated. This is not the case.

When I import the second reqIf package, DOORS wants me to create another ReqIf definition. So I create ReqDef B and then DOORS creates a Module B.

The issue is that Module A is never updated with the second package.

 

Is this coming from DOORS and my way of importing and merging the reqif package received from my client ?

Or is it coming from Polarion and the way the client perfoms its export into reqIF ?

 

Thanks in advance for your help because I am a little bit lost!

 

Jean-Paul