CS 115: Introduction to Computer Science 1, UAE edition

General information

Assignments are designed to give you practice in programming, to prepare you for exams, and to give you feedback on your mastery of course material. You rob yourself of these benefits if you hand in work that is not your own. Please read about plagiarism on the Course Description. These apply to every course you will take at UW, and you should be familiar with them.

Submission: You will submit program files electronically as described in the style guide for assignments (PDF); the markers will run your code through automarking scripts and grade your work on MarkUs.

MarkUs (for assignment submission)
Use your Quest ID and password.

Late assignments: MarkUs lets you submit assignments after the deadline. It will give you a warning, but it will not reject your submission. However, all late assignments except assignment 0 will receive no marks.

• Assignment 0: You can submit assignment 0 anytime before the term is over and you will not be penalized in any way for it. It will be as if you submitted on time. If you do submit assignment 0 late, please email the tutor so that he is aware of your late submission.
• All other assignments: Late submissions will receive a mark of zero. Nevertheless, you can still receive feedback on your late assignment. The tutor will give you zero marks but he/she will make annotations. If you submitted an assignment late and want feedback on it, please email the tutor so that he/she is aware of your late submission.

Corrected assignments: Corrected assignments will be available on MarkUs. The Common Errors page will discuss common errors found on assignments. Complete solutions will be posted online after the assignment is due. If you believe that errors were made in the marking, please email the tutor and state clearly what you feel was mis-marked. The deadline for this is two weeks after the marks are released.

Group work: Assignments should be done individually.

Style guidelines: Your assignment submissions should conform to the guidelines laid out in the style guide for assignments (PDF). Some of the main points are summarized here.

• The file for one question should have a file extension of .rkt.
• Please do not submit code using the embedded Special Boxes offered by DrRacket, such as Comment Boxes or Test Boxes; these cause problems for our marking procedures.
• Use semicolons for comments, and check-expect tests as described in the style guide and in lecture.
• Do not cut anything out of the Interactions window of DrRacket and paste it into the Definitions window. There is no need for you to do this, and because of the way DrRacket works, what you are pasting is not simple text; it also causes problems with our marking procedures.

Interfaces: We will typically include an "interface" which contains the correct spelling of all functions and structures requested by the assignment. Since the markers will be running their own tests of your code, spelling errors can result in loss of marks. Use the interface provided as a starting point for your own work.

Questions and interfaces