I'm afraid the bad news is that tools like Rose don't help much when it
comes to finding package or class dependancies. It's perfectly feasible to
track dependant types that are used as either method arguments or as return
values, but if you are referencing types inside method bodies only then you
need to model their internal processes, too (perhaps using activity
diagrams). It's a side effect of "stateless" distributed systems that a lot
of work goes on inside the method body which the signature doesn't even hint
at.

Constraints on classes (invariants) and methods (pre and post-conditions)
might reveal dependancies that the interfaces don't reveal, as they will
often reference the state of external objects. Stereotypes for methods might
also be a way to capture implementation details of methods (eg, <<SQL
Update>> might show that your method contains references to ADO or java.sql
types).

As always, the only safe way to ensure all dependancies are reported is to
create a complete executable model!

Good luck

Jason Gorman
http://www.xml-objects.com

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Eric D. Tarkington
Sent: 12 December 2000 06:14
To: ROSE_FORUM
Subject: (ROSE) Big System Traceability



"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
*
*************************************************************************


************************************************************************
* 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
*
*************************************************************************

Reply via email to