ENTDThreeTwoOnce Assignment Seven Week Seven

I’m working on a Computer Science question and need guidance to help me study.

Note : Need Origianal work and Assignment #6 document attached along with Professor Feedback..

Feedback on Assignment #6 : All the required sections are completed. But section 5.1 should contain a special connection between the two indicating the composition relationship(look at the sample diagram attached to the message I sent to the class).

Section 5.1 ShoppingCart and ShoppingCartItem UML Class Design diagrams representing composition relationship is not completed.

Section 5.2 Discussion of the above class design is not completed.

Assignment 7 – Implementation

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 create a persistent UML class diagram and SQL statements for ShoppingCart and ShoppingCartItem. Finally you will map your domain classes ShoppingCarat and ShoppingCartItem to Java statemens. Use you domain class diagram with attributes and operations.

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 forShoppingCart 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, 6.1, 6.2, 6.2.1, 6.3, 6.3.1 on test cases, Sections 7, 7.1, 7.1.2, 7.2, 7.2,1 on SQL, and Sections 8, 8.1, 8.2 on Java.

Instructions

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

Test Scenario and Test Cases

2. Section 6, 6.1. You will identify and document one test scenario (name and description) based on the Manage Shopping Cart use case and complete Sections 6 and 6.1 in your design specification. A test scenario is not the same thing as a test case!

3. You will create and discuss two test cases for your scenario above 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!

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>

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

3.1.1 You will add a discussion of Test Case 1 to Section 6.2.1 in your design specification.

3.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.

3.2.1 You will add a discussion of Test Case 2 to Section 6.3.1 in your design specification.

4. Your 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

4.1 Create a persistent UML class diagram (without operations) of persistent data. You already have this from Assignment 2. Make certain that you include ShoppingCart and ShoppingCartItem. Designate primary and foreign keys. Add this to Section 7.1 in your design specification.

4.2 Include a discussion of your persistent class diagram in Section 7.1.2 in your design specification.

SQL Statements for ShoppingCart and ShoppingCartItem

5. You will use two classes (ShoppingCart and ShoppingCartItem) from your persistent UML class diagram 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.

5.1 Include a discussion of your SQL statements in Section 7.2.1 in your design specification

6. Complete Section 7 of your design specification.

Java for ShoppingCart and SoppingCartItem

7. 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 and 8.2 discussion. You need to map the attributes and methods.

Submission Directions

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

Your assignment will be graded with the following rubric:

Rubric for Assignments

Points

Content & Development 50%

50/50

Organization 20%

20/20

Format 10%

10/10

Grammar, Punctuation, & Spelling 15%

15/15

Readability & Style 5%

5/5

Timeliness (late deduction 10 points) Optional

Total

100/100

Quick Resources

Test Scenario and Test Cases

1. Difference between Test case and Test scenario. (2012, October 5). Retrieved from http://tfortesting.wordpress.com/2012/10/05/difference-between-test-case-and-test-scenario/

2. Guru99. (n.d.). How to Write Test Cases: Step by Step Guide with Examples. Retrieved from http://www.guru99.com/test-case.html

3. Software Testing Help. (2016, December 24). Writing Test Cases from SRS Document (Download Live Project Sample Test Cases) – Software Testing QA Training Day 4. Retrieved from http://www.softwaretestinghelp.com/writing-test-cases-from-srs-software-testing-qa-training-day-4/.

SQL

1. Chapter 19 in your textbook provides a mapping from Java classes to SQL and sample SQL statements for implementing your tables. See Figure 19.5 p. 355 for a 1:N mapping to SQL.

UML to Java

1. See Chapter 18 in your Blaha textbook.

2. See Java Coding and UML Aggregation v/s Composition at https://coderanch.com/t/443002/java/Java-Coding-UML-Aggregation-Composition for an example of implementing composition in the Engine and Piston example.

3. Wampler, Bruce E. (2001). The Essence of Object Oriented Programming with Java and UML. Chapter 3. Objects in Java. Retrieved from http://www.lcc.uma.es/~amg/ISE/OOP-Java-UML/Chapter3.html

4. DZone/Java Zone. (2012 December 31). UML2 Class Diagram in Java. Retrieved from https://dzone.com/articles/uml2-class-diagram-java

5. Gudmestad, Evan (2011 November 1). Java Tutorial – 9 – UML to Code conversion. Retrieved from https://www.youtube.com/watch?v=6wyk5BrgOFo This is a video of how to convert a class diagram to Java.

Course and Program Objectives

CO6: Describe the software development process including the implementation of models and object oriented languages.

CO9: Apply object oriented and UML concepts by designing and developing UML models.

SLO (Program Objectives): Apply industry driven techniques for designing, developing, deploying, and securing enterprise applications on the desktop and on the Web.

SLO (Program Objectives): Demonstrate use of analytical, logical, and critical thinking to design, develop, and deploy effective Information Technology solutions.

Posted in Uncategorized