Analysis -> Design

[gluzm]

Hi,

how to solve this problem.

First I draw the analysis diagrams, (to remember the clear system) then I wish to draw the design diagrams, where are some analysis elements reduced and are some new implementation specific elements.

First I come to the Idea, to use for analysis and design projects two files.

Then i found is better to have all in one project file each in separate package, but there is a lot of elements handling to do this, and the performance of EA is decrased.

What is the most used Idea?

Thank's
Jan Hornych

[JEff Russell]

Using one file is best.
JEff

[Fintan]

First I draw the analysis diagrams, (to remember the clear system) then I wish to draw the design diagrams, where are some analysis elements reduced and are some new implementation specific elements.

First I come to the Idea, to use for analysis and design projects two files.

Hi Jan,

Normally Analysis diagrams are temporary steps towards defining the Design diagrams.  As such, once the analysis diagrams are completed and design is begun the original Analysis diagrams are modified to show the Design.  Of course your Analysis diagrams are lost.  Is there a reason for you to keep the Analysis diagrams?  Could you keep a hard copy of the Analysis diagrams on file?

If you must keep the Analysis diagrams, I would put a copy of the Analysis diagrams in a new package and modify the Analysis diagrams as per the above process to create my Design diagrams.  This will much less of a workload on you trying to keep diagrams in synch, and should help the EA performance.

Regards,

Fintan

[CJ]

G'day folks,

Just to add a bit to Jeff's post...

If the project is big enough, I think it's worth keeping your analysis work around.  Traceability from your design back to your analysis work can be useful.

I'm a real pack rat.  I figure, if it isn't taking any room and isn't creating any confusion, keep it.

I guess the answer boils down to the usual:  "it depends..."

[mbc]

I would definitely always keep my analysis model. I keep all my models (Use Case Model, Analysis Model, Design Model) in their own package in the same EA project.
I am a follower of iterative design, which means that my development flow goes: Requirements (use cases), Analysis, Design, Implementation (coding), Test, Requirements, Analysis, .... etc.
For that reason, the Analysis Model needs to stay.
However, at later design stages, only keep your Analysis Model updated if you believe that is of some value to you. But even if it is out of date, by all means, keep it!

Mikkel

[gluzm]

Hi,

the reason to keep my design model, is that it describes the pure Bussines tier. The next design modifications depreciate the pure model.
The conlusions of your responses:

All of you have analysis model.. hura

*- some of you redo it to the design model (the analysis is lost) good EA performance

* - some store it in new file (analysis model is not lost, EA performance is good, but there is need of good file versioning, and sharing of the work)

* - the others store each model type in separate package (analysis is not lost, code sharing is easz, but EA performance is very bad, this is usable only for small projects, the work is more package and items sorting then analysis)

All this I know before I posted this question. But what is the best way?

Thank's
Jan