Overall Organization

Weeks 1-4: Project 1 (prototype)
Weeks 5-9: Revise and extend to final project, OR option of selecting another project.
Week 10: Final presentations

Those who want to take the option of completing a project of their own choosing in the second half of the term should indicate that on the entry questionnaire on the first day of class, and must in addition submit a project proposal by Monday of week 4.

Each Week

Notes on presentations

Presentation duties should rotate among team members. Presentation and verbal communication skills are important; use this as an opportunity to practice in a friendly environment. Everyone should give at least part of one presentation during the term.

I know some people have deep anxiety about public speaking since I have had this as well. If you do not feel able to take a turn presenting to the class, come talk to me about it.

Week by Week Schedule

This schedule is preliminary and subject to change over the term.

Readings: Readings are from the van Vliet text with occasional downloads. Reading should be done before the class where they are listed. Papers labeled "522" are additiional readings from the literature required for graduate students and recommended for undergraduates.

Date	Lecture/Discuss in Class	Reading	Project milestones
Week 1 Mon. 1/7	Overview of Software Engineering and the class. Slides in PDF: download		Due: Read Project Description, fill out and return team formation survey
Week 1 Wed. 1/9	Software Processes Assembla workspaces Slides in PDF: download	Text: 1 Read Project Description	Project 1 groups are assigned. first meeting Assembla team workspaces created: Team 1, Team 2, Team 3, Team 4, Team 5
Week 2 Mon. 1/14	Project Planning Teamwork. Effective meetings	Text: 2, 3	Due: look at example projects for some guidance 1. Create the "Our Team" wiki page on your Assembla worksite, 2. Create an entry for the first meeting on the Meeting Notes page 3. Fill out first Developer Log entry for Week 1 (each team member) 4. Choose initial roles and responsibilities for each team member. Quick Status: team meeting, status First meeting completed, project decisions
Week 2 Wed. 1/16	Requirements analysis Quality Assurance	Text:. 8 522: Fake It	Due: Initial cut at project plan including team member roles, risks and risk mitigations, choice of process, list of deliverables, and major milestones to the end of the first development iteration.
Week 3 Mon. 1/21	QA Continued Software Design		Quick Status: Documentation, planning
Week 3 Wed. 1/23	Software Design	Text: 9	Review: Groups meet with instructor. Set up time for team to meet with instructor
Week Mon. 1/27	Documentation principles		Quick Status: progress agains plan
Week 4 Wed. 1/29	Midterm Review
Week 5 Mon. 2/4	Project 1 review and post mortem		Project 1 is due. Groups present Project 1 results and lessons learned. Use this guideline for your team presentation
Week Wed. 2/6	Midterm		In class midterm, mutliple choice and short answer. Closed book and notes.
Week 6 Mon. 2/11	Software Processes Revisited		Project Phase 2 Kickoff Schedule meeting with Instructor for Project 1 review, Phase 2 planning
Week 6 Wed. 2/13	Requirements Analysis	Text: Ch. 11
Week 7 Mon. 2/18	Quality Assurance		Quick status:
Week 7 Wed. 2/20	Architecture I: Architectural Design
Week 8 Mon. 2/25	Architectrue II: Modularizatio and Design Principles	Text: Ch. 12.1-12.4	Data Banker Interface Specificaton example
Week 8, Wed. 2/27	Architecture III: Interface Design and Specification		Simulated management review of project. Present project status.
Week 9, Mon. 3/4	Verification and Validation
Week 9, Wed. 3/6			Work on projects
Week 10, Mon. 3/11	Final lecture and overview of the course
Week 10, Wed. 3/13	Project 2 demos.		Project 2 code is due (projects should be compled by Wed. evening, latest). Read instructions for final presentations and handins here (donwload)

Notes:
GME = Group Member Evaluation