[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 64147] steretype enhancements for uml objects
From:       Antonio <freenix () libero ! it>
Date:       2007-08-31 23:22:20
Message-ID: 20070831232220.22318.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=64147         




------- Additional Comments From freenix libero it  2007-09-01 01:22 -------
I spent a bit of time looking howto use in a use case diagram the <<extend>> and \
<<include>> dependencies between use cases. What I found (maybe wrong) is that one \
need to write <<include>> and <<extend>> as labels on dependencies. To me this is not \
                the best way it could be done for same reasons:
- one cannot use the dropdown selection list for stereotypes and has to manually \
                write them every times (or copy&paste)
- one has to manually write the guillemets using for example KCharSelect or using \
                double < and >
- (Most important reason) extend and include are stereotypes so I think capture it in \
the model as stereotypes is the right way to do it. So, concluding, having umbrello \
supporting stereotypes for all uml objects is also useful for use cases. Should I \
submit a new bug [whish] for the dropdown stereotypes selection list on use case \
dependencies or is this comment sufficient?


[prev in list] [next in list] [prev in thread] [next in thread]