COMP10002 Assignment 1 Feedback: XXUSERNAMEXX

Program Presentation

• Up to Stage 1 initial allocation, +0.5.
• Up to Stage 2 initial allocation, +1.5.
• Up to Stage 3 initial allocation, +2.5.
• Up to Stage 4 initial allocation, +2.5.
• Up to Stage 5 initial allocation, +2.5.

Deductions

Some subset of the following lines will be retained by the marker. Deduct 0.5 marks for every type of errors found. Marks in each section won't go below zero.

• #defines not in upper case;
• absence of function prototypes;
• bad choice for function names;
• bad choices for variable names;
• excessive commenting;
• inconsistent bracket placement;
• inconsistent indentation;
• insufficient commenting (at least one comment per function to explain what the function does);
• lack of whitespace (blank line between functions or code blocks);
• lines >80 chars;
• no authorship statement (student name and id at the top of program);
• use of external code without attribution, -0.5 for each occurrence;
• use of magic numbers;
• other stylistic issue (minor);
• other stylistic issue (major), -0.5 for each occurrence;

Additions (included in total mark only if marks lost within this first section)

• comment that says "algorithms are fun", +0.5;
• overall care and presentation, +0.5;

Other Comments from Marker

Structure and Approach

Some subset of the following lines will be retained by the marker.

• Up to Stage 1 initial allocation, +0.5.
• Up to Stage 2 initial allocation, +1.5.
• Up to Stage 3 initial allocation, +2.5.
• Up to Stage 4 initial allocation, +2.5.
• Up to Stage 5 initial allocation, +2.5.

Deductions
Some subset of the following lines will be retained by the marker. Deduct 0.5 marks for every type of errors found. Marks in each section won't go below zero.

• duplicate code segments;
• global variables;
• main function modified, -1;
• insufficient use of functions;
• functions too long (over 50 lines for any function) or too complex;
• overly complex algorithmic approach;
• unnecessary duplication/copying of data;
• typedefs without "_t";
• overly complex function argument lists;
• using == for equality on doubles;
• using any string.h functions in Stage 5, -1;
• other structural issue (minor);
• other structural issue (major), -0.5 for each occurrence;

Other comments from marker:

Program Execution

Some subset of the following lines will be retained by the marker.

• Up to Stage 1 initial allocation, +2.
• Up to Stage 2 initial allocation, +4.
• Up to Stage 3 initial allocation, +6.
• Up to Stage 4 initial allocation, +8.
• Up to Stage 5 initial allocation, +10.

Deductions

Some subset of the following lines will be retained by the marker. Marks in each section won't go below zero.

• deduct all execution marks if program generates no output at all; otherwise, deduct marks for the following items:
  
  
• incorrect Stage 1 output on invis0, -1 (for all formatting errors in Stage 1, deduct 0.5 marks once across all test cases)
• incorrect Stage 2 output on invis0, -1 (for all formatting errors in Stage 2, deduct 0.5 marks once across all test cases);
• incorrect Stage 3 output on invis0, -1 (for all formatting errors in Stage 3, deduct 0.5 marks once across all test cases);
• incorrect Stage 4 output on invis0, -1 (for all formatting errors in Stage 4, deduct 0.5 marks once across all test cases);
• incorrect Stage 5 output on invis0, -1 (for all formatting errors in Stage 5, deduct 0.5 marks once across all test cases);
  
  
• incorrect Stage 1 output on invis1, -1;
• incorrect Stage 2 output on invis1, -1;
• incorrect Stage 3 output on invis1, -1;
• incorrect Stage 4 output on invis1, -1;
• incorrect Stage 5 output on invis1, -1;

Late Penalty

XXMARKXX