UML Diagram
CLASS Diagram
Component Diagram
Component diagrams are used to represent how the physical components in a system have
been organized. We use them for modelling implementation details.
Component Diagrams depict the structural relationship between software system
elements and help us in understanding if functional requirements have been covered by
planned development.
Component Diagrams become essential to use when we design and build complex
systems.
Interfaces are used by components of the system to communicate with each other.
,Component Diagram
Deployment Diagram
Deployment Diagrams are used to represent system hardware and its software. It tells us
what hardware components exist and what software components run on them.
We illustrate system architecture as distribution of software artifacts over distributed
targets.
An artifact is the information that is generated by system software.
They are primarily used when a software is being used, distributed or deployed over
multiple machines with different configurations.
Deployment Diagram
Package Diagram
We use Package Diagrams to depict how packages and their elements have been organized.
A package diagram simply shows us the dependencies between different packages and
internal composition of packages.
Packages help us to organise UML diagrams into meaningful groups and make
the diagram easy to understand.
They are primarily used to organise class and use case diagrams.
, Package Diagram
Object Diagram
An Object Diagram can be referred to as a screenshot of the instances in a system and the
relationship that exists between them. Since object diagrams depict behaviour when objects
have been instantiated, we are able to study the behaviour of the system at a particular
instant.
An object diagram is similar to a class diagram except it shows the instances of classes
in the system.
We depict actual classifiers and their relationships making the use of class diagrams.
On the other hand, an Object Diagram represents specific instances of classes and
relationships between them at a point of time.
Object diagram
=================================================================
CLASS Diagram
Component Diagram
Component diagrams are used to represent how the physical components in a system have
been organized. We use them for modelling implementation details.
Component Diagrams depict the structural relationship between software system
elements and help us in understanding if functional requirements have been covered by
planned development.
Component Diagrams become essential to use when we design and build complex
systems.
Interfaces are used by components of the system to communicate with each other.
,Component Diagram
Deployment Diagram
Deployment Diagrams are used to represent system hardware and its software. It tells us
what hardware components exist and what software components run on them.
We illustrate system architecture as distribution of software artifacts over distributed
targets.
An artifact is the information that is generated by system software.
They are primarily used when a software is being used, distributed or deployed over
multiple machines with different configurations.
Deployment Diagram
Package Diagram
We use Package Diagrams to depict how packages and their elements have been organized.
A package diagram simply shows us the dependencies between different packages and
internal composition of packages.
Packages help us to organise UML diagrams into meaningful groups and make
the diagram easy to understand.
They are primarily used to organise class and use case diagrams.
, Package Diagram
Object Diagram
An Object Diagram can be referred to as a screenshot of the instances in a system and the
relationship that exists between them. Since object diagrams depict behaviour when objects
have been instantiated, we are able to study the behaviour of the system at a particular
instant.
An object diagram is similar to a class diagram except it shows the instances of classes
in the system.
We depict actual classifiers and their relationships making the use of class diagrams.
On the other hand, an Object Diagram represents specific instances of classes and
relationships between them at a point of time.
Object diagram
=================================================================
