SIT773 - Software Requirements: Identifying and Describing Use Cases

This assignment focuses on identifying and describing use cases for the Leckie's Choice (LC) e-store, addressing requirements from both the front-end (contractor/client) and back-end (administrator/marketing manager) perspectives. The solution details the functionalities of the e-store, including contractor actions such as browsing, adding items to a shopping cart, order confirmation, payment processing, and order tracking. It also outlines the administrator's responsibilities, such as managing product categories, offers, products, suppliers, shipping, and taxes. The use cases are developed considering personas, scenarios, and requirements, drawing on established methodologies from various sources. The analysis includes the roles of key players and their normal tasks, providing a comprehensive understanding of the e-store's operational dynamics. The assignment references established literature to support the use case development process.

Identifying And Describing Use Cases

Use Cases
Explanation of Use Cases
The LC e-store has two main sub-systems; a front end which is is the web portal for logging in and
a back-end where the administrator/ marketing manager can log in and make changes. The
contractor logs in using authentication credentials provided by the administrator. The contractor
then browses available items and adds them to their shopping cart. The contractor can delete or
update/ add items to the cart and proceeds to confirm the order. A payment page then comes through
which they select an appropriate payment method such as Pay-pal, credit card, or a digital wallet.
Upon making the payment and getting a conformation, the contractor logs out and can track their
order online. On the back med, the administrator can add product categories or offers and update/
delete them. The administrator can add, update, or delete products, update or delete a supplier/
manufacturer, add countries and states, and add/ update shipping charges and taxes payable and
verifies contractor log-out. In creating the use case, previous tasks were considered, such as the
personas and use scenarios, as well as the requirements and based on these, including a definition of
who the users are, the normal course of events used in developing the use case diagrams (Jennings-
Balthazar, 2011). The use case diagrams considered all the players; the front end has the contractor

client while the back end has the administrator and/ or the marketing manager and their roles or he
normal tasks they would undertake (Rana, 2016). Additional ideas for developing use cases
borrowed from (Kulak and Guiney, 2012; Pohl and Rupp, 2015; and Wiegers, 2013).

References
Jennings-Balthazar, D. (2011). Use case quick start guide. 1st ed. Dallas: Lulu Com.
Kulak, D. and Guiney, E. (2012). Use Cases: Requirements in Context. 2nd ed. Boston, MA:
Pearson, p.175.
Pohl, K. and Rupp, C. (2015). Requirements engineering fundamentals. 1st ed. Hobken: Wiley.
Rana, A. (2016). How to Write Effective Use Cases?. [online] Visual-paradigm.com. Available at:
https://www.visual-paradigm.com/tutorials/writingeffectiveusecase.jsp [Accessed 31 Aug. 2019].
Wiegers, K. (2013). Creating a Software Engineering Culture. 1st ed. Boston: Addison-Wesley
Professional, pp.80-81.