Communication Diagram

Hi darren,

That was my question last time. :-) So is that what I am supposted to do?  Why diffrent names if they are the same?

Ah, I didn't realise, sorry.

They are not the exact same but they both try to show the same information although in my opinion sequence diagrams are better due to the fact that you can show combined fragments.

The same two first steps in the previous diagram would look like this in a communication diagram

|----------------------|
|                           |
|   Administrator   |
|----------------------|
            |
            |   1. mnuMatchResult
           \|/
|----------------------|
|                           |
|       frmMain        |
|----------------------|

Each participant is a regtangle and every message is numbered in sequence. This is different in that it does not contain lifelines and in my opinion is not as neat as a sequence diagram. Also as you get more detailed you cannot show combined fragments and these are extremely useful in large sequence diagrams.

If I was you I would create a communication diagram using the above syntax shown in this post.

http://publib.boulder.ibm.com/infocenter/rsasehlp/v7r5m0/index.jsp?topic=/com.ibm.xtools.sequence.doc/topics/rexamplecommdiag.html

You should also have a look at this power point presentation as it will help explain the differences

http://ait.unl.edu/siau/mgmt456/Booch-chpt19.ppt#2

Hope this helps a little,

Darren

Hi,

Let me know how you are getting on with this and if you need more information .

Darren

Ohhh this is so hard. This is not so easy. :-/

Well this is what I got so far. Is it correct? Do i miss something?
First of all I will show you the real quiz and not my fake one.

Use Case 4 Searching for film
Primary actor:
Users
Stakeholders:
User - want to find interesting film
Shopkeepers - want the user to easily find interesting films to possibly hire
these
Priority:
Should be
Prerequisite (preconditions):
The server running
Internet
The user is identified
Success Scenario (item conditions):
Users will find searching film
Primary success scenario (Basic Flow):
1. The user chooses to search by movie
2. The system displays form for entering the crawl and search
3. The user fills in crawl and search
4. The system validates the information and look for the film sought
5. The system displays information for the film sought to the user.
Extensions (Alternative Flows):
* At any time during the process:
1. The user chooses to cancel the search
2. The system interrupts the search
4a. The system validates the information, where the user crawl and search not authorized
10. The system displays to crawl and search are not correct
11. The user changes the crawl and search and submit these
12. To paragraph 4 of the primary success scenario
4b. The system will find not sought film
1. Announced that applied films can not be found and provides an opportunity to search again.

Sorry to be late to the party, but Sequence diagrams and Communication diagrams are NOT the same.  Communication diagrams used to be called Collaboration diagrams.  Read more here:

UML 2 Communication Diagrams
http://www.agilemodeling.com/artifacts/communicationDiagram.htm

Hi Marklorenz,

You are correct they are not the same but they are similar in that they show messages between objects.

Also I have never said that they were the same. As I said in an above post "They are not the exact same but they both try to show the same information "

From your article:
"my experience is if you feel the need to use sequence numbers on communication diagrams this is a good indication you should be using sequence diagrams instead. The main difference between communication diagrams and sequence diagrams is that sequence diagrams are good at showing sequential logic but not that good at giving you a big picture view whereas communication diagrams are the exact opposite."

Also I would like to point out that Mickeys is trying to create a communication diagram from a use case which is why I suggested a sequence diagram in the first place. Again from your article

"You draw communication diagrams in the same way as you draw sequence diagrams, the only real difference is that you lay out the notation in a different manner.  To tell you the truth I rarely find the need to create communication diagrams although I have found them useful in situations where we didnt have use cases as the primary requirements artifact.  Sequence diagrams and use cases seem to go hand in hand because of how easy it is to model the sequential logic of a use case using a sequence diagram."

So I think that you have simply misread your article.

Cheers,

Darren

Thx Darren,

You are very kind that helps me.