Overview Pseudocode is language agnostic. This means that you can create pseudoc

Overview
Pseudocode is language agnostic. This means 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 of all experience levels.
In this milestone, you will be working with the same scenario as in Project One. You are part of a development team that has been asked to design and develop custom software for a local pet boarding and grooming business, Pet Boarding and Grooming (Pet BAG). In this milestone, you will work on creating pseudocode and a flowchart for either the pet check in or pet check out method to meet the Pet BAG company’s specifications. Your work in this milestone is one portion of the work you will need to complete for Project One. After you have completed this milestone, make sure to review any instructor feedback you receive so that you can make improvements before your final submission in Project One.
———————————————————————————–
Your supervisor has provided you with the Pet BAG Specification Document PDF. This document reviews Pet BAG’s software needs. Review the pet check in and pet check out methods, which are described in the Functionality section. Then choose one of these methods (check in or check out) to implement. As you read through the descriiptions 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 decision branching, such as “IF” and “IF ELSE” statements?
Next, write pseudocode that outlines a plan for the method you chose and aligns to the specifications. Start by breaking down the descriiption of your chosen method into a series of ordered steps. As you write and review each step, consider the following:
What input does the computer need to complete the task? Be sure to prompt the user for the appropriate input.
What output should the computer display to the user?
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?
Reminder: You do not need to write pseudocode for both methods.
Based on the pseudocode you wrote, create a flowchart for the method you selected. Remember, you do not need to create a flowchart for both methods. 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:
Include start and end points.
Include appropriate decision branching.
Align the flowchart to the check in or check out process you selected.
Submit your pseudocode and flowchart in a 1- to 2-page Microsoft Word document with double spacing, 12-point Times New Roman font, and one-inch margins.