7.8.0.10

Code Grades

grades

In order to get a grade for your productes, you will need to perform a self-evaluation. As we harvest your code from your git repos, we will push out a self-evaluation report form (in plain txt). You will have 25 hours to fill it out and push it back to origin.

Your submissions will be evaluated along two dimensions:
  • for correctness, via delivery inspections of all requested files (and no extras) plus "test fests." The latter means we will run your test harnesses on the instructor’s and all of your peers’ tests.

    If you disagree with the result of a test fest, send email to the technical TA and set up an appointment. You will have to argue that the lead instructor’s code and/or integration tests are wrong. (This is not impossible.)

  • for systematic design, via code inspections. That is, after you turn in your self-evaluations, we will read select pieces of your requested files and check them against basic software quality criteria, design standards taught in Fundamentals I, II, OOD and Logic.

    For any disagreements concerning your grades, first see the person who "signed" the code inspection report. If you can’t resolve the issue, see the pod leader of the grader’s pod:

    instructor

     

    time

     

    pod leader

     

    shoulder

     

    grader 1

     

    grader 2

     

    grader 3

    Matthias

     

    09:50

     

    Suzanne Becker

     

    Kanika Rana

     

    Peter Abbondanzo

     

    Evan Hiroshige

     

    Felicia Zhang

    Jason

     

    01:35

     

    Julia Belyakova

     

    Suzanne Becker

     

    Mownika Asokan

     

    Deepak Kumar

     

    Dhaval Dedhia

    Jason

     

    03:25

     

    Kanika Rana

     

    Julia Belyakova

     

    Akanksha Gupta

     

    Ritika Gupta

     

    Mohan Shobana

    As a last resort, see your instructor.