UML Concepts-2

Nitasha Thakur SG10342

 Sequence Diagrams Collaboration Diagrams Class Diagrams Component Diagrams Deployment Diagrams

Sequence Diagrams
describe interactions among classes. interactions are modeled as exchange of messages.
focus on classes and the messages interaction diagrams

Elements in Sequence diagrams

Class roles: represent roles that objects may play within the interaction. Lifelines: represent the existence of an object over time. Activations: represent the time Messages: represent communication between objects.

*
Object: Class

* A sequence diagram
is * An interaction diagram that details how operations are carried out. * What messages are sent and when. * Sequence diagrams are organized according to time

Operations
Lifeline
6

Message

Sequence diagram for the load piece from production line scenario

crane operator
request

ADMSys

crane PLC

production line

database

send get piece confirm send moving confirm send stopped confirm send clamped confirm send you are loaded send piece removed confirm update piece status

inform

*
*Captures dynamic behavior
(time-oriented)

*Purpose *Model flow of control *Illustrate typical scenarios

*
* Captures dynamic behavior (time-oriented)

Collaboration Diagrams
describe interactions among classes and associations.

interactions are modeled as exchanges of messages between classes through their associations..

Collaboration elements.
Class roles: represent roles that objects may play within the interaction. Association roles: represent roles that links may play within the interaction. Message flows: represent messages sent between objects via links. Links transport or implement the delivery of the message

*
* Captures dynamic behavior (message-oriented)

*
*Captures dynamic behavior
(message-oriented)

*Purpose *Model flow of control *Illustrate coordination of

object structure and control

*
*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

*
Name

Class diagrams show the classes of the system, their interrelationships (including inheritance, aggregation, and association), and the operations and attributes of the classes.
Relations Associations Aggregation Generalization

Attributes Operations
16

*
*Association -- a relationship between
instances 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 link indicating one class is a superclass of the other. -- a triangle pointing to the superclass.
17

*
* Captures the physical structure of the implementation

*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

programmers

*
*shows the physical
dependency relationships (mapping to a file system) between components--main programs, subprograms, packages, and tasks--and the arrangement of components into component packages. *contained (owned) either at the top level of the model or by a package.

*
shows processors, devices, and connections. *Each model contains a single deployment diagram that shows the connections between processors and devices, and the allocation of its processes to processors.

*A deployment diagram

Component Diagrams
organization of and dependencies among software implementation components.
contain components, which represent distributable physical units, including source code, object code, and executable code.

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 or computational resources, including computers, printers, etc.

*
* Captures the topology of a systems hardware

*
*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