Why do we model?
Model is a simplification of reality.
Provides blueprint of sys.
May be structural or behavioural.
Modeling-For better understanding of sys.that are
Achieve 4 aims:
1. Helps to visualize sys.
2. Permits to specify struc or behav of sys.
3. Provide templates to guide in constructn sys.
4. Document decisions made.
Applications of UML
Enterprise infmn sys.
Banking and financial services.
Distributed Web-based services
Building blocks of UML
Things in the UML:
1. Structural things
2. Behavioral things
3. Grouping things
4. Annotational things
4. Use case
5. Active class
a description of a set of objects that
share the same attributes,
operations, methods, relationships
Collection of operation that specify
service of a class or
visible behavr of an element.
Defines interactn and is a society of
roles and other elements that work
together to provide some cooperative
behavr that’s bigger than sum of all
Have structural and behavioral
Description of set of sequence of
action that a sys performs.
Used to structure the behavioral things
in a model
A class whose objts own one or more
processes and therefore intiate cntrl
Physical and replaceable part of a
system that conform to and provides
realizn of a set of interfaces
a run-time physical object that
represents a computational resource.
A set of msgs exchangd
among a set of objts vd in
a particular context to
accomplish a specific
other elements including
Specifies sequences of
state of an objt goes thru
during its lifetime
response to those
other elements includn
Organizational parts of UML models.
Models decomposed in to boxes
Primary kind is Package
Packages are basic grouping things with which UML
model can be organized.
Explanatory parts of UML models.
Comments to describe illuminate or remark about
any element in a model.
Primary kind of annotation thing called note.
Note is simply a symbol for rendering constraints
and comments attached to an element or collection
II. Relationships in the UML
a relationship between two modeling
elements, in which a change to one
modeling element (the independent
element) will affect the other modeling
element (the dependent element).
a relationship between two or more
classifiers that involves connections
among their instances.
Aggregation is a spl kind of assocn
represntn structural reltnshp b/w
whole and its parts
generalization Objts of specialized element(child) are
substitutable for objts of the
a relationship between a specification
and its implementation.
III. Diagrams in the UML
3.Use case diagram
It depicts the static view of a model
It is the basic building block of the object oriented system
It illustrate the relation ship between classes in the system
Class diagram consist of:
It consist of rectangle with three compartments
Class name is added in this this compartment (teacher)
Class attribute is added in this department (name )
Class methods are placed in this compartments (teach)
• Object diagrams emphasize the relationship
between instances of classes at some point in time
Object is shown by a rectangular with classifier
name in the center f rectangular and under line.
3.USE CASE DIAGRAM
This diagram consist of:
It is represented by a human, either the actor is a human
Or and external system.
Actor is role
It is represented by an oval shape with title in it
Sequence diagrams provide a graphical
representation of object interactions over time
The diagrams show the flow of messages from one
object to another, and as such correspond to the
methods and events supported by a class/object.
Type of an interaction diagram emphasizes structural organization of objt that
send and receive msgs
Collaborates the static and dynamic relationship
Each message in a collaboration diagram has a sequence number.
A statechart diagram shows the possible states of the object and the transitions that
cause a change in state.
States are rounded rectangles.
Transitions are arrows from one state to another.
Events or conditions that trigger transitions are written beside the arrows.
Activity diagram is also dynamic view of the system
Activity diagram is used to describe the individual use case
Use case is used to describe the user goal
Activity diagram’s similar to flow charts
Each activity consist of series of actions
Actions are represented by oval shapes
Actions are connected by arrows
Arrow shows the flow of the activity diagram
Activity diagram also shows decision points called decision
• Shows the organizations and dependencies among software
Shows system in terms of modules.
Shows the configuration of run-time processing elements
and the software components, processes and objects that
live on them.
Deployment diagrams may be used to show which
components may run on which nodes.