sequence diagram create new object staruml

#Sequence diagram create new object staruml verification#

The Delete Message symbol is used to delete an object. This is represented with the created word on top of a dotted arrow. By the way, you can also show on the diagram that you expect delays with non-horizontal arrows (see example in this SO question). This message is used when we create a new object in the sequence diagram. Here you can find some real life message scenario for Apache-Sandesha with some asynchronous messages. The viewpoint of the receiver is different from your point of view of human reading the diagram : the diagram as a whole should give you some idea about sequence and kind of interactions (to see if there could be delays or not). So yes, the receiver doesn't need to know when the message was sent: it's just that he has to act on the message (immediately for synchronous messages, or asap for asynchronous). Message timing (for your initial wording 'the receiver doesn't have to know when')įor asynchronous messages, the principle is to avoid that senders have to wait for feedback and that receivers have to act immediately. The ':class' notation is quite common and googling for sequence diagrams will return you plenty of examples.Īnother case where the receiver is unknown (at least according to my own understanding), would be when you send a create message that instantiates a new object (that was not known at the moment the message was initiated). This article explains the graphical notation. Unknown receivers are unnamed objects of a given class. The sequence diagram may use lifelines for known or unknown receivers. Indeed, the user simulates a scenario using the sequence diagrams and.

#Sequence diagram create new object staruml verification#

Edit: Unknown receiver (for updated wording 'the receiver doesn't have to be known') Verification Tools: OCLE (Object Constraint Language Environment)6 is a tool with.