Program Grading Criteria

CS 202 Programming Systems

Fall 2013

Program (60 points max) (-5 to -25) Segmentation Fault

Complete and Correct Code (30) (-5 to -25) Does not compile

• Implements the Correct Data Structures
• Written using Functions
• Functions have Arguments
• No Global Variables used
• No String Class used
• Uses well designed Conditional Expressions to stop loops (no while(1) statements)
• Clear demonstration that all features implemented have been tested

OOP Design (10)

• Minimal use of Structs
• No Classes with just Set and Get functions
• Member functions must use have a reasonable set of Arguments
• Separation in classes that have specific Responsibilities
• Use of Single Inheritance Hierarchies

Exclusive use of Dynamic Memory (5)

• No statically allocated arrays

Destructors that Deallocate all Dynamic Memory (10)

Efficient Design (5)

Design Considerations and UNIX Tools (20 points max)

Readable with Complete Sentences (5)

Completely discusses primary design issues (in paragraph form, minimum 1 pg) (5)

Completely discusses how UNIX debuggers were used(minimum 1 pg) (10)

o These must be submitted as separate documents appropriately named in the D2L dropbox for each assignment. Prefer word, pdf or plain text.

Program Style, comments, and documentation (20 points max)

Headers to all Files and all Functions(5) *** Important ***

o Includes your name in the program

o If your program has multiple files, your name must be in each file

o Each file has a header comment describing the purpose of the file

o Every function has a header comment describing the purpose of the function and arguments

Indentation and White Space (5)

In-line Comments and Overall Documentation (5) ***Important***

Consistent Use of Identifiers, program is Maintainable and Readable (5)