Please take a look at figure 3-11 (on page 84, back in chapter 3). This is a Use Case Diagram, showing the shipping clerk as an actor outside the automation boundary. What does that oval inside the automation boundary represent? It is a Use Case, entitled "Ship items". But what does that Use Case actually do? To answer that question we need a more detailed model, looking inside the Use Case itself.

Now look at figure 5-3 (page 136 in chapter 5). This is the fully developed Use Case Description for Ship items. It is the most common way to define what this aspect of the system must do, and gives the software engineer the key details needed to build it.

But also look at figure 5-5 (page 138, chapter 5). This is the Activity Diagram for the same Use Case. Spend some time comparing the details on this diagram with the details in the fully developed Use Case Description.

QUESTIONS:

a) What advantages do you see in using Activity Diagrams?

b) What advantages do you get by using fully developed Use Case Descriptions?

** PLEASE DON'T POST THE SAME ANSWER THAT SOMEONE ALREADY HAS SUBMITTED. THANK YOU!(:

FIGURE 3-11 A simple use case with an actor Actor is a stick figure, usually meaning an actual person using the system Connecting line to show which actors participate in use cases Automation boundary Ship items Shipping clerk FIGURE 3-11 A simple use case with an actor Actor is a stick figure, usually meaning an actual person using the system Connecting line to show which actors participate in use cases Automation boundary Ship items Shipping clerk