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 minuet) status report from each team.
Date |
Lecture/Discuss in Class |
Reading |
Project milestones |
Week 1 |
Overview of Software Engineering and the class. |
|
Due: fill out and return team formation survey |
Week 1 |
Software Processes |
Read Project Description |
Project 1 groups are assigned. first meeting Assembla team workspaces available: Team1, Team2, Team3, Team4, Team5, Team6 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. |
Week 2 |
Project Planning |
522: Fake It |
Due: look at example projects for some guidance. Familiarize yourselves with the assembla site: Quick Status: team meeting results, project decisions |
Week 2 |
Requirements analysis |
Due: Resources: Project planning summary, Create a PERT chart |
|
Week 3 |
Requirements & QA |
|
Due: 1) First draft of Requirements including key Use Cases and 2) First set of test cases. Everyone on the project need to know Use Case basics, 3) Initiate design: decompose software into work assignments. Quick Status: status of deliverables, work for this week, issues delaying progress |
Week 3 |
Requirements & QA II: download
|
Due: 1) Finalize requirements, 2) Draft of User's Guide, 3) initial implementation of all modules.
|
|
Week 4 |
Project 1 review and post mortem (presentations) |
|
Project 1 is due. Groups present Project 1 results and lessons learned. Use this guideline for your team presentation. All project materials are due by class time. Fill out Peer Evaluation Forms and return (Word or PDF format) |
Week 4 |
Project Phase 2 Kickoff: project ideas Group Dynamics |
|
Assignment in IV&V: Provide independent assessment of another team's work product and software as described here. Return on Monday Review: Schedule meeting with Instructor for Project 1 review, Phase 2 planning |
Week 5 |
Midterm Review
|
Due: Selection of Project 2 or proposal in the form of a draft ConOps document. |
|
Week 5 |
Midterm |
|
In class midterm, multiple choice and short answer. Closed book and notes. |
Week 6 |
Architecture I: Introduction to software architecture |
|
Due: ConOps complete, initial project plan including schedule and milestones. |
Week 6 |
Guest Lecture: Quality Assurance, Prof. Michal Young |
Due: first draft of SRS, identify and prioritize project risks, plan for risk mitigation |
|
Week 7 |
Architecture II: Design goals and the meaning of "design" in the software context |
|
|
Week 7 |
Architcture II contd: Modularization |
|
|
Week 8 |
Architecture III: Design examples, class exercise |
|
Due: minimal subset (iteration 1 of code) |
Week 8, Wed. 11/20 |
Architecture IV: Design Principles |
|
|
Week 9, |
Architecture V: Documenting design decisions |
|
Due: second code increment |
Week 9, |
Industry Guest Lecture: Lloyd Madden, Fabtrol |
|
|
Week 10, |
Final lecture and review of course concepts |
|
|
Week 10, Wed. 12/4 |
Project 2 demos. | Project 2 code is due (projects should be completed by Wed. 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) |
|
12/10 |
Final exam: 10:15AM |
|
|