NOTICE: Our Community is moving. Get more information.
Why are some requirements created with Import Factory being imported in the wrong hierarchy order?
NOTE: Import Factory for CaliberRM is not an
officially supported Borland utility. This article is
provided to help guide you through a common problem observed with
Requirements created with Import Factory are being imported out
of order. The requirements are defined in Excel as a .csv
file and then converted into an importable text file by Import
Factory. This text file is then imported into CaliberRM using
One of the most common causes of requirements being imported out
of order is due to a problem with the numbering scheme and sequence
of the defined hierarchy. For example, Requirement number 48
is being inserted after requirement 18 and before 19.
The following provides an example use case on how this would happen
and what to look for to resolve this.
In the requirements.txt file, all of the requirements are in the
correct order (numbers 1-50). However, the hierarchy on
requirement 48 is incorrect.
Requirement #18 has a Hierarchy level
Requirement #19 has a Hierarchy level of "1.6.2"
Requirement #47 has a Hierarchy level of "220.127.116.11"
Requirement #48 has a Hierarchy level of "1.6.1"
Requirement #49 has a Hierarchy level of "18.104.22.168"
As this example shows, Requirement 48 has the same hierarchy level
as Requirement 18 (both 1.6.1), hence why it would be inserted out
of order on the Import.
But looking a bit further into the hierarchy numbering sequence, it
appears that Requirement 48 should actually be 1.6.10, not
1.6.1. By changing the 1 to a 10 for this requirement, it
will be imported correctly with RMImport.
Additional Note: It is possible for this
to occur with RM Export / RM Import if the requirements.txt file is
modified. Borland does not support modifiying the
requirements.txt file that is created with RM Export.