Sequence Diagrams

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/17

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

18 Terms

1
New cards

Synchronous Message

Sender waits until is has received a response message before continuing

<p>Sender waits until is has received a response message before continuing</p>
2
New cards

Asynchronous Message

Sender continues without waiting for a response message

  • msg(par1,par2)

<p>Sender continues without waiting for a response message</p><ul><li><p>msg(par1,par2)</p></li></ul><p></p>
3
New cards

Response Message

  • msg(par1,par2)

May be omitted if content and location are obvious

  • att=msg(par1,par2):val

<p>May be omitted if content and location are obvious</p><ul><li><p>att=msg(par1,par2):val</p></li></ul><p></p>
4
New cards

Object Creation

Arrowhead points to the head of the lifeline of the object to be created

  • Keyword new

<p>Arrowhead points to the head of the lifeline of the object to be created</p><ul><li><p>Keyword new</p></li></ul><p></p>
5
New cards

Object Destruction

Object is deleted

  • Large cross (×) at the end of the lifeline

<p>Object is deleted</p><ul><li><p>Large cross (×) at the end of the lifeline</p></li></ul><p></p>
6
New cards

Found message

Sender of a message is unknown or not relevant

<p>Sender of a message is unknown or not relevant</p>
7
New cards

Lost message

Receiver of a message is unknown or not relevant

<p>Receiver of a message is unknown or not relevant</p>
8
New cards

Time-consuming message

Message with duration:

  • Usually messages are assumed to be transmitted without any loss of time

  • Express that time elapses between the sending and the receipt of a message

<p>Message with duration:</p><ul><li><p>Usually messages are assumed to be transmitted without any loss of time</p></li><li><p>Express that time elapses between the sending and the receipt of a message</p></li></ul><p></p>
9
New cards

Coregion

To model concurrent events of a single lifeline

  • Order of event occurrences within a coregion is not restricted

  • Area of the lifeline to be covered by the coregion is marked by square brackets rotated by 90 degrees

10
New cards

Bad Smells - God Class

One class carries out most of system functionality, others are auxiliary

11
New cards

Bad Smells - Excessive

  • Excessive Class Length

  • Excessive Method Length

  • Excessive Inheritance use

12
New cards

Bad Smells - Excessive Parameter List

e.g., more than 10 parameters in an operation

13
New cards

Bad Smells - Duplicate Code

Sections of identical code in different locations

14
New cards

Bad Smells - Cyclomatic Complexity

High number of logical loop/if conditions in a method

15
New cards

Bad Smells - Too Many Methods

e.g., more than 20 in a class

16
New cards

Bad Smells - Too Many Fields

e.g., more than 20

17
New cards

Bad Smells - Design quality flaws (bad smells)

  • God Class

  • Excessive Class Length

  • Excessive Method Length

  • Excessive Inheritance use

  • Excessive Parameter List

  • Duplicate Code

  • Cyclomatic Complexity

  • Too Many Methods

  • Too Many Fields

18
New cards

x3---op3---> y1

  • Offered by class Y (because Y objects can do op3)

  • Called on object y1 (because y1 is being asked to do op3)

  • Called by object x3 (because x3 is making the request)