activity diagram

[luvcloud]

i'm having trouble coming up with an activity diagram. i'm developing a multiplayer
networking checkers game. should i have activity diagram for both the client
and the server in one diagram, or should i separate them into two?

if i were to put it into one diagram, how do i differenciate which activity
is done by the server, and the one by the client? put it into swinlanes?

also, should i show the client and the server communicating through one common
activity, ie 'sending to server' or 'receiving from server, 'sending to client'
or 'receiving from client' or should they communicate directly with the activity
that the server/client will perform.

[elliferg]

"luvcloud" <luvcloud_say@yahoo.com> wrote:
>
>should i have activity diagram for both the client
>and the server in one diagram, or should i separate them into two?

I would probably make up to 3 diagrams. One with a moderately low level
of detail. Then if there are important activities on the client and/or server
sides that need to be broken down further, I would make more detailed diagrams
for one or both of the platforms.


>
>if i were to put it into one diagram, how do i differenciate which activity
>is done by the server, and the one by the client? put it into swinlanes?
>

yes

>also, should i show the client and the server communicating through one
common
>activity, ie 'sending to server' or 'receiving from server, 'sending to
client'
>or 'receiving from client' or should they communicate directly with the
activity
>that the server/client will perform.


on the main diagram, i would just have the arrows going directly into the
activity on the other platform. in the more detailed diagrams, you could
put a send/receive activity if you really need that level of detail.