Description
New Import option for DNG Advanced ReqIF Import: Enable or disable “Allow Module Name modification”.
When the option is enabled, DNG Advanced ReqIF Import shall be able to modify the name of modules
When the option is disabled, DNG Advanced ReqIF Import shall not be able to modify the name of modules
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 changes to the name of modules, as the OEM wants to keep their module name even if the Supplier has changed the module name on their side. Additionally, the Supplier may also not want to import any changes to the name of modules.
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 type 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.
Both sides of the exchange may want to use their own name for each module and would not want to be "forced" by DNG ReqIF Import to keep the module names the same.
Example:
OEM "SampleOEM" has a module called "Specification" and exports it to Supplier
Supplier imports module as "Specification_SampleOEM" (e.g. because the Supplier has imported multiple modules called "Specification" from different OEMs and wants to differentiate the modules)
Both OEM and Supplier do not want their "custom" module name to be overwritten by import
This RFE is especially critical if the ReqIF file to be imported does not have a Module name specified via the attribute ReqIF.Name, but perhaps via LONG-NAME. Such a ReqIF is still valid according to the ReqIF Standard.
If a ReqIF file has the module name in the attribute ReqIF.Name, this attribute can be unselected for import in the import GUI. This prevents DNG ReqIF Import from changing the name of the module.
If a ReqIF file does not have the module name in the attribute ReqIF.Name, but has the module name in LONG-NAME, the user cannot unselect ReqIF.Name (because it is not in the ReqIF) nor LONG-NAME (because unselecting it is not a feature of DNG ReqIF Import) and thus cannot prevent DNG ReqIF Import from changing the name of the module. In other words, using the current DNG ReqIF Import behavior, the user has no option to prevent import changing the name of their module.
ReqIF Ranking
13
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=139892
Creation date of original RFE:
Mar 4, 2021
This RFE is derived from the following PMRs:
https://www.ibm.com/mysupport/s/case/5003p00002UuuQtAAJ (TS004815690)
https://www.ibm.com/mysupport/s/case/5003p00002UxCyFAAV (TS005065695)