I've played around with messages in the sequence diagram, and i find it puzzling.
If a have two classes that are related (for example a business layer class that uses the data access layer class to save some data)
ClassDAL
-------
-------
Save()
Read()
ClassBLL
------
-DAL:ClassDAL
------
Save_DAL()
In the sequence diagram, when i create both of them to represent the sequence, the message i choose then BLL calls DAL, should be the ones from DAL (since i am "calling them"), and not the ones from BLL
This is how it works right now:
|ClassBLL| |ClassDAL|
| |
| Save_DAL() |
|||--------------------->|||
| |
x x
This is how (as far as i know) should be:
|ClassBLL| |ClassDAL|
| |
| Save() |
|||--------------------->|||
| |
x x
A workaround is this (with current implementation):
How do I draw a "Destroy message" where an arrow from 1 lifeline leads to an 'X' in another lifeline?
(e.g. http://www.umlgraph.org/doc/uml-182.html)
I've tried using:
i) The "Destroy Action", but that only lets me place a 'X' without the arrow
ii) The "Call Action", where I changed Properties -> Message -> Type to "Destroy", but it still looks like a normal call. Also, SIM won't let me attach that arrow to the 'X'.
First of all, thank you for this software, i am using it for my thesis and i am seriously enjoying it! You are nothing short of a genious here.
I've couldn't find a way to pull actions from the classes's medthods i am using. That means that if the action (method) ever changes, i have to manually go and changeit in every other model i used it.
I'm working on a newest translation for Version 5.06(chinese simplified).
Is there any tool to help translate?
(already work for this for a couple of days,it's seems that all Strings in the resx file,but many repeated words,so just done 2/3 for keep the translation be consistent)
If have such tool,could email me(cnlcz20@gmail.com)
--------------
by the way ,those translations(zh-cn&zh-TW)too old and many things are lost(it's based on a very old version,I guess)
I am considering using this tool in the Systems Analysis and Design course I teach. You seem to have the diagramming mechanisms nailed down quite nicely for our purposes. However, I don't see how this tool ensures consistency among diagrams. E.g., I create an actor in a use case diagram; now I build a sequence diagram and want to use the actor already defined in use case - it looks like I have to create another actor.
Dusan Rodina - softwareideas.net
9 October 2011 16:33:10
RE: diagram linking
This seems to be a problem. I'll check it out and I'll fix it in the next release.
Other types of elements can be shared among diagrams - switch project tree to 'All Entities' view and drag the desired element from list of entities to diagram.
How can I remove a ref frame(interaction use) which is attached to a timeline. If I delete this ref frame will the timeline be removed too.
You should think, Ok I can use a workaround by drawing a new timeline but the activation bar is in this case not linked anymore to the new timeline-> you have to redraw everything(timline, call actions,...)
Dusan Rodina - softwareideas.net
1 September 2011 6:20:37
RE: RE: timeline=lifeline
Hi,
it is bug and will be fixed soon.
The workaround:
Move lifeline so, that it doesn't intersect with interaction use element. Then move interaction use element and then delete it. Ref element should be so deleted and lifeline preserved.
Dusan Rodina - softwareideas.net
7 July 2011 13:26:35
RE: ref
Right-click on Interaction Use element and in the context menu click on Add New Diagram (and choose the Sequence diagram item) or Add Existing Diagram (and select an existing sequence diagram from the list).
Dusan Rodina - softwareideas.net
5 July 2011 6:50:47
RE: Drag&Drop
The hotfix allowed to change the start and end activation bar of sequence message (call, return, send). It is not possible to change the parent lifeline of activation bar. I agree, that it would be useful - I will add this option in the next release.
Juan José 3 October 2012 7:51:06
Messages from classes
Juan José 3 October 2012 7:52:09
RE: Messages from classes
Dusan Rodina - softwareideas.net 3 October 2012 7:58:54
RE: RE: Messages from classes
Dusan Rodina - softwareideas.net 3 October 2012 14:40:32
RE: RE: RE: Messages from classes
Juan Jose 4 October 2012 15:27:41
RE: RE: RE: RE: Messages from classes
JKSH 24 September 2012 2:34:00
Sequence Diagram: Show destruction by other class
Dusan Rodina - softwareideas.net 25 September 2012 14:38:25
RE: Sequence Diagram: Show destruction by other cl
JKSH 30 September 2012 5:50:03
RE: Sequence Diagram: Show destruction by other cl
Juan José 17 September 2012 7:48:50
Actions pulled from Class
Dusan Rodina - softwareideas.net 17 September 2012 14:04:27
RE: Actions pulled from Class
Juan José 17 September 2012 16:51:42
RE: RE: Actions pulled from Class
lcz20 14 March 2012 11:11:11
Newer translation working
Dusan Rodina - softwareideas.net 14 March 2012 14:58:16
RE: Newer translation working
Peter 19 December 2011 8:45:16
Stop automatically lifeline when using the destruc
Peter 19 December 2011 7:41:45
Signature options
denkir 27 October 2011 6:52:32
gates
Dusan Rodina - softwareideas.net 27 October 2011 13:53:46
RE: gates
Randy 7 October 2011 12:02:39
diagram linking
Dusan Rodina - softwareideas.net 9 October 2011 16:33:10
RE: diagram linking
Frank 1 September 2011 6:09:54
Frank 1 September 2011 6:12:53
RE: timeline=lifeline
Dusan Rodina - softwareideas.net 1 September 2011 6:20:37
RE: RE: timeline=lifeline
Frank 1 September 2011 9:08:38
RE: RE: RE: timeline=lifeline
denkir 7 July 2011 6:54:06
ref
Dusan Rodina - softwareideas.net 7 July 2011 13:26:35
RE: ref
denkir 5 July 2011 6:30:40
alt
Dusan Rodina - softwareideas.net 5 July 2011 6:43:55
RE: alt
John 4 July 2011 0:32:36
Drag&Drop
Dusan Rodina - softwareideas.net 5 July 2011 6:50:47
RE: Drag&Drop
Dusan Rodina - softwareideas.net 10 July 2011 8:31:11
RE: RE: Drag&Drop
Aleksey Gorkovenko 14 June 2011 7:08:39
Reroute calls
Dusan Rodina - softwareideas.net 14 June 2011 23:18:50
RE: Reroute calls
Dusan Rodina - softwareideas.net 27 June 2011 15:12:21
RE: RE: Reroute calls