Re: [rmf-dev] Corrupt DOORS TOOL-Extension section after opening ReqIF w

[Arne Noyer <anoyer@xxxxxxxxxx>]

Hello!

Thank you very much for your quick response. You find the ReqIF files attached.

I have used RMF version 0.12.0.201503190302 programmatically at first and afterwards, i downloaded the most current version of formalmind studio with RMF version 0.13.0.201505310301 and observed the same behavior.

Attachment: FromDoors_SavedInProR.reqif
Description: Binary data

Attachment: FromDoors.reqif
Description: Binary data

Best regards,

Arne

Am 09.09.2015 um 14:52 schrieb Mark Brörkens <mark.broerkens@xxxxxxxxx>:

Hello,

this looks like an issues that is related to the serialization.
In order to reproduce the error, it would be great if you could send me the original file that was exported by DOORS and the file that was saved by RMF.

Which version of RMF are you using?

First analysis: The namespace prefix „doors“ is a shortcuts for the complete namespace uri which should be registered in the header of the reqif file.
I assume that the mapping of the doors tool extension namespace uri to its namespace prefix is somehow broken.

Kind regards

Mark




Am 09.09.2015 um 14:19 schrieb Arne Noyer <anoyer@xxxxxxxxxx>:

Hello all!

I have exported a ReqIF file using IBM DOORS, opened it with ProR / RMF / formalmind Studio and saved it. Afterwards, when re-importing the ReqIF file in DOORS, DOORS is unable to identify, which ReqIF-Definition (DOORS Configuration for the ReqIF Export) has to be used. Thereby, it is not possible to update an existing DOORS document when the ReqIF file was opened and saved with ProR.

I have observed, that after opening the ReqIF file with ProR, there are some minor changes in the TOOL-EXTENSION section of DOORS.
Especially, a prefix "doors" in xml tags is replaced with "xmlns" like this:


Before opening with ProR:


<REQ-IF-TOOL-EXTENSION>
....
<doors:DOORS-RIF-DEFINITION>
<doors:IDENTIFIER>_a51e5f1d-f828-4207-820f-cbbe71ffa855</doors:IDENTIFIER>
<doors:MODULE-DEFINITION>
<doors:DDC-MODE>NO_DDC</doors:DDC-MODE>
<SPECIFICATION-REF>_c73b196c-5836-49c1-9d99-57a6433ba446</SPECIFICATION-REF>
</doors:MODULE-DEFINITION>
</doors:DOORS-RIF-DEFINITION>
....
</REQ-IF-TOOL-EXTENSION>


After opening with ProR:

<REQ-IF-TOOL-EXTENSION>
....
<xmlns_1.0:DOORS-RIF-DEFINITION>
<xmlns_1.0:IDENTIFIER>_a51e5f1d-f828-4207-820f-cbbe71ffa855</xmlns_1.0:IDENTIFIER>
<xmlns_1.0:MODULE-DEFINITION>
<xmlns_1.0:DDC-MODE>NO_DDC</xmlns_1.0:DDC-MODE>
<SPECIFICATION-REF>_c73b196c-5836-49c1-9d99-57a6433ba446</SPECIFICATION-REF> </xmlns_1.0:MODULE-DEFINITION>
</xmlns_1.0:DOORS-RIF-DEFINITION>
....
</REQ-IF-TOOL-EXTENSION>


I think this results in the issues when re-importing the ReqIF file to DOORS. When copying the TOOL-EXTENSION section from the file, before opening it with ProR and pasting it in the newly saved file, everything works fine, again. Please contact me, if you want to have the complete ReqIF files as an example.

Is there any way to prevent RMF and/or ProR from making such changes?

Best regards

Arne
_______________________________________________
rmf-dev mailing list
rmf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rmf-dev

_______________________________________________
rmf-dev mailing list
rmf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rmf-dev

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail