Hi ,
is it possible to map a Doors import to non Requirements model?
Background:
We have a Doors dokument with a Harm collection and want to import in a Harm collection.
Thanks
Hi Sven,
this is currently not supported, though its something we started to look into. The technical base of our integrations is rather flexible
but never was offered for other things than requirements/goals. We saw more and more use cases like yours recently (e.g. also Safety Mechanisms, etc)
so we want to solve that in a generic way (would then work for any integration).
I see some difficulty more in the user interaction, for example, currently selecting the "Requirements Package" and opening the "Import" menu
is rather clear, the user wants to import requirements, but how to express that he wants to import a collections of mechanism or even hazards/harms
instead? Ideas are welcome here.
Jan
Hi Jan,
is it possible to map DOORs Requirements directly to Goals in Medini?
(e.g. via mapping file)
Sven
I think for DOORS classic that currently indeed not possible. The importer is somehow special and different than the others: imported requirements are read-only etc.
Our plan is to give this "special handling" up when we migrate to sysml2 requirements latest.
Happy Working