The Unified Modeling Language

The Unified Modeling Language

The Unified Modeling Language (UML) is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct, and document the artifacts of a software-intensive system. Grady Booch James Rumbaugh (OMT) Ivar Jacobson (OOSE)
1 2

Building Blocks of UML

Things Relationships Diagrams

Things
Structural things
classes, interfaces, collaborations, use cases, active classes, components, nodes.

Behavioral things
interactions, state machines.

Grouping things
packages.

Annotational things
notes.
3 4

Relationships
Dependency Association Generalization Realization
5

Diagrams
1. 2. 3. 4. 5. 6. 7. 8. 9. Class diagram Object diagram Use case diagram Sequence diagram Collaboration diagram Statechart diagram Activity diagram Component diagram Deployment diagram
6

Structural Things
Structural things are the nouns of UML models. These are the mostly static parts of a model, representing elements that are either conceptual or physical.

Class
Class
A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics.

Attribute
An attribute is a named property of a class that describes a range of values that instances of the property may hold.

Operation
An operation is the implementation of a service that can be requested from any object of the class to affect behavior.
7 8

Use Case
Use case
A use case specifies the behavior of a system or a part of a system and is a description of a set of sequences of actions, including variants, that a system performs to yield an observable result of value to an actor.

Use Case Diagram

Use case diagram A use case diagram shows a set of use cases and actors and their relationships.

Actor
An actor represents a coherent set of roles that users of use cases play when interacting with these use cases.
9 10

Interface
Interface
An interface is a collection of operations that specify a service of a class or component.

Collaboration
Collaboration
Cross between an symbol diagram and a sequence diagram (interaction). Describes a specific scenario Numbered arrows show the movement of messages during the course of a scenario

Billing.exe Billing System

Register.exe

When to use a Collaboration Diagram

When you prefer to show a spatial organization of symbols and interaction rather than concentrating on the sequence of the interaction
11 12

Collaboration Diagram
Node
A node is a physical element that exists at run time and represents a computational resource.
em City

Student DB

tornado Course S cheduling

Enrollm ent

13

14

Behavioral Things
Behavioral things are the dynamic parts of UML models. These are the verbs of a model, representing behavior over time and space.

Behavioral Things (contd)

Interaction
An interaction is a behavior that comprises a set of messages exchanged among a set of objects within a particular context to accomplish a specific purpose.

State machine
A state machine is a behavior that specifies the sequences of states an object or an interaction goes through during its lifetime in response to events, together with its response to those events.

15

16

Grouping and Annotational Things

Grouping things are the organizational parts of UML models. Package
A package is a general purpose mechanism for organizing elements into groups.

Dependency
Dependency
A dependency is a using relationship that states that a change in specification of one thing may affect another thing that uses it, but not necessarily the reverse.

Annotational things are the explanatory parts of UML models. Note

A note is simply a symbol for rendering constraints and comments attached to an element or a collection of elements.
17

ScheduleAlgorithm RegistrationManager

18

Association
Association
An association is a structural relationship that specifies that objects of one thing are connected to objects of another.

Aggregation
Aggregation
An aggregation is a special form of association that specifies a whole-part relationship between the aggregate (the whole) and a component (the part).
Course

Bank Teller

serves

Customer

CourseOffering

19

20

Generalization
Generalization
A generalization is a relationship between a general thing and a more specific kind of that thing. Sometimes it is called an ''is-a-kind-of'' relationship. Employment

Realization
Realization
A realization is a semantic relationship between classifiers, wherein, one classifier specifies a contract that another classifier guarantees to carry out.

Billing.exe

Billing System <<interface>>

Register.exe

Teller

Manager

21

22

Class and Object Diagram

Class diagram
A class diagram shows a set of classes, interfaces, and collaborations and their relationships.

Sequence Diagram
Sequence diagram A sequence diagram is an interaction diagram that emphasizes the time-ordering of messages. This diagram is a model describing how groups of objects collaborate in some behavior over time. The diagram captures the behavior of a single use case. It shows objects and the messages that are passed between these objects in the use case. When to use a sequence diagram A good design can have lots of small methods in different classes. Because of this it can be difficult to figure out the overall sequence of behavior. This diagram is simple and visually logical, so it is easy to see the sequence of the flow of control. A sequence diagram also clearly shows concurrent processes and activations.
23 24

Object diagram
An object diagram shows a set of objects and their relationships.

Sequence Diagram

State Chart Diagram

Statechart diagram
A statechart diagram shows a state machine, consisting of states, transitions, events, and activities. Provides a very detailed picture of how a specific symbols changes states. A state refers to the value associated with a specific attribute of an object and to any actions or side effects that occur when the attributes value changes

When to use a State Diagram

Used when you are working on real-time process control applications or systems that involve concurrent processing When you want to show the behavior of a class over several use cases
25 26

State Chart Diagram

Activity Diagram
Activity diagram
An activity diagram is a special kind of a statechart diagram that shows the flow from activity to activity within a system.

27

28

Deployment Diagram
A Deployment diagram shows the configuration of run-time processing elements and the software components, processes, and objects. Software component instances represent run-time manifestations of code units. Components that do not exist as run-time entities do not appear on these diagrams. These components should be shown on component diagrams.

Component Diagram
A component diagram shows the dependencies among software components, including source code, binary code and executable components. Some components exist at compile time, some exist at link time, and some exist at run time; some exist at more than one time.

29

30

Example
An University wants to computerize their registration system
The Registrar sets up the curriculum for a semester
One course may have multiple course offerings

Actors
An actor is someone or some thing that must interact with the system under development

Students select 4 primary courses and 2 alternate courses Once a student registers for a semester, the billing system is notified so the student may be billed for the semester Students may use the system to add/drop courses for a period of time after registration Professors use the system to receive their course offering rosters Users of the registration system are assigned passwords which are used at logon validation
31

Registrar Professor

Student Billing System

32

Use Cases
use case is a pattern of behavior the system exhibits
Each use case is a sequence of related transactions performed by an actor and the system in a dialogue

Use Case Diagram

Actors are examined to determine their needs

Registrar -- maintain the curriculum Professor -- request roster Student -- maintain schedule Billing System -- receive billing information from registration
Maintain Curriculum Request Course Roster Maintain Schedule 33 Student Maintain Schedule

Request Course Roster Professor

Billing System

Maintain Curriculum

Registrar

34

Sequence Diagram
StudentR ecord E nrollm ent Student StudentId prompt for password password password verified selectCourse getPrerequisites verifyPrerequisites prereqs not met prereqs met addCourse display studentSchedule prerequisites deny enrollment checkEnrollment space available create studentSchedule display studentSchedule StudentSchedule courseOffering

Collaboration Diagram
1: set course info 2: process course form : CourseForm

: Registrar

3: add course

aCourse : Course 4: new course

theManager : CurriculumManager

select another course?

C ourse Enrollm ent

35 36

Classes
RegistrationForm RegistrationManager Course Student ScheduleAlgorithm

Classes
RegistrationForm RegistrationManager
addStudent(Course, StudentInfo)

ScheduleAlgorithm

Course
name numberCredits

Student
name major

open() addStudent(StudentInfo)

Professor CourseOffering Professor

name tenureStatus

CourseOffering
location open() addStudent(StudentInfo)

37

38

Relationships
RegistrationForm RegistrationManager
addStudent(Course, StudentInfo)

Multiplicity and Navigation

ScheduleAlgorithm RegistrationForm 0..* Course
name numberCredits

ScheduleAlgorithm 1 RegistrationManager
addStudent(Course, StudentInfo)

1 0..* Student
major

Course
name numberCredits open() addStudent(StudentInfo)

Student
name major

open() addStudent(StudentInfo)

1 3..10 Professor
name tenureStatus

Professor CourseOffering
location open() addStudent(StudentInfo) tenureStatus

4 1 0..4

1..* CourseOffering
location open() addStudent(StudentInfo)

39

40

Inheritance
RegistrationForm RegistrationManager
addStudent(Course, StudentInfo)

State Transition Diagram

ScheduleAlgorithm Add Student / Set count = 0 Add student[ count < 10 ] Initialization
do: Initialize course

Open
entry: Register student exit: Increment count

Course
name numberCredits

RegistrationUser
name

Student
major

Cancel Cancel Canceled

do: Notify registered students

open() addStudent(StudentInfo)

[ count = 10 ]

Professor
tenureStatus

Cancel CourseOffering
location open() addStudent(StudentInfo)

Closed
do: Finalize course

41

42

Component Diagram
Billing.exe Billing System Register.exe

Deployment Diagram
Registration Database

People.dll Course.dll
Course User

Library Student Course Course Offering Professor Dorm

Main Building

43

44