Messages

1

Suggestions and Requests / Specialize associations between realized interface

« on: May 21, 2009, 03:53:33 am »

Although I can specialize associations between classes linked by class generalization, I can't specialize associations between classes/interfaces linked by realization. For example, interfaces ISys and ISysVer have an association between them, class ConcSys realizes ISys, and class ConcSysVer realizes ISysVer. An association drawn between ConcSys and ConcSysVer cannot specialize the relationship between the interfaces.

I can change the type of the realization connectors to generalization, create the specialization, then change the connector type back, but this is definitely a hack. If there is a prohibition of this kind of specialization in the official UML spec, then I would be interested to learn of it- in general, it would seem useful to allow what I seek to model.

2

Suggestions and Requests / Feature request: propagate method to subclasses

« on: March 25, 2008, 01:48:45 am »

(I don't see how to do this without Automation programming, but it seems like a no-brainer feature...)

When I add an abstract method to an interface or class, it must eventually have implementations in inheriting classes. I'd really like to be able to pick one or more such methods (in the abstract class), then obtain a list of inheriting/realizing classes and ensure that they contain concrete implementations/overrides of these methods. I can do this on a subclass-by-subclass basis through Cntrl-Shift-O, and I get the option once when I first establish the realizes/gen-spec relationship, but thereafter it all seems very disconnected. Similarly, if the abstract signature changes, I need to propagate changes to subclasses. But it seems that EA does not know that a method in a subclass is actually an override of a method in a base, so when the base changes the subclass's must change.

If I am missing knowledge of a function already present, please let me know (I know about Shift-Ctrl-O, it just works in the wrong direction). If someone has solved this in Automation already, please respond.

Thank you-
George Spofford

3

Suggestions and Requests / HTML documetation - retain old style?

« on: January 03, 2007, 03:18:46 pm »

I just recently generated HTML documentation using version 6.5 for the first time, and I see a new look to it. It's slick, everything seems to work right, but I find that it doesn't work well for me, and I'm wondering if there's a way to generate the older style.

(If this is a question of HTML and CSS hacking, I suppose I can roll up my sleeves, but I'll have a learning curve.)

The old HTML doc was really handy for putting all the information about a class in one place. At-a-glance acccess to everything was very easy- nothing was hidden. When I had to communicate a model, it was much easier to walk through the HTML than the EA diagrams because information was not hidden behind dialogs and traversals. The pages could be large, but they were well laid out- they made very good use of space. In the new one, there's a lot of whitespace that doesn't seem to serve a purpose, and just scanning the notes for parameters to methods (to pick one use) requires a lot of tree-node expansion.

Any chance of getting an option to produce the classic, flatter form?

Thanks for your consideration here!

4

General Board / Ditto (Re: From Class model to Data model?)

« on: April 15, 2009, 05:39:03 am »

I have the same question: This seems like a use for Automation or MDG, but I haven't yet seen any object-relational mapping capability described anywhere I can find.

The "DDL" MDA transform is a beginning, but the whole mapping of multiple classes to a single table (attributes, class discriminants, etc.) needs to be much more powerful.

5

Uml Process / typedef stereotype, esp. nested within class scope

« on: August 15, 2005, 06:59:10 pm »

I find after importing quite a bit of C++ code that although the C++ parser is quite good so far, it does not create any classes for typedefs.

Even knowing that a particular class/struct/type is the result of a typedef is helpful; I end up manually creating these classes otherwise.  A lot of these typedefs are simply collection classes scoped to within the container of the collection.

(In general, the C++ parser seems quite good, and I hope that you continue to provide rich support for C++)

6

Automation Interface, Add-Ins and Tools / Re: Moving attributes/methods from class to class

« on: January 09, 2006, 08:44:12 pm »

Thanks for the fast reply.  I wasn't going to make it any easier than that.

7

Automation Interface, Add-Ins and Tools / Moving attributes/methods from class to class

« on: January 09, 2006, 07:43:09 am »

I'm interested in the capability to move one or more attributes/methods from one class to another. I understand EA is not geared to "refactoring", but as an editing capability this seems to be helpful. When code has been generated for the classes I could move the text and synchronize, but I'm interested in being able to do this prior to code being generated.

Is this a problem others have solved? Looks like not too hard, not trivial exercise from the documentation