Install Oracle JDeveloper 10g .

In the Applications Navigator, right-click Applications and choose New Application Workspace from the context menu.

In the Create Application Workspace dialog, rename the application Application1 to ProductOrdering.
.(Notice that the directory name changes to match the new name.) For the application template, select No Template [All Technologies], and click OK.

The ProductOrdering workspace is created and displayed as a node in the navigator. A default project named Project has also been added. Save your work by clicking on the Save All button. You should save your work at regular intervals as you work through the rest of this tutorial.

Select the Project node in the Navigator, and right-click to choose New to display the New Gallery.

In the New Gallery, expand the General node, select the Diagrams category and double-click the UML Use Case Diagram item.

In the Create UML Use Case Diagram dialog, enter Web Ordering as the name, and leave the default package value. Click OK.

The Web Ordering empty diagram opens.

Select Component Palette from the View menu (if it is not already open) to display the various diagram components.

Select the Actor icon in the Component Palette and click in the left part of the diagram surface. Replace the default Actor1 name with Customer .

Select the Use Case - Casual icon and drag it from the Component palette to the right of the Customer silhouette. Rename it to Order Products .

Select the Communication icon and draw a line between the Customer actor and the Order Products Use Case.

Select the Use Case - Fully Dressed icon and drag it to the right of the Order Products Use Case. Change the name to Browse Product Descriptions .

Select the Use Case - Fully Dressed icon and click below the Browse Product Descriptions Use Case. Change the name to Manage Shopping Cart .

Select the Use Case - Fully Dressed icon and click below the Manage Shopping Cart Use Case. Change the name to Process Order .

Your Use Case diagram should now look like this:

Since the Order Products Use Case includes all three other use cases on the diagram, do the following:

Select the Inclusion icon in the Component Palette and draw a line from the Order Products Use Case to the Browse Product Descriptions Use Case.

Repeat the same operation to include the Manage Shopping Cart Use Case in the Orders Products Use Case.

Repeat the same operation to include the Process Order Use Case in the Orders Products Use Case.

Choose File | Save All to save all your work thus far.

Your diagram should now look like this:

Double click on the Customer actor silhouette to open its definition.

In the Responsibilities section, click next to the bullet below actor_responsibilities, and enter the following text:

As the user has validated his order, he becomes a "de facto" customer.

In the Background and skills section, under the actor_profile, enter the following text:

The term Customer applies to anyone connecting to our merchant site on the web. Therefore, anyone is a prospective customer.

In the Referenced By section notice the link to Order Products. This was automatically created when you added the Communication line on the diagram.

Click the Web Ordering tab on the top of the editor window to display the Web Ordering diagram.

Double click the Order Products Use Case to open it. Notice that this use case was created using the Casual icon.

In the Scenario section you can see that references to the other use cases are included. Just above the reference to Browse Product Descriptions, cut and paste the following description for the scenario:

Customer connects to our merchant site home page to order products. The home page displays product categories allowing customer to do X through categories links. The customer may also use a direct link to do Y and change quantities or remove a product. When the customer has finished shopping, he can then do Z to validate the purchase.

Select the " Browse Product Descriptions" link and drop it next to the do X words. Remove the placeholder words.

Select the “ Manage Shopping Cart” link and drop it next to the do Y words. Remove the placeholder words.

Select the “ Process Order ” link and drop it next to the do Z words. Remove the placeholder words.

The Use Case should look like this:

Click on the Web Ordering tab to open the diagram in the editor.

Double click the Browse Product Definitions Use Case to open its definition.

Notice that the sections are more detailed than the previous use case. This use case was created using the Fully dressed icon.

In the Scenario section, select the <<< Insert Next Element Here message, delete it and click on the Unordered list icon in the editor toolbar to replace the numbering by a bulleted list.

In the Scenario section, below the usecase_includes add the following description for the use case:

• Browse product catalog
• Check details of selected products (description, unit price and available quantity)
• Add product to shopping cart
  

Open the Web Ordering diagram. (use the tab on the top of the editor window)

Double click on the Manage Shopping Cart Use Case to open its definition.

In the Scenario section, select the <<< Insert Next Element Here message, delete it and click on the Unordered list icon to replace the numbering by a bulleted list. In the Scenario section, below the usecase_includes add the following description for the use case:

• When the customer selects a product to fill his shopping cart, each selection creates an entry in the shopping cart with a default quantity of one unit. When viewing the shopping cart content, the customer has the opportunity to update the quantity.
• The customer may also want to delete an item in his shopping cart. He can either specify a null quantity or delete a product line in the shopping cart.
• At any time, the customer is kept informed of the value of his shopping cart.
• When the customer finally agree with the number of items in his shopping cart and the shopping cart value, he can then confirm the order.

Open the Web Ordering diagram. (use the tab on the top of the editor)

Double click the Process Order Use Case to open its definition.

In the Scenario section, select the <<< Insert Next Element Here message, and delete it.

Add the following actions:

1. Calculate total
2. Register providing Username and Password
3. Enter Delivery Address
4. Enter Credit Card Information
5. Submit Order
   

In the Precondition section add the following text:

Shopping cart is not empty
Provide username and password

In the Postcondition section, enter the following text for Minimal Guarantee(s) :

Credit card information is valid

In the Postcondition section, enter the following text for Success Guarantee(s) :

No products are ordered if the payment cannot be verified

Open the Web Ordering diagram in the diagram.

Choose File | Save All to save all your work thus far.

Select the text for the Process Order Use Case and change it to Finalize Order .

Double click the Order Products Use Case.

Note that the Finalize Order link in the Scenario section has been changed to the new name.

Choose File | Save All to save all your work thus far.

Open the Web Ordering diagram in the editor.

In the Component Palette, select the Actor icon and click below the already existing Customer actor on the diagram.

Rename the new actor Actor1 to Registered Customer .

Select the Generalization icon from the Component Palette.

Click in the Registered Customer silhouette as the source and draw a Generalization line toward Customer. (Hint: the arrow head of the generalization should be pointing to “ Customer”, not “ Registered Customer”).

Double click on the Registered Customer silhouette to open its properties.

In the Background and skills section below the actor_profile reference cut and paste the following text:

A registered customer is a customer that has previously ordered products from our site.The customer has already provided a username and password, and the system tracks of the customer's address and credit card information.
A registered customer is eligible for a discount.

Open the Web Ordering diagram in the editor.

Select the Use Case - Fully dressed icon from the Component Palette and click in the diagram below the Finalize Order Use Case.

Change the UseCase1 name to Finalize Order For Registered Customer .

Select the Communication icon in the Component Palette

Click in the Registered Customer silhouette as the source and draw a communication line toward Finalize Order For Registered Customer.

Select the Extension icon in the Component Palette.

Click in the Finalize Order For Registered Customer Use Case and draw an Extension line toward the Finalize Order Use Case. (Hint: the arrow head of the extension should be pointing to “ finalize order”, not “ Finalize Order For Registered Customer”).

Double click the Finalize Order For Registered Customer Use Case to display its properties.

In the Precondition enter the following text and set the block format to "paragraph":

Customer provides a valid Username and Password combination.

In the Scenario section, select the <<< Insert Next Element Here message, delete it and add the following text:

1. Customer logs in and his information are retrieved
2. New total is calculated to apply registered customer discount
3. If credit card validation date has expired, new credit card information is requested

Open the Web Ordering diagram in the editor.

Select the Note icon and click on the diagram below the Registered Customer.

In the text area enter the following text:

Username and password need to be valid.

Select the Attachment icon in the Component Palette.

Draw a line from the note to Registered Customer.

Choose File | Save All to save all your work thus far.

Your diagram should now look like this:

In the Applications Navigator, select the Project node.

From the menu, select Run | Javadoc Project.jpr option.

Open the log window View | Log.

Select the Javadoc tab in the Log window and Click on the View Documentation hyperlink.

The editor window has navigation links generated for each component in the diagram sorted by categories.

Click on the various links to display the full properties of a component.

Notice that a new file named index.html has been generated and appears in the Applications Navigator.

In the menu select Tools | External tools..., and click Add in the dialog.

In the Create External Tools dialog click Browse next to the Program Executable field.

Locate the browser executable in your directory structure, and click Open.

Click Insert next to the Arguments field.

Select File URL from the list, and click OK.

Click Browse button next to the Run Directory field.

In the Choose directory dialog, select {jdev_home}\jdev\mywork and click Select.

Click Next to display Step 2 of the wizard. This step doesn't require any change. Click Next again.

Click Next.

In Step 4 of the wizard, select the When Specific File types are Selected option.

In the Available types list, select HTML Source and XHTML Source and use the Move button to move them in the Selected Types list , Click Finish.

Click OK to exit the wizard.

In the Applications Navigator, right click index.HTML.

You should now see in the context menu a new option for Internet Explorer. Select it.

A browser opens, allowing you to browse the Use Case documentation using the links on the left frame of the page.