Description

New Import option for DNG Advanced ReqIF Import: Enable or disable “Allow creation or modification of ReqIF IDs in DNG”.

• When the option is enabled, DNG Advanced ReqIF Import shall be able to create and modify ReqIF IDs in DNG, i.e.:

  • Create / import a new ReqIF ID for a newly imported element (i.e. an element that does not yet have a ReqIF ID in DNG) and store the ReqIF ID in DNG

  • Create / import a new ReqIF ID for an already existing element (i.e. an element that may already have ReqIF IDs in DNG)

  • Change the Preferred ReqIF ID of an element

  • Any other modification of the ReqIF IDs stored in DNG

• When the option is disabled, DNG Advanced ReqIF Import shall not be able to create and modify ReqIF IDs in DNG (see above for details)

If the option is disabled and importing an element in the ReqIF would require the creation or modification of ReqIF IDs, that element in the ReqIF shall not be imported.

Example:

• The user has disabled “Allow creation or modification of ReqIF IDs”

• The ReqIF contains the new artifact attribute “Attr” (meaning that the attribute does not yet exist in DNG)

• The user has selected the artifact attribute “Attr” for import

• Expected behavior: DNG Advanced ReqIF Import does not import the artifact attribute “Attr”, as importing it would require creation or modification of ReqIF IDs in DNG (i.e. import ReqIF ID of “Attr” in ReqIF and store it in DNG).

DNG shall also make this DNG Advanced ReqIF Import option available via the DNG OSLC API. The corresponding DNG OSLC API shall be public and documented.

Motivation / Reason

The reason for a ReqIF roundtrip exchange is that the other side is supposed to do some changes to the data.

Depending on the use case different sides of the exchange will not want to import certain changes to the data, even if those changes are present in the ReqIF (either because the other side of the exchange erroneously did these changes or the data inside the ReqIF was changed due to the import / export tools being used).

One prominent example is the exchange of requirements between an OEM and a Supplier. The OEM will never want to import any new artifacts, artifact attributes, data types, etc., or any ReqIF IDs for new or existing elements, as the Supplier is not supposed to change any of these aspects of the data and is not supposed to introduce any new ReqIF IDs to the exchange.

To prevent the import of unwanted data / unwanted changes to DNG by the import, the user must be able to select what type of data in the ReqIF shall be imported and which one shall not be imported. In other words, the user must be able to select what kind of changes the DNG Advanced ReqIF Import is allowed to do.

ReqIF Ranking

11

Idea History

This idea has been copied from the following RFE:

https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=138579

Creation date of original RFE:

Nov 11, 2020 ​​​​​​​