Concurrent Paths but do not come together

[Bill Egge]

Please let me know if these questions are not appropriet.

I am learning UML and in the book I am reading it shows how to diagram concurrent paths in an activity diagram.  All their examples show the concurrent activities comming back together.  But I have some source code in which the paths do not come back together but end separately.

Below is my guess to diagram this.

The digram below is probably self explanatory but I will tell you what it is in case it is not.

We have a proposal generation system.  Brokers log into the system through a web interface and make changes to existing proposals (they create them too but this diagram only shows modifying).  All admins then get an email notification stating that a proposal was changed.  I coded this system.  Since emailing takes a long time, I decided to run it in a background thread so that the broker would not have to wait so long.

Here is a diagram.  Have I diagrammed it correctly?

[sargasso]

Looks good to me, in that the diagram effectively conveys your textural description.

Remember, you are diagramming a situation to either solve a problem or to communicate something.  If the model is effective then d*mn the standard.  The only thing I may add to your diagram, and only if necessary, is a note on both of the split threads explicitly stating they are asynchronous and any ramifications thereof.  For example, you may wish to highlight to some audience that the email does not happen immediately and that if the user makes more than one change they will get motre than one email.

btw Your questions are appropriate!

bruce

[Bill Egge]

Thanks Bruce, thats a good idea to add a note.  Another programmer that comes behind me would need to realize that there is no indication to the user if the emailing fails.

These advices are good since I am new to this.