It's all about the answers!

Ask a question

DOORS 9.7 to DNG 7.0.2 migration - how to create a DNG artifact type given D9 object attribute


Dariusz Walter (111) | asked Apr 30, 12:17 a.m.
edited Apr 30, 12:19 a.m.

Hi,


Given available IBM tools, please advise how to configure the existing IBM migration process such that a DNG artifact of a desired type is created based on a given D9 object attribute.

For example,
    If the original D9 object has an attribute isReq and the value of isReq is set to true, 
    Then 
      the imported DNG artifact is to be of type _Req
    Otherwise
      the imported DNG artifact is to be of type _TBD

One answer



permanent link
Davyd Norris (2.4k217) | answered Apr 30, 12:49 a.m.
The first thing you want to do is run the Migration Metrics Tool and very carefully examine the results. One of the things that's absolutely crucial for a good migration is to do what the Knowledge Center calls "Harmonising the Type System". 

What this basically means is that you need to REALLY carefully examine the attributes and their types and make sure that attributes with the same name have the exact same data type. This means things like Text vs String need to be tidied up, and enumerations need to be the exact same spelling, values, order and content (no missing values). 

This is by far the most tedious part but, if you do it carefully, will get you a really clean migration. See this section:

Once this is done, create a new single valued enumerated attribute at both Module and Object level and make it the same across all modules. The enumeration values of this attribute must be the exact artifact names in your DNG project area. Then set the value of this attribute for both the DOORS module(s) you're migrating and every object inside them, choosing the artifact type you want the row to become. Then create and export your migration package.

Finally, during the migration package Import process, the wizard will have a section where you can type the attribute name you used for the artifact types at both Module and Object level.

Do a trial migration in a test project area first and look for renamed Artefacts, Attributes and Data Types - these are the ones that haven't been correctly 'harmonised', so go back to your DOORS project and fix them up



Comments
Dariusz Walter commented May 22, 3:30 a.m.

Thanks Davyd, this is useful.


My experiments to date led me to searching for a workflow with least pain. At the moment that is:
  1. do a "dirty" migration from D9 to DN "dirty" component, 
  2. export to excel for a clean up, 
  3. import from excel to a "clean" DN component
Fundamentally, doing clean up work in excel seems like the least painful path forward atm.


Davyd Norris commented May 22, 8:50 p.m.
It depends on what your project looks like - there's quite a bit that can't be exported to Excel.

In the end, if you are migrating and never looking back, then whatever gets you to a good end state is the correct solution - sometimes you may want a shower and a stiff whisky afterwards but, for most of your users, they have no idea the pain you went through

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.