SIT773 Software Requirements Analysis: Create Order Activity Diagram

This document presents a detailed activity diagram for the 'Create Order' use case, developed for the SIT773 Software Requirements Analysis and Modeling course. The diagram illustrates the complete process flow, beginning with user login and authentication, proceeding through product selection, adding items to a shopping cart, and the ability to modify the cart by adding or removing items. The process incorporates conditional checks to manage order validity and item selection, followed by order confirmation and payment processing. The system then dispatches the order, allowing the contractor to track its status, and finally terminates the process. The assignment references key academic sources, including works by Brügge and Dutoit (2013), Garrido (2009), Gomaa (2011), and Sapna and Balakrishnan (2015), to support the methodology and design choices. The activity diagram effectively models the requirements of the Leckie's Choice (LC) case study, focusing on online ordering functionalities such as shopping cart management and order tracking.

Activity Diagrams

Updated Use Case with ‘Create Order’
The
‘create order’ use case activity has been added; it is shaded blue and encompasses the tasks of
selecting items and adding to the cart, updating the cart by adding or deleting items, and then
confirming the order.

Detailed ‘Create Order’ Activity Diagram
In the detailed ‘create order’ activity diagram, the process begins after the user has logged in and
been authenticated and has browsed available items. This leads to the contractor choosing the
products they need and places an order request into the system by selecting various items. The task
‘requests’ the LC e-store system to confirm receipt of the order, which then places it n the shopping
cart in a way that the contractor can see (the shopping cart). The system then checks if the order is
normal and this stage is a condition check. This is for each and every item selected by the
contractor. The next step is a conditional case where the contractor can remove/ delete some items
from the cart or can add/ adjust some items. Based on the condition, if there are items remaining in
the shopping cart, then the process continues, else, if all items are removed, then the process comes
to an end. If there are items in the shopping cart, the contractor then makes a conformation and
makes a payment. The system then dispatches the order to the stated destination and there is a
condition of the contractor tracking their order. The system then terminates the process, bring the
‘create order’ task to an end.
Sources used: (Brügge and Dutoit, 2013; Garrido, 2009; Gomaa, 2011; Sapna and Balakrishnan,
2015).

References
Brügge, B. and Dutoit, A. (2013). Object-oriented software engineering. 1st ed. London: Pearson
Education Limited.
Garrido, J. (2009). Object oriented simulation. Dordrecht: Springer-Verlag.
Gomaa, H. (2011). Real-time software design for embedded systems. 1st ed. Cambridge: Cambridge
University Press, pp.91-92.
Sapna, P. and Balakrishnan, A. (2015). An Approach for Generating Minimal Test Cases for
Regression Testing. Procedia Computer Science, 47, pp.188-196.