Hi Niloofar,

(note to all: I'm having my CSCI 578 students at USC this semester look at OODT 
in a number of their assignments, see [1])

As far as discussing the below, please provide some context for your 
questions/discussion on this mailing lists. Remember, not everyone here is a 
student in CSCI 578, and currently working on assignment #2 :)

Answers below:

> 1) I wanted to ask you whether you are able to identify different 
> relationships (inheritance, method call, ...) with CDA? Do I need to install 
> any plug-ins? Currently it only shows one kind of arrow to depict 
> dependencies. 

CDA is a class dependency analysis tool that the class is using to do static 
analysis on OODT. The tool should provide you with visualization of the 
relationships you cite above w/o any additional plugins. If it's only showing 1 
arrow, I think there is an issue.

> 
> 2) I gave the CDA the root directory of the downloaded OODT code and it lists 
> a huge number of packages and it becomes very difficult to search for the 
> class and package names. Do you have the same problem?

This is a side effect of the size of the OODT code base. Hard to get around it 
:(

> 
> 3) It seems that now that I have loaded all packages into CDA, it doesn't 
> show the some dependency graphs anymore. Should I restrict the packages that 
> I import?

I think you may want to restrict your focus to your components that you are 
working on as part of your assignment.

Cheers,
Chris

[1] http://sunset.usc.edu/classes/cs578_2011b/

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to