You are working for a small manufacturing organization that has outgrown its current inventory system. Members of the organization have been using a spreadsheet program to manually enter inventory additions, deletions, and other data from a paper-based system but would now like you to develop a more sophisticated inventory program.

You have been provided with a mock-up of the user interface to use in the design and development of the system (see the attached “Software 1 GUI Mock-Up”) and a class diagram to assist you in your work (see the attached “UML Class Diagram”). The organization also has specific business requirements that must be considered for the application. A systems analyst created the solution statements outlined in the requirements section of this task based on the business requirements. You will use these solution statements to develop your application.

Your submission must be your original work. No more than a combined total of 30% of the submission and no more than a 10% match to any one individual source can be directly quoted or closely paraphrased from sources, even if cited correctly. The originality report that is provided when you submit your task can be used as a guide.

You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course.

Tasks may not be submitted as cloud links, such as links to Google Docs, Google Slides, OneDrive, etc., unless specified in the task requirements. All other submissions must be file types that are uploaded and submitted as attachments (e.g., .docx, .pdf, .ppt).

Javadoc comments are required for this performance assessment. It is recommended you document comments for each member during the coding process. Please see aspect G.

I. User Interface

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.

II. Application

• inheritance

• abstract and concrete classes

• instance and static variables

• instance and static methods

• The Add button under the Parts TableView opens the Add Part form.

• The Modify button under the Parts TableView opens the Modify Part form.

• The Delete button under the Parts TableView deletes the selected part from the Parts TableView or displays a descriptive error message in the UI or in a dialog box if a part is not deleted.

• When the user searches for parts by ID or name (partial or full name) using the text field, the application displays matching results in the Parts TableView. (Including a search button is optional.) If the part or parts are found, the application highlights a single part or filters multiple parts. If the part is not found, the application displays an error message in the UI or in a dialog box.

• If the search field is set to empty, the table should be repopulated with all available parts.

• The Add button under the Products TableView opens the Add Product form.

• The Modify button under the Products TableView opens the Modify Product form.

• The Delete button under the Products TableView deletes the selected product (if appropriate) from the Products TableView or displays a descriptive error message in the UI or in a dialog box if a product is not deleted.

• When the user searches for products by ID or name (partial or full name) using the text field, the application displays matching results in the Products TableView. (Including a search button is optional.) If a product or products are found, the application highlights a single product or products or filters multiple products. If a product or products are not found, the application displays an error message in the UI or in a dialog box.

• If the search field is set to empty, the table should be repopulated with all available products.

Note: A product’s associated parts can exist independent of current inventory of parts. You are not required to display sample data upon launching your application. You do not need to save your data to a database or a file; data for this application is nonpersistent and will reside in computer memory while in use.

• The Exit button closes the application.

• The In-House and Outsourced radio buttons switch the bottom label to the correct value (Machine ID or Company Name).

• The application auto-generates a unique part ID. The part IDs can be, but do not need to be, contiguous.

• The part ID text field must be disabled.

• The user should be able to enter a part name, inventory level or stock, a price, maximum and minimum values, and company name or machine ID values into active text fields.

• After saving the data, users are automatically redirected to the Main form.

• Canceling or exiting this form redirects users to the Main form.

• The text fields populate with the data from the chosen part.

• The In-House and Outsourced radio buttons switch the bottom label to the correct value (Machine ID or Company Name) and swap In-House parts and Outsourced parts. When new objects need to be created after the Save button is clicked, the part ID should be retained.

• The user can modify data values in the text fields sent from the Main form except the part ID.

• After saving modifications to the part, the user is automatically redirected to the Main form.

• Canceling or exiting this form redirects users to the Main form.

• The application auto-generates a unique product ID. The product IDs can be, but do not need to be, contiguous. - The product ID text field must be disabled and cannot be edited or changed.

• The user should be able to enter a product name, inventory level or stock, a price, and maximum and minimum values.

• The user can search for parts (top table) by ID or name (partial or full name). If the part or parts are found, the application highlights a single part or filters multiple parts. If the part or parts are not found, the application displays an error message in the UI or in a dialog box.

• If the search field is set to empty, the table should be repopulated with all available parts.

• The top table should be identical to the Parts TableView in the Main form.

• The user can select a part from the top table. The user then clicks the Add button, and the part is copied to the bottom table. (This associates one or more parts with a product.)

• The Remove Associated Part button removes a selected part from the bottom table. (This dissociates or removes a part from a product.

• After saving the data, the user is automatically redirected to the Main form.

• Canceling or exiting this form redirects users to the Main form.

Note: When a product is deleted, so can its associated parts without affecting the part inventory. The Remove Associated Part button removes a selected part from the bottom table. (This dissociates or removes a part from a product.)

• The text fields populate with the data from the chosen product, and the bottom TableView populates with the associated parts.

• The user can search for parts (top table) by ID or name (partial or full name). If the part or parts are found, the application highlights a single part or filters multiple parts. If the part is not found, the application displays an error message in the UI or a dialog box.

• If the search text field is set to empty, the table should be repopulated with all available parts.

• The top table should be identical to the Parts TableView in the Main form.

• The user may modify or change data values.

• The product ID text field must be disabled and cannot be edited or changed.

• The user can select a part from the top table. The user then clicks the Add button, and the part is copied to the bottom table. (This associates one or more parts with a product.)

• The user may associate zero, one, or more parts with a product.

• The user may remove or disassociate a part from a product.

• After saving modifications to the product, the user is automatically redirected to the Main form.

• Canceling or exiting this form redirects users to the Main form.

Note: The Remove Associated Part button removes a selected part from the bottom table. (This dissociates or removes a part from a product.)

• 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 application 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.

• a detailed description of a logical or runtime error that you corrected in the code and a detailed description of how you corrected it above the line of code you are referring to

• a compatible feature suitable to your application that would extend functionality to the next version if you were to update the application