On Criteria for Gradin g Student Program s James W . Howatt Department of Computer Scienc e St . Cloud State Universit y St . Cloud, MN 5630 1 jhowatt@eeyore .stcloud .msus .edu Introduction . For many of us, the initial experience of grading programs brings a quick realization of the need for objectivity and consistency . When grading, we should consider onl y the program before us and the requirements tha t led to it . We should not be swayed by comparisons with other programs, by distracting characteristics of the code, or by past interaction s with the coder . Also, we should focus on th e same concepts to the same degree in every pro gram, otherwise grading becomes nonuniform ( a fact that students see quickly) . This is especially important when several teaching assistant s are grading for the the same course . To help u s achieve this needed consistency and objectivity, we developed set of grading guidelines . Originally defined in 1989, they have evolved into th e criteria described here . Since we were reasonably sure that others ha d recognized the same needs, we looked to the literature for
/lp/association-for-computing-machinery/on-criteria-for-grading-student-programs-Tqg6B8K2mx