UML Basics

and G2 compatibility (SDL/MSC to UML)

Project example
Coffee Machine

available at:
http://www.omg.org/uml
Examples
Introduction in TAU G2
UML language description
TAU G2 environment
TAU G2

installation

a single, standardized, powerful language for precisely describing
systems design and

software design, which can be interchanged with other
UML 2.0 users.

• How cans UML 2.0 help create effective solutions?
It gives systems engineers a way to visually define the information they want
to describe, such as architecture, interfaces, and functional requirements.
However, this visual description is more than pictures; it is precise and can be
automatically checked.

• How does UML 2.0 help manage technical complexity?
It gives systems engineers the means to visually describe technically complex
information, in ways which reflect the development process, completely
specify the behavior of complex systems and can be tested during design creation.

• How else cans UML 2.0 help systems engineers?
It increases reuse within and between projects, through reuse of design
components, and as a reusable common language between systems engineers
and software developers and testers.

of actors interacts in terms of use cases, usually in

the context of a subject (the described system).

Architecture diagram (composite structure diagram) - Describes how parts of a (container) class are connected to each other to form an internal structure of the container.

Class diagram - Declares classes and their relations to each other, typically in the scope of a package or another (container) class.

for a use case or an operation.


State Chart Diagram -

Defines the behavior of classes, state machines and operations.


Text diagram - Defines an entity textually (textual stubs)

presentation elements and their relations. Package diagrams can exist in

packages and classes.

Interaction Overview diagram - An interaction overview diagram describes some form of parallel behavior. It is often used to describe a use case.

Activity diagram - An activity diagram can show parallel and intertwined behavior. This may allow a simplified view of a complex structure where it is possible to focus on a specific flow of control.

primarily focused on the design of components and shows relations

and structure of components.

Deployment diagram - The deployment diagram can be used to show how the physical implementation is structured and the relations between software and hardware.

emphasizes the behavior as it appears to outside users. A

use case model partitions system functionality into transactions (‘use cases’) that are meaningful to users (‘actors’). Environment can play actor role.
Use case diagram: a diagram that shows the relationships among actors, use cases and the subject system.
Notes: - Use case diagram can define scenarios for different modes of target application - Use case descriptions can be specified by text and/or interaction diagrams

Structure Diagram.
• The Architecture Diagram is used to show:
– The

internal run-time structure of an active class.
• This is done using:
– Instances of active classes that are attributes of the containing class.
– The interface points of these active classes.
– The communication channels between the instance interface points.
– The discrete packages of information that are exchanged by the instances along the communication channels.

share the same attributes, operations, methods, relations and semantics.

Class diagram:

A diagram that shows a collection of declarative (static) model elements, such as classes, types and their contents and relationships.
Class diagram should:
Emphasize a particular of the structural model
Contain classes at the same level of abstraction

for
capturing requirements, design, traces, test cases and test suites

A Sequence Diagram is a variant of an Interaction Diagram.
It consists of a set of entities and the Messages that are communicated
among them.

A Sequence Diagram focuses on the time ordering (sequence) of the
interchanged Messages.

Mealy-type machine, where the output depends on both the present

state and the inputs.
• It normally sits waiting in a State until an Event occurs, usually the reception of a Signal.
• If the received Signal is not somehow explicitly handled by the current
State, then the Signal is discarded, i.e., thrown away.
• If the Signal can be handled by the current State, then
– the Signal is “consumed”
– the corresponding Transition is taken
– any actions (including outputs) are executed
– the State Machine enters its Nextstate.

trying to describe advanced algorithms.

Capturing such functionality in textual form

provides a concise way of describing them.

– Easier to read
– More comprehensible
– More maintainable
– Significant savings in diagram size (page Real Estate)

different entities.

• A Package defines a new scope unit (namespace).
•

A Package is normally used to organize elements into groups.
– It can also contain other Packages.

• Packages allow control of visibility and access rights to their elements.
– Better compartmentalization.
– Decreased coupling.
• Everything in UML is ultimately contained in one Package or another.

Diagrams that define interactions in a way that promotes overview

of the control flow.

Interactions focus on the communications between instances, using message passing to express operation invocation and signal sending
Interactions are used
during analysis, to improve individual or group understanding ofinter-object behavior
during design, to precisely describe inter-process communication
during testing, the traces can be compared with those described in the earlier phases.

flow

Activity modeling emphasizes the sequence and conditions for
coordinating other

behaviors, using secondary constructs to show which
classifiers are responsible for those behaviors.

Typical applications of Interactions include:
– process modeling (business, physical)
– workflow modeling
– requirements

+ +
Sequence Diagram

+ + +
Interaction Overview Diagram + + +
Activity Diagram + +
State Machine Diagram + +
Class Diagram + + +
Component Diagram +
Deployment Diagram +
Package Diagram + + +

button is pressed - request shall be ignored
if the

tea or coffee making process is in progress and “Tea” or “Coffee” button is pressed - request shall be ignored
if a coin with the value of 5 is inserted and the “Tea” button is pressed, the tea making process begins
if a coin with the value of 10 inserted and the “Tea” button is pressed, the customer receives a change and the tea making process begins
if a coin with the value of 5 is inserted and the “Coffee” button is pressed, user receives a change and the coffee making process ignored
if a coin with the value of 10 is inserted and the “Coffee” button is pressed, the coffee making process begins

Requirements specification