GPA survey: Suppose that an instructor needs a piece of software to record the GPA of a class, and to find the number of students in each GPA. The software first allows the instructor to enter the number of students enrolled in the class, and then to enter the GPA of all students one by one. For each student, the input must be between 1 and 4 inclusively. Otherwise, the software displays a message as Invalid number! and asks for a new GPA for the same student. A sample interaction is shown below:

Sample input: Sample Output:

Note: you should trace the GPA list just once. So, you should use an array int GPAFreq[4] to store the frequencies of each GPA from 1 to 4.

Part A: RAPTOR Exercise

1. Understand more about RAPTOR by watching the video clip about arrays
2. Start RAPTOR and create the flowchart of GPA survey. To save time during software development, your algorithm needs to use random number generator to simulate the input of GPAs. For example, floor(Random*6) produces a random number between 0 and 5.
3. Save the flowchart to a file named gpaSurvey.rap in the working directory on the PC you are using.

1. Demonstrate the gpaSurvey.rap file to GA/TAs and run with different input values.

Suggestion: Use subcharts to help improving the readability of the flowchart.

Part B: C Programming Exercise

1. Implement the algorithm as represented by gpaSurvey.rap, and write an equivalent C program that accomplishes what the flowchart does.

Hints: On page 173 of the textbook, an example of using random numbers is showed in the C codes of deal.c.

1. Save your program to a file named gpaSurvey.c in the working directory on the PC you are using.
2. Demonstrate the gpaSurvey.c file to GA/TAs and run with different input values.

EVALUATION:

You need to show your GA/TA the complete programs at the end of this lab, or at the beginning of your next lab. The marks you will receive for this lab are made of two parts: Lab work marks 10 and attendance marks 5. Total 15 marks.

Lab Work Mark: Your C code will be evaluated based on your solutions for the problems based on the following scheme:

1. Does the code run and meet specifications?
   • Is input adequate and input data type properly validated?
   • Is processing adequate?
   • Is output correct and adequate?
   • Is the code compliable? Is the code run properly?

2. Is the code properly commented?
   • Is the program title, programmers first and last name, and the date posted at the top in a multi-line comment?
   • Is each significant step of the program properly commented?
   • Are comments added to clarify details?
   • Are comments clear, accurate, neatly formatted, and have no misspellings?

3. Is the code properly formatted?
   • Are blocks of code indented according to their parent-child relationship?
   • Do curly braces line up vertically?
   • Is there an empty line between significant steps (blocks) of the program?
   • Is the width of the code contained within a reasonable limit so that minimal horizontal scrolling is required (with 800 x 600 monitor resolution), and there is minimal linewrapping when printed?
   • Is camel-case notation used for variable, e.g. employeeLastName?