"Alberto Fossati [ND Solutions]" wrote:
> [snip] I'll be working for a very large
> distribuited project that I estimate will have about 18.000 methods... would
> I look for dependancy by hand?
> [snip]... could lead to a disaster.
It sounds to me as if "big sequence diagram" is not a good description
of your problem.
I don't know enough yet, but it also sounds to me as if your problem
should be decomposable in at least two ways.
First, you need to solve the layering problem (which 3-tiered
architecture are you referring to?) Second, you need to solve the size
problem (2000-3000 nontrivial classes?) Both of these relate to
traceability and dependency, but they are not the same problem.
Using packages and use case diagrams, you should be able to layer the
use cases.
Reducing the size problem depends on things that I don't know. Are all
of your distributed nodes identical?
What exactly do you mean by "dependency"? Could you solve your problem
via the Component view?
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
