It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×12,010
×5,945
×173

question asked: Jul 01 '15, 1:21 a.m.
question was seen: 4,578 times
last updated: Aug 03 '15, 10:21 p.m.

Related questions

Doors Next Generation creates attribute type name with numbers appended to it

1
Tiffany Pei (139●6●23) | asked Jul 01 '15, 1:21 a.m.
I exported 2 DOORS 9.6.1 modules. Both modules have an attribute type called MyRequirement.
Before exporting to a reqifz file, I made sure module 1's MyRequirement attribute type has the same RDF URL as module 2's MyRequirement attribute type.
After I imported this reqifz into DOORS Next Generation 5.0.2 ifix 6, I found that I have both "MyRequirement" and "My Requirement 2" attribute types in Project Properties.
Why is it the case? Is there a way to import without duplicating the attribute type?

Accepted answer

3
permanent link
Howard Hsiao (5.5k●1●7) | answered Jul 01 '15, 4:26 a.m.
JAZZ DEVELOPER
edited Aug 03 '15, 10:21 p.m.
I am not a big fan of hacking. But due to the deadline of my DOORS-to-DNG migration is imminent, I have no choice but to hack reqif.

Below is how I hacked the reqif.

1. Change type ID and its base type ID of duplicated attribute type to be the type ID and its base type ID of the attribute type of the same name that appears first.

For example (concept only, not the actual texts in reqif), I changed 
basetype_ID=b01 type_ID=t01 type_name="MyRequirement"
basetype_ID=b02 type_ID=t21 type_name="MyRequirement"
basetype_ID=b03 type_ID=t31 type_name="MyRequirement"
to 
basetype_ID=b01 type_ID=t01 type_name="MyRequirement"
basetype_ID=b01 type_ID=t01 type_name="MyRequirement"
basetype_ID=b01 type_ID=t01 type_name="MyRequirement"

2. change all objects' associated type ID appropriately

For example (concept only, not the actual texts in reqif), I changed 
type_ID=t01 object1
type_ID=t21 object2
type_ID=t31 object3
to 
type_ID=t01 object1
type_ID=t01 object2
type_ID=t01 object3

I have achieve some degree of success:
1. same attribute type names from different DOORS modules are imported into DNG without duplication.
2. objects of the "same" attribute type from different DOORS modules are imported into DNG with correct attribute type.
3. no need to rely on attribute URI in DOORS, just make sure attribute types in different DOORS modules have the same name

Hope that helped.
Tiffany Pei selected this answer as the correct answer
Comments
Tiffany Pei commented Jul 01 '15, 11:38 p.m.

I have tested with a very small reqif and it worked. For the reqif that I am importing is really big, there are hundreds of attribute types across several modules. It will be very time consuming to do it manually.

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Howard Hsiao (5.5k●1●7) | answered Jul 01 '15, 1:29 a.m.
JAZZ DEVELOPER
Did you follow the following article?
https://jazz.net/library/article/1243
Comments
Tiffany Pei commented Jul 01 '15, 1:30 a.m.

I did. Setting URI seems to have no effect on the outcome of the import.

Howard Hsiao commented Jul 02 '15, 12:50 a.m.
JAZZ DEVELOPER

I have tested with DNG 5.0, and setting attribute URI in DOORS can avoid duplicating attributes in DNG.

This must be a defect in DNG 5.0.2.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.