A Need for Class Operation Diagrams

[kelly_sumrall]

I would like to associate a diagram with a class operation. I am currently using build 766. If there is a way to associate a diagram with a class operation and have all elements be contained by the class operation, I havn't found it. Here is an example of a class with only one operation added.

I was wanting to associate an activity diagram with the operation DisplayMetricGraphs, but was unable to. I can associate a diagram with the class though. But this seems to leave the project looking like my garage. All attributes, operations, diagrams, and diagram entities are at the same level, and intermixed based on sort order. This is more of what I was expecting...

Here, the diagram and its entities are contained in the operation (ignore the sort order, I wasn't paying attention when slicing/dicing the original image). If I don't want to see them, I just collapse the operation node.

I know this has been suggested in the past, atleast a year ago. If this is possible, please tell me how. Also, what are some other organizational techniques you guys use?

[Paolo F Cantoni]

Kelly,

FWIW, the reason you can't do this is because attributes and operations aren't objects (elements) in EA speak.  Only objects (stored in t_Object) can have a Child Diagram.  Right-Click in the browser against different types of things and you'll see what can and can't have a Child Diagram.

HTH,

Paolo

[kelly_sumrall]

OK. What is a workable technique to organize all the class operation activity (and others) diagrams in the project? I am looking for an organization strategy that fits within the limits of the application.

[Paolo F Cantoni]

OK. What is a workable technique to organize all the class operation activity (and others) diagrams in the project? I am looking for an organization strategy that fits within the limits of the application.

Kelly,
I can't answer that, since I don't know what requirements you may have with repect to organisation...

However, I can provide the following observations which may help your decision.  
Once the diagram has been linked, it can be moved, and the linkage will remain.  So you can create a suitable package elsewhere and move the diagram and its contents there.  
The contents of the diagram don't need to be in the same hierarchy as the diagram.  You could thus leave the diagram under the classifier, but move the contents to another package.

HTH,

Paolo