> Dear All,
>
> What is the different between class diagram, sequence
> Diagram and Collaboration Diagram.
>
> Thanks
no relation so cannot compare all are different but in what way see the link below
http://umlcenter.visual-paradigm.com/umlresources/nota_11.pdf
Class Diagrams
These are not interaction diagrams. They basically describe the types of objects in the system and the various kinds of static relationships that exist among them. The two kind of relationships are :
associations
subtypes
Collaboration diagram
They unlike class diagrams are basically interaction diagrams(the other type of interaction diagrams are sequence diagrams). So in case you have to make a choice you could choose between a collaboration diagram or a sequence diagram.
In UML usually you can classify diagrams types under two categories, Static or Interactive.
Static: are diagrams that represent a SW system or a SW module from a static point of view. Taking Class diagrams as an example, they represent your system in terms of Objects. When you are talking about a simple system for a Clinic then you will have patient, Provider, Procedure ..etc as objects. Patient object will have properties like Patient Name, Age, Diagnosis and will have functions like payBill(), takeMedicine(). The Clinic object is composed of Rooms, Chairs and so on. One Clinic object is associated with one Doctor/Provider object. Therefore, Class diagram is trying to represent your Classes, their properties, functions, and the structural relation between the classes like Association, Aggregation.
Dynamic/Interactive: in this type of diagrams you will try to describe the flow of your system or the changes in its status. If we wanted to develop a sequence diagram for our Clinical SW system we will put our objects and start to draw the flow of messages between the objects. For example, a Patient make a reservation, then Patient arrives inside the Clinic, then the Doctor check up the Patient, and then Patient pay the Bill (which is the worst part of the scenario!). Now you will notice that we did had Patient, Clinic, Bill, and Doctor objects interacting with each other. Patient object sends a message to Clinic object saying "addReservation()" and so on.
So the relation between the Class diagram and Sequence/Collaboration diagrams is that Class diagram listed your classes and their properties, and methods: "class1" has "property17", "class2" has "method29" and "property27" but the Sequence told you that "class1" should call first "method29" on "class2", then "class2" should update its own property "property27".
Sequence and Collaboration diagrams are so tight and similar to each other, though; they differ in the time factor. Sequence diagram emphasis the sequence of the messages while Collaboration show the interoobject links.
For a good jump-start try SAMS "UML teach yourself in 24 hours" for author Joseph Schmuller.