what is UML? Unified modeling language (UML) for visualizing, specifying, constructing, documenting of artifact of a software system The blueprint of a system is written in it UML is also used for modeling non-software system It is standard for building object oriented and component based software system UML is a notation system though which we can visualize a model of a system It describe only design or structure of system

1. Presented by Sandip Sitaula

2.  Unified modeling language (UML) for visualizing, specifying,
constructing, documenting of artifact of a software system
 The blueprint of a system is written in it
 UML is also used for modeling non-software system
 It is standard for building object oriented and component based
software system
 UML is a notation system though which we can visualize a model of
a system
 It describe only design or structure of system

3.  In early stages of model driven development there was a great need
for some universal approach for modeling a software system
 As deferent people understand the notation in different way if there
is no universal model approach
 UML is also used for modeling non-software system
 At that time brooch, rumba, Jacobson gave there theories and
universally accepted
 All of three decided to build a notation language by merging all of
three language and out product of that was UML

4.  In 1997 OMG a non profit organization standardized the UML
 Since then they are making improvement in UML

5.  UML is divided into two types
 Structured Modeling Diagram
It depicts the static view of the model
 Behavioral modeling diagram
Behavior diagrams depicts the varieties of interaction within a model as it
'executes' over time

6. Class Diagram
Object Diagram
Component Diagram
Package Diagram
Composite Structure
Deployment Diagram

7. Use case Diagram
Activity Diagram
Communication Diagram
Sequence Diagram
Timing Diagram
Interaction Overview Diagram

8. Author writes chapter.
Reviewer reviews chapter.
Author revises Chapter.
If Book not complete:
 Author writes another chapter.
If book complete:
 Typesetter typesets book.
Author corrects proofs
Typesetter resets book.
Printer prints book

10. You can model just about any type of application
UML is effective for modeling large, Complex software.
It is simple to learn for most developers, but provides
systems.
Advanced Features for expert analysis, designers and
architects.
It can specify system in an implementation- independent
manner.

11. It takes a lot of time to keep the diagram reasonable and
synchronized with the actual code. UML diagrams don’t run,
but require a lot of time. So they are good only if your
organization size can manage them.
You cannot represent every condition in sequence diagram.
It’s impossible if you want to deliver. So state diagram should
convey basic facets, not all possible outcomes.
Good UML software cost money and takes some time to
master properly