(1): Use Case Diagrams in UML:
UML uses the case diagrams to overview the requirements for the system. They are useful for presentation to management and/or Project stakeholders. Use case diagram depict:
i: Use cases=a use case describes a sequence of actions that provides something of measurable value to an actor and is drawn as a horizontal ellipse.
ii: Actors= an actor is a person, organization or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures.
iii: Associations= associations between actors and use cases are drawn by solid lines.
iv: System boundary boxes= A rectangle can be drawn around the use cases called the system boundary box, to indicate the scope of the system.
v: Packages= Packages are UML constructs that enable to organize model elements (such as use cases) into groups. 1

(2): Class Diagrams in UML:
Class diagrams are widely used to describe the type of objects in a system and their relationships. Class diagrams model class structure and contents using design elements such as classes, packages and objects. Class diagrams describe three different perspectives when designing a system, conceptual, specification and implementation. Classes are composed of three things: a name, attributes and operations.

Class diagrams also display relationships such as containment, inheritance, associations and others
Another relationship in class diagram is generalization. A generalization is used when two classes are similar, but have some differences. 2
(3): Sequence Diagrams in UML:
A sequence diagram is made up of objects and messages. Objects are represented exactly as rectangles with the underlined class name within the rectangle.. The primary element involved in a sequence diagram is an object-instance of a class A sequence diagram consists of sequences of interaction among different objects over a period of time. The other object in sequence diagram is represented as message. A message is denoted by a directed arrow. 3
(4): Collaboration Diagrams in UML:
The elements of a collaboration (Communication Diagram in UML 2.0) are essentially the same as that of a sequence diagram. A sophisticated modelling tool can easily convert a collaboration diagram into sequence diagram and vice versa. There are following elements in the collaboration diagram:
i: Objects: Objects interact with each other in the system. Depicted by a rectangle with the name of the object in it preceded by a colon and underlined.
ii: Relation/Association: A link connecting the associating objects.
iii: Messages: An arrow pointing from the commencing object to the destination object shows the interaction between the objects. 4

(5): State Chart Diagrams in UML:
A UML state chart diagrams depict the various states that a class can be in and the transaction between those states. Not each class can have state chart diagrams but only classes with three or more potential states can be modelled. 5
(6): Activity Diagrams in UML:
Activity diagrams represent the business and operational workflow of a system. An activity diagram is a dynamic diagram that shows the activity and the event that causes the object to eb in the particular state. An activity diagram consists of the following behavioural elements.
i: Initial activity.
ii: Activity.
iii: Decisions.
iv: Signal.
v: Concurrent activities.
vi: Final activity. 6

(7): Component Diagrams in UML:
The main purpose of component diagram is to show the structural relationships between the components of a system. Component diagrams offer system architect a natural format to begin medalling a solution. Component diagrams allow an architect to verify that a syatem's functionality is being implemented by components. In addition, component diagrams are useful communication tool for presentation to key project stakeholders. 7
(8): Deployment Diagrams in UML:
The deployment diagram shows how a system will be physically deployed in the hardware environment. Its purpose is to show where the different components of the system will physically run and how they will communicate with each other. 8
A deployment diagram consists of the following elements:
i: Node=The element that provides the execution environment for the components of the system. They are depicted by the queue with the name of the object in it, preceded by a colon and an underline.
ii: Connection= They define the interconnection between the nodes e.g. arrows and lines. 9
References:
1: UML 2 case diagrams accessed on May 28, 2009 at http://www.agilemodeling.com/artifacts/useCaseDiagrams.htm
2: Class diagrams, accessed on May 28, 2009 from http://atlas.kennesaw.edu/~dbraun/csis4650/A&B/UML_tutorial/class.htm
3: http://www.developer.com/design/article.php/3080941
4: Collaboration diagrams in UML, accessed on May 28, 2009 from http://developer.com/design/article.php/10925_3102981
5: UML basics an introduction to the unified modelling language_state chart diagram accessed on May 28, 2009 from http://www.ibm.com/developerworks/rational/library/769.html
6: Activity diagram in UML accessed on May 28, 2009 at http://www.developer.com/design/article/php/10925_2247041
7: UML basics-componet diagram, accessed on May 28, 2009 at http://www.ibm.com/developerworks/rational/library/dec04/bell/
8: UML basics: an introduction to the unified modelling language, accessed May 28, 2009 at http://www.ibm.com/developerworks/rational/library/769.html
9: Deploment diagram in UML, accessed on May 28, 2009 at http://www.developer.com/design/article.php/3291941