Week 1 iLab

------------------------------------------------- TCO 1: Given a simple problem, design and desk-check a solution that is expressed in terms of pseudocode, flowchart, and/or input-process-output (IPO) diagrams. iLab This exercise will cover the steps used to create a solution. You will use variable lists, IPO charts, pseudocode, flowcharts, and desk-checking. Rubric

Point distribution for this activity: Lab Activity | Document | Points possible | Points received | Part 1 | 10 | | Part 2 | 10 | | Part 3 | 10 | | Part 4 | 10 | | Part 5 | 10 | | Total points | 50 | |

Problem

You have an idea for a restaurant tip calculator app that you want to develop for use on your mobile phone when you go out to eat. You can enter the amount of the check before taxes, the tax rate, and the tip percentage. It should display the amount before taxes, the dollar amount of the taxes, the dollar amount of the tip (calculated on amount before taxes), and the total amount including taxes and tip.

(1) Variable List With Data Type
List all the variables you will use (use valid variable names). Indicate whether the data type is string, integer, or decimal, and so on.

(2) IPO Model
List the inputs, any processes, calculations, and outputs. Use the same valid variable names you used in Step 1.

Inputs | Process (calculations) | Outputs | | | |

-------------------------------------------------
Hints: (1) While it is true that some additional string literal messages (those that don’t incorporate variables into the expression) are outputs of the program, you instructor does not require these to be listed in the Outputs of the IPO table. It would not be “wrong” to do so, but these are not usually helpful as a design document. A programmer looking at the IPO table will primarily be concerned with outputs that