Pseudocode and Flowchart

Overview Pseudocode is “language agnostic,” meaning that you can create pseudocode with little to no experience in a specific programming language. Pseudocode helps you plan out your code in a logical manner. Flowcharts are a powerful way to graphically represent logic, decisions, and branching. This activity will help you develop the skills necessary to plan and organize your code, which is an important skill for programmers at all experience levels. In this activity, you will write pseudocode and create a flowchart for a basic computational task. The purpose of this assignment is to prepare for your Project One submission in Module Three. Remember to revisit the pseudocode and flowchart you create in this module and implement any feedback from your instructor before you submit your pseudocode and flowchart in Project One. Prompt Your client, Pet BAG, has provided you with a specification document detailing its software needs. To begin, review the Pet BAG Specification Document. Select either the Pet Check-In or Pet Check-Out method, which are detailed in the Functionality section. You will design a solution using pseudocode and a flowchart for the method you select. You do not need to write pseudocode for both methods. As you read through the descriptions for each method, ask yourself the following: • How would I break down these steps in a way that a computer can understand? • What information would I need from the user at each point? • When would it be a good idea to use “IF” and “IF ELSE” statements? After reading through the specification document and selecting your method, follow these steps to complete this assignment: 1. Based on the method you chose, write pseudocode that lays out a plan for the method. Start by breaking down the description of the method into a series of ordered steps. As you write and review each step, consider the following: o What input does the computer need to complete the task? Be sure to prompt the user for the appropriate input. o When might you need to use decision branching and use a different set of steps depending on the user input? If you used decision branching, did you account for all possible input values? 2. Based on the pseudocode you wrote, create a flowchart for the method you selected. You may draw your flowchart by hand, or you may use a flowcharting tool such as Lucidchart. Your flowchart will help your team communicate to your client how you are planning to develop the software. In your flowchart, be sure to do the following: o Include start and end points. o Include appropriate decision branching. o Align the flowchart to the check-in/check-out process you selected.