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 Tuesday of week 4.
Each Week
Tuesday
Many Tuesdays beginning week 2 will begin with short presentations by each project team. You should prepare slides for these. You should also provide constructive criticism of both content and presentation to other teams. Status report means a 5-7 minute presentation recapping your plan and describing what has gone according to plan, what has not, what adjustments you have made to your plan, and what your next steps are. Quick status means a shorter, 1-3 minutes report, briefly reporting on progress, problems, and next steps. Project pitch means a 5-7 minute presentation on your project concept (requirements, purpose, etc), feasibility, key technical approaches, team roles, and schedule.
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 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.
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.
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. There are a few additional notes below the schedule.
Date |
Discuss in Class |
Reading |
Project milestones |
Week 1 |
Overview of Software Engineering and the class. |
|
Hand out Project 1 and conduct survey. |
Week 1 |
Teamwork. Effective meetings. Software development processes I |
Text: 1, 2, & 3 |
Project 1 groups are assigned. first meeting |
Week 2 |
Software Processes II. |
Text: 5 |
Quick Status: Team name, team Role, issues |
Week 2 |
Project planning and management. Project I documentation |
Text: 8 |
Early project plan, Requirements questions |
Week 3 |
Documentation principles
|
|
Quick Status: Documentation, planning Groups turn in initial project documents. Groups meet with instructor. |
Week 3 |
Requirements analysis |
Text: 9 |
|
Week |
Software Architecture |
|
|
Week 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 5 |
Midterm Review |
|
Project 2 groups are formed. |
Week |
Midterm |
|
|
Week 6 |
Software Architecture I |
|
Project 2 Kickoff Schedule meeting with Instructor for Project 1 review, Project 2 planning |
Week 6 |
Guest Lecture:Prof. Steve Fickas, Jason Prideaux |
|
|
Week 7 |
Architecture II |
Text: Ch. 11 |
|
Week |
Architecture III: Modularization and information hiding |
|
|
Week 8 |
Architecture IV |
|
|
Week 8, Thur. |
Midway project review --> |
|
Simulated management review of project. Present project status. Your task is to convince management your project is under control and should not be cancelled. |
Week 9, |
|
|
|
Week 9, |
Thanksgiving (no class) |
|
Work on projects |
Week 10, |
Final lecture and overview of the course |
|
|
Week 10, |
Project 2 demos. Meet in the Deschutes colloquium room |
|
Project 2 code is due (projects should be compled by Wed. evening, latest) |
GME = Group Member Evaluation