PROJECT 1
INTRODUCTION
Throughout your career in software design and development, you will be asked to create applications with various features and functionality based on business requirements. For this assessment, you will create a Java desktop application using the solution statements provided in the requirements section of this assessment.
The skills you showcase in your completed application will be useful in responding to technical interview questions for future employment. This application may also be added to your portfolio to show to future employers.
The preferred integrated development environment (IDE) for this assignment is NetBeans version 11.1 or later or IntelliJ IDEA (Community Edition). Use the links in the web links section of this assessment to install one of these IDEs. If you choose to use another IDE, you must export your project into NetBeans 11.1 or later or IntelliJ IDEA format or your submission will be returned.
This assessment also requires the following software: the latest long term support (LTS) version of JDK and JavaFX SDK or Module (for NetBeans or IntelliJ IDEA), and Scene Builder, which are also available for download in the web links section of this assessment, as well as a video demonstration of the completed application.
Your submission should include a zip file with all the necessary code files to compile, support, and run your application. Your submission should also include a folder with descriptive Javadoc comments in the .java files. The zip file submission must keep the project file and folder structure intact for the IDE.
In NetBeans, zip your file by going to File > Export Project > To ZIP and click Export. In IntelliJ IDEA, go to File > Export to Zip File and click OK. If you try to zip your project files with an external program, it will include the build files and make the zip files too large for submission.
Note: You may receive an error message upon submitting your files because the automated plagiarism detectors will not be able to access the zipped file, but the evaluation team members will run their checks manually when evaluating your submission.
SCENARIO
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.
REQUIREMENTS
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).
I. User Interface
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
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.
II. Application
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:
• inheritance
• abstract and concrete classes
• instance and static variables
• instance and static methods
D. Add the following functionalities to the Main form:
1. The Parts pane
• 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.
2. The Products pane
• 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.
3. Exit button
• The Exit button closes the application.
E. Add the listed functionalities to the following parts forms:
1. The Add Part form
• 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.
2. The Modify Part 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.
F. Add the following functionalities to the following product forms:
1. The Add Product 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.)
2. The Modify Product form
• 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.)
G. Write code to implement input validation and logical error checks using a dialog box or 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 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.
H. 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.
I. Demonstrate professional communication in the content and presentation of your submission.
File Restrictions
File name may contain only letters, numbers, spaces, and these symbols: ! – _ . * ‘ ( )
File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z
PROJECT 2
INTRODUCTION
Throughout your career in software design and development, you will be asked to create applications with various features and criteria based on a variety of business requirements. For this assessment, you will create your own GUI-based Java application with requirements that mirror those you will likely encounter in a real-world job assignment.
The skills you will showcase in this assessment are also directly relevant to technical interview questions for future employment. This application may become a portfolio piece for you to show to future employers.
Several attachments and links have been included to help you complete this task. The attached “Database ERD” shows the entity relationship diagram (ERD) for this database, which you can reference as you create your application.
For this task, you will use the Performance Assessment Lab Area accessed by the Performance Assessment Lab Area in the web link to access the virtual lab environment to complete this task. The preferred integrated development environment (IDE) for this assignment is IntelliJ IDEA (Community Edition). If you choose to use another IDE, you must export your project into NetBeans 11.1 or later, or IntelliJ format, or your submission will be returned. This assessment also requires the following software: the latest long term support (LTS) version of JDK, JavaFX SDK, and Scene Builder which are also available the Performance Assessment Lab Area.
Your submission should include a zip file with all the necessary code files to compile, support, and run your application. Your submission should also include an index.html file with reflective Javadoc comments in the .java files. The zip file submission must keep the project file and folder structure intact for the IDE.
In NetBeans, zip your file by going to File>Export Project>To ZIP and click Export. In IntelliJ Idea, go to File>Export to Zip File and click OK. If you try to zip your project files with an external program, it will include the build files and make the zip files too large for submission.
Note: You may receive an error message upon submitting your files because the automated plagiarism detectors at WGU will not be able to access a zipped file, but the evaluation team will run their checks manually when evaluating your submission.
SCENARIO
You are working for a software company that has been contracted to develop a GUI-based scheduling desktop application. The contract is with a global consulting organization that conducts business in multiple languages and has main offices in Phoenix, Arizona; White Plains, New York; Montreal, Canada; and London, England. The consulting organization has provided a MySQL database that the application must pull data from. The database is used for other systems, so its structure cannot be modified.
The organization outlined specific business requirements that must be met as part of the application. From these requirements, a system analyst at your company created solution statements for you to implement in developing the application. These statements are listed in the requirements section.
Your company acquires Country and First-Level-Division data from a third party that is updated once per year. These tables are prepopulated with read-only data. Please use the attachment “Locale Codes for Region and Language” to review division data. Your company also supplies a list of contacts, which are prepopulated in the Contacts table; however, administrative functions such as adding users are beyond the scope of the application and done by your company’s IT support staff. Your application should be organized logically using one or more design patterns and generously commented using Javadoc so your code can be read and maintained by other programmers.
REQUIREMENTS
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).
A. Create a GUI-based application for the company in the scenario. Regarding your file submission—the use of non-Java API libraries are not allowed with the exception of JavaFX SDK and MySQL JDBC Driver. If you are using the NetBeans IDE, the custom library for your JavaFX .jar files in your IDE must be named JavaFX.
Note: If you are using IntelliJ IDEA, the folder where the JavaFX SDK resides will be used as the library name as shown in the “JavaFX SDK with IntelliJ IDEA webinar.
1. Create a log-in form with the following capabilities:
• accepts username and password and provides an appropriate error message
• determines the user’s location (i.e., ZoneId) and displays it in a label on the log-in form
• displays the log-in form in English or French based on the user’s computer language setting to translate all the text, labels, buttons, and errors on the form
• automatically translates error control messages into English or French based on the user’s computer language setting
Note: Some operating systems require a reboot when changing the language settings.
2. Write code that provides the following customer record functionalities:
• Customer records and appointments can be added, updated, and deleted.
– When deleting a customer record, all of the customer’s appointments must be deleted first, due to foreign key constraints.
• When adding and updating a customer, text fields are used to collect the following data: customer name, address, postal code, and phone number.
– Customer IDs are auto-generated, and first-level division (i.e., states, provinces) and country data are collected using separate combo boxes.
Note: The address text field should not include first-level division and country data. Please use the following examples to format addresses:
• U.S. address: 123 ABC Street, White Plains
• Canadian address: 123 ABC Street, Newmarket
• UK address: 123 ABC Street, Greenwich, London
– When updating a customer, the customer data autopopulates in the form.
• Country and first-level division data is prepopulated in separate combo boxes or lists in the user interface for the user to choose. The first-level list should be filtered by the user’s selection of a country (e.g., when choosing U.S., filter so it only shows states).
• All of the original customer information is displayed on the update form.
– Customer_ID must be disabled.
• All of the fields can be updated except for Customer_ID.
• Customer data is displayed using a TableView, including first-level division data. A list of all the customers and their information may be viewed in a TableView, and updates of the data can be performed in text fields on the form.
• When a customer record is deleted, a custom message should display in the user interface.
3. Add scheduling functionalities to the GUI-based application by doing the following:
a. Write code that enables the user to add, update, and delete appointments. The code should also include the following functionalities:
• A contact name is assigned to an appointment using a drop-down menu or combo box.
• A custom message is displayed in the user interface with the Appointment_ID and type of appointment canceled.
• The Appointment_ID is auto-generated and disabled throughout the application.
• When adding and updating an appointment, record the following data: Appointment_ID, title, description, location, contact, type, start date and time, end date and time, Customer_ID, and User_ID.
• All of the original appointment information is displayed on the update form in local time zone.
• All of the appointment fields can be updated except Appointment_ID, which must be disabled.
b. Write code that enables the user to view appointment schedules by month and week using a TableView and allows the user to choose between these two options using tabs or radio buttons for filtering appointments. Please include each of the following requirements as columns:
• Appointment_ID
• Title
• Description
• Location
• Contact
• Type
• Start Date and Time
• End Date and Time
• Customer_ID
• User_ID
c. Write code that enables the user to adjust appointment times. While the appointment times should be stored in Coordinated Universal Time (UTC), they should be automatically and consistently updated according to the local time zone set on the user’s computer wherever appointments are displayed in the application.
Note: There are up to three time zones in effect. Coordinated Universal Time (UTC) is used for storing the time in the database, the user’s local time is used for display purposes, and Eastern Time (ET) is used for the company’s office hours. Local time will be checked against ET business hours before they are stored in the database as UTC.
d. Write code to implement input validation and logical error checks to prevent each of the following changes when adding or updating information; display a custom message specific for each error check in the user interface:
• scheduling an appointment outside of business hours defined as 8:00 a.m. to 10:00 p.m. ET, including weekends
• scheduling overlapping appointments for customers
• entering an incorrect username and password
e. Write code to provide an alert when there is an appointment within 15 minutes of the user’s log-in. A custom message should be displayed in the user interface and include the appointment ID, date, and time. If the user does not have any appointments within 15 minutes of logging in, display a custom message in the user interface indicating there are no upcoming appointments.
Note: Since evaluation may be testing your application outside of business hours, your alerts must be robust enough to trigger an appointment within 15 minutes of the local time set on the user’s computer, which may or may not be ET.
f. Write code that generates accurate information in each of the following reports and will display the reports in the user interface:
Note: You do not need to save and print the reports to a file or provide a screenshot.
• the total number of customer appointments by type and month
• a schedule for each contact in your organization that includes appointment ID, title, type and description, start date and time, end date and time, and customer ID
• an additional report of your choice that is different from the two other required reports in this prompt and from the user log-in date and time stamp that will be tracked in part C
B. Write at least two different lambda expressions to improve your code.
C. Write code that provides the ability to track user activity by recording all user log-in attempts, dates, and time stamps and whether each attempt was successful in a file named login_activity.txt. Append each new record to the existing file, and save to the root folder of the application.
D. Provide descriptive Javadoc comments for at least 70 percent of the classes and their members throughout the code, and create an index.html file of your comments to include with your submission based on Oracle’s guidelines for the Javadoc tool best practices. Your comments should include a justification for each lambda expression in the method where it is used.
Note: The comments on the lambda need to be located in the comments describing the method where it is located for it to export properly.
E. Create a README.txt file that includes the following information:
• title and purpose of the application
• author, contact information, student application version, and date
• IDE including version number (e.g., IntelliJ Community 2020.01), full JDK of version used (e.g., Java SE 17.0.1), and JavaFX version compatible with JDK version (e.g. JavaFX-SDK-17.0.1)
• directions for how to run the program
• a description of the additional report of your choice you ran in part A3f
• the MySQL Connector driver version number, including the update number (e.g., mysql-connector-java-8.1.23)
F. Demonstrate professional communication in the content and presentation of your submission.
File Restrictions
File name may contain only letters, numbers, spaces, and these symbols: ! – _ . * ‘ ( )
File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z