Messages

1

Suggestions and Requests / Re: Suppressing New Links On Class Diagrams

« on: October 05, 2003, 07:59:44 pm »

Yes, I found this to be an issue as well.  I had a set of classes on one diagram, then via a different diagram flushed out the class.  When I went back to the first diagram all the new relationships I added on the second diagram showed up on the first diagram.  I had to go and delete all of the new relationship lines from the first diagram manually.  

I seem to remember the inverse functionality in Rose (i.e. links in the diagram only showed up when you dropped a class to the page, but once a class was on the page you had to manually add those links to the diagram even though you had already added them via a different diagram).  

It would be even cooler if you could select what links were displayed for a class on a per diagram basis (e.g. have a "Displayed Links" option that allowed you to select which links for a specified class should be shown in a specific diagram.  

Then, if you wanted to display links for a class in one diagram that you had added to that class in another diagram, you could just go to the diagram, right click context menu select the links that you wanted to be displayed.

-Phil

2

Suggestions and Requests / Relationship Matrix Filtering

« on: October 05, 2003, 08:04:08 pm »

It would be nice if there were an option in the Relationship Matrix to auto filter on elements that had a realtionship so you could use it more easily for dependency analysis.

-Phil

3

General Board / Issues Importing C# Source (Generalization Links)

« on: October 05, 2003, 07:12:46 pm »

In general I am very impressed with the job EA does importing from sources, however I am encoutering issues in a couple places.  Both of these issues relate to generalization relationship links not being created when C# source is imported (via import source directory).

I'm importing approx. 100+ packages into the model and without these generalization links being created I'm experiencing two main problems:
1) The relationship matrix wont have the info it needs to show the relationships.
2) The inherited methods for collaboration/sequence diagrams are not available in the methods drop down.

I can manually add the generalization link when doing the sequence/collaboration diagrams (since I know what classes I'm dealing with).  However with the relationship matrix this is more of an issue since I was hoping to use that to map out the dependencies of some packages we were thinking of moving around.

I haven't had a chance to create an isolated repro case but I thought I'd run it by you guys in case they're already known issues.

Thanks,
Phil

========================================
Case #1
Importing a file that contains a class that inherits from a base class in a different namespace (base class located in seperate file).  

Note the use of [System.Serializable()] here instead of [Serializable].  This was one thing that stood out as being different.

-------------
namespace Test.P1.P2.P3
{
   
   
   /// <summary>
   ///     omitted
   /// </summary>
   [System.Serializable()]
   public class MyClass : Test.P4.P5.MyBaseClass
   {
      ...
   }

Expected Behavior:
Generalization link is created

Actual Behavior:
No generalization link is created, but the name of the base class still appears in the upper right corner of the class in the diagram.

========================================
Case #2
Importing a file that contains a class that inherits from a base class in a different namespace (base class located in the *same* file as the subclass).  

---------------------
using System;
using System.Reflection;
using System.Collections;

namespace Test.P8.P9
{
   /// <summary>Autogenerated on 11:38:31 AM</summary>
   public abstract class MyBaseClass
   {
        ...
   }  
}
namespace Test.P6.P7
{
   /// <summary>Autogenerated on 11:38:31 AM</summary>
   public abstract class MyClass : Test.P8.P9.MyBaseClass
   {
        ...
   }  
}

Expected Behavior:
Generalization link is created

Actual Behavior:
No generalization link is created, but the name of the base class still appears in the upper right corner of the class in the diagram.