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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

160<br />

Saturday Afternoon<br />

Figure 15-1 implies that you would let them try again or cancel. <strong>To</strong> do that, you need to<br />

loop back to the beginning and offer them a choice. Figure 15-2 illustrates the needed<br />

changes. <strong>To</strong> loop back to a previous place in the logic, use a merge point diamond. <strong>To</strong> provide<br />

a choice, use the decision diamond. Then each path out of the decision diamond must<br />

be labeled with a guard condition. In this case, you offer them two choices: proceed to<br />

Enter Shipper_ID or cancel.<br />

start<br />

merge point<br />

proceed or cancel<br />

[cancel]<br />

[proceed]<br />

cancelled<br />

Enter Shipper_ID<br />

Prompt to<br />

re-enter or<br />

cancel<br />

[Shipper not found]<br />

Find Shipper<br />

Display<br />

Shipper details<br />

[Shipper found]<br />

Figure 15-2 Modeling a looping condition and merge point<br />

Next identify the post-conditions and terminations. (I do these together because there is<br />

often a great deal of overlap.) The narrative told you that the Use Case terminates when:<br />

The system displays the message that it could not find the Shipping company and<br />

the user cancels<br />

Accounts Payable has been notified and the inventory has been updated<br />

The user cancels the transaction

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

Saved successfully!

Ooh no, something went wrong!