Suppose I have a use case, like this example.
Normal Flow: The user will indicate that she wants to order the items that have already been selected. The system will present the billing and shipping information that the user previously stored. The user will confirm that the existing billing and shipping information should be used for this order. The system will present the amount that the order will cost, including applicable taxes and shipping charges. The user will confirm that the order information is accurate. The system will provide the user with a tracking ID for the order. The system will submit the order to the fulfillment system for evaluation. The fulfillment system will provide the system with an estimated delivery date. The system will present the estimated delivery date to the user. The user will indicate that the order should be placed. The system will request that the billing system should charge the user for the order. The billing system will confirm that the charge has been placed for the order. The system will submit the order to the fulfillment system for processing. The fulfillment system will confirm that the order is being processed. The system will indicate to the user that the user has been charged for the order. The system will indicate to the user that the order has been placed. The user will exit the system.
I would be grateful if you could let me know of a procedure or guideline that helps in converting this to use case diagram, more specifically the use case bubbles.
Going back to the example, I think I would have one use case bubble named place order, and I probably have another bubble named payment, and there is am "include" relation from payment to place order. But I hope there is something more formal than intuition to help me come up with a more accurate diagram. Thanks!!