The purpose of this assignment is to get you back into programming and give you some practice with the new concept of recursion. It also utilizes many of the C$++$ topics that you should be familiar with from your first course in C$++.$

Suggestion: Get in the habit of reading the instructions carefully. Make notes about the various requirements. If you simply skim the instructions, you run the strong risk of losing points.

FYI: There is a checklist at the end of all instructions that you can review before submitting to help ensure you have what is needed.

Tip: This tip applies to all Lab assignments. Information is to be displayed and entered in the order in which you see examples in the instructions. If you change displayed text or input order because you think it looks better, you will lose points. All of your career, you will be developing software that has instructions, often called Requirements. Start today learning to follow the instructions you are given. This includes any input prompts that show an example or range of values.

Reminder: All inputs and outputs provided in each set of instructions are what you are to follow as closely as possible.

Reminder: Asking the professor questions is encouraged. Questions are taken in the order received. If you wait until the last minute to ask questions, they might not be answered before the submission deadline.

Visual Studio Warning:

There are times when you will find that a Visual Studio project gets messed up$.$ That happens, so do not beat yourself up for it$.$ Simply start over.

Some of you may discover that in Visual Studio, you can link existing code files to the project instead of copying them physically into the project. This can be beneficial in the work world. However, in CSIS $112,$ doing this will cause your Lab not to compile. A compile failure earns you a $0$ for the Lab.

The reason for this is that the project will compile and execute on your computer when you link in code files. However, when you zip up the entire project to submit it$,$ the zip process only pulls in the files and folders that are physically directly below your start point in the folder hierarchy. When you link files into a Visual Studio project, they do not necessarily reside in the project folder hierarchy. Here are the steps you need to follow to ensure all code files are inside the project folder.

$1.$ Determine the folder that your code files are in for the new project.