Diagrams

Diagrams in the UML  

·      Diagram is the graphical presentation of a set of elements, most often rendered as a connected graph of vertices (things) and arcs (relationships).

·         In theory, a diagram may contain any combination of things and relationships.

·         For this reason, the UML includes nine such diagrams:

·         Class diagram

·         Object diagram

·         Use case diagram

·         Sequence diagram

·         Collaboration diagram

·         State chart diagram

·         Activity diagram

·         Component diagram

Class diagram 

•  A class diagram shows a set of classes, interfaces, and collaborations and their relationships.Class diagrams that include active classes address the static process view of a system.                   
  

Object diagram 

• Object diagrams represent static snapshots of instances of the things found in class diagrams
• These diagrams address the static design view or static process view of a system
• An object diagram shows a set of objects and their relationships

Use case diagram

•  A use case diagram shows a set of use cases and actors and their relationships andUse case diagrams address the static use case view of a system.  
• These diagrams are especially important in organizing and modeling the behaviors of a system.

Interaction Diagrams

              Both sequence diagrams and collaboration diagrams are kinds of interaction diagrams

               Interaction diagrams address the dynamic view of a system.

                      A sequence diagram is an interaction diagram that emphasizes the time-ordering of messages

                      A collaboration diagram is an interaction diagram that emphasizes the structural organization of the objects that send and receive messages

                        Sequence diagrams and collaboration diagrams are isomorphic, meaning that you can take one and transform it into the other

State chart diagram

• A statechart diagram shows a state machine, consisting of states, transitions, events, and activities
• Statechart diagrams address the dynamic view of a system
• They are especially important in modeling the behavior of an interface, class, or collaboration and emphasize the event-ordered behavior of an object

Activity diagram

• An activity diagram is a special kind of a statechart diagram that shows the flow from activity to activity within a system. Activity diagrams address the dynamic view of a system
• They are especially important in modeling the function of a system and emphasize the flow of control among objects

Component diagram 

• A component diagram shows the organizations and dependencies among a set of components. Component diagrams address the static implementation view of a system.
• They are related to class diagrams in that a component typically maps to one or more classes, interfaces, or collaborations

Deployment diagram

• A deployment diagram shows the configuration of run-time processing nodes and the components that live on them
• Deployment diagrams address the static deployment view of an architecture