Skip to content

Latest commit

 

History

History
32 lines (23 loc) · 2.36 KB

README.md

File metadata and controls

32 lines (23 loc) · 2.36 KB
Raw

Order Management

Getting Started

The startup project is OrderMgmtUI. Please run this project to start the application.

Application Description

The solution is divided into two parts: OrderMgmtUI and OrderMgmtLibrary. OrderMgmtUI holds all the forms and UI logic. OrderMgmtLibrary is responsible for communicating with the database and storing the connections.

There are two forms that a user can open: CustomerGridForm and CustomerOrderListForm.

  • CustomerGridForm

    • This form lists all the customers and allows the users to add, edit, and delete customers.
    • This form has a button that says "View Customer Orders," which will open the CustomerOrderListForm.
    • Adding and editing customers will open up CustomerForm, which will either add or edit customers depending on whether it's in edit or add mode.
    • The add and edit customer form requires users to input all fields and fill in a valid zip code.

  • CustomerOrderListForm

    • This form lists all and each customer's orders.
    • "Select All" option in the dropdown will list all orders while selecting a specific customer in the dropdown will list all that customer's orders.
    • Once a user selects an order, it will display the Order Details on the right side.
    • If a customer is selected, clicking the "Add New Order" button opens the Add New Order form, AddNewOrderForm.
      • The add new order form has a grid that allows the user to select an item in the dropdown. Then, the item and order total prices are automatically updated and calculated.
      • The add new order form requires the user to fill in an order name and ship date. Also, the total quantity of items should be at least 1, and no multiple-item entries are allowed. Otherwise, the order is not created for the customer.

Database Design

  • Load SalesProcess database backup file in MS SQL server. This file contains table design and some customer/order/item data.
  • All customer, order, and item fields are not nullable.
  • OrderDetails maps an Order and Item together. This means that OrderDetails will include how many of those items are in the order and the total price of that item in the order (calculated as the quantity of item * its unit price).
  • OrderDetails cannot have multiple item entries of the same item for an order. In other words, ItemNumber and OrderId are considered a primary key pair.