By Sarah

1. UML Practicaly
Sarah BEIRKDAR

2. OVERVIEW
1- What is UML?
2- How and when do we use it?
3-UML Diagram Types with examples.

3. OVERVIEW
• UML is a standard language for specifying, visualizing,
constructing, and documenting the software systems.
• UML stands for Unified Modeling Language.
• UML is a pictorial language used to make software blue
prints.
• UML is not a programming language but specific tools can
be used to generate code using UML diagrams.
• UML has a direct relation with object oriented analysis and
design.

4. Bayi??
Depo??
Satıcı??
Ayrı class mı
?!

5. «A picture is worth a thousand words.»
The most important goal for developing
UML is to..
Define some general purpose modeling language which
all stakeholders can use.
İt needs to be made simple to understand and use.

6. UML as a Roadmap
- UML diagram should not contain a 100%
specification of the real software.
- A single diagram is not enough to cover all aspects
of the system.
- Up-to-date documentation available for anyone
who joins the project later.

7. Before
Learning UML
It’s handy to understand
OO concepts.

8. Modeling Types
1- Structural Modeling: Captures the static features of the
system.
+ Class diagram
+ Object Diagram
+ Use Case Diagram
2- Behavioral : Describes the interaction in the system.
+ Sequence Diagram
+ Activity Diagram

9. CLASS Diagram
1- The most common diagram used in UML.
2- Class diagram consists of classes, interfaces,
associations and collaboration.
3- Basically represents the object oriented view of a
system which is static in nature.

11. OBJECT Diagram
• Object diagrams are derived from class
diagrams
• Object diagrams represent an instance of a class
diagram.
• The basic concepts are similar for class
diagrams and object diagrams.

13. USE CASE Diagram
• Used to get an outside view of the system.
• Show the interaction among the requirements and actors
• The actors can be human user, some internal applications or may
be some external applications.
• A single use case diagram captures a particular functionality of
the system.
• Use case diagram can be imagined as a black box where only the
input, output and the function of the black box is known.
• These diagrams are used at a very high level of design.

14. USE CASE Diagram - Order

15. SEQUENCE Diagram
1- Models the sequential logic, in effect the time
ordering of messages between classifiers.

16. SEQUENCE Diagram – Chain
Store Delivery
Dealer’s agent collects order from customer. A new order is
created with DocumentType = 1. Then after the dealer
delivers goods he create a new document with
DocumentType = 18 ….etc.

18. “
Activity Diagram
• Activity diagram is basically a flow chart to
represent the flow form one activity to another
activity.
• The activity can be described as an operation of the
system.

19. Activity Diagram - Promotion

20. Summary
1- 2 Dimensional representation.
2- A way of thinking.
3- Sometime when too much details required we should
have them as text.

21. THANKS!
Any questions?