UML (Unified Modeling Language) is a standard language for modeling software systems using visual diagrams. It includes structure diagrams for modeling static aspects and behavioral diagrams for dynamic aspects. Some key UML diagrams are class, use case, sequence, state machine, package, and deployment diagrams. UML has evolved over time through the merging of different modeling techniques and is now maintained by the Object Management Group.

1. Prepared by:
*Mohammad Baddad
*Anas Za’z’a
Dr. Sami Awad.
Software Analysis and Design.

2. UML
Unified Modeling Language : A standard Language for designing and documenting a system in an
object oriented manner.
Modeling
Why UML for Modeling?
History of UML
Types of UML Diagrams :
 Structure diagrams :
• Class Diagram
• Component diagram
• Composite structure diagram
• Deployment diagram
• Object diagram
• Package diagram
• Profile diagram
 Behavior diagrams :
• Activity diagram
• UML state machine diagram
• Use Case Diagram
• Interaction diagrams :
 Use Case Diagram
 Class Diagram
 Sequence Diagram
 Collaboration Diagram
 State Diagram
 Communication diagram (combination from Class, Sequence, and Use Case Diagrams)
 Interaction overview diagram
 Sequence diagram
 Timing diagrams

3. UML
UML Definition .
UML history and Versions.
UML Types.

4. UML Definition
 UML stands for “Unified Modeling Language”.
 A standard Language for designing and documenting a system in an
object oriented manner
 Industry standard for specifying, visualizing, constructing and documenting
the artifact of software systems.
 Graphical Notation to express the OO analysis and design of software
project.
 Modeling Tools that simplifies the complex process of software design.
 UML® specification (standard) is updated and managed by the Object
Management Group (OMG™)

5. UML history and version’s
 Booch: OOAD => very complex, Good at low level design.
 Rumbaugh: OMT => simple modeling language, Good at middle ground.
 Jacobson : OOSE=> use classes, good at high level of design
 In 1994, three method was merge to gather.
 In 1996,UML 0.9 and then 0.91.
 In 1997, UML 1.0
 In 2000, the UML is accepted in ISO as industry standard for modeling software-intensive
systems
 ………..
 In 2003, UML 2.0
 ……….
 In 2012, UML 2.5 Adopted

7. UML 2.0 features
 Increased degree of precision in the definition of the language, and
minimize ambiguity.
 improved language organization.
 Large-scale system modeling capabilities
 Improved support for domain-specific specialization
 New diagrams: object diagrams, package diagram, composite structure
diagram, interaction overview diagrams, timing diagrams, profile diagrams.
Collaboration diagrams were renamed to communication diagrams.
 Activity diagram and sequence diagram were enhanced. Activities were
redesigned to use a Petri-like semantics. Edges can now be contained in
partitions. Partitions can be hierarchical and multidimensional. Explicitly
modeled object flow are new.

8. UML Type
Two type of UML:
First: Structure diagrams show the static structure of the system and its parts on
different abstraction and implementation levels and how they are related to each
other.
Second: Behavioral diagrams show the dynamic behavior of the objects in a
system, which can be described as a series of changes to the system over time.

10. UML type
 Class diagrams: are arguably the most used UML diagram type. It is the
main building block of any object oriented solution. It shows the classes in a
system, attributes and operations of each class and the relationship
between each class. In most modeling tools a class has three parts, name
at the top, attributes in the middle and operations or methods at the
bottom.
 Use case: Most known diagram type of the behavioral UML diagrams, Use
case diagrams gives a graphic overview of the actors involved in a system,
different functions needed by those actors and how these different
functions are interacted

11. Continue…..
 Sequence diagrams: in UML shows how object interact with each other
and the order those interactions occur.
 Communication diagram: was called collaboration diagram. It is similar to
sequence diagrams but the focus is on messages passed between objects.
The same information can be represented using a sequence diagram and
different objects
 State machine Diagram: Describes the states an object or interaction may
be in, as well as the transitions between states
 Package Diagram: Shows how model elements are organized into
packages as well as the dependencies between packages

12. Continue…..
 Deployment Diagram: shows the hardware of your system and the software in
those hardware.
 Composite structure diagram: could be used to show:
- Internal structure of a classifier
- A behavior of a collaboration.
 Timing Diagram: are used to show interactions when a primary purpose of the
diagram is to reason about time.