CSE 258:
Operating Systems
Homework
and Programming Assignment Grading
Some basic information about grading of homeworks and programming
assignments:
- The due time of the homework is on the assignment.
Written assignments should be handed in class. Anything turned in after
the class will be considered late. Late homework with no justified reasons is
NOT permitted.
- Copying of programs, written homeworks, or exams is not permitted. You can talk to other
students
about the assignments, but the work must be substantially your own. If you're having trouble
with an assignment or having trouble meeting a deadline, see
the instructor or the TA. We will bend over backwards to help
you but we will not tolerate cheating.
Written Assignments
Please type the text part of your homework (e.g., using MS
Word or other word processors). You can draw pictures by hand. Please make sure to show
all of your work. We will give partial credit, but only if you show the
work involved!
Programming Assignments
For your programming assignments, you should hand in both an
electronic copy and a hardcopy. See the respective assignment on what is
required for the electronic copy. For the hardcopy, you should include:
- your source code with in-line documentation. Not
documented program will be heavily punished.
- a separate (typed) document describing the
overall
program
design, a description of ``how it works'', and design tradeoffs considered and
made. Also describe possible improvements and extensions to your program (and
sketch how they might be made). The format of the
description file should be as follows:
Description: describe the overall program design and ``how it works''
Tradeoffs:
discuss the design tradeoffs you considered and made
Extensions
:
describe possible improvements and
extensions to your program, and describe briefly how to achieve them.
Test cases:
describe the test cases that you ran to convince yourself that it is
indeed correct. Also describe any cases for which your program is known not to
work correctly. I should emphasize the importance of designing appropriate test
cases. In general, thorough test cases of a program should contain both special
cases and normal cases. The description of your test cases should follow the
following format:
First, describe your overall design for the test cases.
Then, for each
test case:
Describe your test case:
Describe why you choose this test case:
Describe the output of the test case:
If your turn-in does not follow the above format, you'll get 10 points off
automatically.
Grading
Program Listing
works correctly 50 points (shown by testing results)
in-line documentation 10
quality of design 10
Design Document
description 5
tradeoffs discussion 5
extensions discussion 5
Thoroughness of test cases 15
Total 100 points
Extra Credit up to 10 points, depending on assignment
Late Programs NOT allowed
Notes:
- A full 10 points for quality of design will only be given to
well-designed,
thorough programs. A correctly working, documented and tested program
will
not necessarily receive these 10 points.
- Extra Credit: If you are not sure that you can complete a working
program that earns your the extra credit, be sure to submit a solution to the basic assignment.
bing@engr.uconn.edu