Use Case Diagram: Use case diagrams describe the functionality of a system and users of the
system. They contain the
following elements:
1. Actors , which represent users of a system, including human users and other systems
2. Use cases , which represent functionality or services provided by a system to users
Here, is a use case diagram for the ATM System.
Use case for customer
Use case for admin
Class Diagram:- Class diagrams describe the static structure of a system, or how it is structured
rather than how it behaves.
These diagrams contain the following elements:
1. Classes , which represent entities with common characteristics or features. These features include
attributes, operations, and associations.
2. Associations , which represent relationships that relate two or more other classes where the
relationships
have common characteristics or features. These features include attributes and operations.
Sequence Diagram: Sequence diagrams typically show the flow of functionality through a use case,
and consist of the following
components:
1. Actors, involved in the functionality
2. Objects that a system needs to provide the functionality
3. Messages, which represent communication between objects
Example of Sequence diagram for withdrawing amount from ATM
Activity Diagram:- Activity diagrams describe the activities of a class. They are similar to state
transition diagrams and use similar conventions, but activity diagrams describe the behavior/states of
a class in response to internal processing rather than external events. They contain the following
elements:
1. Swimlanes , which delegate specific actions to objects within an overall activity
2. Action States , which represent uninterruptible actions of entities, or steps in the execution of an
algorithm
3. Action Flows , which represent relationships between the different action states on an entity
4. Object Flows , which represent utilization of objects by action states, or influence of action states
on objects.
Following are the examples of Login, Withdraw Activity Diagrams.
State Diagram:- State transition diagrams provide a way to model the various states in which an
object can exist. While the class diagram show a static picture of the classes and their relationships,
state transition diagrams model the dynamic behavior of a systen in response to extermal events
(stimuli). State transition diagrams consist of the following:
1. States , which show the possible situations in which an object can find itself
2. Transitions , which show the different events which cause a change in the state of an object.
Here, is an example of the state diagram for the session of ATM.
Component diagram: Component diagrams are used to model physical aspects of a
system. Physical aspects are the elements like executables, libraries, files, documents
etc which resides in a node. So component diagrams are used to visualize the
organization and relationships among components in a system. These diagrams are
also used to make executable systems. Component diagrams can be described as a
static implementation view of a system. Static implementation represents the
organization of the components at a particular moment.
Deployment diagram
• Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
• So deployment diagrams are used to describe the static deployment view of a
system. Deployment diagrams consist of nodes and their relationships.