2 of teams will present their design concepts. You should be hacking like crazy by now, once again refining a working product rather than waiting to fit the pieces together.

10

Project 2 presentations

Project 2 presentations

Summing up

Final GME due

Take a deep breath. The hacking is over, you can start thinking about the final exams in your other classes.

Week	Lecture Monday	Lecture Wednesday	Class Friday	Assignments/Projects
1	Course overview Project introduction and discussion Teamwork	Teamwork Process (if time allows)	Select groups Project discussion: Small group and full class Discuss product concept documents	The main work this week is to form teams for the initial project, including a work breakdown among team members.
2	Software process: Sequential (waterfall) models, exploratory prototyping and RAD, incremental development, spiral models	Software process (continued)	Project concept presentations Hand out GME 1	Each team must prepare a "product concept" document and presentation, as well as an overview of team organization. At the same time, teams will be discussing overall design and implementation approaches, including tools or reusable software components.
3	Configuration management First GME due	Coding hygiene	Set demo schedule Project design discussions	Set overall product architecture and begin prototyping key pieces. Shoot for having a rudimentary working system by Wednesday, so that any huge problems can be discussed Friday.
4	Michal is in Japan this week, giving a tutorial and attending the International Conference on Software Engineering. Teams should use this time to build and refine the product. Remember that "the product" includes documentation, test cases, etc. in addition to running code. I strongly suggest that you use scheduled class time for team meetings. I also strongly suggest that you proceed incrementally, so that this whole week is spent improving a working product rather than trying to make something work. Be sure you have adequate revision control so that, if the latest changes break the product, you can still ship an earlier working version. You should also be preparing an in-class presentation on your project. Your project is due Friday evening at 5pm. Have a nice weekend.
5	Project 1 presentations	Project 1 presentations	Project 2 discussion Optional team changes	Each team will have approximately 15 minutes to present their project to the class. In-class demonstrations are encouraged but not mandatory.
6	Requirements elicitation	Requirements specification	Project 2 requirements dicussion	Teams should prepare questions and scenarios for requirements discussion on Friday.
7	Architectural design	Module interface design Hand out GME	Project 2 concept presentations Initial GME for project 2 due	Architectural design should be underway, in addition to the product concept
8	Software evolution: Maintenance and reuse	Software evolution cont.	Project 2 design approach presentations	Each team should prepare a design concept presentation; 1/2 will be selected for presentation and discussion
9	Memory Day Holiday, no class	Software quality Analysis and Testing	Project 2 design approach presentations	The remaining 1/2 of teams will present their design concepts. You should be hacking like crazy by now, once again refining a working product rather than waiting to fit the pieces together.
10	Project 2 presentations	Project 2 presentations	Summing up Final GME due	Take a deep breath. The hacking is over, you can start thinking about the final exams in your other classes.

Group member evaluations: Each student will be asked to (anonymously) rate each member of his or her team on productivity, cooperativeness, and other attributes. The final GME of each project will be used in grading. Other evaluations are for information only, and chiefly help us find and deal with team problems before they become disasters.