UML

Case Use

administrator
18:47 2010 .27

Use case diagrams

use case :

actor

value

Use case
.

Actor .

actor

: Actor

actor (arrowhead ) use case

. actor actor use case

use case

use case Association . . .

actor

Association
use case . ) box

data flow :( release use case (packages ) :( )

. . . . 3 . 2 ( use case

system boundary box Box . . ) use case UML box

use case

UML

file folders . 1

. . (association) .( use case use case actor case use use case actor . . use case . actor) actor seminar . . . case use activity diagrams UML . actor use case arrowhead . use case association arrowhead case use

1 association (4 ) seminar association

Seminar Enroll

arrowhead

registrar

use case

use case

Actor

use case

:1

release

System boundary boxes

:2

use case

package

:3

use case
. use case use case use case (association lines ) . actor actor . arrowhead . (information flow ) . actor use case actor

use case

actor

." actor

" .

use case . . Model With Others

"hardware interrupt " UML Inheritance

extend " . "

. Include

use case

(inheritance

include

extend ) . class diagrams

extending use case Reuse in Use Case Models

.use case

:4

Agile
. stakeholder . . . 5 . 5 (representation ) use case modeling agile use case AM .

:5

use case .case system use essential/business use case

use case .

: Case Diagrams UML Use

administrator
13:01 2010 .30

(UML Use Case Diagram (UCD

. flow chart sequence diagram . UCD . sub-action systems action . UML Use Case UCD

case use
.

actor :

UCD

) .(

top-down

UCD

database

task

UCD

task

(error

) .

UCD Sequence

(branching behaviors )

(exception cases )

TCP/IP . (conditional functionality)

UCD

UCD
actor " Actor's Actions" . : actor component

actor
Action/Response "System's Response "

) . actor actor ( .(

actor actor legacy system .(

sequence agent ) database ) .

. . actor

database

System" box "

( . : UML Use Case actor . system box ) system box Use case

session

actor

use case .

use case ).

" Close Shutter " " take picture"

" "Flash Open Shutter"" use case

use case . . (.

shutter

.
UCD . . actor actor actor

actor

. actor : . . .

.
(top-down) . chart flow sequence UCD . UCD . use case .( (simple branching conditions ) UML Use Case Diagram . )

flow chart
. flow chart

UML Use Case Diagram

UCD . develop

. use case . feature set . flow chart flow chart UC . . flow chart use case : use case . UCD

UCD

.( .

):

uses arrow
X subtask case Y use use case . use case use case X (extends

edge) extends arrow

. Y

. ( " " . : . ( ) " " UML . . )

a common, more general process extend both processes

extend
:

use

" Y"

"X "

" Y"

"X "

"Y

uses X"-

" Y" . Y

"X "

" Y"

"X "

"Y

extends X"X Y

UCD

" Assign a seat " .

"luggage Weigh "

"Check-in " use case use case

. )

uses
. ( . :

extends

extends

Diagrams Use Case

Case Use grey-area use case

error

chart flow Case Diagram Use

Sequence branching . : diagramming . Diagram

. use case Use case

FLOW CHART
(

UCD ) use case . . extend

UCD

branching use case :

extension extends

Branching .( )

use case use case

CD . CD play .( . CD CD extend

CD player .( ) CD . CD CD CD

. play play .

CD Player use case) CD

use case CD

use case CD

5.0

UML administrator
18:31 2010 .6

) /

UML 2 class diagram . diagram Class . .

UML

class diagrams)) (association aggregation .

class diagram .

Class diagram class diagrams

UML class diagram

y y y

Conceptual Class
Class . attribute . class box .( UML class diagram . (Artifact(s CRC . . ) UML class diagram attribute 1

.1

CRC mode

ORM

Apply the Right AM s

diagram
.

class diagram

:1

attribute .( 2

association ) refactore . . . associative 2

(associative) notion) association ) association

Enrollment

stakeholder

List Waiting
. association .

Seminar
0 .

attribute :

associative UML 2.0 .

. association property

1 association operation

2 Attribute

attribute

Create Simple Content

association enrollment object

. association association . . .

association

waiting list on

enrolled in .
student association

Enrollment Student

student professor

Seminar Enrollment Seminar

.

association

enrolled in
association

Professor

instructs

. .

Method Name Attribute Name

(Visibility) . .

attribute

Standards Apply Modeling AM s

attribute 2 .

association .

(multiplicity) . stakeholder

Student Seminar

association

{ordered

FIFO}
.

UML constraint FIFO

. predicate

UML constraint description

UML

Constraint

. UML Constraint . calculus

{constraint description }

Class Diagram

.2

Class Diagram
: conceptual class diagram

.3

Association

Composition association Vocabulary

y y y y y y

design class diagram

Association

Composition association Interface

y y y y y y

.3.1
( attribute ) . . Object . object template object .( object ) .

Student

.3.2
. attribute .( . . object . attribute attribute attribute) ( . . . procedure function object ) object :

address

attribute .

student
attribute

Address
.

4 : . . develop . 2

Student Student

Address

.(

Address

(Conceptual

class diagram)

:4

responsibility

Is Eligible to Enroll

Student
. responsibility .

use system Enroll in Seminar

Enroll Determine Eligibility to BR129

.

case
2

" class normalization " 5

refactore .

refactore

Seminar

refactore " Computer Science CSC 148 Introduction to " " CSC 148 " data value ()getFullName develop .

Course
setter getter

fees name
. )

" Science Introduction to Computer " .(conceptual class diagrams

courseNumber
.

getter

.(diagram Conceptual

class)

:5

setter

getter

Course
setter

design setter getter . . setter getter value

getter

accessor

association .3.3
: association association . . 2 .

6 . . .

UML class diagram association association

association .

association

:6

association : multiplicity) association ) .( . association .

0..1 1 0..* 1..* n > 1) n > 1) n > 1) n( n( n( n 0..n 1..n

. association . (symbol ) . 5 ." .

association

Course

Seminar
" "

offering
":

arrowhead .

arrowhead drop

association association arrowhead

(arrowhead) .

value

role

association

(context )

role .

association

association .

Depict Models Simply AM practice

association role .

association

.3.4
. is like A . . A is a B B arrowhead . A UML B . A . . " " B .

. . 7 : . (italics ) (abstract )

Professor Student Person Student Person

. 2

Person
(concrete ) .

Person
.

(inheritance hierarchy) capture

. .

parent

Purchase Parking Pass Person

Person
.

Professor Student

:7

Composition Association .3.5

8 ) . aggregation UML 2 .( . ( ) . composition composition

composition

:8

composition . .

"

"

" part of" . composition

. .

association

composition coding

(Craig Larman (2002 composition association

composition

:9

capture

(semantics )

single section . UML 1.x .( ) . set ( ) . .generalization set ) UML 2.0 generalization set . discriminator generalization set .( sub generalization generalization " " . set set set

y y y y y

Gender

Role

Nationality :

Person

set

Role Student
exclusive set

discriminator

XOR constraint

Class Diagram RUP

UML

administrator
18:15 2010 .7

Class diagram .

UML

class diagram

domain

domain

y y y

class diagram :

Composition

Aggregation

y y y y y y

.1
. . class diagram class diagram (style )

:1

association

:2

. Diagrams Identify Responsibilities on Domain Class .Indicate Visibility Only On Design Models . Indicate Language-Dependent Visibility With Property Strings .Indicate Types Only On Design Models .Requirement Indicate Types On Analysis Models Only When The Type is an Actual

.1 .2 .3 .4 .5 .6

Order

design version

.Design Class Diagrams Should Reflect Language Naming Conventions

()calculateTaxes dashed line .

placementDate
association class UML

convention Java programming

. 2 dashed line . Model Association Classes On Analysis Diagrams association association .8 .9 .7

Do Not Name Associations That Have Association Classes Center The Dashed Line of an Association Class

Class Style
Student
(interface) . Bill John Doug instance . . . template .

.2

scaffolding

OrderItem

:3

Use Common Terminology for Names Prefer Complete Singular Nouns for Class Names Name Operations with a Strong Verb Name Attributes With a Domain-Based Noun Scaffoldin . code scaffolding .Do Not Model Scaffolding Code

.1 .2 .3 .4 .5

OrderItem

. .6 .7 .8 .9 .10 .11 .12 .13 .14 Label Uncommon Class Compartments

Never Show Classes With Just Two Compartments Include an Ellipsis ( ) At The End of Incomplete Lists

List Static Operations/Attributes Before Instance Operations/Attributes List Operations/Attributes in Decreasing Visibility For Parameters That Are Objects, Only List Their Type Develop Consistent Method Signatures Avoid Stereotypes Implied By Language Naming Conventions . UML property string .Indicate Exceptions In An Operation s Property String

(Interface)
UML parlance interface . interface component interface . component interface interface component /

.3
interface component .

UML class diagram

interface :5

interface

standard class box

.Interface Definitions Must Reflect Implementation Language Constraints .

.1

PersistentObject
.2 .3 .4 .5 .6

Name Interfaces According To Language Naming Conventions Interface Apply Lollipop Notation To Indicate That A Class Realizes an Define Interfaces Separately From Your Classes

Shipment

.Do Not Model the Operations and Attributes of an Interface in Your Classes . interface Contract Consider an Interface to Be a

(Relationship)
realization inheritance dependency composition aggregation . association UML UML class diagram relationships

.4

order

Shipping :6

order

Modeling :7

:8

:9

Collaboration Indicates Need for a Relationship Model a Dependency When The Relationship is Transitory

.1 .2

dependency

Order

Delivery
tree configuration

.Depict Similar Relationships Involving A Common Class As A Tree dependency . .

.3

OIDGenerator
clutter .4 .5 .6 * Avoid a Multiplicity of

Always Indicate the Multiplicity

shippingAddress

.Replace Relationships By Indicating Attribute Types scaffolding

Address
.7 .8 .9 .10 .11 .12 .13 .14 .15 .16 .17 .18 Center Names on Associations

Do Not Model Implied Relationships Do Not Model Every Single Dependency Write Concise Association Names In Active Voice Indicate Directionality To Clarify An Association Name Associations In The Same Direction Name Unidirectional Word Association Names Left-To-Right Indicate Role Names When Multiple Associations Between Two Classes Exist Indicate Role Names on Recursive Associations . 9 association

lives at .Directions Make Associations Bi-Directional Only When Collaboration Occurs In Both
Something Changes Redraw Inherited Associations Only When Question Multiplicities Involving Minimums And Maximums

.6
"A " UML " B" . " A" " . " . "B" " A" . is like " A" (arrowhead ) is a " B" "B "

Apply the Sentence Rule For Inheritance Place Subclasses Below Superclasses Beware of Data-Based Inheritance A Subclass Should Inherit Everything

.1 .2 .3 .4

Composition
delivery shipment (whole-part) whole . . . ( ) aggregation Aggregation . " " " " . is part of association

Aggregation
. . shipment aggregation composition package Composition . aggregation

.7

association

.composition

aggregation

:10

Apply the Sentence Rule for Aggregation You Should Be Interested In Both The Whole And The Part Depict the Whole to the Left of the Part Apply Composition to Aggregates of Physical Items Share The Persistence Lifecycle With the Whole Apply Composition When the Parts Don t Worry About Getting the Diamonds Right

.1 .2 .3 .4 .5 .6

5.0

Sequence Diagram

RUP

UML
administrator 13:12 2010 .9

interaction Sequence diagram . . procedural logic Sequence diagram .

interaction diagram trigger

sequence diagram

(Lifeline)
. . sequence diagram diagram sequence classifier (individual participant ) " self" .

entity

control boundary

actor

sequence diagram .

signal

call .

(Execution Occurrence)

. .

Self Message
nested focus . call . self message

. . .

stop .

. . .

. . action .

. . processing sequence

sequence diagram . heading :

. . . .

if then else switch

construct alt")") construct opt")") break (" par") (" seq ")

y y y y y y y y y y y y

. . . . . . . (operand) . : ignore ignore consider (" assertion ("assert ("strict") (" neg ")

(loop)

"ref"

interaction occurrence .

. frame

(interaction occurrence) frame

(Gate)
fragment frame . EA . fragment diagram sequence fragment off-page . . box shape render connector .

Part Decomposition . lifeline .

State Invariant / Continuations

. . true lifeline constraint state invariant

(stretch)

lifeline

state invariant

continuation

5.0

. Currently 5.0/5 Stars

UML

administrator
14:55 2010 .15

Unified Modeling
IT .

OMG) ) (Object Management Group)

UML IT . . (UML) UML .

1997 (Language UML

UML UML UML . . . UML (visual)

75

. . UML

UML .

21

Jacobson Ivar Jim Rumbaugh UML .

. .(Booch . . OOSE OMT ) UML .

UML Grady Booch

Process "IBM Rational Unified IBM UML . UML class diagram use case diagram : UML . deployment diagram .

" artifact"

UML .("lingo

UML

omponent diagram activity diagram diagram statechart sequence diagram

Use-case diagram
development use use use use case use case ( . . ) actor use case use case use case . actor . use case use-case ( use case . ) actor case case case . use case

use-case diagram :1

1 . Billboard CD

. Billboard 200 . . CD

use case . Billboard 200 (Billboard (Billboard Reporting Service

Billboard 200

. use case . .

use case .

Class diagram
class diagram CD rock)) . logical classes diagram . HashMap Vector . static business Class diagram . implementation class diagram . implementation class diagram ( ) logical

.2 . ( )

class diagram

class object :2

diagram class class .

. . association superclass class association 3

class object

class diagram

:3

CD .

CDSalesReport .

Report

CDSalesReport Band

. CD

association CDSalesReport

3 CD

class diagram

Sequence diagram
. use case . use case Sequence diagram sequence

sequence diagram .

.(4 class

) .

class instance

) ) class instance

sequence diagram class instance instance class instance .

class instance

.(myReportGenerator : ReportGenerator : .

" : " space/colon /space

. .

sequence

" class instance "driver 4

sequence diagram : .

sequence diagram

sequence diagram

:4

aServlet . generateCDSalesReport cdId CDSalesReport aServlet aCDReport gen aServlet

driver aServlet

Sales CD . gen cdId generateCDSalesReport

sequence diagram ReportGenerator class instance . gen instance . . aCDReport . gen

generateCDSalesReport CDSalesReport sequence .

generateCDSalesReport aCDReport

diagram sequence

sequence diagram : . nested calls

Statechart diagram
. . " " . statechart diagram

: statechart diagram .

diagram statechart .

Statechart

:5

" " " " "

. . " " . " " " " .

statechart diagram . . "

Activity diagram
Activity diagram . . . activity diagram . . action activity diagram sequence diagram activity diagram

statechart diagram . . . 6

statechart diagram

activity diagram . swimlane .

:object

swimlane

Activity diagram

:6

. activity diagram .

: .

swimlane

activity diagram .

Component diagram
. : ) Java ]. component (component (component package level (System.Web.UI ) NET . dependency . component component package level . (java.util

Servlet 2.2 API Billboard JDBC API

: component

component

component diagram component . .JDBC API

Servlet 2.2 API Service Billboard

component

interdependency component diagram :7

.

Deployment diagram
component . . runtime .

Node . sequence

node . node

diagram component node .

deployment diagram diagram

(" w3reporting.myco.com : Application Server"

) [instance name] : [instance type]

diagram Deployment :7

Reporting . .

HTTP w3reporting.myco.com Application Server . IBM WebSphere node w3.reporting.myco.com

deployment diagram Tool component

Reporting Tool

DB2 SOAP component .

Java language to IBM DB2's JDBC interface db1.myco.com .

Reporting Tool HTTPS

native DB2 communication Billboard Service

UML UML .

UML UML

5.0

. Currently 5.0/5 Stars

UML

administrator
15:20 2010 .15

. . " " . :

. flowchart .

y y

. (depict ) . document .

. . capture

. . (redundancy)

capture

UML document

. UML . . UML (notation)

UML .

depict .

!" Jacobson

": Booch Rumbaugh .

" . . ! . UML . UML

UML

"

. UML use case . .

UML . " " UML

UML UML

(dependency) . NET . J2EE .

UML

Rational

UML

UML

UML .

UML Design Patterns Unified Process

UML
9 UML . capture : UML . UML

" actor"

. . use case actor case use .

:Use

case diagram

"use cases "

actor . " has-a"

. " is-a " . " " .

use case

refine . .

:(Class

Diagram)
use case diagram " attribute)) "

object capture

object

:Object

diagram
.

diagram object .

object object state diagram . . capture

state diagram

:State

diagram

Object .

activity diagram

state diagram

capture .

activity diagram

:Activity

diagram

. .

sequence diagram sequence diagram

. Object .

object object

:Sequence

diagram

. . object object

object

collaboration diagram collaboration diagram .

:Collaboration

diagram

. .

:Component component diagram .

diagram

Capture

:Deployment

diagram
.

UML

UML
. : : UML .

. . .

: : :

y y y
UML

o
Use case diagram

Class diagram

o
Object diagram

State diagram

Activity diagram

Sequence diagram

Collaboration diagram

o
Component diagram

Deployment diagram

UML
view 1+4 . . . UML UML "view 1+4" view 1+4 . . UML UML

1+4

view

view

view

. .

view

view

:Design

View
object

design view

activity diagram state diagram

process view
. view

:Process collaboration diagram

View

sequence diagram

component view

:Component .

View

component

UML

view

:Deployment

View

UML

Use case

use case view

:Use

case View
.

UML

UML .

4.3

. Currently 4.3/5 Stars

Collaboration Diagram

: UML

administrator
14:06 2010 .16

Collaboration diagram . :

sequence Collaboration diagram .

UML OO

collaboration/communication (message flow )

.(real-time environment )

.1

.2

.3

.1
Collaboration
:1

(Instance-level)

Collaboration .

.Instance-Level Diagrams To Explore Object Design Issues . 1 .

(Specification-level)

Collaboration

.Use Specification-Level Diagrams to Explore Roles . 2 . domain

.Collaboration Diagrams Do Not Model Process Flow . 3

.When Sequence Is Important Use a Sequence Diagram . 4

collaboration collaboration sequence

.Diagrams Apply Sequence Diagram Guidelines To Instance-Level Collaboration . 5 . : sequence

Name Objects When Your Reference Them In Messages

Name Objects When Several of the Same Type Exist

Apply Textual Stereotypes Consistently

Apply Visual Stereotypes Sparingly

Focus on Critical Interactions

Prefer Names Over Types for Parameters

Indicate Types as Parameter Placeholders

Do Not Model a Return Value When it is Obvious What is Being Returned

Model a Return Value Only When You Need to Refer to it Elsewhere

Model Return Values as Part of a Method Invocation

Indicate Types as Return Value Placeholders

.2
()orderTotal

:= calculateTotal :1.2
. ()calculateTotal

collaboration

2 2 .1

orderTotal
.

Collaboration diagram

:3

.Clear Indicate a Return Value Only When It Isn t .1

.Clear Indicate Parameters Only When They Aren t .2

. Message Arrow For Each Depict an .3

()getInfo

getter

.Consolidate Getter Invocations .4

B A

.With Letters Concurrent Threads Indicate .5 .

composition

aggregation

association

classifier

UML

collaboration .

classifier dependency

Collaboration

:4

.Model Bare Links On Instance-Level Collaboration Diagrams

.Show Role-Pertinent Information on Specification-Level Diagrams

. Prefer Roles on Links Instead of Within Classes

. Links Should Be Consistent Static Relationships

5.0

. Currently 5.0/5 Stars