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.

Session 7—Building the Use Case Narrative 77<br />

Did you find the error in the Use Case diagram In Table 7-5, the dialog said, “The system<br />

asks for the location of the item and unfilled quantity (from the LocateProduct Use Case).”<br />

You need to add an dependency from the FillOrder Use Case to the<br />

LocateProduct Use Case.<br />

Use Case termination in the case study narrative<br />

In the termination row in Table 7-6, you list all the ways that this Use Case could end. Use<br />

Cases are not good at showing concurrency and interrupts, so this is often the only place to<br />

identify things such as a cancel event and timeouts. You’ll need to use the Activity diagram<br />

or even the Sequence diagram a bit later to flesh out the concurrency and interrupt requirements.<br />

The termination section also provides you with a list of actions to consider when<br />

writing the post-conditions.<br />

Tip<br />

No one diagram can show everything. This is why it is so important to understand<br />

the purpose and features of each diagram. The diagrams are like tools<br />

in a toolbox. You have to know which one to use for each task.<br />

Most business applications like FillOrder will let you cancel the session at specific points<br />

in the process. It is also usually wise to handle the condition where a user gets interrupted<br />

and leaves a session open. The timeout termination could watch for a specified period of<br />

inactivity before closing the transaction. And of course the user can actually complete the<br />

process of filling the order or simply indicate that he is done.<br />

Table 7-6<br />

The Fill Order Use Case Narrative: Termination<br />

Field Name<br />

Use Case termination<br />

Field Description<br />

The user may cancel<br />

The Use Case may timeout<br />

The user can indicate that he is done<br />

The user can fill all items on the Order<br />

Post-conditions in the case study narrative<br />

Finally, in the Post-conditions row in Table 7-7, you list the conditions that must be true<br />

when the Use Case ends. These conditions are especially important in that they reveal processing<br />

steps that may need to be added to the dialog to ensure that the system is stable<br />

when this Use Case is completed.

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

Saved successfully!

Ooh no, something went wrong!