6.031: Software Construction
Fall 2017 · Course Staff · MWF11-12:30 (34-101)
Mon Sep 18: Problem Set 1
Problem Set 1 is now available. The ps1 iter1 deadline is Monday at 10pm.
After you wrap up ps0, please fill out the required Problem Set 0 reflection, which asks a few questions about how you worked on ps0. It should take only a minute to fill out, and is due by Thursday at 10pm.
Sun Sep 17: Nanoquiz makeup reminder
Just a reminder that nanoquiz grades are posted on Omnivore shortly after the end of each class, at which point the 7 × 24-hour makeup period begins.
For example, if you plan to submit a makeup for nanoquiz 3, the deadline is tomorrow afternoon. See nanoquiz grading and makeup for details.
Fri Sep 15: Problem Set 0 iter1 reports
- To see your iter1 autograde report, go to Didit, follow the link to your psets/ps0 page, and click “iter1” in the “Milestones” section.
- To see your code reviews, go to Caesar and click on “ps0-iter1” under “submitted assignments.”
In autograding, your submission was tested both by the public tests that were shown to you and by hidden tests. If you failed any hidden tests, you’ll see the name of the test that failed and a stack trace of where it failed. The test case inputs or code will not be revealed to you, either by Didit or by staff. The hidden tests are like bug reports from users in the field, where you get a rough idea of what the user was trying to do (the test name) and a stack trace of where the failure occurred. You need to figure out what’s wrong with your code from those clues.
You should revise ps0 for the iter2 deadline on Monday at 10pm. You can take slack on this deadline using Caesar, just like the iter1 deadlines.
Your revised version of ps0 should fix any bugs found by the hidden tests, and you must address each of your code review comments made by humans or marked #important by Checkstyle, as described in the code reviewing guidelines.
See the problem set handout for a breakdown of how your overall ps0 grade will be calculated.
Good luck! Please ask questions on Piazza and visit lab or office hours.
Wed Sep 13: Problem Set 0 code review due Friday 11am
Code reviews are due before class on Friday.
Mon Sep 11: Problem Set 0 iter1 due 10pm
Problem Set 0 iter1 is due at 10pm tonight.
Remember that if you need an extension on a problem set iteration deadline, you must request it before your current deadline passes using Caesar, as described on the General Information page.
- 01: Static Checking
- 02: Basic Java
- 03: Testing
- 04: Code Review
- 05: Version Control
- 06: Specifications
- 07: Designing Specifications
- 08: Avoiding Debugging
- 09: Mutability & Immutability
- 10: Abstract Data Types
- 11: Abstraction Functions & Rep Invariants