Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

UML Reference Cheat Sheet, Cheat Sheet of Software Engineering

This cheat sheet contains the UML diagrams

Typology: Cheat Sheet

2019/2020

Uploaded on 10/23/2020

ehaab
ehaab 🇺🇸

4.2

(32)

275 documents

1 / 5

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
UMLReferenceSheet
[ThisUMLreferencesheetwasinspiredbyMartinFowler’s UMLDistilled.]
*Examinable
****
*
Usecasediagrams
Actor
UseCase UseCase
<<include>>
Systemname
Actor
UseCase
Usecasediagrams[example]
EditPost
CreatePost
Calculate
Stats
BlogSystem
DeletePost
ViewPost
StatSystem
Guest
Blogger
Choose
template
<<include>>
Notesandconstraints
Notetext {constraint}
Notetext {constraint}
pf3
pf4
pf5

Partial preview of the text

Download UML Reference Cheat Sheet and more Cheat Sheet Software Engineering in PDF only on Docsity!

UMLReferenceSheet

[ThisUMLreferencesheetwasinspiredbyMartinFowler’s

UMLDistilled

.]

*Examinable *

Usecasediagrams

Actor

UseCase

UseCase

<>

Systemname

Actor

UseCase

Usecasediagrams[example]

EditPost

CreatePost

Calculate

Stats

BlogSystem

DeletePost

ViewPost

StatSystem

Guest

Blogger

Choose

template

<>

Notesandconstraints

Notetext

{constraint}

Notetext

{constraint}

Classdiagrams

ClassA

ClassB

multiplicityofA

associationlabel>

<>

EnumerationName

value2 value

roleofA

roleofB

multiplicityofB

Superclass

Subclass

Subclass WholeClass

Partclass Classname

attribute2 attribute

association

generalization

composition

enumerations

Classdiagrams

Classname

visibilityname(parameterlist):returntype visibilityname:typemultiplicity=defaultvalue

AbstractClass

abstractOperation

{abstract}

AbstractClass

staticAttribute

staticOperation abstractOperation {abstract}

<>

Interfacename

Class

Class

interfaces

abstract/static

ClassA

ClassB

navigability

ClassA

ClassB

dependency

Classdiagrams[example]

Minesweeper

Player

Minefield

Cell

MinedCell

adjacentto

< playedby

MineFreeCell

Mine

W*H

playedon>

digit:ADJACENT_MINES

<> ADJACENT_MINES

classdiagrams[example]

Table

+totalTables:Integer chairs:Chair[0..6]=null  number:Integer

+Table(n:Integer,p:Integer)+getTotal():Integer+setNumber(n:Integer) +getNumber():Integer

TableManager

Activitydiagrams

Action

Action

Action

Action

[condition]

Action

[condition]

Actiondescribed

asanotheractivity

diagram

join fork

merge

branch

end

Activitydiagrams[example]

Putpieceon

Square

Throwdie

[

th

square

reached?]

[else]

Movepiece

Waitforturn

Otherstake

turns

Superstatename

Statemachinediagrams

Statename

Statename

entry/

activity

do/ event/activity

activity

exit/

activity

event[guard]/activity

Statename

H

Active

Statemachinediagrams[example]

PRE_GAME

LOST

READY

new

WON

deduce

deduce

deduce

[incorrectdeduction]

deduction][incorrect

[correct

deduction]

nomorecellstodeduce][correctdeduction&&

deduce [correctdeduction&&

morecellstodeduce]

IN_PLAY

entry/

starttimer

exit/

stoptimer

/starttimer

/stoptimer

/stoptimer

quit/recordresult

Other

UML

diagrams

A

package

diagram

shows

packages

and

their

dependencies.

A

package

is

a

grouping

construct

for

grouping

UML

elements

(classes,

use

cases,

etc.).

Deployment

diagrams

show

a

system's

physical

layout,

revealing

which

pieces

of

software

run

on

what

pieces

of

hardware.

Communication

diagrams

are

like

sequence

diagrams

but

emphasize

the

data

links

between

the

various

participants

in

the

interaction

rather

than

the

sequence

of

interactions.

Interaction

overview

diagrams

are

a

combination

of

activity

diagrams

and

sequence

diagrams.

Timing

diagrams

focus

is

on

timing

constraints.

diagram structure composite A

its into class a decomposes hierarchically

structure. internal

A

component

diagram

is

used

to

show

how

a

system

is

divided

into

components

and

interrelationships

through

interfaces.

This

page

contains

a

peek

of

UML

diagrams

not

covered

in

lectures.

These

are

not

examinable.