CS 416 Assignment Home page
In this document:
Assignment Guidelines
- Grading Policy
- As stated by Ricardo, late homeworks will not be
accepted. If you have emergencies or special situations, talk
to us or the professor BEFORE the deadline.
- Copies of homework from former students will be assigned a
negative
grade.
- Copies of homework from another classmate will be assigned
negative
grades (to both) unless it is a group assignment.
- Any other form of copying or cheating will be assigned negative
grades. Check with us what is considered cheating and dishonesty if
you have questions.
- Regrading can be asked by e-mail or personally up to 48 hours
(not
counting weekends) after the homework was handed back to you. After
that,
grades are final unless Ricardo authorizes us to regrade it.
- When asking for your assignment to be regraded, keep in mind
that your
grade can move up, down or stay the same.
- Show your work. Turn in what you did or explain why you
couldn't do it.
You get partial credit even if the answer is wrong, as long as you show
a correct
understanding of the problems.
- Be neat. Decent reports help grading and avoid incorrect
interpretation
by the grader.
- Issues not addressed here will be discussed with Ricardo when
(and if)
needed.
Office Hours
- Fabio Oliveira: Fri 8:30-10:30am, Hill 411. E-mail:
fabiool at cs dot rutgers dot edu
- Saif Iqbal: Tue 6-8pm,
Hill 266. E-mail: saiqbal at
paul dot rutgers dot edu
Course Material & Assignments
Here are some things you will need for the assignments.
For all assignments, C programming skills will be necessary. Here
are some links to C programming guides. You can always look
more up on the web.
Material for specific assignments:
Results
Assignment
|
Max
|
Median
|
Average
|
Standard
Deviation
|
| Assignment 1 |
100
|
60
|
55.9
|
34.4
|
| Midterm |
100
|
17
|
29.3
|
24.1
|
| Assignment 2 |
100
|
85
|
76.6
|
27.8
|
| Assignment 3 |
85
|
35
|
46.67
|
25.97
|
| Final Exam |
98
|
65
|
58.57
|
24.74
|
Comments on assignment 1 grading
(By Saif Iqbal)
Grading Scheme:
Weightage was given to the following aspects of the assignment:
- Code implementation;
- Performance tests executed and results obtained;
- Test cases made by the tester and matched against published
results;
- Report - Design description (optional), results, performance
analysis;
General Observations:
One of the common mistakes that people did was not complete all of the
requirements. As an example, printing the reduced matrix but not
performing the back-substitution and printing the final variable
values. Or, getting the results but not analyzing them.
Implementation is not the end, but the means to get some results. Code
should be backed by comprehensive test cases and corresponding results.
Graphs/tables are useful visual tools in collecting the
information in an orderly manner, and explaining why the specific
results were obtained.
Rigorous testing should be done to avoid segmentation faults, etc. Some
special cases might not work, and will not be caught if the program is
tested with just simple inputs. Error handling should be incorporated
lest it crashes the whole program.
Acknowledgements
This page is heavily based on the one originally written by Eduardo
Pinheiro, a former TA for this course.
Last updated:
05/13/2005