Slide INF205 RPL Pertemuan 8

(1)

UML: Unified Modeling

Language

 _Story:

 _{What UML is for}

 _{Some of the main diagrams are and what you}

use them for

 _{Class diagrams and class forms}  _{Use Case Diagrams}

 _{Sequence (Event) Diagram}  _{State Diagrams}

(2)

UML: Unified Modeling

Language

 _{Developed by the “Three Amigos”: Grady}

Booch, Jim Rumbaugh, Ivar Jacobson

 _{Each had their own development methodology}  _{More or less emphasis on notation and process}

 _{UML is a notation and a process}

 _{Diagrams and notation from UML 1.3 Definition}

(3)

Diagrams

 _{Class diagrams: Represents static structure}  _{Use case diagrams: Sequence of actions a}

system performs to yield an observable result to an actor

 _{Sequence diagrams:Shows how groups of}

objects interact in some behavior

 _{State diagrams: Describes behavior of}

(4)

Class Diagrams

 _{Better name: “Static structure diagram”}

 _{Doesn’t describe temporal aspects}

 _{Doesn’t describe individual objects: Only the overall}

structure of the system

 _{There are “object diagrams” where the boxes} represent instances

 _{But rarely used—other diagrams serve the role of}

describing object interaction better

 _{When used, object diagrams describe static}

(5)

(6)

Notation in Class Boxes

 _{Abstract classes (and operations) in italics}  _{+ is public, - is private, # is protected}

 _{Can also specify stereotypes or}

compartments

 _{“constructors” or “query”}

(7)

Other variations in Class

specifications

 _{Use of}

templates,

interfaces, and types

 _{Can even}

(8)

Components of Class

Diagrams

 _{Multiplicities}

 _{How many of}

each?

 _{Labels to}

indicate how reference is viewed

 _{Role and}

(9)

Navigability and

Aggregations

 _Navigability

 _{Who owns/contains/has who?}  _{Arrows not strictly required}

 _{Aggregation: Open diamond}

 _{“Part-of” relationship, but disagreement}

 _Composition:

closed diamond

 _{Part can only}

(10)

Qualifiers

 _{Serves to describe an instance variable}

(11)

Use Case Diagrams

 _{Means of capturing requirements}

 _{Document interactions between user(s)}

and the system

 _{User (actor) is not part of the system itself}  _{But an actor can be}_another_system

 _{An individual use case represents a task to}

(12)

Simple Use Case Diagram

Reserve book

Borrow book

Return book

(13)

(14)

Use Cases

 _{Are actually defined as text, including}

descriptions of all of the normal and exception behavior expected

 _{Do not reveal the structure of the system}  _{Collectively define the boundaries of the}

system to be implemented

 _{Provide the basis for defining}

(15)

(16)

Sequence (Event) Diagrams

 _{Shows individual objects and how they}

interact

 _Describes

 _{Lifelines of objects}

 _{Who sends what messages when}

 _{Can also describe sending messages to self}

("self-delegation")

(17)

(18)

State Diagrams

 _{Describe all the possible states a}

particular object can get into, and the events that lead to those changes

(19)

(20)

Other Kinds of UML Diagrams

 _{Collaboration Diagrams}

 _{An alternative to sequence diagrams for}

(21)

Other kinds of UML Diagrams

 _{Activity Diagrams}

 _{Alternative to}

(22)

Other kinds of UML Diagrams

 _{Implementation}

Diagrams

 _{Down at the detail}

level

 _{What piece of code}

goes where?

 _{How are they}

(23)

UML in Real Practice

 _{You don't typically use}_all_{the diagrams}

 _{You'll choose between them based on preference and}

particular situation

 _{You typically use}_many_diagrams

 _{A single use case may not capture all scenarios}

 _{If you are going to use statecharts, there are probably}

lots of objects with states

 _{Each sequence/collaboration diagram only shows}_one

(24)

Example: Student Registration

System

 _{Not going to do}_all_{the diagrams}

 _{Not all types, not even all that completely}

specify the system

 _{But this is an application you know, so the}

(25)

Student Registration Class Diagram

*

removeStudent _*_* 1

*

* sectionssections

(26)

Partial Use Case Diagram

Withdraw from a Course

Apply for Admission

Student

Enroll in the University

Enroll in a Course

(27)

States of a Student

EnrollInClass ( Add a Transcript )

Enrolled

Apply [ Must be accepted first ]

Graduate [ All courses must be completed ] AddCourse

Registered

(28)

Sequence Diagram: Registering

for Course

theRegistrar aSection theTranscript

aStudent

state of prereq have prereq

enrolled

enrollInSection:

return sections

getSectionsFor:

addStudent:

enrolled

takenCourse: prerequisite

(29)

Process to Representations

 _OOA

 _{CRC Cards (but they’re not officially UML)}

 _{Use Cases}

 _OOD

 _{Just about all of the rest}

 _{But variations—some detail is later}

 _OOP

(30)

Slide INF205 RPL Pertemuan 8

UML: Unified Modeling

Language

UML: Unified Modeling

Language

Diagrams

Class Diagrams

Notation in Class Boxes

Other variations in Class

specifications

Components of Class

Diagrams

Navigability and

Aggregations

Qualifiers

Use Case Diagrams

Simple Use Case Diagram

Use Cases

Sequence (Event) Diagrams

State Diagrams

Other Kinds of UML Diagrams

Other kinds of UML Diagrams

Other kinds of UML Diagrams

UML in Real Practice

Example: Student Registration

System

Partial Use Case Diagram

States of a Student

Sequence Diagram: Registering

for Course

Process to Representations

UML v1.3 Copyright Notice