MDG Link for DOORS v 3.0 GUIDs

[Roche Pso]

If I import requirements through the link into an EA model a new EAGUID attribute is created in the DOORS module, this means next time that model imports those requirements it knows which requirements are old, which are new and which have changed.

If I import the same requirements into another EA model, the EAGUID attribute in DOORS is overwritten by a new one, breaking the ability for the first model to update requirements and making it think this is a new set of requirements.

Is there any reason for this behaviour rather than using one EAGUID for all models that want to import from that module?

[qwerty]

Export the DOORS import from EA and import it into the "other" model. You should determine who is master and who is slave.

Alternatively write your own DOORS importer. Have done that in the past with a guy scripting the DOORS side. We had quite some requirements the DOORS MDG could not fulfill.

q.