Automator

Have you ever wanted to share your knowledge to someone else, who havent got the process well enough ? Have you ever trying to make you solution plain to your colleges ?
If he or she are close to you, in the same room, the best way is to use paper and draw diagram in pencil. But if someone are far from you and only communication channel available, the only way is e-mail your drawings and comments.
Long ago, standard UML was put out as a graphical representation of a system's model.
And recently, smart men come up with SD / MSC Generator, which situated on the site websequencediagrams.com. There are also sites to generate other types of UML diagrams, but now want to talk about this particular one.

Click the button "Make all" and get a nice diagram. Style and scale of schematic can be changed immediately. In the description of the sequence took for maximum about 15 minutes. I am horrified to think how much time I spent on it in the WYSIWYG tool, sharpened under the arm-type mouse.

The service has a necessary and sufficient set of control sequences (sorry for tautology):

->

Synchronous message

-->

Asynchronous message or reply

participant

Participant declaration
Not necessarily, but you need when you need to specify the correct order of participants in the diagram

alt

Branching

loop

Iteration

opt

Optional grouping

note

Comment
may be left, right or over one or many participants

activate

Activation of participant

deactivate

Deactivation of participant

destroy

Destruction of participant

See examples on their side.

Also, you can easily embed result onto you blog:

User --> Client: Load
activate Client
Client --> Server: getPage
note left of Server: Here "Client" is browser, and \n"Server" some web-server part
activate Server
Server -> Servlet1: createServlet
activate Servlet1
Server -> Servlet2: createServlet
activate Servlet2
Server -> Servlet1: processRequest
Servlet1 -> Server: response
destroy Servlet1
Server -> Servlet2: processRequest
Servlet2 -> Server: response
destroy Servlet2
Server -> Client: resultPage
deactivate Server
Client -> User: show
deactivate Client