18.6. Homework: Grade Calculation from Individual Scores¶

18.6.1. Functional Requirements¶

1. Instead of bombing out if the weights don’t add up to 100, use Do-While Loops to prompt the user again for all of the weights until they do add up to 100. A do { ... } while loop is the right choice here, because you can test all of the weights at the end of the loop, after each time they have been entered in the loop.

2. Write a function, FindAverage, to do the following. The example refers to the category exam, but you will want your code to work for each category, and hence the category name will need to be a parameter to FindAverage.)

   Prompt the user for the number of items in the category:

   Please enter the number grades in category exam: 4

   Instead of prompting the user for an overall average exam grade, use a loop to read one grade at a time. The grades will be added together (on the fly) to give the grade for that category. For example, after you have asked for the number of exams, you’d prompt the user to enter each exam grade and have the program compute the sum. As soon as a category sum is calculated, also print out the average as shown in the sample below:

   Please enter the grade for exam 1: 100

   Please enter the grade for exam 2: 90

   Please enter the grade for exam 3: 80

   Please enter the grade for exam 4: 92

   Calculated average exam grade = 90.5

   Of course you must return the grade to the caller for use in the overall weighted average grade.

   A category may have only a single grade, in which case the user will just enter the number of grades as 1.

3. Once you have read in the data for each of the items within a category, you’ll basically be able to reuse the code that you developed in the previous assignment to compute the weighted average and print the final letter grade.

4. Print the final numerical average, this time rounded to one decimal place. If the final average was actually 93.125, you would print 93.1. If the final average was actually 93, you would print 93.0. If the final average was actually 93.175, you would print 93.2.

18.6.2. Style Requirements¶

1. For this assignment, you are expected to start using functions for all aspects of the assignment. For example, it can become tedious in a hurry to write code to prompt for each of exams, labs, homework, etc. when a single function (with parameter named category) could be used to avoid repeating yourself. In particular you should write your function to take advantage of our UI class, from User Input: UI.
2. Also beginning with this assignment, it is expected that your work will be presented neatly. That is, we expect the following:
   • proper indentation that makes your program more readable by other humans. Use all spaces, not tabs to indent. You never know what default tabs your grader will have set up.
   • proper naming of classes and functions. In C#, the convention is to begin a name with a capital letter. You can have multiple words in a name, but these should be capitalized using a method known as CamelCase [CamelCase]. We also recommend this same naming convention for variables but with a lowercase first letter. For variables, we are also ok with the use of underscores. For example, in homework 1 we used names like exam_grade. If you use CamelCase, you can name this variable examGrade.
   • If you have any questions about the neatness or appearance of your code, please talk to the instructor or teaching assistant.
   • This guide from CIS 193 at [UPennCSharp] provides a nice set of conventions to follow. We include this here so you know that other faculty at other universities also consider neatness/appearance to be important.

18.6.3. Grading Rubric¶

25 point assignment broken down as follows:

• Loop until weights add to 100: 5
• Average any number of grades in a category: 5
• One function that is reused and works for the average in each category: 5
• Print final numerical grade rounded to one decimal place: 2
• Previous program features still work: 3
• Style: 5

18.6.4. Logs and Partners¶

You may work with a partner, following good pair-programming practice, sharing responsibility for all parts.

Only one of a pair needs to submit the actual programming assignment. However both students, independently, should write and include a log in their Homework submission. Students working alone should also submit a log, with fewer parts.

Each individual’s log should indicate each of the following clearly:

• Your name and who your partner is (if you have one)
• Your approximate total number of hours working on the homework
• Some comment about how it went - what was hard ...
• An assessment of your contribution (if you have a partner)
• An assessment of your partner’s contribution (if you have a partner).

Just omit the parts about a partner if you do not have one.