OK, now I've got it.
I used to do this a lot, a few years ago. I ended up writing my own engine to handle a lot of it. Frankly, that was too much work, considering that the results were not great.
However, things have improved.
First, a 'quick and dirty' solution that might be enough.
Just use a class model. Using the example in Figure 7.30, you would start with a class that you would name Window. Add another class, and name it Area. Give the Area class a stereotype of «attribute». Now just use an Association connector to join them. If you need to, set the direction of the connector, or set the default for connectors using the Tools | Options | Links dialog. You can also draw the connector and set the direction with the quick linker. [But note that the F3 shortcut (repeat last connector) will give you an Association, but use the default direction setting from the Options dialog.]
So far so good. But you are still left with a few problems. In no particular order, here are some examples. How do you gracefully handle the stereotype? [It is not one of the set provided with EA, meaning you have to type - or mistype - it each time. It is also displayed on diagrams, which you might not want.] How do you prevent display of the «attribute» stereotype on diagrams? And how do you get rid of the annoying compartment line in «attribute» (and perhaps Class) elements?
These are all problems. It would be great if we could handle them all, but at present we're forced to make some trade-offs. Here's some, but please take a look at the bottom of this message for how to submit feature requests.
For the stereotype, you can display it in the drop-down by adding it with the (default) Stereotypes tab of the Settings | UML dialog. Make sure to tell EA which element types it applies to. And make sure to explicitly save the stereotype (this dialog can be picky about saving).
The other two problems can be solved as well, at least for the stereotyped classes (not for the 'normal' class, like the Window in diagram 7.30). You can create a simple shape script, which will display classes with the «attribute» stereotype as a simple rectangle, and add the name near the top, centered, and (if you wish) in bold face. Not bad, but you'll have to maintain the shape script if you want more detail. [Not a huge penalty, since UML offers no additional notation. You'd have to solve this problem anyway if you wanted a custom extension.]
You are still left with the annoying line across the Window class. Nothing you can do about this one, Except...
Another trade-off. You can do the whole diagram as an Object model. Remember that this breaks the semantics of the model; it only addresses the display. Now you don't have the lines, but object names are underlined. Not bad for display though. Classes still have the additional partition, but you could use objects for them too. You'll have to revisit the whole stereotyping issue, unless you only use object elements for attributes, or don't mind the stereotype displaying on the diagram.
For the best result, you'd want to go with the class model, but not have the stereotype displayed, nor have the partition. For these two features, EA would need to be enhanced. Make a separate feature request for each.
HTH, David
Now the feature request part...
If we don't tell Sparx what we need out here, it is hard for them to recognize and prioritize new features. So make the requests! Here's a best practice we in the user community have been using.
Begin by starting a new thread in the Suggestions and Requests section of the forum. Give the thread a short but meaningful title; not too long or overly specific, that's what you'll explain in your initial posting to the thread. Be as specific as you can. Remember that other users, and Sparx, will likely chime in, and may improve on the idea. Take a moment to select and copy the URL of the thread from your browser's address bar - you'll see why in a moment.
Now submit a request by clicking - or shift-clicking, or control-clicking - the Feature Request link below the Support link at the bottom of any forum page. Quote the title of your thread, and paste in the URL. [That's why you kept the title short, grabbed the URL, and considered the shift or control clicks. Some browser settings (including some very common IE ones) will clear your feature request form if you use go back to get the title or URL, leaving you to retype your feature request.] Submit the request as usual.
Check your suggestion thread from time to time to see if there's any useful dialog, or if someone has a solution or a workaround that helps in your specific situation. You can also use the Notification link in the forum top menu - not the page top, the one just above the forum text - to email you when there is a posting to your thread.
Finally, if you hear back from Sparx, please post it to the forum, so the rest of us know what's happening.
