1. Use Case Descriptions and System Level Scenarios
SW DESIGN PROJECT
Adela Sarca and Ligia Gaspar
Order
 User: Salesman
 Objective: Orders products
 Trigger: Customer needs
 Preconditions: The salesman is logged into the system
 Postconditions: The order is sent to the storeman
 Use Case Interaction:
1. Customer’s name is entered
2. System identifies the customer
3. User opens the products list
4. Items are selected along with desired amount
5. System calculates total price
6. User makes payment with cash or credit card
7. System prints receipt
8. User sends the order
9. System confirms
 Exceptional Operating:
2a. Customer not found/Salesman creates new customer account
6a. Payment could not be made/User cancels order
6b. Payment can be made partially/User removes items from order

2. View Orders
 User: Storeman
 Objective: View orders
 Trigger: Storeman needs
 Preconditions: Storeman is logged into the system
 Postconditions: -
 Use Case Interaction:
1. User requests to view the orders
2. System shows the orders
 Exceptional Operating:
2a. There are no pending orders/System shows message

3. Deliver Order
 User: Storeman
 Objective: Deliver products
 Trigger: Customer needs
 Preconditions: Order was sent by the salesman
 Postconditions: The order is ready to be delivered
 Use Case Interaction:
1. Order id is entered
2. System checks if order items are in storage and returns order information
3. User creates bill
4. System returns bill information
5. User makes delivery
6. System removes items from storage, sends email to customer and deletes order
 Exceptional Operating:
2a. Order items not in storage/Delivery cancelled

4. Add Product Items
 User: Storeman
 Objective: Add items to storage
 Trigger: Customers need more items
 Preconditions: Storeman is logged into the system
 Postconditions: The items are added to storage
 Use Case Interaction:
1. Storeman enters product id
2. System identifies existing product
3. Storeman enters the number of items to add
4. System confirms
 Exceptional Operating:

5. 2a. Product not found/Items cannot be added
Remove Product Items
 User: Storeman
 Objective: Remove items from storage
 Trigger: Items added by mistake
 Preconditions: Storeman is logged into the system
 Postconditions: The items are removed from storage
 Use Case Interaction:
1. Storeman enters product id
2. System identifies existing product
3. Storeman enters the number of items to remove
4. System confirms
 Exceptional Operating:
2a. Product not found/Items cannot be deleted
4a. The entered number is higher than available items in storage/Items are not removed

6. Add Product
 User: Admin
 Objective: Add product to the system
 Trigger: New product is available and needs to be seen by all system users
 Preconditions: Admin is logged into the system with Admin Session
 Postconditions: The product is added to the system database
 Use Case Interaction:
1. Admin enters product id
2. System create new product in database
3. Admin enters name and description of the product
4. System saves new product
 Exceptional Operating:
1a. Product already exists/ id already exists

7. Edit Product
 User: Admin
 Objective: Edit product information into the system
 Trigger: New product information is available and needs to be seen by all system users
 Preconditions: Admin is logged into the system with Admin Session
 Postconditions: The product information is edited to the system database
 Use Case Interaction:
1. Admin enters product id
2. System finds product in database
3. Admin makes required changes to the product
4. System saves new product format
 Exceptional Operating:
1a. Product does not exist/ no id found

8. Remove Product
 User: Admin
 Objective: Remove items from system database
 Trigger: Product added by mistake or does not exist in storage anymore
 Preconditions: Admin is logged into the system
 Postconditions: The product is removed from database
 Use Case Interaction:
1. Admin enters product id
2. System identifies existing product
3. Admin confirms the product to be removed
4. System deletes product from database
 Exceptional Operating:
2a. Product not found/Product cannot be deleted

9. Create Employee Account
 User: Admin
 Objective: Add employee to the system database
 Trigger: New employee needs to access the system
 Preconditions: Admin is logged into the system with Admin Session
 Postconditions: The employee is added to the system database
 Use Case Interaction:
1. Admin enters employee ID and password
2. System create new employee in database
3. Admin gives required access for to the system to the new account
4. System informs new employee and asks login
 Exceptional Operating:
1a. Employee already exists/ id already exists

10. View Employee Account
 User: Admin
 Objective: See employee information
 Trigger: Need to check employee information or history of the account
 Preconditions: Admin is logged into the system with Admin Session
 Postconditions: The employee information is shown to admin
 Use Case Interaction:
1. Admin enters employee ID
2. System finds employee in the database
3. System shows information about employee
 Exceptional Operating:
1a. Employee does not exist/ id not correct

11. Delete Employee Account
 User: Admin
 Objective: Remove employee from the system database
 Trigger: Employee does not work there anymore
 Preconditions: Admin is logged into the system with Admin Session
 Postconditions: The employee is deleted from the system database
 Use Case Interaction:
1. Admin enters employee ID
2. System finds employee in database
3. Admin requests deleting of the employee with all information
4. System confirms
 Exceptional Operating:
1a. Employee does not exists/ id incorrect