Engineering Requirements Management

 Derived requirements linkage to the parent requirement (import)

Marina Magalnik's profile image
Marina Magalnik posted Wed January 15, 2025 06:49 AM

We have the parent requirements in our DOORS GN DB. Our contractor will receive our requirement and derive them (develop many derived reqs related to the parent Req).

1. Of course, the the parent requirement IDs differ between the Contractor database and the our database in DOORS,  (may be, we need some mapping table for parent IDs? or just to save the parent ID as additional attribute in the Contractor DB?) 

2. When exporting the derived requirements from the Contractor' DB, we need to ensure that we include the parent requirement IDs as they exist in that table.

3. When we import the derived reqs to our DB, how can we associate them to the parent reqs? manually??

Nikolai Stein's profile image
Nikolai Stein IBM Champion posted Fri January 17, 2025 01:57 AM

Hi,

the best way would be if you export your requirements using reqif to your contractor and your contractor links the requirements and then send them back also using reqif. Reqif will take care about all the ID issues as it uses internal ids that are mapped on both sides.

Of course that will have you to setup the new process but I think it is worth it.

How did you do in the past? Csv, excel, doors archives?

Regards,

Nikolai

Kyösti Huhtala's profile image
Kyösti Huhtala posted Mon January 20, 2025 01:28 AM

Reqif would be fine if you share the same database structure with the Contractor. We have used the following

  • include a copy of your Object Identifier in the DOORS module, Excel table, or such you pass to the Contractor
  • require Contractor to include an attribute indicating the parent object's Object Identifier they are referring to
  • use link by attribute to link the "Contractor's objects" to your objects