Touchstones are projects that illustrate your comprehension of the course material, help you refine skills, and demonstrate the application of knowledge. You can work on a Touchstone anytime, but you must pass this unit's assessments before you submit it. Once you've submitted a Touchstone, it will be graded and counted toward your final course score. Touchstone 4: Final Java Project ASSIGNMENT: For this Touchstone, you will learn how to effectively plan, design, develop, and test an original program of your choosing. This program is your choice and it can be as complex as you wish. The goal is to start with an idea for your program and then step through the process of most phases of the development lifecycle to turn your idea into an actual program. This includes planning out the algorithm using pseudocode, coding your program using everything you learned from Units 1-3, and finally, testing and debugging your program to make sure it fulfills your intended purpose. You will fill out a journal (template link below) which has five sections that correspond to the five steps you will complete for your final project. Use this template to write your journal responses for each section of the project. When you have finished, you will submit this journal as a Word .doc/docx. Java Journal Template The following Example Java Journal Submission will be helpful to you as you work on this assignment and shows acceptable submissions for each entry. Example Java Journal Submission Being able to create your own program can be beneficial in any career field. Anything that can be programmed or automated in any industry could make your work a lot easier. Even as a hobby, it can give you a reference point to have a better understanding of how to deal with common issues. Using basic Java to automate menial tasks can save you time and money! Whether you were in this class to learn programming at a professional level or if it's just for fun, you will benefit from learning coding as a foundation of your technical skills. In order to foster learning and growth, all work you submit must be newly written specifically for this course. Please note that you cannot use the same program used in a previous programming course. Any plagiarized or recycled work will result in a Plagiarism Detected alert. Review Touchstones: Academic Integrity Guidelines for more about plagiarism and the Plagiarism Detected alert. For guidance on the use of generative Al technology, review Ethical Standards and Appropriate Use of Al. A. Directions Step 1: Download Template Download and review the Java Journal Template. Step 2: Review Requirements Review Section C (Requirements) to get acquainted with the requirements for this Touchstone before you begin writing your journal entries. Step 3: Complete Journal Follow the directions for each part of the journal template. Make sure to include in your response all the elements listed under the Requirements section. Prompts in the Inspiration section are not required; however, they may help you to fully think through your response. Follow the journal creation process that is presented in your Unit 4 lessons to ensure you write a thorough journal entry. There is also an example of a successful journal entry for each submission in the Assignment description above. Review Section B (Rubric) to make sure you have an understanding of how each journal entry will be graded. Step 4: Submit Journal Once your journal is complete, including the code link, submit your journal for grading. HINT There are helpful tips on "How Do I Submit My Java Journal?" in the first lesson of Unit 4, Java Touchstone Overview. Refer to the checklist below throughout the writing process. Do not submit your Touchstone until it meets these guidelines. PART 1: Defining Your Problem Did you describe the problem you are trying to solve? Did you describe any input data you expect to use? Did you describe what the program will do to solve the problem? Did you describe any outputs or results the program will provide? PART 2: Working Through Specific Examples Did you write down clear and specific steps to solve a simple version of your problem you identified in Part 1? ☐ Did you state any necessary input data for your simplified problem? Did you write clear and specific steps in English (not Java) detailing what the program will do to solve the problem? ☐ Did you describe the specific result of your example/scenario? PART 3: Generalizing Into Pseudocode Did you write out the general sequence your program will use, including all specific examples/scenarios you provided in Part 2? ☐ Did you write pseudocode for the program in English but refer to Java program elements where they are appropriate? Does the pseudocode represent the full functionality of the program, not just a simplified version? ☐ Is the pseudocode broken down enough that the details of the program are no longer in any paragraph form? PART 4: Testing Your Program While writing and testing your program code, did you describe your tests, record any errors, and state your approach to fixing the errors? For at least one of your test cases, did you describe how your choices for the test helped you understand whether the program was running correctly or not? ☐ For each error that occurs while writing and testing your code, did you record the details of the error from Replit? Did you describe what you attempted in order to fix the error? PART 5: Commenting Your Program Did you submit your full program code, including thorough comments describing what each portion of the program should do when working correctly? ☐ Are the purpose of the program and each of its parts clear to a reader that does not know the Java programming language? PART 6: Your Completed Program ☐ Did you provide the Replit link to your full program code? B. Rubric Advanced (100%) Proficient (85%) Acceptable (75%) Needs Improvement (50%) Non-Performance (0%) PART 1: Defining Your Problem (17 points) State the problem you are planning to solve. The student clearly stated the problem they are trying to solve, including what the program is expected to do to solve the problem and any necessary inputs and outputs required for the program. The student clearly stated the problem they are trying to solve, including answers to most of the required questions. The student clearly stated the problem they are trying to solve, including answers to some of the required questions. The student did not clearly state the problem they are trying to solve and/or did not include answers to most of the required questions. No problem was identified and/or no details were given for the expected solution. PART 2: Working Through Specific Examples (17 points) Write down clear and specific steps to solve a simple version of the problem you identified in Part 1. The steps to solve the problem are in English and easily understood and appear in logical order. The journal entry fully satisfies the requirements. The steps to solve the problem are in English and easily understood and appear in logical order; however, some minor steps may be missing. The journal entry mostly satisfies the requirements. The steps to solve the problem are in English but may not be in logical order or may be missing some steps. The journal entry barely satisfies the requirements. The steps to solve the problem are in English but highly illogical, confusing, or missing critical step(s), and/or the journal entry does not satisfy the requirements. No steps were provided in English and/or no answers to the required questions were submitted. PART 3: Generalizing Into Pseudocode (17 points) Write out the general sequence your program will use in pseudocode, including all specific examples you provided in Part 2. The pseudocode submitted encapsulates the full functionality of the program and includes common program elements. The pseudocode is clearly laid out and readable to a person that does not know Java. The pseudocode submitted encapsulates most of the functionality of the program, including common program elements. The pseudocode is clearly laid out and readable to a person that does not know Java. The pseudocode submitted encapsulates most of the functionality of the program, including common program elements. However, the pseudocode is not clearly laid out and readable to a person that does not know Java. The pseudocode submitted does not encapsulate the functionality of the program to include common program elements. The pseudocode is also not clearly laid out and readable to a person that does not know Java. No pseudocode was submitted and/or the pseudocode submitted was not understandable. PART 4: Testing Your Program (17 points) While writing and testing your program code, describe your tests, record any errors, and state your approach to fixing the errors. Entry consists of a thorough explanation of the testing utilized and why, recording the error(s) found and the approach to fixing the error(s) for each of the test cases. Entry consists of a thorough explanation of the testing utilized, including answering most of the required questions. Entry consists of a thorough explanation of the testing utilized, including answering some of the required questions. Entry does not give a thorough explanation of the testing utilized and/or does not include answers to the required questions. No testing explanation was provided and/or no answers to the required questions were submitted. PART 5: Commenting Your Program (17 points) Submit your full program code, including thorough comments describing what each portion of the program should do when working correctly. The provided code in the journal entry includes comments that thoroughly describe the program flow to a degree that a non-programming individual can easily follow the steps and conclude the outcome of the program. The provided code in the journal entry includes comments that describe the program flow to a degree that a non-programming individual should be able to follow the steps and conclude the outcome of the program. There could be some additional comments needed or added clarity. The provided code in the journal entry includes some comments on the program flow that may not be clear to a non-programming individual and/or may be missing some comments that would make the flow easier to understand. The provided code in the journal entry includes minimal comments to explain the program flow and/or is missing comments that would make the program easy for a non-programming individual to be able to follow the steps and conclude the outcome of the program. The provided code in the journal entry did not include comments and/or comments provided do not provide any description or clarity on program flow. PART 6: Your Completed Program (20 points) Provide the Replit link to your full program code. The program works as expected. No errors present. Any required user input executed correctly. Output was as expected. Performance level not used. Performance level not used. Program did not work as expected; however, detailed comments were given as to why the student felt it did not run, including testing efforts. No link to a program was submitted for testing. C. Requirements The following requirements must be met for your submission: Use a readable 11- or 12-point font. Journal entries must be original and written for this assignment. All writing must be appropriate for an academic context. Follow academic writing conventions (correct grammar, spelling, punctuation, and formatting). Plagiarism of any kind is strictly prohibited. Submission must include your name and the date (included in the template). Include all of the journal parts in a single .doc and .docx file. Include your Replit share link at the appropriate location in the journal template.