Example overview
The example uses the JPetStore application, an on-line pet store web application.
The application provides typical merchant website functionalities : creating an account, signing in, browsing through pets, adding pets to a shopping cart, and finally checking out and purchasing what has been added to the cart. You can identify the purchasing phase as critical because it is resource greedy and time consuming. You may need and want detailed statistics on this phase.
You can ignore the interactions concerning the actual choice of pets and their quantity. You are only interested in the pages in which the client confirms and checks out what he or she has purchased. The following screen shots depict those pages:
- Whatever the client has ordered, the following page submits a form containing payment and billing address information (/jpetstore/shop/newOrderForm.shtml):
- The second step is a page prompting the client for confirmation of previously entered billing address information (/jpetstore/shop/newOrder.shtml):
- The final step is a page summing up payment, address and order details (/jpetstore/shop/newOrder.shtml_1):
