DEALING WITH THE SIZE OF EA PROJECTS

[GMFMAS]

Hello EA guru's;

I am working with a company involved on a big project and are using EA with Oracle repository and thousand of elements:

2.000 requirements
more than 500 use cases
+2.000 clases
+2.000 sequence objects
1500 diagrams
near 900 packages.

We have just finished the Analysis phase and we start now the design so the growth of the project will very very sginificative.

the team thought to divide the project in two smaller ones one with the analysis and other with the design and stablish very rigid procedures to upgrade through XMI interchange any possible change in one or another and maintain the integrity on these twoi different project.

I think that this is a big problem because the end customer is very formal and requires an enormous level of traceability with the artifacts and that way we would lost part of this information. Also, I suppose that the overload of extra work could be very dangerous when the project reach the most critics peaks.

Have any of you experienced with such kind of project with the Oracle Repository kowing that probably the size I put before will duplicate when design was finished?

I would appreciate any opinion or advise respect this issue

Regards to everybody