UML Concepts

7/30/2019 UML Concepts

1/26

UMLConcepts-2

Nitasha Thakur

SG10342


2/26

Sequence Diagrams Collaboration Diagrams

Class Diagrams

Component Diagrams

Deployment Diagrams


3/26

Sequence Diagrams

describe interactions amongclasses.

interactions are modeled as

exchange of messages.

focus on classes and the messages

interaction diagrams


4/26

Class roles: represent roles that objectsmay play within the interaction.

Lifelines: represent the existence of anobject over time.

Activations: represent the time

Messages: represent communication

between objects.

Elements in Sequence diagrams


5/26

*


6/26

6

*

*A sequence diagramis

* An interactiondiagram that detailshow operations arecarried out.

*What messages aresent and when.

* Sequence diagramsare organizedaccording to time

Object: Class

Lifeline

OperationsMessage


7/26

send you are loaded

send get piece

ADMSys

productionline database

request

crane PLC

send moving

send clamped

confirm

confirm

confirm

send stopped

confirm

send piece removed

confirm

update piece status

inform

craneoperator

Sequence diagram for the load piece from production line scenario


8/26

*

*Captures dynamic behavior(time-oriented)

*Purpose

*Model flow of control

*Illustrate typical scenarios


9/26

*

*Captures dynamic behavior (time-oriented)


10/26

Collaboration Diagrams

describe interactions amongclasses and associations.

interactions are modeled as

exchanges of messagesbetween classes through their

associations..


11/26

Collaboration elements.

Class roles: represent roles that objectsmay play within the interaction.

Associationroles: represent roles thatlinks may play within the interaction.

Message flows: represent messages

sent between objects via links. Linkstransport or implement the delivery of

the message


12/26


13/26

*

*Captures dynamic behavior (message-oriented)


14/26

*

*Captures dynamic behavior

(message-oriented)

*Purpose

*Model flow of control

*Illustrate coordination ofobject structure and control


15/26

*

*Captures the vocabulary of a system*Built and refined throughout development

*Purpose

*Name and model concepts in the system

*Specify collaborations

*Specify logical database schemas

*Developed by analysts, designers, and

implementers

*


16/26

16

*Class diagrams show the

classes of the system,

their interrelationships(including inheritance,

aggregation, and

association), and the

operations and

attributes of the classes.

Name

Attributes

Operations

Relations Associations

Aggregation

Generalization

*


17/26

17

*

*Association -- a relationship betweeninstances of the two classes.

*Aggregation -- an association in which

one class belongs to a collection.--diamond end pointing to the part

containing the whole.

*Generalization -- an inheritance linkindicating one class is a superclass of theother.

-- a trian le ointin to the su erclass.

*


18/26

*

*Captures the physical structure of the implementation


19/26

**Captures the physical structure of the

implementation*Built as part of architectural

specification

*Purpose

*Organize source code

*Construct an executable release*Specify a physical database

*Developed by architects and

ro rammers

*


20/26

*

*shows the physicaldependency relationships(mapping to a filesystem) between

components--mainprograms, subprograms,packages, and tasks--andthe arrangement of

components intocomponent packages.

*contained (owned) eitherat the top level of the

model or by a package.


21/26

*

A deployment diagramshows processors,devices, andconnections.

*Each model contains asingle deploymentdiagram that shows the

connections betweenprocessors and devices,and the allocation ofits processes toprocessors.


22/26

Component Diagrams

organization of and dependencies

among software implementation

components.

contain components, which

represent distributable physical

units, including source code, objectcode, and executable code.


23/26

Deployment Diagrams

describe the configuration of

processing resource elements and

the mapping of software

implementation components onto

them.

contain components and nodes,

which represent processing orcomputational resources,

including computers, printers,

etc.


24/26

*Captures the topology of a systems hardware

*


25/26

*

*Captures the topology of a systems

hardware

*Built as part of architectural

specification

*Purpose

*Specify the distribution of

components

*Identify performance bottlenecks

*Developed by architects, networking

engineers, and system engineers


26/26

Documents

UML Concepts