6.031: Software Construction
Spring 2019 · Course Staff · MWF11-12:30 (34-101)
Announcements
Fri Apr 26: Problem Set 4 reflection
Now that you’ve completed (2-slack-day-takers, will soon complete) the last problem set, please fill out the required Problem Set 4 reflection, which asks a few questions about how you worked on ps4. It should take only a minute to fill out, and is due by Monday, Apr 29, at 10pm.
Tue Apr 23: Project groups and handout
Your project team and mentor for the group project are posted on Omnivore. The project handout has also been posted.
In tomorrow’s class, after we take a nanoquiz and practice team version control with Git, you will meet with your team, create your group repo, check in with your TA mentor, write a team contract, and start working on the project. The team contract is due tomorrow night, and the first project milestone is due next Wednesday.
You must check in with your TA mentor tomorrow and in every class during the project.
- On Mon Apr 29, you will check in after a short class that includes our last nanoquiz.
- Fri May 3 is a quiz review, no required check-in.
- Mon May 6 is Quiz 2, no required check-in.
All other class time until the last day of classes will be devoted to working on the project.
Mon Apr 22: Problem Set 4 alpha reports
Alpha grade reports and code reviews for ps4 are now available.
- To see your alpha autograde report, go to Didit, follow the link to your psets/ps4 page, and click “alpha milestone.”
- To see your code reviews, go to Caesar and click on “ps4-alpha” under “submitted assignments.”
In autograding this iteration, only your text server was tested for credit.
In manual grading, staff looked at your Board abstraction function and rep exposure safety argument.
As you revise, try to both address their comments directly and generalize the feedback to improve your other ADTs.
The ps4 beta deadline is Thursday at 10pm. Make sure you address all your code review comments from humans or marked #important by Checkstyle. If you need a slack day, remember to request it on Caesar.
Please ask questions on Piazza and visit lab or office hours.
Fri Apr 19: Problem Set 4 code review due Friday 11am
Problem Set 4 code reviewing is now open. Go to Caesar to find your reviewing assignments. You’ll have 6 files to review. Code reviews are due on Monday morning.
Reminder: the project signup form was due tonight. Everyone must submit the form. If you do not fill out the form, you will not be part of a group.
Mon Nov 12: Project group signup
Starting next Wednesday, you will be working on the 6.031 final project in groups of three people. Please fill out the project signup form by this Friday Apr 19 at 10pm.
Fill out the form right now, even if you don’t have a group of three: just choose the appropriate option on the form. You can resubmit another response if your plans change by Friday night, and we will use your last submitted response. To find additional group members, use the Piazza teammates post.
Every member of a group must submit the form. If you do not fill out the form, you will not be part of a group. We will assume you have dropped the course.
As always, if you have any questions, ask on Piazza!
General
Getting Started
Readings
- 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
- 11: Abstraction Functions & Rep Invariants
- 12: Interfaces & Enumerations
- 13: Debugging
- 14: Recursion
- 15: Equality
- 16: Recursive Data Types
- 17: Regular Expressions & Grammars
- 18: Parsers
- 19: Concurrency
- 20: Thread Safety
- 21: Locks & Synchronization
- 22: Queues & Message-Passing
- 23: Sockets & Networking
- 24: Callbacks
- 25: Map, Filter, Reduce
- 26: Little Languages I
- 27: Little Languages II
- 28: Team Version Control
- 29: Ethical Software Engineering