Static: Deployment Diagram

• Deployment Diagram: Focus on the

Placement and Configuration of
Components at Runtime
• Captures the Topology of a System’s
Hardware
• Built As Part of Architectural Specification
• Purposes:
– Specify the Distribution of Components
– Identify Performance Bottlenecks
• Main Concepts: Node, Component,
Dependency, Location
• Developed by Architects, Networking
Engineers, and System Engineers
Static: Deployment Diagram
• Deployment Diagram: Focus on the
Placement and Configuration of
Components at Runtime
• Captures the Topology of a System’s
Hardware
• Built As Part of Architectural Specification
• Purposes:
– Specify the Distribution of Components
– Identify Performance Bottlenecks
• Main Concepts: Node, Component,
Dependency, Location
• Developed by Architects, Networking
Engineers, and System Engineers
 Deployment Diagram
• Captures the Topology of a System’s
Hardware
 Deployment Diagram
• Deploy Components onto Nodes

HospitalServer : H
ost
BloodAna
lyzer PatientRe
(COTS) c
Analyzer update DBMS

TechnicianPC : PC
LabAnalyze
results r
 Combining
Component and Deployment
Diagrams
 Dynamic: Statechart
Diagram
• Statechart Diagrams: Tracks the States
that an Object Goes Through
• Captures Dynamic Behavior (Event-
Oriented)
• Purposes:
– Model Object Lifecycle
– Model Reactive Objects (User Interfaces,
Devices, etc.)
– Are Statecharts Complex FSMs?
– Sequence::Time vs.
Collaboration::Message vs.
Statechart::Event
 Statechart Diagram
• Captures Dynamic Behavior (Event-
Oriented)
Statechart Diagram
 Statechart Diagram
• Composite States Illustrated
• Fork and Join Possible
 Statechart Diagram
HCA
pulse not Cuff Deflating
Cuff Inflating detected (2mmHg/sec)
Findin pulse Systoli
g detected c
pulse Pulse Found
pulse not

emergecy
shut-off
detected detected
Finding
Diastolic
Pulse
start Found
Idle
cuff
deflated Cuff Deflating
(max deflation
rate)
Statechart Diagram
 Statechart Diagram
• Captures dynamic behavior (event-
oriented) – states of a particular object

event [guard] / action

(if TRUE)
 Statechart Diagram
• Captures dynamic behavior (event-
oriented)
• Purpose
– Model object lifecycle
– Model reactive objects (user
interfaces, devices, etc.)
• UML state machine diagrams depict the various states that an object may be in and
the transitions between those states. In fact, in other modeling languages, it is
common for this type of a diagram to be called a state-transition diagram or
even simply a state diagram.
• A state represents a stage in the behavior pattern of an object, and like
UML activity diagrams it is possible to have initial states and final states. An
initial state, also called a creation state, is the one that an object is in when it is
first created, whereas a final state is one in which no transitions lead out of.
• A transition is a progression from one state to another and will be triggered by an
event that is either internal or external to the object.

•
• Figure 1 presents an example state machine diagram for the Seminar class during
registration. The rounded rectangles represent states: you see that instances of
Seminar can be in the Proposed, Scheduled, Open For Enrollment, Full, and
Closed to Enrollment states. An object starts in an initial state, represented by
the closed circle, and can end up in a final state, represented by the bordered
circle. This is the exact same notation used by UML activity diagrams, a perfect
example of the consistency of the UML.