01.01.2015 Views

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

170<br />

Saturday Afternoon<br />

A message or stimulus is usually a call, a signal, or a response. A message is represented<br />

by an arrow. The type of arrow visually describes the type of message. The solid line and<br />

solid arrowhead style represent a message that requires a response. The dashed arrows are<br />

the responses. (I cover more arrow types later in this session.) The messages are placed horizontally<br />

onto the timelines in relative vertical position to one another to represent the<br />

order in which they happen. This arrangement allows you to read the diagram from beginning<br />

to end by reading the messages from top to bottom.<br />

Bill : Customer<br />

Bill's Order : Order<br />

: Inventory<br />

1<br />

2<br />

3<br />

1: Order()<br />

2: return order<br />

3 [for each product] : additem(product)<br />

4: productAvailable(product)<br />

5: return yes<br />

6<br />

7<br />

8<br />

4<br />

6 [product available=yes] : addProduct(product)<br />

9<br />

5<br />

7: return done<br />

10<br />

8: return done<br />

Figure 16-2 Elements of the Sequence diagram notation<br />

The reference numbers on Figure 16-2 denote these items:<br />

1. Object lifeline<br />

2. Message/Stimulus<br />

3. Iteration<br />

4. Self-reference<br />

There is more to this scenario<br />

than shown here.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!