Introduction to Computer Science I
CPSC 231 - Lecture 03 - Fall 2000
There will be SEVEN (7) ASSIGNMENTS which are the same for all CPSC 231 sections (see our common assignments page prepared by Katrin Becker):
Topic Due Date Worth 1 Unix Orientation Sep. 29 3% 2 Working with Binary Numbers Oct. 02 3% 3 First Encounter with C++ Programs Oct. 13 4% 4 Making Change Oct. 27 5% 5 Phone Numbers to Words Nov. 10 5% 6 Minesweeper Nov. 24 5% 7 ??? Dec. 08 5% (8) Optional Bonus Assignment Dec. 11 4%
Assignments are due by 16:00 on the due date and have to be put in the Assignment Boxes on the 2nd Floor (close to the Main Office).
See the section on Preparing Assignments for Submission below.
Late Assignments WILL NOT be accepted for grading.
System failures (weekend or any other time) will not be grounds for extension of assignment deadlines. Note deadlines carefully and pace your work accordingly.
If you choose to do the optional bonus assignment it is to be done in addition to all other work, not instead of. Do one only.
All activities regarding the computer labs, Teaching Assistants, and assignments are coordinated by Katrin Becker (firstname.lastname@example.org). So, if you have any specific questions concerning the labs, TAs, or assignments, you should talk to Katrin.
P.S.: Of course, you are always welcome to talk to me first.
Assignments are not optional.
You may use your own computer for some of the assignments, but all assignments must be written in C++ and the final copy (to be handed in for marking) must be produced using the Sun Workstations (there will be NO exceptions). If you run into problems , the lab can provide an environment where there is someone to answer questions, and other students to interact with.
General Marking Criteria:
- Some assignments may not be marked directly. Instead there will be a quiz based on material learned while doing the assignment. You will not be told ahead of time which assignments will be marked and which assignments will be quizzed. The marks assigned to each assignment will be based either on the assignment itself or the quiz. If an assignment is to be quizzed, a mark will only be recorded if the assignment has been handed in (if not, a '0' will be recorded for that assignment even if your quiz score is 100%).
Grade Evaluation Remarks 0 assignment not handed in F major errors (such as programs that don't compile, serious logic errors, failure to follow assignment specifications, etc.) D less serious errors (numerous smaller logic errors, unjustified deviations from assignment specifications, minimal effort, etc.) C acceptable program: AVERAGE effort (clean; reasonable; acceptable documentation; works, etc.) B above average: a well considered solution; well explained; clean code; efficient A excellent: well done; good writing; has some nice extras;
- 'Extras' and bonuses are no guarantee of an 'A'. If they are not well-designed, they will not be given extra credit (i.e. poorly thought out or designed extras are a liability rather than an asset).
- A mark of 'C' does NOT mean there was anything wrong with your work. 'C' means average.
- All Assignments require at least some documentation, explanation, or discussion.
- You will be marked on your technical writing style and your ability to communicate as well as on content.
- Assignments may be developed anywhere you choose but the final copy must be compiled and run on our UNIX machines.
- You are free to use language constructs not yet covered in class but if you do so they must be used correctly. If you run into trouble, TAs are not required to help you (i.e. current work will take priority).
- IMPORTANT NOTE:
If there is any evidence that you did not do your own work on an assignment, a '0' will be assigned for the work in question and both the CPSC Department Head and Dean of your faculty will be informed in writing.
- Steps in Preparing Assignments to be Submitted
- 1. Start a Script Session.
- 2. Display the contents of your directory (ls -la).
- 3. Display all program parts, data, and documentation (cat).
- 4. Compile your program (make, g++).
- 5. Run your program with sufficient data to prove it works and show off its features.
- 6. If your program produces file output, display that now.
- 7. End the Script Session.
- 8. Print the script file.
- 9. Label it clearly with your name, lecture section, TA's name, lab section
- For assignments where the mark is to be evaluated from a quiz, that mark will be written on the corresponding assignment that was handed in. If the assignment was not handed in, the mark for the quiz will be withheld.
- Uncommented programs will neither be looked at nor marked!
- TA's are not required to accept improperly identified submissions. Do your own work. If 2 or more assignments are found to be the same ALL will get zero until the matter is cleared up.
- Cheating on an assignment is a serious offense. Any student caught cheating on an assignment will be given a zero (0) on that assignment and a letter of explanation will be forwarded to the Head of Computer Science and to the Dean of the student's faculty as a permanent record. Further action may be pursued.
|© Katrin Becker and Christian Jacob||
Last updated: September 2000