This immediately suggests "loops within loops," and whether those inner loops are nested in the outer loops, or are wholly contained within subprograms (or RAPTOR subcharts) is something you'll have to figure out. Think about what will work best for your program.
Be sure to update the documentation in your RAPTOR program, to show when you've modified it and what youve done to it. Use comments within your RAPTOR file to tell us what you changed.
The "default values" strategy that we used last week for the tax rates has really made the bookkeeper happy. Well, happier, that is. He wants more. He'd like to be able to break the processing of the program into a few steps: a step that lets him see and edit all of the tax rate parameters; then a step that lets him do the same for the per-employee paycheck data; then the calculate and print check step.
This immediately suggests "loops within loops," and whether those inner loops are nested in the outer loops, or are wholly contained within subprograms (or RAPTOR subcharts) is something you'll have to figure out.
As part of this, you'll have to modify the prompts to the user, so that theyre told what "good" data is to start with, vs. garbage data. Then develop the logic that checks the data, and either tells the user Wrong, do over! and prompts for and gets input, or moves on to processing.
STRONG HINT: Would these "data validation" chores be a great opportunity to use a subprogram? How would you do this in RAPTOR?
Be sure to update the documentation in your RAPTOR program, to show when you've modified it and what youve done to it.
Once your program is working in RAPTOR, follow the instructions in the associated module item to submit your work.