haas:fall2019:c4eng:projects:mtf0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| haas:fall2019:c4eng:projects:mtf0 [2019/09/16 13:41] – [Output Specifications] wedge | haas:fall2019:c4eng:projects:mtf0 [2019/09/30 11:57] (current) – [Submission] wedge | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| Your program should: | Your program should: | ||
| * have valid, descriptive variable names of length //no shorter than// 4 symbols | * have valid, descriptive variable names of length //no shorter than// 4 symbols | ||
| + | * I will make an exception for the use of ' | ||
| * prompt the user for the operation (' | * prompt the user for the operation (' | ||
| * properly store this in a variable of type (signed) **char** | * properly store this in a variable of type (signed) **char** | ||
| Line 88: | Line 89: | ||
| </ | </ | ||
| - | =====Reflection===== | ||
| - | Be sure to provide any commentary on your journal regarding realizations had and discoveries made during your pursuit of this project. | ||
| - | |||
| - | * Try this algorithm on some years in the 20th century and see how it fares. | ||
| - | * Is it correct? Is it correct for any of them? | ||
| - | * If it isn't correct, is it consistently off by a value? | ||
| - | |||
| - | This isn't just about implementing a particular algorithm, it is about understanding an algorithm- its domain of correctness, | ||
| =====Submission===== | =====Submission===== | ||
| Line 101: | Line 94: | ||
| * Code must compile cleanly (no warnings or errors) | * Code must compile cleanly (no warnings or errors) | ||
| - | * Executed program must display a total of 2 lines, one for input, one for output. | ||
| * Output must be correct, and match the form given in the sample output above. | * Output must be correct, and match the form given in the sample output above. | ||
| - | * Code must be nicely and consistently indented | + | * Code must be nicely and consistently indented |
| - | * Code must be commented | + | * Code must be well commented |
| + | * Do NOT double space your code. Group like statements together. | ||
| * Output Formatting (including spacing) of program must conform to the provided output (see above). | * Output Formatting (including spacing) of program must conform to the provided output (see above). | ||
| * Track/ | * Track/ | ||
| Line 125: | Line 118: | ||
| < | < | ||
| 78: | 78: | ||
| - | *:mtf0:data stored | + | *:mtf0:proper error checking |
| - | *:mtf0:code is pushed to lab46 repository [4/4] | + | *:mtf0:correct variable types and name lengths used [13/13] |
| - | *: | + | *:mtf0:proper |
| - | *: | + | *: |
| - | *: | + | *:mtf0:no negative compiler messages for program [13/13] |
| - | *: | + | *:mtf0:code is pushed to lab46 repository |
| - | *:mtf0:no negative compiler messages for dow0.c | + | |
| </ | </ | ||
| Line 138: | Line 130: | ||
| * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction | * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction | ||
| * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction | * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction | ||
| - | * Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction | + | * Solutions not organized and easy to read are subject to a 25% overall deduction |
haas/fall2019/c4eng/projects/mtf0.1568641310.txt.gz · Last modified: 2019/09/16 13:41 by wedge
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
