You are to develop software for a simple online shopping situation. The entities in this scenario include the web shop, customers, products, orders and invoices. The shop has a list of products available. A customer logs in, selects products and adds them to his/her order. When the shopping is complete an invoice with unique invoice number is generated for the order. There are 10 products in this simple example and they should be stored in an array. Products can be added and deleted from an order. Only one customer at a time need be considered.
Below are shown some suggested attributes and methods for the various possible classes. You do not have to slavishly follow these examples, if you don’t understand them or wish to model differently that is allowed. NOTE: Depending upon your modelling not all components may be used. Below are suggested UML type diagrams representing the object types (classes):
Order
-customer
-country string
-productList[]
-nt
+createOrder(Customer)
+add(product)
+search(string)
+delete(string)
+display()
Customer
-name string
-address string
+createCust(string, string)
+Customer(string, string)
+getName()
Product
-name string
-model string
-price float
+readRecord(ifstream&)
+createProduct(string, string, float)
+getPrice()
+displayDetails()
+getName()
Web_shop
-customer
-products[]
-invoiceNumber int
-order
+Web_shop()
+readProducts()
+login()
+runShop()
+generateInvoice()
Typical data to be found in the file is as follows:
Chainsaw CS001 59.95
Each line is compose of a name space model_number space price If you do not use a file then you may
product prods[10]={{"Chainsaw","CS001",59.95},etc.
prods[0].createProduct("Chainsaw","CS001",59.95);
The Order object is responsible for building a list of products ordered via adding from the list of all products or deleting from the list of ordered products. Thus there are two lists in this program viz. the complete list of products and the list of ordered ones. Some sort of search facility would normally be part of the Order class. The Product class should be able to provide details such as name and price to other classes such as the Order class. If a file is used then it should be able to read a record from the file and load the data. If used the Web_shop class should load the complete list of products from the file, allow customer login, provide the on-screen menus and generate invoices. The Customer class is relatively simple just being able to provide details such as name to other classes and to accept/create details from the login process.
Your program should begin by offering a login prompt on screen. Once a username and password is accepted a customer can be created. At this point a menu of products should appear on screen. These products should either have been loaded from the file or have been hard-coded in the program. The user uses the menu to select products which are added to the order. A facility to quit this menu should be provided. The order thus far should then be displayed on screen. At this stage there should now be a facility to delete items in the order. This can be done on the basis of the name of the product. Once this phase is quit an invoice should be generated and displayed on screen. The program can then finish or the user logout.