DESIGN PATTERN

PRESENTATION

SUPPLEMENTARY MATERIALS
UNIFIED MODELING LANGUAGE(UML)
Unified Modeling Language (UML) is a general-
purpose modeling language for specifying,
visualizing, constructing and documenting the
artifacts of software systems
It is quite similar to blueprints used in other
fields of engineering
UML is not a programming language, it is
rather a visual language
We use UML diagrams to portray the behavior
and structure of a system
UNIFIED MODELING LANGUAGE(UML)
UML helps software engineers, businessmen, and
system architects with modeling, design, and
analysis
The Object Management Group (OMG) adopted
Unified Modelling Language as a standard in 1997
It’s been managed by OMG ever since
The International Organization for Standardization
(ISO) published UML as an approved standard in
2005
UML has been revised over the years and is
reviewed periodically
WHY NEED UML AND ITS TYPES
Complex applications need collaboration and
planning from multiple teams and hence
require a clear and concise way to
communicate amongst them
Businessmen do not understand code, so UML
becomes essential to communicate with non-
programmers about essential requirements,
functionalities, and processes of the system
A lot of time is saved down the line when
teams can visualize processes, user interactions,
and the static structure of the system
TYPES OF UML DIAGRAM
TYPES OF UML DIAGRAM
Structural UML Diagrams

• Class Diagram
• Composite Structure Diagram
• Object Diagram
• Component Diagram
• Deployment Diagram
• Packages Diagram
TYPES OF UML DIAGRAM
Behavioral UML Diagrams

• State Machine Diagram

• Activity Diagram
• Use Case Diagram
• Sequence Diagram
• Communication Diagram
• Timing Diagram
• Interaction Overview Diagram
TYPES OF UML DIAGRAM
Class Diagram
It shows the relationship between classes and
pertinent information about classes themselves
Object Diagram
Object diagrams can be described as an instance
of class diagram, so these diagrams are more
close to real life scenario where we implement a
system
Object diagram are a set of objects and their
relationship just like class diagram and also
represent the static view of the system
TYPES OF UML DIAGRAM
The usage of object diagram is similar to class
diagram but they are used to build prototype of a
system from practical perspective
Use Case Diagram
It shows actors, use cases and the relationship
between them
Interaction Diagram
It shows an interaction between a group of
collaborating objects
It has two types of diagrams like sequence
diagram and collaboration diagram
TYPES OF UML DIAGRAM

Activity Diagram
It very similar to flow chart
It shows action & decision points but with the
ability to accommodate concurrently
State Transition Diagram
It describes behavior of instance of a class in
terms of states, transitions and events
TYPES OF UML DIAGRAM

Package Diagram
It shows system structure at the library or
package level

Deployment Diagram
It shows configuration of hardware and software
in a distributed system
USAGES OF UNIFIED MODELING LANGUAGE
UML has been used in the following areas

Enterprise Information Systems

Transportation
Telecommunications
Retails
Science and Research
Banking and Financial services
STEPS FOR UML DIAGRAMS
Identify the Purpose
Determine the purpose of creating the UML diagram
Different types of UML diagrams serve various
purposes, such as capturing requirements, designing
system architecture, or documenting class
relationships
Identify Elements and Relationships
Identify the key elements (classes, objects, use cases,
etc.) and their relationships that need to be
represented in the diagram
This step involves understanding the structure and
behavior of the system you are modeling
STEPS FOR UML DIAGRAMS
Select the Appropriate UML Diagram Type
Choose the UML diagram type that best fits your
modeling needs
Common types include Class Diagrams, Use Case
Diagrams, Sequence Diagrams, Activity Diagrams,
and more
Create a Rough Sketch
Before using a UML modeling tool, it can be helpful
to create a rough sketch on paper or a whiteboard
This can help you visualize the layout and
connections between elements
STEPS FOR UML DIAGRAMS
Choose a UML Modeling Tool
Select a UML modeling tool that suits your
preferences and requirements. There are various
tools available, both online and offline, that offer
features for creating and editing UML diagrams
Create the Diagram
Open the selected UML modeling tool and create a
new project or diagram
Begin adding elements (e.g., classes, use cases,
actors) to the diagram and connect them with
appropriate relationships (e.g., associations,
dependencies)
STEPS FOR UML DIAGRAMS
Define Element Properties
For each element in the diagram, specify relevant
properties and attributes
This might include class attributes and methods,
use case details, or any other information specific
to the diagram type
Add Annotations and Comments
Enhance the clarity of your diagram by adding
annotations, comments, and explanatory notes
This helps anyone reviewing the diagram to
understand the design decisions and logic behind it
STEPS FOR UML DIAGRAMS
Validate and Review
Review the diagram for accuracy and completeness.
Ensure that the relationships, constraints, and elements
accurately represent the intended system or process
Refine and Iterate
Refine the diagram based on feedback and additional
insights. UML diagrams are often created iteratively as
the understanding of the system evolves
Generate Documentation
Some UML tools allow you to generate documentation
directly from your diagrams. This can include class
documentation, use case descriptions, and other
relevant information
UML BEST PRACTICES
Unified Modeling Language (UML) is a powerful tool
for visualizing and documenting the design of a
system
To create effective and meaningful UML diagrams, it’s
essential to follow best practices where are the
following
Understand the Audience
Consider your audience when creating UML diagrams
Tailor the level of detail and the choice of diagrams
to match the understanding and needs of your
audience, whether they are developers, architects, or
stakeholders
UML BEST PRACTICES
Keep Diagrams Simple and Focused
Aim for simplicity in your diagrams
Each diagram should focus on a specific aspect of the
system or a particular set of relationships. Avoid
clutter and unnecessary details that can distract from
the main message
Use Consistent Naming Conventions
Adopt consistent and meaningful names for classes,
objects, attributes, methods, and other UML elements
Clear and well-thought-out naming conventions
enhance the understandability of your diagrams
UML BEST PRACTICES
Follow Standard UML Notations
Adhere to standard UML notations and symbols
Consistency in using UML conventions ensures that
your diagrams are easily understood by others who
are familiar with UML
Keep Relationships Explicit
Clearly define and label relationships between
elements
Use appropriate arrows, multiplicity notations, and
association names to communicate the nature of
connections between classes, objects, or use cases
CHALLENGES OF UML MODELING
Time-Intensive
UML modeling can be perceived as time-consuming,
especially in fast-paced Agile environments where rapid
development is emphasized
Teams may struggle to keep up with the need for
frequent updates to UML diagrams
Over-Documentation
Agile principles value working software over
comprehensive documentation
There’s a risk of over-documentation when using UML,
as teams may spend too much time on detailed diagrams
that do not directly contribute to delivering value
CHALLENGES OF UML MODELING
Changing Requirements
Agile projects often face changing requirements,
and UML diagrams may become quickly outdated.
Keeping up with these changes and ensuring that
UML models reflect the current system state can be
challenging
Collaboration Issues
Agile emphasizes collaboration among team
members, and sometimes UML diagrams are seen as
artifacts that only certain team members understand
Ensuring that everyone can contribute to and
benefit from UML models can be a challenge
BENEFITS OF USING UML DIAGRAM
Standardization
UML provides a standardized way of representing
system models, ensuring that developers and
stakeholders can communicate using a common
visual language
Communication
UML diagrams serve as a powerful communication
tool between stakeholders, including developers,
designers, testers, and business users
They help in conveying complex ideas in a more
understandable manner
BENEFITS OF USING UML DIAGRAM
Visualization
UML diagrams facilitate the visualization of system
components, relationships, and processes
This visual representation aids in understanding and
designing complex systems
Documentation
UML diagrams can be used as effective
documentation tools
They provide a structured and organized way to
document various aspects of a system, such as
architecture, design, and behavior
BENEFITS OF USING UML DIAGRAM

Analysis and Design

UML supports both analysis and design phases of
software development
It helps in modeling the requirements of a system and
then transforming them into a design that can be
implemented