The table below will form the basis of your pseudocode. Complete the table according to the instructions found in Unit 3 Lesson 9.

Question

Task to Complete:
Original Steps (Three Steps)
More Detailed Steps (Six Steps)
Super-Detailed Steps (Nine Steps)



















Put your code to the test:
Design a plan to collaborate with a friend or family member to use your pseudocode as you witness the performance.
Be sure to document any problems and possible solutions for your code.
And don’t forget to give your collaborator an expected timeline to complete the task.
Make time for the development of a solution to any unexpected setbacks you experience.
Remember to analyze the patterns and sequences you find in your pseudocode. Can you identify its variables?
While observing your helper complete your task, complete the following table to document anything you notice or question about possible patterns in your pseudocode, good or bad. (Remember that when working with algorithms, a pattern is something that repeats an action.)

Patterns
Performance
Pre-testing
Unintentional patterns that you catch



Predictions about how your code will direct performance



Post-testing
Unexpected problem patterns



Ways that further revision might make your code more effective




What to Submit
Save this file as a PDF and submit to the dropbox in lesson 9.

Grading Rubric:

Content
Format
Communicate
Full Credit

Pseudocode shows a full analysis of a problem, leading to a thorough solution.
Analysis of helper’s performance led to improvements in pseudocode.

The pseudocode is clear, neat, and easily understood by someone other than the student.

Clearly communicates their findings, project, and/or results.
Partial Credit

Pseudocode shows some analysis of a problem, leading to a solution.
Analysis of helper’s performance led to changes in pseudocode.

Pseudocode is somewhat clear, neat, and easily understood by someone other than the student.

Attempts to communicate their findings, project, and/or results but could have done so in a more effective manner.
Little Credit

Pseudocode shows little to no analysis of the problem.
Analysis of helper’s performance led to additional mistakes in pseudocode.

Pseudocode is not clear, neat, and easily understood by someone other than the student.

Does not communicate their findings, project, and/or results.

Answer 1

Here’s a template to help you organize your pseudocode analysis and document the required elements based on the instructions provided.

Pseudocode Development Table

| Task to Complete | Original Steps (Three Steps) | More Detailed Steps (Six Steps) | Super-Detailed Steps (Nine Steps) | |--------------------------|---------------------------------------------|-----------------------------------------------------------------|---------------------------------------------------------| | Example Task: | 1. Go to the store | 1. Put on shoes | 1. Get out of bed | | | 2. Buy groceries | 2. Grab my wallet | 2. Walk to the front door | | | 3. Return home | 3. Check shopping list | 3. Open the front door | | | | 4. Get in the car | 4. Walk to the car parked in the driveway | | | | 5. Drive to the store | 5. Get in the car and close the door | | | | 6. Pay at the cashier | 6. Start the car and drive to the store | | | | | 7. Go into the store and find groceries | | | | | 8. Pay for groceries at the cashier | | | | | 9. Drive home and park the car |

Collaboration Plan

1. Identify a Collaborator: Choose a family member/friend who is willing to help.
2. Sharing Pseudocode: Provide the pseudocode you’ve developed for your task.
3. Collaborative Testing: Schedule a time to observe them performing the steps in your pseudocode.
4. Documenting Problems: Create a log for any issues or unintentional patterns they encounter while performing the steps.
5. Timeline: Allocate a specific timeframe for each task, allowing extra time for unexpected setbacks.
6. Analysis After Testing: Discuss with your collaborator what went well, what didn’t, and how you can improve the pseudocode.

Observation Table

| Patterns | Performance | Pre-testing | Unintentional patterns that you catch | |------------------------------------|----------------------------------------|------------------------------------------------|-----------------------------------------------| | Repeat actions (e.g., “Check shopping list” multiple times) | The process is fast or slow based on certain steps | Noted that using a list saves time | Realized I didn’t account for waiting in line | | | | | | | Predictions about how your code will direct performance | Tasks should naturally flow from one to the next. | Should avoid confusion in complex steps | Steps too complex for the collaborator |

| Post-testing | Unexpected problem patterns | Ways that further revision might make your code more effective | |------------------------------------|---------------------------------------|---------------------------------------------------------------| | Found that some steps were missed | Skipping steps due to similarity in tasks | Split larger steps into smaller, more achievable actions | | | Trouble remembering sequential order | Added reminders or prompts within the pseudocode | | | Overall time to complete tasks slower than expected| Create a visual checklist for guidance |

Conclusion

Make sure to take detailed notes while observing your collaborator. This will help you understand how effective your pseudocode is and what improvements might be necessary. Once you have completed your observations and analysis, compile all your findings into a comprehensive report that adheres to the submission guidelines provided. Don’t forget to save the document as a PDF before submitting it.

Good luck!