Overall Organization
- Weeks 1-4: Project 1
- Weeks 5-9: Project 2 - select or define
- Week 10: Wrap-up and final presentations
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 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 approximate and will change in response to class needs. It will be updated to reflect current assignments and any changes in class schedule. You should check the schedule routinely during the quarter to make sure you are keeping up as things change.
Readings: Reading should be done before the class where they are listed. Papers labeled "522" are additional readings from the literature required for graduate students and recommended for undergraduates.
Status Reports: Monday classes will begin with a quick (2-3 minute) status report from each team.
Date |
Lecture/Discuss in Class |
Reading |
Project milestones |
Week 1 |
Overview of Software Engineering and the class. |
Read Project Description Read Team Roles
|
Due: fill out and return team formation survey before class. Read Project 1 requirements and discussion of team roles. Consider which roles you would be best suited for and most interested in trying. |
Week 1 |
Software Processes |
Process Models. Short summary description.
|
Assembla team workspaces available:Team 1, Team 2, Team 3, Team 4, Team 5, Team 6. Project 1 groups are assigned. Hold first groupmeeting. |
Week 1 |
Software Process (continued): few added slides in PDF or Powerpoint In class exercise: choosing an effective process
|
Examples of of project workspaces from past 422 and 423 classes: Example1, Example2 and Example 3. While overall good examples, these should not be emulated without thought. Milestones: Look at example projects for some guidance. Familiarize yourselves with the Assembla site. |
|
Week 2 |
Project Planning In class: Stand-up Status Report on team meeting results
|
Deliverables: |
|
Week 2 |
Project Planning (cont'd). Short lecture on Use Cases. Download slides in PDF or in Powerpoint. |
Milestones: Resources: Project planning summary, Create a PERT chart |
|
Week 2 |
Requirements analysis and Use cases: In class exercise. Deliverables walkthrough |
Plan "customer" meetings with instructor. Milestones: Everyone on the project should know Use Case basics |
|
Week 3 |
Requirements & QA II |
|
Deliverables: Critical: should include communication and at least one meeting with the client to ensure requirements correctness. |
Week 3 |
Address Book requirements exercise. Discussion of detailed requirements. |
Due: Midway review: Increment 1 due, artifacts graded focusing on whether the team is producing all the artifacts needed and shows basic understanding of planning. |
|
Week 3 |
Short progress meetings with instructor. |
|
|
Week 4 |
Quality Assurance I: |
|
Due: Final increment integration. QA Plan Examples: Cyclone Project (short) and a Data Mining Project (longer) |
Week 4 |
Group Dynamics: |
|
Due: Acceptance testing, final bug fixes, draft of presentation for practice. |
Week 4 |
Project 1 Presentations Slides on final submissions: PDF |
Project 1 is due. Groups present Project 1 results and lessons learned. Use this guideline for your team presentation. All project materials are due class time (freeze Assembla pages). Fill out Peer Evaluation Forms and return (Word or PDF format) |
|
Week 5 |
Midterm Review: Recorded Lecture video here Project Phase 2 Kickoff: project ideas |
Due: Selection of Project 2 or proposal in the form of a draft ConOps document. Review: meeting with Instructor for Project 1 review, Project 2 planning |
|
Week 5 |
Midterm |
|
In class midterm, multiple choice and short answer. Closed book and notes. |
Week 5 |
Quality Assurance: Testing and test planning: |
||
Week 6 |
Quality Assurance III: Software Reviews. Slides in PDF or in Powerpoint |
Due: ConOps complete, initial project plan including schedule and milestones. |
|
Week 6 |
Architecture I: Introduction to software architecture |
Due: first draft of SRS, identify and prioritize project risks, plan for risk mitigation |
|
Week 6 |
Architecture I continued |
||
Week 7 |
Architecture II: Design goals and the meaning of "design" in the software context |
|
Due: schedule customer feedback
|
Week 7 |
Architecture III: Modularization |
|
|
Week 7 |
Architecture III: Design examples, class exercise: Address Book Design |
Due: minimal subset (iteration 1 of code) |
|
Week 8 |
Architecture IV: Design examples. Download slides in PDF or in Powerpoint |
|
|
Week 8, |
Architecture V: Documenting architecture |
|
|
Week 8 |
In class team meetings with instructor: progress check |
||
Week 9, |
Architecture VI (cont'd): Module interface specification |
|
Due: second code increment Example of Architectural design documentation (grad student projects done by professional developers) RequirementsReader Example of Module Structure documentation for a simple system: Floating Weather Station Requirements and Module Guide |
Week 9, |
No Class. Work on projects. |
|
Due: finalizing testing, documentation |
Week 9 |
Thanksgiving: No class |
||
Week 10, |
Short in-class meetings with instructor. Any final questions or issues? |
|
|
Week 10, |
Second half review lecture. Slides in PDF or Powerpoint
|
Assembla pages for the Project Plan, Requirements, and Architecture should be frozen and available for evaluation. Teams should inform the instructor if they cannot meet this deadline. |
|
Week 10 |
Project 2 presentations: in Deschutes colloquium room. | Project 2 code is due (projects should be completed by class time). Read instructions for final presentations and hand-ins here (download). Read the Project Grading page for details on how your project will be graded. Fill out Peer Evaluation Forms and return (Word or PDF format) |
|
10:15 Mon. 12/4 |
Second Midterm. Same format and approximate lenght as midterm. |
|
|