Simple Use Case – Part 2
This is an Individual Lab
For this lab, we will continue modeling a simple use case.
First, edit your simple use case documents, correcting errors as noted by your professor.
Then, add the following 3 components:
Systems Use Case Specification: Write a Systems Use Case Specification to add data.
Class Diagram: Using Visual Paradigm, create a class diagram to support your specification.
Sequence Diagram: Using Visual Paradigm, create a sequence diagram to support your specification.
Use Case Name
Add New Product
Triggering Event
Adds new product to the convenience store/business
Brief Description
Allows the Owner to record a new product.
Actors
Owner
Related Use Cases
Preconditions
Owner has opened the Main Menu.
Post Conditions
Product is saved to the database and now can be purchased.
Flow of activities
Actor
System
1.
Requests to add a new product to
convenience store
Displays a list of product Types and prompts for selection.
Prompts for product name, description, and price
2.
Enter product name, description,
price, qty, and selects product type.
Loop this step until all new items/
products are added.
name, description, and price must be en-
tered. Generates a unique identifier.
Verify if product details are valid
Displays newly added product
Prompts to save.
3.
Request to save
Saves the product and returns to the main
menu
