Tag Archives: You will create and discuss an additional scenario for Manage Shopping Cart including test Case Name Description Prerequisites Steps Input Expected Result Actual Result Status.

Shopping Cart Design

Purpose

The purpose of this assignment is to continue with our design modeling of the ITOT Case Study. For the Manage Shopping Cart use case, you will create a test scenario, and two test cases. You will also add a persistent UML class diagram and SQL statements for ShoppingCart and ShoppingCartItem (these will be provided). Finally, you will map your domain classes ShoppingCart and ShoppingCartItem to Java statements.

Course Objective(s)

CO7: Describe implementation modeling for databases and programming style

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

You will create two test cases following the format described in your design specification. In testing, test cases are developed first and then tested later by a different team. You will not be able to exercise your test cases (so you won’t have Actual Results) but you can create the test case.

You will also create SQL statements including constraints for ShoppingCart and ShoppingCartItem. You will also create sample Java statements for ShoppingCart and ShoppingCartItem design classes.

In this assignment you complete the following sections in your Design Specification

Sections 6 (test cases), Section 7 (SQL), and Section 8 (Java)

Instructions

1. Review the Quick Resources listed at the end of this assignment.

2. Complete the following

Section 6.1

You will identify and document two test scenarios (e.g., “Add a product to cart.”) based on the Manage Shopping Cart use case and complete. Describe the test scenarios (around 100 words) at a high level.

Section 6.2 – Test Case 1

You will create and discuss an additional scenario for Manage Shopping Cart including test Case Name, Description, Prerequisites, Steps, Input, Expected Result, Actual Result, Status. The steps of the test case must be numbered! Example:

Test Scenario: <add your test scenario here for Manage Shopping Cart>

Test Case ID

Test Case Description

Test Case Steps

Expected Results

Actual Results

Test Case Status

TC001

<add description?

1. <add step>

<add expected result>

<add actual result>

<add status pass/fail>

2, <add step>

…

…

…

…

…

…

TC002

<add description?

1. <add step>

<add expected result>

<add actual result>

<add status pass/fail>

2, <add step>

…

…

…

…

…

…

Section 6.3 – Test Case 2

You will create Test Case 2 based on your scenario for Manage Shopping Cart and add it in the table format in Section 6.3 of your design specification.

Section 7

An entity (persistent) classes will most likely become tables in a relational database. In database design, we would follow normalization and functional decomposition guidelines to normalize our entities (classes) into valid relations. Then we would create SQL (Structured Query Language) statements to create the tables and add constraints. After that, we could populate our tables with data. We will assume our classes are normalized for this exercise.

Persistent Class Diagram

An example of a persistent class diagram is below. You can copy these into Section 7 and 7.1 in your document.

7.1 Persistent Data Model

7.1.2 Persistent Data Model Discussion

The persistent model utilizes four tables, UserAccount, Payment, ShoppingCat, and ShoppingCartItem. The ShoppingCart table represents the shopping cart itself, and includes a primary key cart_id, a foreign key user_id column to identify the user associated with the cart, and a created_at column to store the timestamp when the cart was created.

Section 7.2 – SQL Statements for ShoppingCart and ShoppingCartItem

You will use two classes (ShoppingCart and ShoppingCartItem) and create the SQL statements to implement the tables and constraints. You will need to include primary key and foreign key constraints. Add the SQL Statements to Section 7.2 of your design specification.

Section 7.2.1 – Discussion

Include a discussion of your SQL statements in Section 7.2.1 in your design specification (50 to 100 words).

Section 8 – Java

Add the following to Section 8. This section shows how the implementation of the code will look using Java programming language.  

Section 8.1 – Java for ShoppingCart and ShoppingCartItem

Using Chapter 18 examples in your textbook or your resources below, create Java statements for ShoppingCart and ShoppingCartItem detailed design classes. Note that ShoppingCart and ShoppingCartItem have a composition type of part whole relationship. See the Engine and Piston example at https://coderanch.com/t/443002/java/Java-Coding-UML-Aggregation-Composition. Add them to Section 8.1 of your design specification and complete Section 8.

Section 8.2 – Java Discussion.

Include a discussion of your Java statements in Section 8.2 in your design specification (50 to 100 words).

Submission Directions

1. When you submit your Word file, use your name as part of the file name, e.g., ENTD278Assignment7_FirstNameLastName

Your assignment will be graded with the following rubric:

1. Complete Section 6 and 6.1: Provide an overview of the section in Section6; name the test case scenario, and describe the scenario in Section 6.1 (5 points).
2. Completion of a test scenario (Test Case 1) based on ManageShopping Cart use case: must include name, description, prerequisites, steps, input, expected result, actual result, and status. Steps must be numbered (15 points)
3. Complete Section 6.2.1: Provide a discussion of Test Case 1 (5 points)
4. Completion of a test scenario (Test Case 2) based on ManageShopping Cart use case: must include name, description, prerequisites, steps, input, expected result, actual result, and status. Steps must be numbered (10 points)
5. Complete Section 6.3.1:Provide a discussion of Test Case 2 (5 points)
6. Creation of a persistent UML class diagram(without operations) of persistent data. Include ShoppingCart and ShoppingCartItem. Designate primary and foreign keys, and add to Section 7.1 (15 points)
7. Completion of Sections 5, 5.1, and 5.2: Discussion of the design specification and UML class diagram  (15 points)
8. Completion of SQL statements for ShoppingCart and ShoppingCartItem: Create SQL statements to implement the tables and constraints, as well as adding primary and foreign keys (10 points)
9. Completion of Section 7.2.1: Discuss the SQL statements (5 points)
10. Completion of Java code for ShoppingCart and ShoppingCartItem: Create Java statements to create the classes, variables, and methods (10 points)
11. Completion of Sections8 and 8.2: Discussion of the section and Java implementation discussion. (10 points)
12. Sources/formatting: Use APA 7th edition style formatting and correct grammar (10 points)