Building software isn't just programming! Engineering as a process. Decisions (and rationales). Transparency. Team work.

Models:

• Waterfall
  • Requirements elicitation (scenarios and use cases)
  • Analysis
  • System design
  • Object design
  • Implementation
  • Testing

• eXtreme Programming (XP), agile processes - lots more iteration (water doesn't run uphill) but not just hacking away!

Tools that support processes: transparency (wiki, web), IDE (Eclipse, JBuilder, Visual Studio), code management (CVS, RCS, Clearcase), rationale maintenance, bug tracking.

CS capstone experience includes writing and presentation practice. Start with two minute introductions at the next class.

How to speak and how to listen. Two minute presentation from each person.

5:30: Professor Brian White (Biology).

6:00: Nicholas Anzalone, Community Charter School of Cambridge.

First homework assignment due.

5:30: Professor Jason Evans (Chemistry).

6:00: Professor Robert Stevenson (Biology)

Analyzing the potential projects. Team selection.

Homework 2 due in class.

Discuss first project deliverables.

Requirements elicitation. Actors, scenarios and use cases. Functional and nonfunctional requirements.

First team meetings, in class.

Guest lecture: Prof. Robert Morris.

Team progress reports - wiki and web page.