Migration of classic DOORS migration to DOORS NG and possibly Quality Manager
Good day,
There are a set of classic DOORS projects that need to be migrated into DOORS NG. My impression, from this video, is that Artifact Types and Artifact Attributes do NOT need to be created in DOORS NG ahead of time.
If the Artifact Types and Artifact Attributes are created in DOORS NG ahead of time, does the migration overwrite them?
There is also some data that would be something that really should be in Quality Manager. Is it better to migrated everything into DOORS NG first, and then get the testing data moved from DOORS NG into Quality Manager?
Are there any other pitfalls to prepare against before migration? At this time, I am not sure how complex the data is in classic DOORS.
Sincerely,
Mary
Accepted answer
Hi Mary,
You can use either ReqIF or the Data Migration Wizard to bring data into DNG from DOORS Classic.
If have done both and found that the Migration Wizard is by far the better option.
Don't create any of the artifact types or attributes. Let the Wizard create everything.
I found that it will do clever stuff like synchronise duplicate attributes defined in multiple Classic modules into a single attribute in the target DNG project without you having to assign matching URL ID values to the Classic AttrDefs (which you would have to do if you tried using ReqIF)
You can also map artifact types and module types using the Migration Wizard but not using ReqIF.
Here are some notes I took comparing the 2 methods when I was doing this.
You won't be able to use either method to bring test data from DOORS Classic into RQM. I think you might have to resort to an XLSX transfer method for the test data.