Engineering Requirements Management

Engineering Requirements Management

Come for answers, stay for best practices. All we're missing is you.

 View Only
Expand all | Collapse all

PICTURE attributes are lost during ReqIF import

  • 1.  PICTURE attributes are lost during ReqIF import

    Posted Mon August 10, 2020 06:53 AM

    I have an ReqIF that among others also contains the following attribute definitions:

    ```

                         <ATTRIBUTE-DEFINITION-BOOLEAN DESC="System Attribute" IDENTIFIER="_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURE" IS-EDITABLE="true" LAST-CHANGE="2014-12-09T00:00:00" LONG-NAME="Picture">

                            <TYPE>

                               <DATATYPE-DEFINITION-BOOLEAN-REF>_5fb9d931-60e1-494e-b381-aac923de5d0d</DATATYPE-DEFINITION-BOOLEAN-REF>

                            </TYPE>

                            <DEFAULT-VALUE>

                               <ATTRIBUTE-VALUE-BOOLEAN THE-VALUE="false">

                                  <DEFINITION>

                                     <ATTRIBUTE-DEFINITION-BOOLEAN-REF>_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURE</ATTRIBUTE-DEFINITION-BOOLEAN-REF>

                                  </DEFINITION>

                               </ATTRIBUTE-VALUE-BOOLEAN>

                            </DEFAULT-VALUE>

                         </ATTRIBUTE-DEFINITION-BOOLEAN>

                         <ATTRIBUTE-DEFINITION-XHTML DESC="System Attribute" IDENTIFIER="_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURENAME" IS-EDITABLE="true" LAST-CHANGE="2014-12-09T00:00:00" LONG-NAME="PictureName">

                            <TYPE>

                               <DATATYPE-DEFINITION-XHTML-REF>_ec129531-6805-4801-8487-7e1ef53125dc</DATATYPE-DEFINITION-XHTML-REF>

                            </TYPE>

                         </ATTRIBUTE-DEFINITION-XHTML>

                         <ATTRIBUTE-DEFINITION-INTEGER DESC="System Attribute" IDENTIFIER="_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURENUM" IS-EDITABLE="true" LAST-CHANGE="2014-12-09T00:00:00" LONG-NAME="PictureNum">

                            <TYPE>

                               <DATATYPE-DEFINITION-INTEGER-REF>_0f2dad33-de7d-4296-a8d7-3ffd4d0a26df</DATATYPE-DEFINITION-INTEGER-REF>

                            </TYPE>

                         </ATTRIBUTE-DEFINITION-INTEGER>

    ```

    ...as well as attribute values using it in the SpecObjects, like this:

    ```

                         <ATTRIBUTE-VALUE-BOOLEAN THE-VALUE="true">

                            <DEFINITION>

                               <ATTRIBUTE-DEFINITION-BOOLEAN-REF>_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURE</ATTRIBUTE-DEFINITION-BOOLEAN-REF>

                            </DEFINITION>

                         </ATTRIBUTE-VALUE-BOOLEAN>

                         <ATTRIBUTE-VALUE-XHTML>

                            <DEFINITION>

                               <ATTRIBUTE-DEFINITION-XHTML-REF>_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURENAME</ATTRIBUTE-DEFINITION-XHTML-REF>

                            </DEFINITION>

                            <THE-VALUE><reqif-xhtml:img>https://vignette.wikia.nocookie.net/ceal/images/a/a5/Ozymandias.png</reqif-xhtml:img></THE-VALUE>

                         </ATTRIBUTE-VALUE-XHTML>

                         <ATTRIBUTE-VALUE-INTEGER THE-VALUE="1">

                            <DEFINITION>

                               <ATTRIBUTE-DEFINITION-INTEGER-REF>_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURENUM</ATTRIBUTE-DEFINITION-INTEGER-REF>

                            </DEFINITION>

                         </ATTRIBUTE-VALUE-INTEGER>

    ```

    However, when I import the ReqIF to DOORS using `File > Import ReqIF Package`, these three attributes and their values are not imported.

    Why?

    I mean, it's okay-ish for DOORS to not display the pictures, but in essence, these three Attributes are simply a Boolean, an XHTML and an Integer that should be persisted.

    So, what is happening here? And is there any way around this?





    #EngineeringRequirementsManagement
    #Support
    #DOORS
    #SupportMigration
    #Sustainability


  • 2.  RE: PICTURE attributes are lost during ReqIF import

    Posted Wed August 12, 2020 05:21 PM

    Can you please raise a ticket with support? This should really be investigated as a defect through the proper support channels.





    #Support
    #DOORS
    #Sustainability
    #SupportMigration
    #EngineeringRequirementsManagement


  • 3.  RE: PICTURE attributes are lost during ReqIF import

    Posted Fri August 14, 2020 08:02 AM


  • 4.  RE: PICTURE attributes are lost during ReqIF import

    Posted Mon August 17, 2020 05:32 PM

    There should be an "Open a case" button in the top right corner of this browser. If you don't see that you can access the following link:

    https://www.ibm.com/mysupport/s/createrecord/NewCase





    #SupportMigration
    #DOORS
    #EngineeringRequirementsManagement
    #Support
    #Sustainability


  • 5.  RE: PICTURE attributes are lost during ReqIF import

    Posted Mon August 24, 2020 04:37 AM

    Ah yes, I already tried that, but unlike proper issue tracking systems, this makes me dance a scary dance, redirecting me to a support access website or something where I have to enter a Customer number. Is this something I can read out from my DOORS installation? Or do I have to contact my system administrator for this? I should probably also note that I'm just using an evaluation version because we first want to try out if there's anything that speaks against using DOORS such as, say, it not importing PICTURE attributes from a ReqIF file for some reason. =>,<=





    #Sustainability
    #EngineeringRequirementsManagement
    #SupportMigration
    #Support
    #DOORS


  • 6.  RE: PICTURE attributes are lost during ReqIF import

    Posted Mon August 24, 2020 10:56 PM

    I'm not sure to be honest. I would suggest talking to your system administrator and seeing what they say.


    Where did this ReqIF file originate from?





    #SupportMigration
    #EngineeringRequirementsManagement
    #Support
    #DOORS
    #Sustainability


  • 7.  RE: PICTURE attributes are lost during ReqIF import

    Posted Wed August 26, 2020 06:09 AM

    We got the file from one of our business partners. Come to think of it, it is not entirely impossible that this file might have been exported from DOORSNG instead of classic DOORS.





    #EngineeringRequirementsManagement
    #Sustainability
    #DOORS
    #Support
    #SupportMigration


  • 8.  RE: PICTURE attributes are lost during ReqIF import

    Posted Wed August 26, 2020 06:28 AM

    I checked, and apparently that file was exported from classic DOORS after all, which makes it all the more mysterious. Why would DOORS be able to export the PICTURE fields, but not import them?


    Specifically, if I import the ReqIF File into DOORS, and then export it again, information is lost! That should not be the case! The information that is being lost that I know about are the pictures, but there might be other information losses I have not yet spotted.


    The imported ReqIF file is 62,946 lines long.

    The exported ReqIF file is 46,258 lines long.





    #Support
    #SupportMigration
    #EngineeringRequirementsManagement
    #DOORS
    #Sustainability


  • 9.  RE: PICTURE attributes are lost during ReqIF import

    Posted Wed August 26, 2020 04:39 PM

    Pictures are not supported in ReqIF exports, when you try to export a module with pictures it gives you the message: "Picture export is not supported - no pictures have been exported in this package."


    OLE objects are supported however, I would recommend using that for images you wish maintain.


    I thought in the description of this post you said it was Boolean and Integer attributes that weren't persisting?





    #DOORS
    #Support
    #SupportMigration
    #Sustainability
    #EngineeringRequirementsManagement


  • 10.  RE: PICTURE attributes are lost during ReqIF import

    Posted Fri August 28, 2020 12:58 PM

    Yes, exactly! It's not pictures, but rather attributes that have the following attribute definitions which are not being imported:

    • <ATTRIBUTE-DEFINITION-BOOLEAN DESC="System Attribute" IDENTIFIER="_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURE" IS-EDITABLE="true" LAST-CHANGE="2014-12-09T00:00:00" LONG-NAME="Picture">
    • <ATTRIBUTE-DEFINITION-XHTML DESC="System Attribute" IDENTIFIER="_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURENAME" IS-EDITABLE="true" LAST-CHANGE="2014-12-09T00:00:00" LONG-NAME="PictureName">
    • <ATTRIBUTE-DEFINITION-INTEGER DESC="System Attribute" IDENTIFIER="_3471638a-4f37-4627-8c55-dcf025daa5bb_PICTURENUM" IS-EDITABLE="true" LAST-CHANGE="2014-12-09T00:00:00" LONG-NAME="PictureNum">

    It's like DOORS systematically samples them out based on some algorithm, and refuses to import them.





    #EngineeringRequirementsManagement
    #Support
    #DOORS
    #Sustainability
    #SupportMigration