Messages

1

Suggestions and Requests / Reverse Integration with DOORS

« on: November 01, 2013, 12:13:35 am »

Are there any plans to automate or facilitate the return trip from Enterprise Architect to DOORS.  The import from DOORS is so seamless that it is a shame we cannot also seamlessly achieve the export of model elements into DOORS modules and specifically the export of traces between the model elements mastered in EA and requirements imported from DOORS.

I believe there is an open standard for the architecture tool / DOORS interface which is used by IBM for their tools??  :-/

2

General Board / Re: xmi import behaviour

« on: November 02, 2013, 01:25:10 am »

Wow - it took circa 20 hours to run the merge and it still deleted the relationships from the A model to the B model.

I tried making a relationship in the reverse direction from B to A and this survived a re-import of A, so we have a workaround at least.  It also works if the direction of the relationship is set as Destination -> Source, so we can have the arrows pointing in the right direction.

Based on these results I'm even more surprised that we have been able (in a different model) to maintain relationships in both direction to requirements imported and frequently refreshed from DOORS.

3

General Board / Re: xmi import behaviour

« on: November 01, 2013, 02:31:01 am »

Cheers,
I can see way you suggested avoiding baseline compare and merge.  This is a relatively small model on a local eap and it looks as though it may be hours before I know if it had the desired effect.

The packages were already completely separate, but the relationships were mainly from elements in the Model A package that was reimported to elements the Model B package.  When the merge is complete I'll run another import trial with the relationships reversed.

Is that what you were suggesting i.e. to stick with the import approach?  Or is there another way to achieve a merge?

Heather

4

General Board / xmi import behaviour

« on: October 31, 2013, 11:59:03 pm »

We have a need to provide a stable architecture baseline to another project team (Project Team B), who will then trace their own project artefacts (Model A) to our artifacts (Model B).  After this, we need to provide that project team with any updates that occur, without disturbing the traces that are in place.

I had thought we would use a simple mechanism of exporting Model A as xmi for import as Model A into the Project Team B EA project, alongside Model B.  Project Team B would then establish traces between Model A and Model B.  When changes occurred in Model A, the whole of Model A would be reimported into the Model A package in the Project Team B EA project.

When I trialled this, I found the re-import perfectly represented the changes that had occurred in the source EA project (additions, updates and deletions of elements and relationships), but destroyed any links between Model A and Model B artefacts.

I was expecting this to be successful because of the way the DOORS integration works, whereby we have established many traces with requirements as source or target that survive successive re-imports of the requirements.

Any suggestions?

5

Bugs and Issues / Out of Memory

« on: May 21, 2013, 08:51:12 pm »

HELP!! I've been working on creating a basic but sizeable MDG Technology with stereotypes, diagram types, toolboxes and tagged value types.  It worked fine on testing in a trial project when I had a short list of diagrams, but since adding more diagrams and toolboxes yesterday I get an EA "Out of memory" error message when I try to create a new diagram.  The first time, it lets me view the diagram type list (which currently contains 26 bespoke diagram types) but fails on creating the blank diagram, subsequently it fails when trying to display the list.
 :-/
I am unaware of any memory management facilities in EA.