User Tools

Site Tools


haas:fall2017:discrete:projects:pnc2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:fall2017:discrete:projects:pnc2 [2017/09/18 12:23] – [Program Specifications] wedgehaas:fall2017:discrete:projects:pnc2 [2017/09/18 15:58] (current) – [Evaluation Criteria] wedge
Line 190: Line 190:
   * At most, **ONE** return statement per function (in the case of **void**, 0 return statements).   * At most, **ONE** return statement per function (in the case of **void**, 0 return statements).
   * No redundant duplication of code to address different top-level conditions or operational constraints (think quantity vs. range- these can successfully co-exist in the same block of code).   * No redundant duplication of code to address different top-level conditions or operational constraints (think quantity vs. range- these can successfully co-exist in the same block of code).
 +  * Never leave an initialized or allocated resource unverified- always do proper error checking (was the file successfully opened? Was the memory successfully allocated?
  
 A common resistance or complaint I get with imposing these is that it may make your solutions more cumbersome or less optimal; that actually may not be an incorrect assertion, but remember: we are interested in the longer-term pursuit of structured thinking and effective problem solving. To foster your ability to think flexibly and differently. We tend to be naturally more averse to going against the grain, but to be an effective programmer/problem solver, this is absolutely necessary. It may be "annoying", and you may choose to make it more aggravating on both yourself and me by agonizing over it, but history and experience teaching has shown me, time and time again, that this is an investment and it pays off in the long run (assuming one actually plays along). A common resistance or complaint I get with imposing these is that it may make your solutions more cumbersome or less optimal; that actually may not be an incorrect assertion, but remember: we are interested in the longer-term pursuit of structured thinking and effective problem solving. To foster your ability to think flexibly and differently. We tend to be naturally more averse to going against the grain, but to be an effective programmer/problem solver, this is absolutely necessary. It may be "annoying", and you may choose to make it more aggravating on both yourself and me by agonizing over it, but history and experience teaching has shown me, time and time again, that this is an investment and it pays off in the long run (assuming one actually plays along).
Line 749: Line 750:
  
 <code> <code>
-312:pnc2:final tally of results (312/312)+390:pnc2:final tally of results (390/390)
 </code> </code>
  
Line 758: Line 759:
 *:pnc2:primeALGO.c implements only specified algorithm [8/8] *:pnc2:primeALGO.c implements only specified algorithm [8/8]
 *:pnc2:primeALGO.c consistent indentation throughout code [4/4] *:pnc2:primeALGO.c consistent indentation throughout code [4/4]
-*:pnc2:primeALGO.c relevant comments throughout code [4/4]+*:pnc2:primeALGO.c relevant how and why comments in code [7/7]
 *:pnc2:primeALGO.c code conforms to project specifications [4/4] *:pnc2:primeALGO.c code conforms to project specifications [4/4]
-*:pnc2:primeALGO.c runtime output conforms to specifications [4/4] +*:pnc2:primeALGO.c implementation free from restrictions [13/13] 
-*:pnc2:primeALGO.c make checkqty test times within reason [4/4] +*:pnc2:primeALGO runtime output conforms to specifications [4/4] 
-*:pnc2:primeALGO.c make checkrange test times within reason [4/4] +*:pnc2:primeALGO make checkqty test times within reason [4/4] 
-*:pnc2:primeALGO.c make verifyall tests succeed [13/13]+*:pnc2:primeALGO make checkrange test times within reason [4/4] 
 +*:pnc2:primeALGO make verifyall tests succeed [13/13]
 </code> </code>
haas/fall2017/discrete/projects/pnc2.1505737435.txt.gz · Last modified: 2017/09/18 12:23 by wedge