The purpose of this assignment is for you to learn how to create use case diagrams, a detailed use case, use case mockups, and an activity diagram for the detailed use case Manage Shopping Cart using the ITOT Case Study. The steps in the detailed use case should be consistent with the mockups and activity diagram. These activities are complementary and should be developed in tandem.

  

Course Objective(s)

CO3: Describe interaction UML models and their concepts

CO9: Apply your knowledge of object oriented and UML concepts by designing and developing UML models

  

In this assignment you will create a use case diagram with use cases and actors, a detailed use case for Manage Shopping Cart use case using the table version of the Use Case Template, a use case mockup (sketch or design) with dialog (see p. 226 in your textbook for a "mockup" for an ATM interface), and an activity diagram for the detailed steps of the use case. 

For each of your diagrams, include your name and course number directly in the diagram.

You will complete the following sections in your Analysis Specification:

Sections 2, 2.1, 2.2, 2.3, 2.4

You will need the following documents:

1. IT Online Training Project Requirements 2022R1

2. Use Case Template (Section A explains the sections in the template. Definitions of each item in the template is included in Section A. Section B. Use Case Detailed Template has a copy of the template but note that it has already been placed in the analysis specification.)

3. Your Assignment 2 renamed as ENTD278Assignment3_FirstNameLastName

  

Instructions

In addition to your textbook and lessons, review and read the examples and guidelines in the Quick Resources at the end of this assignment. The Quick Resources are also part of your readings in the lessons but are listed here to make it more convenient.

Complete the Following Sections:

Section 2 System Use Case Diagram

Add the following: “Section 2 defines relationship between the different accounts that use the ITOT and the functions that are available for them.”

Section 2.1 List of Actors and Definitions

Identify and define each actor (a role a person or group will play in interacting with the system) who will use the application. Use the definition template for your actors: "A nameOfActor is a …." and complete the sentence. For example, an actor for the case study would be Customer, Schedule Administrator, etc. Try to identify who will actually use this system. Place your actors in a table format

Section 2.2 List of Use Cases and Description

Create a list of 5 use cases for the application. See the Week 3 Lessons for how to identify use cases. Use cases are named as verb + object. See items 1-6 in your Requirements document for use cases including the name and details.

For example, a use cases might be Manage Course, Manage Shopping Cart, Maintain Customer, etc. Add a description to identify what the use case accomplishes, and any data required to complete the use case.

Section 2.3 System Use Case Diagram

Create a UML use case diagram with your CASE tool. It must be in UML format. A use case diagram includes symbols for actors and use cases. A line is used to connect your actors to the use case they use.

Section 2.4 Use Case Diagram Description

Insert a description of the system use case diagram

Section 3: Detailed Use Case and Activity Diagrams

Copy and paste the following into your Section 3. Review the material for understanding. 

Detailed Use Case and Activity Diagram

This section focuses on the shopping cart management use case and its step-by-step path. By using the following us case, it will allow the end user to purchase and select courses, as well as products that are offered on the ITOT system.

3.1. Manage Shopping Cart Use Case

3.1.1. Manage Shopping Cart Use Case Description/Scenario

In the above use case diagram, it shows the actions that can be preformed by a customer that is the main actor of the Shopping Cart. Depending on the customer’s choice there are a variety of actions that can be performed, and the ITOT system responds accordingly to the choice.

3.1.2 Manage Shopping Cart Use Case Detailed Steps 

Use Case and History

  

Use Case ID:

Use Case Name: Manage Shopping Cart

 

Created By: John Doe

Date Created:

5/21/2022

Last Updated By:

Jane Doe

Date Last Updated:

5/21/2022

       

Actors, Description, Preconditions, Postconditions

  

Actors

Customer

 

Description:

The customer is the main user of the Shopping Cart   allowing him/her to enroll in a course and purchase the materials needed for   the course.

 

Preconditions:

The Customer has an account in the ITOT system.

The customer has already logged into the system.

The customer is allowed permission to enroll in   courses.

 

Postconditions:

Item(s) have been added to the customers Shopping   Cart.

Normal Path

  

User Action

System Action

 

1. This use case begins when the customer looks for a   course, they want to enroll in.

2. This use case begins when the ITOT system displays   what course are being offered.

 

3. This use case starts when the customer views the   course they wish to enroll in and selects the course.

4. This use case starts when the ITOT system shows   the details of the selected course.

 

5. This use case begins when a customer adds the   selected course to their Shopping Cart.

6. This use case begins when the ITOT shows the items   currently in the Customers Shopping Cart.

 

7. This use case begins when a customer proceeds to   checkout with items in their Shopping Cart.

8. This use case starts when the ITOT calculates the   payments for the item(s) in the Shopping Cart for the customer.

 

9. This use case starts when the customer enters   their Credit Card info to pay for their items.

10. This use case starts when the ITOT system   processes the customers payment form and issues the receipt .

 

11. This use case ends after the customer logs off   the ITOT.

Alternative Path

  

User Action

System Action

 

1. This use case starts when the customer looks for a   course they want to enroll in

2. This use case starts when the ITOT system shows   courses that are being offered.

 

3. This use case initiates when the Customer views the   course they want to enroll in and choose it.

4. This use case initiates when the ITOT system show the   details of the selected course.

 

5. This use case terminates when the Customer logs off   the ITOT after getting the course requirements or logs off for other reasons.

Use Case Related System Issues

  

Exceptions:

The customer is allowed purchasing for a course or   the courses learning materials.

 

Includes:

Accounting System is included to process the fees.

 

Priority:

The Customers have priority in using the system and   will not be denied access unless their doing malicious content.

 

Frequency of Use:

Every time a customer wishes to view details of a   course or enrolls in a course. When the customer wants to purchase the course   materials.

 

Business Rules:

VAT is inclusive in the course fee and materials.

 

Special Requirements:

TBD

 

Assumptions:

The System is secure and cannot be compromised.

 

Notes and Issues:

3.1.3 Manage Shopping Cart Form/Screen Mockup and Dialog

The above screen mockup we see the manage Shopping Cart Form as it is expected to be designed. The following page will allow the customer to browse for courses they wish to enroll in with the following materials. Once the desired course is found, the buttons on the top bar will enable them to checkout using the Shopping Cart.

3.1.4 Activity Diagram Name for Use Case Manage Shopping Cart and Discussion

The above Activity diagram shows the process of managing the Shopping Cart and shows some of the actions the Customer will be able to take while using it.

Your assignment will be graded with the following rubric:

1. Completion of Section 2.3: Identify and define each actor and insert as a table (30 points)

2. Completion of Section 2.4: Create a lit of use cases for the application and insert as a table (30 points)

3. Completion of Sections 2.1 and 2.2: Create a UML case diagram with the CASE tool (30 points)

4. Sources/formatting: Use APA 7th edition style formatting and correct grammar (10 points)

Quick Resources

Use Case Diagrams

1. Ambler, Scott (n.d.). System Use Cases: An Agile Introduction.  http://agilemodeling.com/artifacts/systemUseCase.htm

2. See Scott Ambler's article Reuse in Use-Case Models: <<extend>>, <<include>>, and Inheritance http://agilemodeling.com//useCaseReuse.htm

3. See http://www.agilemodeling.com/artifacts/useCaseDiagram.htm for other examples of use case diagrams.

4. See Larman, Chapter 6

Using a CASE Tool for Use Case Diagrams

1. Visual Paradigm. (2016 March 4). Drawing use case diagrams. https://www.visual-paradigm.com/support/documents/vpuserguide/94/2575/6362_drawinguseca.html

Activity Diagrams

1. Please see http://www.agilemodeling.com/style/activityDiagram.htm for an example of an activity diagram.

2. Ambler, Scott (n.d.). UML2 Activity Diagrams: An Agile Introduction.  http://www.agilemodeling.com/artifacts/activityDiagram.htm

3. Ambler, Scott (n.d.). UML2 Activity Diagramming Guidelines. http://agilemodeling.com/style/activityDiagram.htm . This style guide includes general guidelines, activities, decision points, guards, parallel activities, Swimlanes, and action objects.

Using a CASE Tool for Activity Diagrams

1. Rmb1905. (2009 March 10). 9.01_Activity Diagrams Basic Symbols. [Video file]. https://www.youtube.com/watch?v=paWIY7EPWpE

2. Visual Paradigm. (2016 March 4). Drawing activity diagrams. https://www.visual-paradigm.com/support/documents/vpuserguide/94/2580/6713_drawingactiv.html

3. Visual Paradigm. (2016 March 4). Splitting control flow in activity diagram. https://www.visual-paradigm.com/support/documents/vpuserguide/94/2580/85419_splittingcon.html

Use Cases, Detailed Use Cases, and Mockups

1. See Maintain Instructor Use Case Example for a use case diagram, detailed use case, and mockups with dialog for the ITOT Case Study.