http:^^www.cs.wisc.edu^~melski^cs302^policy^grading.html
来自「This data set contains WWW-pages collect」· HTML 代码 · 共 78 行
HTML
78 行
Date: Mon, 11 Nov 1996 17:02:22 GMTServer: NCSA/1.5Content-type: text/htmlLast-modified: Wed, 11 Sep 1996 17:16:25 GMTContent-length: 2641<HTML><HEAD><TITLE>CS302 Grading Information</TITLE></HEAD><BODY BGCOLOR=#ffffff><H2>CS302 Grading Policy</H2><HR><H3>Grading Percentages</H3><P>The following percentages have been assigned for CS302:<PRE> <B>Exams</B> 60% - Midterm I (week 7) 20% - Midterm II (week 12) 20% - Final (week 16) 20% <B>Quizzes</B> 5% <B>Programs</B> 35% -------------------------------------- <B>Total</B> 100%</PRE><P>Individual assignments and exams will <B>not</B> be assigned lettergrades. Letter grades will be assigned at the end of the semestersuch that 2.8 is the class's overall grade point average. Exceptionsmay be made for truely exceptional classes.<HR><H3>Program Grading Standards</H3><p> Grading of programming assignments is based upon three criteria:correctness, technique, and readability.<p> <strong> Correctness </strong> is by far the most important criterion. A program which does not correctly fulfill the requirements of theassignment is subject to a grade reduction of as much as 50% or more.<p> The <strong> technique </strong> used in a program is the meansin which that particular problem was solved. A solution which iscorrect but clumsy or awkward is subject to a grade reduction of as muchas 25%. Sometimes there will be very little leeway in this area; othertimes there might be several correct solutions.<p> The <strong> readability </strong> of a program refers to the easewith which a <em>human</em> reader (such as the grader!) can read andunderstand the source code. The readability does not affect theexecution of the program; however, poor readability can result inprogramming errors which make the program incorrect. Poor readabilitycan also result in a grade reduction of as much as 25%. The readabilityof a program includes:<ul> <li> Proper and consistent indentation of statements <li> Documentation (via comments) for functions and parameters, and for non-obvious variables and pieces of code <li> Use of blank lines to separate logically separate pieces of code <li> Use of meaningful identifiers for variables, functions, etc. <li> Correct use of constants <li> Use of <em>idioms</em> (customary standard ways of writing logically equivalent pieces of code) discussed in class</ul><HR>Last modified: Wed Sep 11 12:16:25 1996 by David Melski<ADDRESS> <!WA0><!WA0><!WA0><A HREF="http://www.cs.wisc.edu/~melski/melski.html">melski@cs.wisc.edu</A></ADDRESS></BODY></HTML>⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?