Suggestions

[RonaldTrivera]

1. I would like to be able to define in communication diagram threaded behaviour as defined in the UML spec by using characters after the sequence number so for example being able to specify to messages with this numbering e.g:
1.1.1a
1.1.1b
This of course could then also be applied to sequence diagrams.

2. When using fragments EA could do more with this now its only a visual item and not bound to methods or any. I would love to see that EA would group the methods to its fragment when you place a fragment so it becomes more bound to the context you are using it in.

3.  Destroy mark in sequence diagram can not be controlled. When you define that a message has a lifecycle of 'new' then EA defines the destroy... I would like to be able to control when an instance gets destroyed or not.

4. Constraints/Tagged values in diagrams. We can define these very nicely but they are not visible in the diagrams. Which i find often mandatory. So for example i would like to be able to show attribute and method constraints in an following manner:
-int i = 0 {self.i<=1000} // attribute

+processDocument(Document d): void  { ... }

this could help in illustrating the semantic of the model in diagrams.

5. Querying the model. There are simple examples of this already in EA. But for example for impact analysis i would like to query the model which elements are connected to an certain usecase or requirement. Possible showing me an treeview or something likewise, so i can see tracebility in an better way than just an two dimensional matrix.


Thanks in advance!

[Hans]

I agree wholeheartedly on your points!

Regards
Hans