Created
November 19, 2014 20:54
-
-
Save danieldiekmeier/c2d610568533b1a9d26f to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Use Cases & Scenarios | |
## Use Cases | |
- Searching for product | |
- Listing the available products with further information | |
- Updating existing products | |
- Creating new products | |
- Buying a product | |
- Choosing a language | |
- Choosing a payment method | |
- money transfer | |
- credit card | |
- Money Pal | |
- Creating Order | |
- Sending a mail to customer | |
- Editing reviews | |
- Rating / commenting on a product | |
- Printing a product list of the order | |
- Delivering to customer | |
## Detailed Scenario 1: Buying a Product | |
### Precondition | |
The customer chose one or more products and wants to buys these. All chosen articles are available. | |
### Sequence of Steps | |
1. The user is clicking on the “buy” button on our homepage. | |
2. All products that the user choose are marked | |
3. The user enters his contact information into a form | |
4. Paying process (which is a process of its own) | |
5. The order is sent to the administrator, who in turn uses the mailing system to send an e-mail to the customer. | |
6. A list of items is send to the packer. The packer prints the list, packs the stuff and sends it to the customer. | |
## Detailed Scenario 2: Creating a Product | |
### Precondition | |
A new product needs to be created by the administrator. If this role is assigned to you, you can log into the backend and create a product by filling out a form with additional information. | |
### Sequence of Steps | |
1. Log into backend with administrator rights. | |
2. Validate Login: | |
- if it fails, show error message. | |
- if it doesn't fail, continue. | |
3. Navigate to the input form | |
4. Insert the necessary information: | |
- Price | |
- Name | |
- Type (Example: *Pumpkin, already carved*) | |
- How many items are in stock | |
5. Submit the form | |
6. Validation of the data, was everything entered correctly? | |
- if validation fails, user gets an error message | |
- if validation is correct, the dataset is saved to the database. | |
7. Screen gets updated and the new product shows up. | |
### Postcondition | |
The package is delivered correctly to the customer without any complications between the steps above. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment