Writing Acceptance Criteria And Usage Scenarios

This article provides guidance on writing acceptance criteria and usage scenarios for e-commerce websites. It covers the importance of user-friendly portals, authentication, shopping cart functionality, payment methods, and administrator rights. A usage scenario is also described, highlighting the process of browsing items, making purchases, and receiving transaction summaries.

Writing Acceptance Criteria And Usage Scenarios

Acceptance criteria
The e-commerce website is data driven and provides a user friendly portal with well developed
scripts that users type their log-in credentials to log into the system for registered users. For new
users, they are directed to a registration page where they enter their details and log-in credentials for
purposes of accessing the LC e-store. Log-in must be authenticated, otherwise an error message is
displayed for wrong log-in details, and the us has an option to reset their credentials, should they
forget them.
The e-store displays a list of items in a dynamic way and provides users with search and filtering
options as well as direct links to offer pages. Various buttons are provided so users can navigate the
website easily to access specific pages. When shopping, all items selected by the users are displayed
in a shopping cart, with their prices, quantity, and any qualifying discounts/ offers. Upon
completion of their purchasing, the system gives users a summary of all they have selected and
provides a ‘CONFIRM’ or ‘EDIT’ option where they can conform their order or edit them and add/
remove some items. Upon a final conformation, a total tally is provided and users can then make
payments using suitable methods. A receipt is then sent to the client by e-mail and they can continue
browsing or log out at their pleasure. The marketing manager has administrator rights from the back
end to change product prices and provide promotions to clients.
Usage scenario
Client A visits LC website, and on attempting to browse items is asked after a while to log in with
an option to sign-up. They enter their details, with error messages for wrong formats used. They are
then asked to provide a password which they verify and an e-mail link sent through which they
‘activate’ their account. They then log-in and browse items, select whet hey want, confirm products
and make payments. A then logs out of system and receives an e-mail with summary of transactions
and a link to track their delivery.
Criteria and scenario described following suggestions by (Ambler, 2018; 'Product Plan', 2019;
Ravlani, 2017; and Patton et al., 2014).

References
Ambler, S. (2018). Usage Scenarios: An Agile Introduction. [online] Agile Modeling.com.
Available at: http://agilemodeling.com/artifacts/usageScenario.htm [Accessed 31 Aug. 2019].
Patton, J., Economy, P., Fowler, M., Cooper, A. and Cagan, M. (2014). User story mapping. 1st ed.
Beijing: O'Reilly, p.128.
'Product Plan' (2019). What is acceptance criteria? | Definition and Best Practices. [online]
Productplan.com. Available at: https://www.productplan.com/glossary/acceptance-criteria/
[Accessed 31 Aug. 2019].
Ravlani, K. (2017). 7 Tips for Writing Acceptance Criteria with Examples - Agile For Growth.
[online] Agile For Growth. Available at: https://agileforgrowth.com/blog/acceptance-criteria-
checklist/ [Accessed 31 Aug. 2019].