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:
- Create a main GUI containing the following components:
- An area that allows the user to input data into the application along with the descriptive text that describes each input area.
- A total of six buttons as shown below with functionality as described below.
- As illustrated below, the various buttons on the interface are only accessible at certain points during a user’s interaction with the e-store.
- An input file named “txt”. This is a comma separated file which contains the data that will be read by the application when the user makes a selection. A sample file is provided for you on WebCourses.
- An output file (append only) named “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.
Your source file shall begin with comments containing the following information:
/* Name: <your name goes here>
Course: CNT 4714 – Fall 2017
Assignment title: Program 1 – Event-driven Programming
Date: Sunday September 10, 2017
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.
- Submit a working copy of your source code (all .java files) via WebCourses no later than 11:59pm Sunday September 10, 2017.
- 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.
- 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).
Shown below are example screen shots of the GUI to help illustrate how your application is to operate.
- Screen shot of the contents of an example “inventory.txt” file.
an order –
- Initial GUI: generates
|Note that these|
|Allows for||Confirms that|
|buttons are not||Clears|
|the item is||initially “active”.||order and|
|item once it is|
|order so far.|
- GUI after user specifies total number of items in the order and makes a selection for item #1.
- GUI after user has selected the first item and clicked the “Process Item #1” button.
|Information on the book|
|Note that the “Confirm|
|purchased has been|
|Item #1” button is now||extracted from the|
|active and the “Process||inventory file and written|
|Item #1” button is inactive.||into the window on the|
|line for item #1.|
- When the user clicks on the “Confirm Item #1” button, a confirmation information message appears on the screen.
User entered an incorrect
book ID. This message
would be displayed when
user preseed the Process
|6. The main GUI after the user has confirmed the first item.||Discount is|
|10-14 = 15%|
|Note that||>=15 = 20%|
Note that the text areas
for entering the second
item information are
cleared and ready for
- User enters next item in the order.
|total of all|
- The GUI after the user has entered the information for all the items and confirmed the last item.
- When the user clicks the “View Order” button, the following message box should appear.
- 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
Format is “DD/MM/YY
- 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
8/21/2017 at 15:09:08 pm. See the
invoice message above. Permutation
- The transaction file after several orders have been completed. Note the unique transaction ids based on the date and time for every separate transaction.