Embedded System Design

BITS Pilani Prof. Manoj S Kakade

Dept of EEE
Pilani Campus
 BITS Pilani
Pilani Campus

ESZG512/MELZG526/SEZG516
Embedded System Design
Contact Session 2
CS2 : (Overview of UML)
2  Overview of UML

3 BITS pilani, Deemed to be University under Section 3, UGC Act

UML - Introduction

Modeling System Behavior &

Relationships

Static Behavior

• System Interaction with user – starting point

Dynamic Behavior

• System behavior whiles task execute

• Interaction between threads

BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956

Common UML Diagram

Class Use Case Component Communication

State Chart Timing Sequence Activity

Composite
Object Package Interaction
Structure

Deployment

BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956

Time,PerformanceandQualityof Service

 In 2002, Object Management Group (OMG) adopted the Unified

Modeling Language™ (UML) profile
 Real-Time Profile (RTP): standardized means for
specifying timeliness, performance, and schedulability aspects
of systems and parts of systems
 Profiles provide a minutely specialized form of UML
 Modeling Actions and Concurrency
 Modeling Resources
 Modeling Time
 Modeling Schedulability
 Modeling Performance

Source:Bruce Powel Douglass, “Real-Time UML”

BITS Pilani, Deemed to be University under Section 3 of UGC Act, 1956

Overview of UML Diagram

Diagram Name Used to... Primary Phase

Structure Diagrams
Class Illustrate the relationships Analysis, Design
between classes modeled in the
system
Object Illustrate the relationships Analysis, Design
between objects modeled in the
system; used when actual
instances of the classes will better
communicate the model
Package Group other UML elements Analysis, Design
together to form higher-level
constructs; implementation

BITS Pilani, Pilani Campus

 Overview of UML Diagram

Diagram Name Used to... Primary Phase

Structure Diagrams
Deployment Show the physical architecture of Physical Design,
the system; can also be used to Implementation
show software components being
deployed onto the physical
architecture
Component Illustrate the physical Physical Design
relationships among the software
components; implementation
Composite Structure Illustrate the internal structure of Analysis
Design a class, i.e., the relationships
among the parts of a class

BITS Pilani, Pilani Campus

 Overview of UML Diagram

Diagram Name Used to... Primary Phase

Behavioral Diagrams
Activity Illustrate business workflows Analysis, Design
independent of classes, the flow
of activities in a use case, or
detailed design of a method
Sequence Model the behavior of objects Analysis, Design
within a use case; focuses on the
time-based ordering of an activity
Communication Model the behavior of objects Analysis, Design
within a use case; focus on the
communication among a set of
collaborating objects of an
activity

BITS Pilani, Pilani Campus

 Overview of UML Diagram
Diagram Name Used to... Primary Phase
Behavioral Diagrams
Interaction Overview Illustrate an overview of the flow of Analysis, Design
control of a process
Timing Illustrate the interaction among a set Analysis, Design
of objects and the state changes they
go through along a time axis
Behavioral State Machine Examine the behavior of one class Analysis, Design

Protocol State Machine Illustrate the dependencies among the Analysis, Design
different interfaces of a class
Use-Case Capture business requirements for the Analysis
system and illustrate the interaction
between the system and its
environment.

BITS Pilani, Pilani Campus

Syntax for Use-Case Diagram

 A use case:
 Represents a major piece of system functionality.
 Can extend another use case.
 Can include another use case.
 Is placed inside the system boundary.
 Is labeled with a descriptive verb–noun phrase.

BITS Pilani, Pilani Campus

 Syntax for Use-Case Diagram

An actor:
 Is a person or system that derives benefit from and is external to the
subject.
 Is depicted as either a stick figure (default) or, if a non human actor is
involved, as a rectangle with <<actor>> in it (alternative).
 It is labelled with its role.
 Can be associated with other actors using a specialization/superclass
association, denoted by an arrow with a hollow arrowhead.
 It is placed outside the subject boundary.

BITS Pilani, Pilani Campus

Syntax for Use-Case Diagram

 A subject boundary:
 Includes the name of the subject inside or on top.
 Represents the scope of the subject, e.g., a system or an
individual business process.

 An association relationship:
 Links an actor with the use case(s) with which it interacts.

BITS Pilani, Pilani Campus

 Syntax for Use-Case Diagram

An include relationship:
 Represents the inclusion of the functionality of one use case within
another.
 Has an arrow drawn from the base use case to the used use case.

An extend relationship:
 Represents the extension of the use case to include optional behavior.
 Has an arrow drawn from the extension use case to the base use case.

A generalization relationship:
 Represents a specialized use case to a more generalized one.
 Has an arrow drawn from the specialized use case to the base use case.
BITS Pilani, Pilani Campus
Use-Case Diagram for the Appointment System

BITS Pilani, Pilani Campus

 Syntax for an Activity Diagram

An action:
 Is a simple, non decomposable piece of behavior.
 Is labeled by its name.

An activity:
 Is used to represent a set of actions.
 Is labeled by its name.

An object node:
 Is used to represent an object that is connected to a set of object flows.
 Is labeled by its class name.

BITS Pilani, Pilani Campus

Syntax for an Activity Diagram

A control flow:
 Shows the sequence of execution.

An object flow:
 Shows the flow of an object from one activity (or action) to another activity
(or action).

An initial node:
 Portrays the beginning of a set of actions or activities.

A final-activity node:
 Is used to stop all control flows and object flows in an activity (or action).

BITS Pilani, Pilani Campus

Syntax for an Activity Diagram

A final-flow node:
 Is used to stop a specific control flow or object flow.

A decision node:
 Is used to represent a test condition to ensure that the control flow or object
flow only goes down one path.
 Is labeled with the decision criteria to continue down the specific path.

A merge node:
 Is used to bring back together different decision paths that were created using
a decision node.

BITS Pilani, Pilani Campus

Syntax for an Activity Diagram

 A fork node:
 Is used to split behavior into a set of parallel or concurrent flows of activities
(or actions)

 A join node:
 Is used to bring back together a set of parallel or concurrent flows of activities
(or actions)

 A swimlane:
 Is used to break up an activity diagram into rows and columns to assign the
individual activities (or actions) to the individuals or objects that are
responsible for executing the activity (or action)
 Is labeled with the name of the individual or object responsible

BITS Pilani, Pilani Campus

Activity Diagram for the Manage
Appointments Use Case

BITS Pilani, Pilani Campus

Behavioral State Machine Diagram Syntax

A state:
 Is shown as a rectangle with rounded corners.
 Has a name that represents the state of an object.

An initial state:
 Is shown as a small, filled-in circle.
 Represents the point at which an object begins to exist.

A final state:
 Is shown as a circle surrounding a small, filled-in circle (bull's-eye).
 Represents the completion of activity.

BITS Pilani, Pilani Campus

 Behavioral State Machine Diagram Syntax

An event:
 Is a noteworthy occurrence that triggers a change in state.
 Can be a designated condition becoming true, the receipt of an explicit signal
from one object to another, or the passage of a designated period of time.
 Is used to label a transition.

A transition:
 Indicates that an object in the first state will enter the second state.
 Is triggered by the occurrence of the event labeling the transition.
 Is shown as a solid arrow from one state to another, labeled by the event name.

A frame:
 Indicates the context of the behavioral state machine.

BITS Pilani, Pilani Campus

Behavioral State Machine Diagram

BITS Pilani, Pilani Campus

Sequence Diagram Syntax

An actor:
 Is a person or system that derives benefit from and is external to the
system.
 Participates in a sequence by sending and/or receiving messages.
 Is placed across the top of the diagram.
 Is depicted either as a stick figure (default) or, if a nonhuman actor is
involved, as a rectangle with <<actor>> in it (alternative).

An object:
 Participates in a sequence by sending and/or receiving messages.
 Is placed across the top of the diagram.
BITS Pilani, Pilani Campus
Sequence Diagram Syntax

A lifeline:
 Denotes the life of an object during a sequence.
 Contains an X at the point at which the class no longer interacts.

An execution occurrence:
 Is a long narrow rectangle placed atop a lifeline.
 Denotes when an object is sending or receiving messages.

A message:
 Conveys information from one object to another one.
 A operation call is labeled with the message being sent and a solid arrow,
whereas a return is labeled with the value being returned and shown as a
dashed arrow.

BITS Pilani, Pilani Campus

Sequence Diagram Syntax

A guard condition:
 Represents a test that must be met for the message to be sent.

For object destruction:

 An X is placed at the end of an object’s lifeline to show that it is
going out of existence.

A frame:
 Indicates the context of the sequence diagram.

BITS Pilani, Pilani Campus

Sequence Diagram Example

BITS Pilani, Pilani Campus

Thank you

BITS Pilani, Pilani Campus