SIT773: Software Requirements Analysis and Modelling, LC Case Study

This case study focuses on the Leckie’s Choice (LC) case, specifically addressing the development of personas and user stories for LC's contractor clients. The assignment begins by defining the persona of LC’s contractor clients as corporate/commercial business enterprises that purchase goods in bulk. These clients are characterized by their need for an efficient and convenient online ordering system with features such as order tracking, account access, and payment methods. The user stories detail the interactions of a commercial user with the LC e-store, covering account login, product selection with quantity and price listings, a shopping cart summary, payment processing, purchase history viewing, and online order tracking. The solution is based on references from the provided sources such as Agilemodeling, TechBeacon and Atlassian. Overall, this assignment demonstrates how personas and user stories are used in software requirements analysis to understand user needs and design effective systems.

Leckie’s Choice (LC) Case Study- Person and User Stories

LC Contractors Persona
The person of LC’s contractor clients is a corporate/ commercial business enterprise that buys goods
from LC in bulk either for their internal use or for onward resale to their own clients. The
contractor customers are very time conscious and want a system through which they can make
orders using available technologies, track their orders online from the time they make their orders to
when the orders are delivered. They are seeking efficiency and convenience to keep their own
operations running well; they have other products they purchase from other vendors and so are keen
on an efficient ordering system that uses online/ Internet technologies.
Person developed as per (Ambler, 2018; Billestrup et al., 2014).
User Stories
As a commercial user, I already have an account and user credentials with LC through which I can
log-in to LC’s e-store and place an order. If I am not registered, I will be prompted to register and
enter my details, with log-in credentials. After logging in, I can view available products from the
LC e-store and select the products I want; the products have their quantities and prices listed, as
well as any offers and incentives, such as for bulk buying. When I select a product, the summary is
shown in he shopping cart, including quantity and total prices an I can see this information easily.
When I am done selecting items, the LC system provides a summary together with details for
making payments where I confirm the products and make a payment using suitable methods such as
cards or e-wallets. Upon making payments, I get a conformation sales receipt on e-mail. I can view
my purchase history and also rack the products ordered online as I await delivery; the LC system
gives details on expected delivery time to a location I have specified.
User stories developed based on (Francino, 2019; Rehkopf, 2019).

References
Ambler, S. (2018). Personas: An Agile Introduction. [online] Agilemodeling.com. Available at:
http://www.agilemodeling.com/artifacts/personas.htm [Accessed 31 Aug. 2019].
Billestrup, J., Stage, J., Bruun, A., Nielsen, R. and Nielsen, K. (2014). Creating and Using Personas
in Software Development: Experiences from Practice. In: 5th International Conference on Human-
Centred Software Engineering (HCSE). Lyon, France: HAL, pp.251-258.
Francino, Y. (2019). An agile leader's guide to writing user stories | TechBeacon. [online]
TechBeacon. Available at: https://techbeacon.com/app-dev-testing/agile-leaders-guide-writing-user-
stories [Accessed 31 Aug. 2019].
Rehkopf, M. (2019). User Stories | Atlassian. [online] Atlassian. Available at:
https://www.atlassian.com/agile/project-management/user-stories [Accessed 31 Aug. 2019].