A. Create a JavaFX application with a graphical user interface (GUI) based on the attached “Software 1 GUI Mock-Up.” You may use JavaFX with or without FXML to create your GUI, or you may use Scene Builder to create your FXML file; use of Swing is not permitted. The user interface (UI) should closely match the organization of the GUI layout and contain all UI components (buttons, text fields, etc.) in each of the following GUI mock-up forms:
1. Main form
2. Add Part form
3. Modify Part form
4. Add Product form
5. Modify Product form
Each form has a description of the buttons and how they should react in the Software GUI Mock up.
Note: You may use one FXML file for forms with an identical UI component structure. You may also use a single window that can be switched to a different menu, or a new window can be launched for each form. As of JDK 11, JavaFX is no longer included in the JDK API but is available as an SDK or module.
B. Provide Javadoc comments for each class member throughout the code, and include a detailed description of the following in your comments:
• a logical or runtime error that you corrected in the code and how it was corrected
• a future enhancement that would extend the functionality of the application if it were to be updated
Note: For these comments to accurately export to the Javadoc comments, please add the logical and runtime error comments in the method header declaration comments where the error that was corrected occurred, and include the future enhancement comments in the comments of the main class. Please start these comments with “RUNTIME ERROR” or “FUTURE ENHANCEMENT” as applicable.
C. Create classes with data and logic that map to the UML class diagram and include the supplied Part class provided in the attached “Part.java.” Do not alter the provided class. Include all the classes and members as shown in the UML diagram. Your code should demonstrate the following:
• abstract and concrete classes
• instance and static variables
• instance and static methods
D. Write code to implement error checks using message in the UI displaying a descriptive error message for each of the following circumstances:
• Min should be less than Max; and Inv should be between those two values.
• The user should not delete a product that has a part associated with it.
• The app confirms the “Delete” and “Remove” actions.
• The application will not crash when inappropriate user data is entered in the forms; instead, error messages should be generated.
E. Provide a folder containing Javadoc files that were generated from the IDE or via the command prompt from part B. In a comment above the main method header declaration, please specify where this folder is located.
File name may contain only letters, numbers, spaces, and these symbols: ! - _ . * ' ( )
File size limit: 200 MB