Start with the same partner as last week, but in opposite driver/navigator roles from last week. (See your lab leader if your partner is missing, or if you missed last week.) Remember that only the driver can write/type; the navigator's role is to oversee and make suggestions and corrections.

The Problem:

Assume you have the following degree requirements:

• 20 math credits - only courses from departments 110 and 550 may count.
• 2 writing courses - only courses with at least 3 credits and a W designator may count.
• 18 humanities or social science credits - only courses with at least 3 credits and an H or an S (or both) designator may count.
• 36 credits from your major department, at least 16 of which are upper level courses - only courses that match the input department code may be counted, and only those with numbers >=300 qualify for the upper level category.
• elective credits so that the total number of credits taken is at least 124.

Using this information, your program must then output all the degree requirements that the course could be used to satisfy, including specifically whether it is an upper or lower level major course. If the course does not satisfy any of the first four category requirements, then say it counts as elective credit only. Three sample runs are shown below to give you an idea.

SAMPLE #1
Enter major department code: 550
Enter course data (dpt.num credits HSEQNW): 600.226 3 EQ
This course can be counted as elective credit only.

SAMPLE #2
Enter major department code: 350
Enter course data (dpt.num credits HSEQNW): 350.410 3.5 HWS
This course can be counted towards your writing requirement.
This course can be counted towards your HS requirement.
This course can be counted towards your upper level major requirement.

SAMPLE #3
Enter major department code: 140
Enter course data (dpt.num credits HSEQNW): 110.109 4
This course can be counted towards your math requirement.

Phase 1) ANALYSIS: Figure out minimally how many different test cases your will need in order to be really sure that your program works the way it is supposed to. Write down how many, and an explanation of the different kinds of tests that must be included. Share with your lab leader for approval before continuing.

Phase 2) CODING: In this phase you will get and parse the input data. (This is the hardest part of the project most likely.) Prompt for and read the major code, then prompt for and read the course data. Remember that the user must be able to type all the course data on one line. Now using String methods to separate the course data into 4 parts, saving each into appropriate variables: department, number, credits, areas. Print all five pieces of information (including major code), labelled, one per line.

Phase 3) MORE CODING: Now that the data is in useful forms, we can start to check for requirements. Add statements to see if the course applies to the math credit requirement, and if it applies to the writing requirement. They are not mutually exclusive. Print appropriate statements for each.

Phase 4) STILL MORE CODING: Now check on humanities/social science, and also whether or not the course could be used for the major. If it is a major course, indicate whether it is upper or lower level credits.

Phase 5) FINAL CODING: Lastly, figure out how to keep track of which requirements were met, so that if the course doesn't satisfy any of them, it says that is an elective course. If you have extra time, add input validation: Major codes, department codes and course numbers must be between 1 and 999. Credits must be a multiple of 5 between 1 and 4.5 inclusive. Area designators can only be the letters H,S,E,Q,N,W - you'll need a loop for this last challenge.