Contains the overview of unified Modeling Language UML version 2.0. What is UML, its necessity, components of UML etc. It is important for Software Engineering and System analysis and Design course. This slide gives the overview of the design diagrams of these courses.

1. Unified Modeling Language
(UML 2.0)
Khandaker Mamun Ahmed 1

2. What is UML?
• UML stands for “Unified Modeling Language”
• It is a industry-standard graphical language for specify,
visualizing, constructing and documenting the artifacts of
software systems
• The UML uses mostly graphical notations to express the
object-oriented analysis and design of the software
projects.
• Simplifies the complex process of software design
Khandaker Mamun Ahmed 2

3. UML cont.
UML – general-purpose modeling language in software
engineering, designed to provide a standard way to visualize
design of a system.
Developers
• Grady Booch
• Ivar Jacobson
• James Rumbaugh
Khandaker Mamun Ahmed 3

4. • Use graphical notation to communicate more clearly than
natural language (imprecise) and code (too detailed).
• Help acquire an overall view of a system.
• UML is not dependent on any language or technology.
• UML moves us from fragmentation to standardization.
Why UML for Modeling?
Khandaker Mamun Ahmed 4

5. Types of UML Diagrams
 Structural Diagrams
 Behavioral Diagrams
Khandaker Mamun Ahmed 5

6. Structure Diagram
Structure Diagram - represents data and static relationship.
They include
 Class
 Object
 Package
 Deployment
 Component
 Composite structure diagrams
Khandaker Mamun Ahmed 6

7. Behavioral Diagram
Behavioral Diagram - model dynamic behavior and dynamic
relationships among objects in the system
Used to model functional requirements
They include
Use case
Activity
Interaction (sequence, communication …)
State machine
Khandaker Mamun Ahmed 7

8. Types of UML Diagrams
Khandaker Mamun Ahmed 8

9. Use case
• Use case diagrams are the blueprints
for your system
• Representation of a user’s interaction
with the system
• Provide the simplified and graphical
representation of what the system
must actually do
Khandaker Mamun Ahmed 9

10. Activity Diagram
• Describes the dynamic aspects of
the system.
• Graphical representations of
workflows of stepwise activities and
actions.
Khandaker Mamun Ahmed 10

11. Class Diagram
• Class diagram is the main building block
of object-oriented modelling.
• Describes the static structure of a
system.
Khandaker Mamun Ahmed 11

12. Data Modeling
• It is a process used to define and
analyze data requirement.
• Illustrates the relationships
between data.
Khandaker Mamun Ahmed 12

13. State Diagram
• Shows transitions between
various objects
• Describes the behavior of a
system considering all the
possible states of an object
Khandaker Mamun Ahmed 13

14. Sequence Diagram
• Shows object interactions arranged in time
sequence
• Depicts the objects and classes involved in
the scenario
Khandaker Mamun Ahmed 14

15. Data Flow Diagram
• Graphical representation of the
"flow" of data through an
information system
• Focuses on the flow of
information, where data comes
from, where it goes and how it
gets stored.
Khandaker Mamun Ahmed 15

16. UML Diagram Summary
Khandaker Mamun Ahmed 16

17. Thanks
Khandaker Mamun Ahmed 17
