Pair programming

In this project, we will be using pair programming. This will allow us to divide the project into a manageable number of subsystems/tasks, while still giving everyone significant development responsibility. I give you the freedom to pick your partners. Please keep in mind that you are committing to spending a good amount of time working with your partner, in the same place and at the same time. Yes, collaboration at a distance is possible, but it is greatly inferior to in-person.

Each pair will be responsible for a subsystem of this project, and this means:

1. Fleshing out any "blank spots" in the subsystem specification and handshaking with other pairs to resolve any interface issues that arise.
2. Developing a test plan for your subsystem, including code for stubs, drivers, and test harnesses.
3. Detailed design and code development for your subsystem.
4. Presenting your pair's work during in-class design and code reviews.
5. Doing the actual testing.
6. Integration with other subsystems.

Note that, though I mention in-class design and code reviews, there will certainly be a need for additional pair and team meetings outside of class.