Skip to main content.

Overall Organization

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 Tuesday of week 4 (October 18).

Each Week

Tuesday

Most Tuesdays beginning week 2 will begin with short presentations by each project team. You should prepare slides for these. Handouts are optional. You should also provide constructive criticism of both content and presentation to other teams.

As time allows, Tuesday may also include a conventional lecture or a discussion of a topic related to the project.

Notes on presentation

Presentation duties should rotate among team members. Presentation nand verbal communication skills are important; use this as an opportunity to practice in a friendly environment. I would like everyone to give at least part of one presentation during the term, and everyone to critique presentation style as well as the content of presentations.

I know some people have deep anxiety about public speaking. If you do not feel able to take a turn presenting to the class, come talk to me about it. I'll excuse you from this part of the class provided you are doing something else to hone your verbal communication skills.

Thursday

Most Thursdays will consist of lecture and discussion, including discussion of papers I will assign you to read. Contribution to discussion will be an element of your grade.

Exceptions

There will be occasional days that don't conform to our usual plan of team presentations Tuesday and lecture and discussion Thursday. This will include at least week 1, week 5, and week 10, and other exceptions are likely.

Week by Week Schedule

This schedule is likely to be revised.

Week 1

Tuesday, Sept 22

Entry questionnaire filled out and returned in class.

Project introduction, class introduction, and overview of software engineering.

Thursday, Sept 24

Teams formed; meet briefly in class. More discussion of project 1. Lecture: Teamwork.

Week 2

Tuesday, Oct 2

Short project pitches from each team. Describe features, technical approach, team role breakdown, schedule and milestones. Critique.

Lecture: Process and project management.

Thursday, Oct 4

Lecture: Process and project management cont; architectural design.

Week 3

Tuesday, Oct 9

Architectural design and project status reports: Approximately 5-7 minutes, with slides, delivered in a professional manner.

Thursday, Oct 11

Week 4

Tuesday, Oct 16

Present status and design: 10 minutes per project. Briefly recap requirements, technical architecture, and schedule, then describe progress, challenges, and responses.

Thursday, Oct 18

Week 5

Tuesday, Oct 23

Meet in lab. Project due at 5pm. Scheduling grading session.

Thursday, Oct 25

Week 6

Tuesday, Oct 30

Present design approaches: 5-10 minutes per project. Recap requirements briefly, describe technical architecture, main technical risks and amelioration, schedule and milestones. Present in a professional manner with slides.

Thursday, Nov 1

Week 7

Tuesday, Nov 6

Present status and design: 5-10 minutes per project. Briefly recap requirements, technical architecture, and schedule, then describe progress, challenges, and responses.

Thursday, Nov 8

Week 8

Tuesday, Nov 13

Present status and design: 10 minutes per project. Briefly recap requirements, technical architecture, and schedule, then describe progress, challenges, and responses. Demo if possible.

Thursday, Nov 15

Week 9

Tuesday, Nov 20

Meet in lab. Final project due 5pm.

Thursday, Nov 22

Holiday

Week 10

Tuesday and Thursday

Project demonstrations in Deschutes colloquium room. Approximately 15 minutes per project, presented for a general software development audience. Invite your friends.