1. Introduction to UML

2. UML The UML is a language for
visualizing
specifying
constructing
documenting
the artifacts of a software-intensive system
UML can also be applied outside the domain of software development.

3. ~ U
Unified:
Unification of earlier object-oriented analysis and design methods.
Same concepts and notation for different domains and development processes.
Same concepts and notation through the whole development lifecycle. ~ M
Modeling:
Making a semantically* complete abstraction of a system. (* The formal specification of the meaning and behavior of something) L ~
Language:
A graphical language

4. Software Engineering Methods
Most methods consist of both a modeling language and a development process (who is doing what and when).
A modeling language, typically include some visual language.
A tool to support the method is crucial.

5. UML Is Not a Development Process
A development process defines: Who is doing What, When to do it, and How to reach a certain goal
The UML is intentionally process independent - different domains may require different processes.
But the UML authors promote a development process that is use-case-driven, architecture centric, iterative and incremental. (Example of method: RUP)

6. Looking back in time: Three of the most popular methods
Object Modeling Technique, OMT, introduced by Jim Rumbaugh. OMT is considered to be strong on analysis and weaker in the design area.
Booch, introduced by Grady Booch (Rational Software). This method is considered to be strong in design and weak when it comes to analysis.
OOSE, (use cases ) introduced by Ivar Jacobson. OOSE is considered to be strong when it comes to behavior analysis and weaker in the other areas.

7. Business Process Modelling Notation (BPMN) is a graphical representation for specifying business processes in a workflow.
The Systems Modeling Language (SysML), is a Domain-Specific Modeling language for systems engineering. It supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems. SysML was originally developed by an open source specification project, and includes an open source license for distribution and use. SysML is defined as an extension of a subset of the Unified Modeling Language (UML) using UML's profile mechanism.

8. The Value of UML Open standard. Supported by many tools.
Supports the entire development lifecycle.
Support diverse application areas.
Based on experience and needs of the user community.

9. UML Is Based on Object-Oriented Concepts
Class and Object as Defined by Booch, Rumbaugh and Jacobson
Class: A description of a set of objects that share the same attributes, operations, relationships, and semantics.
Object: A concrete manifestation of an abstraction; an entity with a well defined boundary and identity that encapsulates state and behavior; an instance of a class.

10. Diagrams
A diagram is typically a view of a part of the model and a diagram does not have to be complete, some elements may be missing or presented in a simplified fashion.
UML: ”A well-formed model is one that is semantically self-consistent and in harmony with all related models.”

11. There are 13 types of diagrams in UML 2.0
Use Case Diagrams
Package
Diagrams
Activity Diagrams
Deployment Diagrams
Class Diagrams
Component
Diagrams
Composite
Structure Diagrams
Statemachine Diagrams
Object Diagrams
Model
Timing Diagrams
Sequence Diagrams
Interaction
OverView Diagrams
Commun-
ication* Diagrams
* Communication diagrams was called Collaboration diagrams in UML 1.x