Maintain Customer Orders - Use Case Diagram (User Stories)

Maintain Customer Orders - Use Case

One of the first things you do in analysis and design is create use case diagrams. A use case diagram allows you to understand how the system should work from the user's perspective. If you are using Agile methodologies, you create user stories instead. The concept is similar in that you are trying to determine how the user accomplishes a particular task.

In this Jump Start, we'll be modeling a simple "Maintain Customer Orders" use case. Here's the diagram and the associated description:

1. The actor navigates to the Customer Orders form.

2. The Customer Orders form displays a text box allowing the actor to enter a customer ID.

3. The actor enters the customer ID and clicks the Get Orders button.

4. The system retrieves all orders for the specified customer and displays them in a grid.

5. The actor selects an order in the grid to be edited, and clicks the Order Detail tab.

6. The Order Detail tab displays order header information and a grid containing the associated order items.

Although there are other things the actor can do with the orders (edit, delete, save, etc.), we'll stop here since we're only trying to give you a basic grasp of the process.