Your application must include at least three tabs. The user will choose wood flooring or carpet, enter the length and width of the floor, as well as the customer name and address. The application will compute the area of the floor and the cost of the flooring considering that wood floor is $20 per square foot and carpet is $10 per square foot. A summary should be displayed, either in a tab or another window, listing the customer name and address, floor selection, area, and cost. This information should also be stored in the MySQL database table. The program should validate that all information is entered and that the length and width are numeric values. Any numeric or currency values must be formatted appropriately when output. Recommendations for the components used for input are
- radio buttons—flooring type (wood or carpet).
- text fields—customer name, customer address, floor length, and floor width
- buttons—calculate area, calculate cost, submit order, display order summary, display order list.
The MySQL database table is called flooring and has the following description:
In addition to entering new customer orders, your application should list all customer orders stored in the database. These will be viewed as a list, in a text area, and will not be updated by the user.
User Manual (Due Week 7)
Your actual Course Project and user manual are due at the end of Week 7. However, it is strongly recommended that you start your project in Week 5 to avoid many last minute issues.
In Week 7, you will be required to submit a user manual, as well as your Java code. The user manual can be a simple Word document with screenshots that explains how to run your application. Your mark will depend both on the program quality and the quality of the user manual.
Here are some more detailed guidelines about the user manual.
It does not need to be long, probably not more than 5 pages, including screenshots.
Write at the expected user’s level, not too technical.
Detail all the functionality that the application provides.
For each function, show what is its purpose and sample execution, with a screenshot.
|Sufficient length to describe the application||5||Manual contains explanation in detail of all relevant areas of the application|
|Contains screenshots of the key interface components||5||Images of each section of the application|
|Operations are explained||5||Detailed operation of each section of the application|
|Written to the user’s level and is not technical||5||Must not contain code or any other technical items irrelevant to the users|
Application Code (Due Week 7)
The following grading rubric will be used for the code portion of the project.
|Standard header included||2||Must contain program name student name and description of the program|
|Program compiles||2||Program does not have any error|
|Program executes||2||Program runs without any error|
|Includes at least 3 tabs||10||Three or more tabs are used|
|Includes components for all required inputs||35||Components for customer name address floor type length width area and cost with buttons to calculate area calculate cost display order summary and display order list are included|
|Area calculation||4||Area is calculated correctly|
|Cost calculation||5||Cost is calculated correctly|
|Included data validation||10||If no values or non-numeric values are entered. the proper error message should display.|
|Correct data is stored in the database table||10||When values are entered the data is stored correctly in the database table.|
|Customer orders are displayed in a list||10||All records saved to the database are displayed in a list with appropriate formatting.|
|Correct output is displayed||10||When values are entered the order summary is shown with appropriate formatting.|