Scalability in EA

[Felipe_Menezes]

Is anyone facing scalability issues in Enterprise Architect? Does anyone know how scalable it is? (If it has a limit of diagrams, classes, etc.)

Thanks,

Felipe

[PhilR]

We have just completed a project with the following vital statistics (as taken from the project statistics screen in EA):

231 packages
988 objects
792 connections
218 diagrams
1252 objects in diagrams
146 use cases
134 classes
219 objects
80 requirements
131 activities
1460 attributes

There were three of use working on the project and we used the replication feature.  We had a couple of scares about lost information but decided in the end that they were due to "human error" rather than problems with EA.

I have used a stack of CASE tools over the years and found EA to be one of the least obtrusive.  We went straight from EA to client documentation with the help of a MS Word clean up macro.  We did suffer from persistent diagram layout and clipping problems that detracted form the final presentation.  If EA has any weak areas it would seem to be in the diagramming area!

However as a comparison, I recently had a much more expensive "floral" tool scramble all my diagrams which cost me a heap of time to lay them out again!

Sparxsystems have mentioned larger projects on this board.

Hope this helps,
Phil.

[mkroumer]

I'm involved in a project that have been using EA as the primary modelling tool. It has been used for everything, except forward code engineering and testing/maintenance. The MS Access file size (after compacting) is around 19MB. We have around 20 EA users, 5-7 were working on the model simultaneously. Entire project analysis & design documentation had been generated from EA, with some 'compelmentary' clean up. From project stats: total packages=1538, total elements=12692, total connections=11845, total diagrams=910.