Description
Objectives: To practice event-driven programming using Java-based GUIs. To refresh your basic Java skills. Description: Develop a Java program that creates a standalone GUI application (not an applet) that simulates an e-store which allows the user to add items (books) to a shopping cart and once all items are included, total all costs (including tax), produces an invoice, and append a transaction log file. Your program development must include the following steps: 1. Create a main GUI containing the following components: a. An area that allows the user to input data into the application along with the descriptive text that describes each input area. b. A total of six buttons as shown below with functionality as described below. c. As illustrated below, the various buttons on the interface are only accessible at certain points during a user’s interaction with the e-store. 2. An input file named “inventory.txt”. This is a comma separated file which contains the data that will be read by the application when the user makes a selection. Each line in this file contains three items; a book id, a quoted string containing the book title and author’s name, and the price for one copy of the book. A sample file is provided for you on WebCourses. 3. An output file (append only) named “transactions.txt” must be created that uniquely logs each user transaction with the e-store. The unique transaction id will be generated as a permutation of the date/time string when the transaction occurred. Restrictions: Your source file shall begin with comments containing the following information: /* Name: Course: CNT 4714 – Fall 2019 Assignment title: Program 1 – Event-driven Programming Date: Sunday September 15, 2019 */ Input Specification: The file “inventory.txt” as described above (see example below as well). Output Specification: Output is to appear in the specified components of the GUI and various message boxes that appear, plus the contents of the “transactions.txt” log file that will be generated. Deliverables: CNT 4714 – Programming Assignment #1 – Fall 2019 Page 2 (1) Submit a working copy of your source code (all .java files), including your inventory.txt file, via WebCourses no later than 11:59pm Sunday September 15, 2019. (2) Include a file that contains screen shots, similar to those illustrated below, that shows your application in action as a user interacts with your e-store to purchase books. (3) Include a screen shot of your “transactions.txt” file showing at least the last few transactions (similar to the one shown on the last page of this document). Additional Information: Shown below are example screen shots of the GUI to help illustrate how your application is to operate. 1. Screen shot of the contents of an example “inventory.txt” file. Page 3 2. Initial GUI: 3. GUI after user specifies total number of items in the order and makes a selection for item #1. Note that these buttons are not initially “active”. Allows for processing an item once it is selected. Confirms that the item is correct. View the order so far. Completes an order – generates invoice and adds to the transaction file. Clears order and starts over – no write to transaction file Quit! Page 4 4. GUI after user has selected the first item and clicked the “Process Item #1” button. 5. When the user clicks on the “Confirm Item #1” button, a confirmation information message appears on the screen. Note that the “Confirm Item #1” button is now active and the “Process Item #1” button is inactive. Information on the book purchased has been extracted from the inventory file and written into the window on the line for item #1. User entered an incorrect book ID. This message would be displayed when user pressed the Process Item button. This is the only “error” you will need to catch. Page 5 6. The main GUI after the user has confirmed the first item. 7. User enters next item in the order. Information for previous item remains on display. Subtotal should reflect current total of all confirmed items. Note that the text areas for entering the second item information are cleared and ready for input. Discount is based on the quantity of a item. If: 1-4 = 0% 5-9 = 10% 10-14 = 15% >=15 = 20% Note that the buttons change number. Page 6 8. The GUI after the user has entered the information for all the items and confirmed the last item. 9. When the user clicks the “View Order” button, the following message box should appear. Page 7 10. When the user clicks the “Finish Order” button, the invoice message should be generated and displayed. The date and time are used to create the unique transaction id in the “transactions.txt” file. For the invoice the format is “DD/MM/YY HH:MM:SS TMZ” Page 8 11. The transaction file after order shown above was finished. Note the unique transaction ids based on the date and time. The last transaction occurred on 08/27/2019 at 13:37 (1:37pm). See the invoice message above. Permutation used here is: DDMMYYYYHHMM. Page 9 12. The transaction file after several orders have been completed. Note the unique transaction ids based on the date and time for every separate transaction. This file shows seven separate transactions. Page 10
