DOORS NG REQIF import without using auto created types
I am looking at using REQIF to import a number of requirements from DOORS 9.6 to DOORS NG 5.0.2. When I generate the REQIF file and import it it will create a new Type for each module and define each object in it as a heading or Feature.
Is there a way to define how it imports the module? We have a number of types defined which meet our company schema and we would like these to be used. At the moment we have to import and then manually change each of the types to meet our schema (which we use for document generation)
eg I would like DOORS 9.6 Module X to be of type Schema_Module (with its appropriate attributes)
and DOORS 9.6 heading to be set to type Schema_Heading (with its appropraite attributes)
and DOORS 9.6 Object Text to be set to type Schema_Requirement (with its appropriate attributes)
Any assistance appreciated
Thanks
Peter
Is there a way to define how it imports the module? We have a number of types defined which meet our company schema and we would like these to be used. At the moment we have to import and then manually change each of the types to meet our schema (which we use for document generation)
eg I would like DOORS 9.6 Module X to be of type Schema_Module (with its appropriate attributes)
and DOORS 9.6 heading to be set to type Schema_Heading (with its appropraite attributes)
and DOORS 9.6 Object Text to be set to type Schema_Requirement (with its appropriate attributes)
Any assistance appreciated
Thanks
Peter
One answer
If you set a unique URI for each type in DOORS 9 (and use the same URI for the corresponding type in DOORS NG) then DOORS NG will not create new types when you import.
Comments
Donald Nong
Jan 13 '15, 11:58 p.m.Peter Morgenthaler
Jan 14 '15, 12:53 a.m.