Syllabus

January 30.

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.

A real project for a real customer: preparation for Thursday visit.

CS capstone experience includes writing and presentation practice. Start with two minute introductions.

First homework assignment.

Thursday, February 1. Customer presentation: Marc Welch.

Tuesday, February 6 Requirements elicitation. Actors, scenarios and use cases. Functional and nonfunctional requirements. Examples from WISER.

Sketch out scenarios to submit to Marc Welch.

Second homework assignment.

Thursday, February 3. UML Sequence and Class diagrams. Application to our project.