Description

During DNG ReqIF Import, the user shall be able to specify which ReqIF Definition shall be used for import via one of the following options:

• Select an existing ReqIF Definition

  • If the ReqIF contains additional information that identifies which of the existing ReqIF Definitions shall be used (e.g. in TOOL-EXTENSIONS), DNG shall highlight the ReqIF Definition, but still give the user the option to select another ReqIF Definition

• Create new ReqIF Definition

Motivation / Reason

In roundtrips you often exchange the same set of modules. The ability to reuse existing ReqIF Defintions has the following advantages:

• User is able to see:

  • Which modules are new for the exchange (exchange represented by the ReqIF Definition, i.e. "I have not received this module for import before, I should look at it closely")

  • Which modules are missing (i.e. "Normally I receive Module A as part of the exchange (which I can see since it's in the ReqIF Definition), but this time I have not received it - I might want to ask the exporting side about why Module A is missing")

• Everything that belongs to a specific exchange scenario (e.g. "exhange between OEM X (me) and Supplier Y") uses the same ReqIF Definition and thus all exports and imports are tracked in the same ReqIF Definition

• Prevent unnecessary bloat / too many different ReqIF Definitions

  • Currently, user cannot prevent DNG ReqIF Import from automatically creating new ReqIF Definitions in some cases

  • Leads to too many ReqIF Definitions

  • Difficult for user to keep track of all ReqIF Definitions / know which ReqIF Definition is for what

ReqIF Ranking

24

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=116747

Creation date of original RFE:

Aug 3, 2017