Overall Organization
- Weeks 1-4: Project 1
- Weeks 5-9: Project 2 - select or define
- Week 10: Wrap-up and final presentations
Dates
Week | Date | Topics | Milestones |
---|---|---|---|
1 | Sep 29, Oct 01 | Project 1 kickoff. What is software engineering? Process. Team roles. Discussion of algorithms and approaches for project 1. | Survey Tuesday, teams formed Thursday. |
2 | Oct 06,08 | Deliverables: What's in a product? User and developer documentation. Short presentations Tuesday. | |
3 | Oct 13,15 | Requirements elicitation and specification. Configuration and deployment. Short presentations Tuesday. | Prelim GME due Tuesday. Mini-exam 1. |
4 | Oct 20,22 | Safety and security. | Project 2 proposals due Tuesday. Project 1 and GME due Friday. |
5 | Oct 27,29 | Wrap / kickoff. What have we learned? Usability. Short presentations Tuesday. | Mini-exam 2. |
6 | Nov 03,05 | Accessibility. Software testing. Short presentations Tuesday. | Prelim GME due Thursday. |
7 | Nov 10,12 | Architectural design. Performance. | Mini-exam 3. |
8 | Nov 17,19 | Ethics in software engineering. Short presentations Tuesday. | |
9 | Nov 24,26 | Work session Tuesday. Crunch time! | Project 2 code due Tuesday. Thanksgiving holiday Thursday. |
10 | Dec 01,03 | Presentations | Project 2 presentations |
11 | Dec 08,10 | Exams week. | GME and project post-mortem. Mini-exam 4. |
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 anxiety about public speaking. If you do not feel able to take a turn presenting to the class, come talk to me about it.