6.031: Software Construction
Fall 2018 · Course Staff · MWF11-12:30 (34-101)
We have some Constellation bug fixes that require an updated version of the Eclipse plug-in.
Before you come to class on Monday, please update Constellation:
- Quit and re-launch Eclipse
- In the Quick Access field at the top right of the window, enter “installation details” and pick Installation Details
- Select Constellation in the list and click Update…
- Accept the license, install unsigned content, and restart Eclipse to complete the update
Please visit lab over the weekend if you have trouble updating. The new version will be required for Monday’s in-class exercises.
To see your beta autograde report, go to Didit, follow the link to your psets/ps0 page, and click “beta milestone.”
Your manual grade was assigned by staff inspection of your personal art code and your response to code reviews.
If you have questions, please see the FAQ about grading questions.
Problem Set 1 is now available. The ps1 alpha deadline is next Monday at 10pm.
After you wrap up ps0 (due tonight), 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.
- To see your alpha autograde report, go to Didit, follow the link to your psets/ps0 page, and click “alpha milestone.”
- To see your code reviews, go to Caesar and click on “ps0-alpha” 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 beta deadline on Monday at 10pm. You can take slack on this deadline using Caesar, just like the alpha deadline.
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 the Checkstyle automatic style checker, as described in the code reviewing guidelines. You can also run Checkstyle yourself.
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.
Code reviews are due before class on Friday.
- 01: Static Checking
- 02: Basic Java
- 03: Testing
- 04: Code Review
- 05: Version Control
- 06: Specifications
- 07: Designing Specifications
- 08: Mutability & Immutability
- 09: Avoiding Debugging
- 10: Abstract Data Types