Python Journal Template
Directions: Follow the directions for each part of the journal template. 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.
Remember to review the Touchstone page for entry requirements, examples, and grading specifics.
Name:
Date:
Final Replit Program Share Link:
Complete the following template. Fill out all entries using complete sentences.
·
Inspiration
When writing your entry below ask yourself the following questions:
· Do you see common program elements and patterns in your specific examples/scenarios in Part 2, like variables, conditionals, functions, loops, and classes? These should be part of your pseudocode for the general sequence as well.
· Are there places where the steps for your examples/scenarios in Part 2 diverged? These may be places where errors may occur later in the project. Make note of them.
· When you are finished with your pseudocode, does it make sense, even to a person that does not know Python? Aim for the clearest description of the steps, as this will make it easier to convert into program code later.
<Write your pseudocode here>
PART 4: Testing Your Program
Task
While writing and testing your program code, describe your tests, record any errors, and state your approach to fixing the errors.
Requirements
· For at least one of your test cases, 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:
· Record the details of the error from Replit. A screenshot or copy-and-paste of the text into the journal entry is acceptable.
· Describe what you attempted in order to fix the error. Clearly identify what approach was the one that worked.
Inspiration
When writing your entry below ask yourself the following questions:
· Have you tested edge cases and special cases for the inputs of your program code? Often these unexpected values can cause errors in the operation of your program.
· Have you tested opportunities for user error? If a user is asked to provide an input, what happens when they give the wrong type of input, like a letter instead of a number, or vice versa?
· Did the outcome look the way you expected? Was it formatted correctly?
· Does your output align with the solution to the problem you coded for?
<Record your errors and fixes here>
PART 5: Commenting Your Program
Task
Submit your full program code, including thorough comments describing what each portion of the program should do when working correctly.
Requirements
· The purpose of the program and each of its parts should be clear to a reader that does not know the Python programming language.
Inspiration
When writing your entry, you are encouraged to consider the following:
· Is each section or sub-section of your code commented to describe what the code is doing?
· Give your code with comments to a friend or family member to review. Add additional comments to spots that confuse them to make it clearer.
<Copy your full program code here, including comments>
PART 6: Your Completed Program
Task
Provide the Replit link to your full program code.
Requirements
· The program must work correctly with all the comments included in the program.
Inspiration
· Check before submitting your touchstone that your final version of the program is running successfully.
<Provide the link to your program here>
Python Journal Template 1