What types of diagrams are generally created while designing an use case / functionality ?

Class   Diagram  : They describe the static structure of a system.
Package Diagram  : Package diagrams organize elements of a system into related groups to minimize dependencies between packages.
Object  Diagram  : Object diagrams describe the static structure of a system at a particular time. They can be used to test class diagrams for accuracy. They can be      used to test class diagrams for accuracy. They can be used to test class diagrams for accuracy.
Use Case Diagrams : Use case diagrams model the functionality of system using actors and use cases.
Sequence Diagrams : describe interactions among classes in terms of an exchange of messages over time.
Collabration Diagram    : Collaboration diagrams represent interactions between objects as a series of sequenced messages. Collaboration diagrams describe both the static      structure and the dynamic behavior of a system.
Activity Diagram : Activity diagrams illustrate the dynamic nature of a system by modeling the flow of control from activity to activity. An activity represents an      operation on some class in the system that results in a change in the state of the system. Typically, activity diagrams are used to model workflow      or business processes and internal operation.
Component Diagrams : Component diagrams describe the organization of physical software components, including source code, run-time (binary) code, and executables.
Deployment Diagrams : Deployment diagrams depict the physical resources in a system, including nodes, components, and connections.

  2 Users have rated as useful.

  

Login to rate this answer.