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 with.
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
|
Due: fill out and return team formation survey before class. Project 1 groups are assigned. first meeting. Fill out FERPA consent form. Read Project 1 requirements |
Week 1 |
Software Processes
|
Assembla team workspaces available:Team 1, Team 2, Team 3, Team 4, Team 5, Team 6 |
|
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 Example3. While overall good examples, these should not be emulated without thought. Milestone: 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: Report on progress in Stand-up in class |
|
Week 2 |
Requirements analysis and Use cases: In class exercise. |
Due: Resources: Project planning summary, Create a PERT chart |
|
Week 2 |
Deliverables walkthrough |
Due: Everyone on the project should know Use Case basics |
|
Week 3 |
Holiday, no class. View lecture video on line. 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: 1) initial implementation of all modules. 3) Module level testing |
|
Week 3 |
Group Dynamics: |
|
|
Week 4 |
Quality Assurance I: |
|
Due: Final increment integration. QA Plan Examples: Cyclone Project (short) and a Data Mining Project (longer) |
Week 4 |
Final Project 1 meetings in class. |
|
Due: Acceptance testing, final bug fixes, draft of presentation for practice. |
Week 4 |
Project 1 Presentations in Deschutes Colloquium room. 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 |
Architecture I: Introduction to software architecture |
|
Due: ConOps complete, initial project plan including schedule and milestones. |
Week 6 |
Architecture II: Design goals and the meaning of "design" in the software context |
Due: first draft of SRS, identify and prioritize project risks, plan for risk mitigation |
|
Week 6 |
Architecture III: Modularization |
||
Week 7 |
In class Exercise: Address Book Design |
|
|
Week 7 |
Architecture III: Design examples, class exercise |
|
|
Week 7 |
Architecture IV: Design examples (cont'd). Download slides in PDF or in Powerpoint |
Data Banker Interface Specification example | |
Week 8 |
Address Book design example. |
|
Due: minimal subset (iteration 1 of code)
|
Week 8, |
Review of concepts. |
|
|
Week 8 |
Architecture V: review of concepts |
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, |
Architecture VI: Documenting architecture |
|
Due: second code increment |
Week 9, |
Architecture VII: Module design and specification
|
|
Due: finalizing testing, documentation |
Week 9 |
Quality Assurance II: Video lecture on software reviews (~35 mi.). Download slides in PDF or in Powerpoint | ||
Week 10, |
Quick project status meetings in class. |
|
|
Week 10, |
No class, work on projects.
|
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 demos. | 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) |
|
Week 11 |
Second Midterm Review lecture video covering material since midterm. |
|
|