Data Modeling Analysis
From each use case, create two test cases. In the summary/conclusion, please note how use cases are used to create test cases and what you have learned from this exercise.
Test cases help to determine how valid use cases are. Utilized early on, test cases help to alleviate some of the problems that occur later in system projects (Heumann, 2001).
Use Case: Order New Inventory
Test Case 1. Employee orders one item. Expected result: item is ordered successfully.
Test Case 2. Employee orders multiple items. Expected result: Employee successfully orders multiple items
Use Case: Label created for ordered item
Test Case 1. Item is ordered. Expected result: Label successfully prints
Test Case 2. Multiple items ordered. Expected result: All required labels are printed successfully
Use Case: Item received and inventoried
Test Case 1. Item is received and appropriate label is scanned. Expected result: item is successfully added to system inventory
Test Case 2. Item is received and incorrect label is added. Expected result: system incorrectly updates inventory
Use Case: Item is sold
Test Case 1. Item is sold and scanned. Expected result: system updates inventory correctly
Test Case 2. Item is sold but not scanned. Expected result: system does not update to reflect current inventory
Creating both use cases and test cases are very useful steps in the analysis phase of system projects. Each can help to point out potential flaws and make designers think about how the system needs to operate in a more critical way.
