There will be 3 programming assignments, and one warm-up assignment. All of them will count. Together they will account for 35% of your overall course grade. Solutions to the assignments will require version 4.8.1 of g++, the GNU C++ compiler.
Each programming assignment will be clearly described in a README file accessible from a link below. The README tells you every thing you need to know about the assignment: so read it!
The README file specifies a due date and time for the assignment. Your solution files to the assignment must be turned in before the due time, using the appropriate submission procedure, which will be described in the assignment. You have two 24-hour "slip days" to use at your discretion. You may use them both on a single assignment, or you may use them on two different assignments. You do not need to ask to use these slip days. Just use them and you'll be automatically charged. If you submit an assignment late and you are out of slip days, you will not receive credit for that assignment.
The best way to make sure you don't lose credit for your assignments is to plan to finish them and turn them in well before the deadlines. Make sure your submitted files compile and meet the assignment specifications; source code that doesn't compile won't receive any credit. Your assignments will be graded using the compilers and runtime environment on ieng6, so you should test your code there. Make sure you include exactly the files that you are required to submit, and make sure you add any files you have created to your repository!
Your turned-in assignment solution will be graded by the CSE 100 staff within one week of the due deadline, and your grade will be emailed to your class account, and it will be posted on gradesourse. You don't need to do anything to get your assignment graded, other than turning it in before the deadline. If you have a question about the grade you received, email the grader. You have one week from the time your grade is returned to you to contest your grade; after that it is set in stone.
Note. In this course, you can do your programming assignments in teams of two, if you wish. If you choose to do so, you must engage in TRUE pair programming. Your team cannot collaborate with other teams or individuals on the assignment; see the integrity of scholarship page. Tentative deadlines and topics for assignments. Subject to slight change.
The programming assignments require knowledge of Git. You can find instructions on using Gitlab here.