You can use the following guidelines to interpret your scores.
The total points is distributed and graded under Execution (40%) and
Code (60%) - which appears under E and C in the graded paper. . The
meaning and distribution of marks in each category is given below.
Execution (40 points)
Here, the source code submitted is (without looking into the code)
compiled and run with important test cases. In this category, marks are
deducted in the following way:
* Not Compiling -40
* Compiling ,but no response -30
* Running but giving wrong output upto 20
A tick mark means that no points are deducted.
Code, Comments, Style and Logic (60 points)
Here, the source code submitted(as hard copy) is evaluated. Marks
in this category is deducted in the following way .
* No Comments , sparse comments or upto -20
meaningless comments
* Hard to follow or convoluted logic upto -15
* Logical errors upto -25
As before, a tick mark means that no points are deducted.
Comments from the grader
The overall performance of all the students was remarkably good.
Here are some of my observations.
(i) It is unfortunate that some students who had a perfect program
lost 40 points because of just missing little things like a
semi colon. These students could have avoided this problem by running their
program atleast once before turning it in.
(ii) Lack of comments is one reason why many students lost some points.
Comments are important for a good program
(iii) Some students have not followed the requirements for submission
such as using the name project1.cpp for your program or having
exactly one file on your diskette.
Imagine yourself grading around 200 projects.
This is an impossible task, if every student uses a different file name or
has three or four files on the disketter.
Please follow the given instructions; next time you will loose points for
violating these instructions.
If you have any questions, feel free to meet either the professor
(Sriram Pemmaraju) or the grader (Kannan Janakiraman) .
Kannan Janakiraman
8 March 1997