Instructions

Note: Complete this activity before completing zyBooks Lab 3.11: Painting a Wall.

This activity is divided into two parts: Part one involves developing a flowchart (for printing a food receipt) and pseudocode (to help with painting a wall), and part two is a reflection on the flowchart/pseudocode development process and its value.

For part one of this activity, you will need to use a digital diagramming tool. The two links below lead to web-based diagramming tools, but you may also choose a different tool. When your flowchart is complete, save it as a PNG file and insert it in a Microsoft Word document for submission.

draw.io is a web-based, cross-platform (Windows, Mac, Linux) diagramming software application. Diagrams are drawn online and can be downloaded to a file. For assistance, visit the draw.io online support page.

Lucidchart is also a web-based, cross-platform digital diagramming software application. This resource requires registration. Once you are registered, a brief tutorial is provided when you start your first project.

Part One

• Develop a flowchart to illustrate the steps and logic necessary to print the kind of food receipt you might receive from a food truck or restaurant. You must allow for the input of a food item’s name and price, the quantity purchased, and a 6% meals tax to be added to the total bill. The printed receipt should list each item, quantity, individual price, and total price, as well as a subtotal, the calculated meals tax, and the grand total. If you would like to test your logic, you may complete the optional lab in Chapter 2 of zyBooks: Program: Food Receipt. For assistance in creating your flowchart, refer to the Guide to Flowcharts PDF document.
• Develop pseudocode that corresponds to (implements) the Chapter 3 zyBooks activity, Program: Painting a Wall. You will write the actual code for this program in your next activity, so your pseudocode should contain the following components:
  • The size of the wall (input)
  • How much paint is needed based on size (calculation)
  • The ability to print this information (output)

Be sure that your pseudocode has a logical flow, and that the terminology is not too technical or too vague. For assistance creating your pseudocode, refer to the Guide to Pseudocode PDF document.

Part Two

Discuss the value in producing pseudocode and flowcharts:

• Which one did you find easier?
• What challenges did you face creating pseudocode or a flowchart (or both)?
• Given that functioning programs are what is actually run by users, how would skipping the creation of pseudocode and flowcharts impact the program and/or the programming process?

To complete this assignment, review the Module Two Short Paper Guidelines and Rubric PDF document.