operations.
In this assignment, you will design and implement an object-oriented database system that tracks activities for a small warehouse. Some business terms:
Client: Customers who order things from warehouse
Product: Items that are stocked in the warehouse. Sale price: Price paid by the customer for a specific product.
Wishlist: Products, with quantities, in which a customer has indicated interest
Waitlist: Products, with quantities, which a customer has ordered, but are not available yet Order: A client’s commitment to pay for a list of products with associated quantity for each product.
Invoice: A list of products, associated quantities and unit sales prices, and total cost for a package that is being shipped to a client.
The business has the following requirements for the system. Note that some of these require- ments correspond to a single business process, some to multiple business processes, and some re- quirements may only influence how a business process should be implemented :
1. Adding clients. Note that deletion is not required. The ID for clients must be generated by the system. Allow for adding multiple clients; each client has a name and address
2. Adding products. Note that deletion is not required. The ID for products must be generated by the system. Allow for adding multiple products; product has a name, amount in stock, and a sale price.
3. Keeping track of customer transactions. Whenever there is a transaction involving a customer, the system keeps a record. Each transaction has just a date, a descriptive string and an number (for a dollar amount).
4. Keeping track of customer’s wishlist. A client should be able to specify a product and an associated quantity that they plan to purchase in the near future; the system will keep track of all this information.
5. Accept a client’s order (i.e. procced to check-out). When a client places the order, the system goes over the client’s wishlist and asks if each of the items should be ordered, and a quantity for each. Whenever the client answers yes, the product and quantity are added to the order and the product is removed from the clients wishlist. Next it asks if the client wants to add any more products (with quantities) and adds them to the order. Then the system creates an invoice that shows all the products and quantities that can be shipped at that time. The items that cannot be shipped are wait-listed. The transaction is amount due is debited to the Clients’ account.
6. Generate Invoices. An invoice consists of a set of products with associated quantities and sale prices, and a total cost. Invoices result when customer orders are accepted, or when wait-listed items become available.
7. Accept payment from a client. The amount is credited to the customer’s account. Note that a client order can be processed and shipped before the payment has been made. In other words, placing and processing the orders is independent of the payment process.
8. Accept a shipment for a product. Shipment details specify a productid and quantity. wait- listed orders must be filled first, before amount in stock is updated.
9. Queries to be processed. The following queries must be handled:
• List all transactions for a specified client.
• List all clients who have an outstanding balance.
• List all products, quantity in stock, and total quantity of outstanding(waitlisted) orders.
10. Additional queries. As you build the system you will need some queries to verify that the system is behaving correctly. These should be added as required. Your overall submission will be evaluated for testability - for every business process implemented, it should be possible to easily query the system and verify that the implementation is correct.
DescriptionIn this final assignment, the students will demonstrate their ability to apply two ma
Path finding involves finding a path from A to B. Typically we want the path to have certain properties,such as being the shortest or to avoid going t
Develop a program to emulate a purchase transaction at a retail store. Thisprogram will have two classes, a LineItem class and a Transaction class. Th
1 Project 1 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of
1 Project 2 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
23 | 24 | 25 | 26 | 27 | 28 | 1 |
2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 | 21 | 22 |
23 | 24 | 25 | 26 | 27 | 28 | 29 |
30 | 31 | 1 | 2 | 3 | 4 | 5 |
