Preliminary scores for Project 4 from scripted grading is available in your 00Gradesheets directory. Homework 4 grades posted. Project 5 posted. Homework 3 grades posted. Homework 6 posted. Complete write up of Project 4 posted. The draft version has been removed. Updated Project 4 Draft. Still need test programs and submission instructions, but the requirements are in place. Project 4 Draft is available, if you want to see the main idea. Details soon. Homework 5 posted.

The due date for Project 3 has been pushed back by a week. The new due date for Project 3 is 8:59:59pm Nov 7. With Nov 8, 9 and 10 being 1, 2 and 3 days late respectively.

Project 4 will be pushed back to be due after Thanksgiving. Project 5 will be due Dec 12, which is the last day of classes. The due date of Project 5 is not ideal since the late days now overlap the final exams, but you can always submit early.

As a reward for those students who have been working diligently, if you submit Project 3 by the original due date (Tuesday 10/31, 8:59:59pm), you will receive a 10% bonus on Project 3. This bonus can push your grade over 100% and make up for deductions in other projects.

If you are done with Project 3 and have it fully tested, then go ahead and submit tomorrow as usual. Your files will be moved over to a new "proj3-bonus" directory. (If you change your mind and submit again, we will as usual pick up the later submission for grading.) If you have not fully tested your code, then I suggest that you take the extra time to make sure that your code is fully debugged, does not seg fault and has no memory leaks.

Finally, there are no more "extra weeks" in the semester, so there cannot be any extensions for Projects 4 and 5.

Fixed some typos in Homework 4. Homework 4 posted. Posted Project 3 test programs and submission instructions. Added recommended incremental development schedule to Implementation Notes. Project 3 posted. The write up needs some spiffying up, but this gives you an idea. Updated Project 2 g++ command. For Project 2, changed instructions for compiling and running the project to include logging into the "fedora" machines. Gradesheets for Project 0 are in your 00Gradesheets directory and your grade report on Google Sheets have been updated. Preliminary gradesheets for Homework 2 are in your 00Gradesheets directory. The answers to Homework 1 are: a, d, d, a, d, d, c, c, b, b, b, d, c, b, d. You can go to Homework 1, click on "View your score" to see your responses and see which ones you got right. Project 2 updated with new version of p2comptest.cpp. Homework 3 instructions updated to say that you should find good upper and lower bounds. Homework 3 posted. Added link to Google sign-in form for TA office hours to Staff page. Project 2 completed with sections on "Testing", "How to Submit" and "A Note on Timing". Project 2 posted. The test program and submission instructions will be posted soon. Project 1 assignment operators clarified. In Project 1 there is a change in the specification of CBofCB::isFull(), because the oldest InnerCB does not have to be full when you can't add another item to the data structure. Question #3 of Homework 2 was re-written for clarification. Homework 2 posted. Test program p1test11.cpp of Project 1 revised to include calls to CBofCB::isFull() and CBofCB::isEmpty(). Project 1 posted. Updated link for a C++ Tutorial on the FAQ page. TA office hours start next week. Please check the Staff page for hours. The hours may change from week to week. So do check the calendar beforehand. Homework 1 is posted. This is a Google form restricted to UMBC accounts. You must be logged into your UMBC Google account to have access to the homework.

You may edit your responses up until the due time of the homework, but answers will not be revealed until after the due time. A Piazza site has been created for this course:

https://piazza.com/class/j77how4ra446ww
If you do not have an account on Piazza yet, you should create one. (It's free.) This where students can post questions about the programming projects.

Two rules about Piazza:

  1. Do not post your code, not even snippets.
  2. No debugging by Piazza. Go to office hours if you need help debugging your code.
Piazza is good for questions about the project (but read the project description thoroughly first). Since students tend to have the same questions, this saves us all the trouble of writing email if the same question has been posted and/or answered already. Project 0 has been posted. Please check the Projects page for due dates for all of the projects this semester and plan your calendar accordingly! Web page is up.