3. Introduction
ď‚— The Unified Modeling Language (UML) is a general
purpose visual modeling language that is used to
specify, visualize, construct, and document the
artifacts of a software system.
ď‚— It is intended for use with all development methods,
life cycle stages, application domains, and media.
ď‚— It captures information about the static structure and
dynamic behavior of a system.
4. Characteristics
ď‚— It is standardized and widely accepted today.
ď‚— It is conceptually rich.
ď‚— It is extensible in a standardized, controlled way.
 It’s concise.
 It’s comprehensive.
 It’s scalable.
5. Views
Different UML diagrams provide different
perspectives of the software system to be developed
and facilitate a comprehensive understanding of the
system.
6.  User’s View: This view defines the functionalities
made available by the system to its users.
ď‚— Structural view: The structural view defines the
kinds of objects (classes) important to the
understanding of the working of a system and to its
implementation. It also captures the relationships
among the classes.
7. ď‚— Behavioural view: The behavioural view captures
how objects interact with each other to realize the
system behaviour.
ď‚— Implementation view: This view captures the
important components of the system and their
dependencies.
ď‚— Environmental view: This view models how the
different components are implemented on different
pieces of hardware
8. UML Diagrams
Since UML is a collection of different modeling
types, it divides diagrams into two categories:
ď‚— Structural diagrams
ď‚— Behavioral diagrams
9. Structural UML diagrams
ď‚— Structural diagrams are used to capture the physical
organization of the things in our system i.e., how one
object relates to another.
ď‚— They emphasize the things that must be present in the
system being modeled.
ď‚— They are used extensively in documenting the
software architecture of software systems.
12. Behavioral UML Diagrams
ď‚— Behavior diagrams emphasize what must happen in
the system being modeled.
ď‚— They are used extensively to describe the
functionality of software systems.
13. Behavioral Diagrams Types
ď‚— Activity diagrams
ď‚— Communication diagrams
ď‚— Interaction overview diagrams
ď‚— Sequence diagrams
ď‚— State machine diagrams
ď‚— Timing diagrams
ď‚— Use case diagrams
15. Application Domains
ď‚— Banking and investment sectors
ď‚— Health care
ď‚— Defense
ď‚— Distributed computing
ď‚— Embedded systems
ď‚— Retail sales and supply
16. Applications Of UML
ď‚— Designing software.
ď‚— Communicating software or business processes.
ď‚— Capturing the details about a system for requirements
or analysis.
ď‚— Documenting an existing system, process or
organization.
ď‚— UML provides a vocabulary of diagrams and chart
types to describe almost any application in almost
any domain.
17. Limitations
ď‚— UML is very complex and heterogeneous.
ď‚— A large part of UML does not yet have precise
semantics.
ď‚— Problems in learning and adopting.
Hinweis der Redaktion
Why modeling with UML is usedModeling provides structure for problem solving.if we model system, we may find multiple solutions.Modeling helps us manage complexity of system before actually starting working on system.With various diagrams from UML we can show perfect and clear view of system thus reducing time-to-market for business problem solutions.If we model any problem before its development there are less chances that our development plan will go wrong thus decreasing development costs.Modeling reduces the risk of mistakes.