Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Michael Lutz

Pages: [1]
1
General Board / Re: Display OCL constraint instead of constraint n
« on: June 30, 2008, 10:47:05 pm »
Now I tried to use the same for visualising a constraint on an association. And that doesn't seem to work. I can attach a note to the association (using "Attach Note or Constraint" in the context menu), but then I cannot select the note link or access its context menu. This seems very strange (and inconsistent).

Is there a trick to do this?

Cheers,
Michael

2
General Board / Re: Display OCL constraint instead of constraint n
« on: June 30, 2008, 10:22:05 pm »
Thanks a lot! That did the trick.  :)

For others having the same question, here's the help topic:

Help Topic: Link a Note to Internal Documentation
(...)

Procedure

To link a Note element to a feature of another design element, follow the steps below:

1. Insert the target element into a diagram.

2. Drag the Note icon from the Common page of the Toolbox onto the diagram, next to the target element.

The Notes dialog displays. Do not type any text, just click on the OK button.

3. Click on the Note Link icon from the Common page of the Toolbox, click on the Note, and drag across to the target element to create the connector.

4. Right-click on the Note Link to display the context menu.

5. Select the Link this Note to an Element Feature menu option. The Link note to element feature dialog displays.

3
General Board / Display OCL constraint instead of constraint name
« on: June 27, 2008, 10:48:51 pm »
When adding an OCL constraint for a class (in the constraint tab), only the name of the constraint is displayed in a class diagram. Is there a way to display the constraint "value" (i.e. the OCL expression) instead?

On a related note, is there a way to connect the "note" representation of a constraint with a constraint defined on a class?

Cheers,
Michael

4
I'm trying to distinguish generalizations from associations in an RTF report. In fact, I would like to include associations but not generalizations. Is there any way to do this, e.g. by including conditions on properties of the connectors? Something like IF Connector.Type = "Association" THEN ...?

Thanks for any ideas on this,
Michael

5
Thanks, Oliver. This works nicely for at least listing the classes shown in the diagram. However, we would also need to list their attributes, operations etc. (everything that I can select in the normal "elements" checkbox). Any idea how I could get EA into doing this for me? (I've already tried copy-pasting the "element" fields into the "diagram" tag in the RTF - but not surprisngly, that didn't work...)

Thanks, Michael

6
I would like to generate a report including all classes in a diagram (i.e. potentially classes from different packages), not only those in one package. Is this possible somehow?

Cheers, Michael

7
I would like my RTF reports to include also attributes and operations that classes inherit from their superclasses (especially if those are from another package). Is it possible to show these features, too?

Cheers, Michael

Pages: [1]