Engineering

Hello,

I want to import ReqIF files. Is it possible to import them to a specific folder rather than the root or a project?

G. Azar 

Hello,

I want to import ReqIF files. Is it possible to import them to a specific folder rather than the root or a project?

G. Azar 

Hey John,

I'm trying to import my Polarion data into IBM Rational DOORS Next Generation (DNG) using the ReqIF format, but the system is not supporting it properly and the traceability information is missing. Can you help me resolve this issue? and second issue is it will create duplicate attributes

Best Regards

Rajashekar

Hello,

I want to import ReqIF files. Is it possible to import them to a specific folder rather than the root or a project?

G. Azar 

Using ReqIF is really tricky. There are lots of reasons why things won't work or work but not as you might expect. I'd suggest getting in touch with support.

However, there are some useful places to start. For example this one (also from 2018 but I think mostly still accurate:

Configuration management: Best practices for collaborating with ReqIF between Rational DOORS Next Generation instances - Library: Articles - Jazz Community Site

And the problem is also described here:

Importing artifacts from ReqIF files to a requirements project or component - IBM Documentation

One area that caught me out that looks like it is catching you is type management. A lot of other products don't have the type management that DOORS Next has. When something is imported and DOORS Next is not absolutely certain the type matches it creates a new type (hence the DNG-Renamed...) types. It is best if possible to have the type defined in DOORS before you do an import with all the appropriate Attributes etc already present.

An example of how this can go wrong...

In Doors Next a Requirement can have an Attribute with a type that can be defined with an enumerated list of values. That Requirement definition can be reused in several modules. In the source system you are importing from it might be that the requirement type is defined inside each module or equivalent.

In the case I'm thinking of in one module the order of the enumerated values was different from the other order in another module. As far as Doors was concerned it thought it safer to assume these must be different definitions of the requirement type. So it ends up creating two (one with the DNG-Renamed...). Re imports tend to just make this worse. If you are using a Requirement type that appears to match the built-in requirement types in Doors Next, then it is rare that your import would match the built in definition so even your first import will result in DNG-Renamed... cases.

There a few things that can help too. One is ReqIF definitions. You can find them in the Project Properties of the Doors Next Project you are importing into.

Good luck,

Mark

Hey John,

I'm trying to import my Polarion data into IBM Rational DOORS Next Generation (DNG) using the ReqIF format, but the system is not supporting it properly and the traceability information is missing. Can you help me resolve this issue? and second issue is it will create duplicate attributes

Best Regards

Rajashekar

Hello,

I want to import ReqIF files. Is it possible to import them to a specific folder rather than the root or a project?

G. Azar 

Using ReqIF is really tricky. There are lots of reasons why things won't work or work but not as you might expect. I'd suggest getting in touch with support.

However, there are some useful places to start. For example this one (also from 2018 but I think mostly still accurate:

Configuration management: Best practices for collaborating with ReqIF between Rational DOORS Next Generation instances - Library: Articles - Jazz Community Site

And the problem is also described here:

Importing artifacts from ReqIF files to a requirements project or component - IBM Documentation

One area that caught me out that looks like it is catching you is type management. A lot of other products don't have the type management that DOORS Next has. When something is imported and DOORS Next is not absolutely certain the type matches it creates a new type (hence the DNG-Renamed...) types. It is best if possible to have the type defined in DOORS before you do an import with all the appropriate Attributes etc already present.

An example of how this can go wrong...

In Doors Next a Requirement can have an Attribute with a type that can be defined with an enumerated list of values. That Requirement definition can be reused in several modules. In the source system you are importing from it might be that the requirement type is defined inside each module or equivalent.

In the case I'm thinking of in one module the order of the enumerated values was different from the other order in another module. As far as Doors was concerned it thought it safer to assume these must be different definitions of the requirement type. So it ends up creating two (one with the DNG-Renamed...). Re imports tend to just make this worse. If you are using a Requirement type that appears to match the built-in requirement types in Doors Next, then it is rare that your import would match the built in definition so even your first import will result in DNG-Renamed... cases.

There a few things that can help too. One is ReqIF definitions. You can find them in the Project Properties of the Doors Next Project you are importing into.

Good luck,

Mark

Hey John,

I'm trying to import my Polarion data into IBM Rational DOORS Next Generation (DNG) using the ReqIF format, but the system is not supporting it properly and the traceability information is missing. Can you help me resolve this issue? and second issue is it will create duplicate attributes

Best Regards

Rajashekar

Hello,

I want to import ReqIF files. Is it possible to import them to a specific folder rather than the root or a project?

G. Azar