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 Tue. 1/7	Overview of Software Engineering and the class. Slides in PDF: download		Due: fill out and return team formation survey
Week 1 Thur. 1/9	Software Processes Assembla workspaces Slides in PDF: download	Read Project Description Process Models Recent Software Failures: Of 2011, Agile	Project 1 groups are assigned. first meeting Assembla team workspaces available:Team 1, Team 2, Team 3, Team 4, Team 5, Team 6, Team 7. 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 Tue. 1/14	No Class 1. Work on projects 2. Set up instructor meeting	522: Fake It	Due: look at example projects for some guidance. Familiarize yourselves with the assembla site: 1. Create accounts for all team members, then create the "Our Team" wiki page on your Assembla worksite 2. Create an entry for the first meeting on the Meeting Notes page 3. Choose initial roles and responsibilities for each team member, fill out roles inoperculate Plan page 4. Individuals fill out developer logs
Week 2 Thur. 1/16	Project Planning Slides in PDF: download	IBM Use Case Guide	Due: 1. Initial cut at project plan including team member roles, risks and risk mitigations, choice of process, list of deliverables, and major milestones to the end of the first development iteration. 2. Fill out ConOps part of Requirements template, generate questions on expected behavior for customer (instructor). Resources: Project planning summary, Create a PERT chart
Week 3 Tue. 1/21	Requirements analysis Quality Assurance Slides in PDF: download	Faulk: Software Requirements	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 Thur. 1/23	Requirements & QA II: download	Software Problems in the healthcare exchanges	Due: 1) Finalize requirements, 2) Draft of User's Guide, 3) initial implementation of all modules.
Week 4 Tue.1/28	Group Dynamics Slides in PDF: download		Due: Acceptance testing, final bug fixes, draft of presentation for practice.
Week 4 Thur. 1/30	Project 1 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 the end of the day (freeze Assembla pages). Fill out Peer Evaluation Forms and return (Word or PDF format)
Week 5 Tue. 2/4	Midterm Review Project Phase 2 Kickoff: project ideas	Midterm Review Questions	Due: Selection of Project 2 or proposal in the form of a draft ConOps document. Review: Schedule meeting with Instructor for Project 1 review, Project 2 planning
Week 5 Thur. 2/6	Midterm		In class midterm, multiple choice and short answer. Closed book and notes.
Week 6 Tue. 2/11	Architecture I: Introduction to software architecture Slides in PDF: download		Due: ConOps complete, initial project plan including schedule and milestones.
Week 6 Thur. 2/13	Verification and Validation		Due: first draft of SRS, identify and prioritize project risks, plan for risk mitigation
Week 7 Tue. 2/18	Architecture II: Design goals and the meaning of "design" in the software context Slides in PDF:download
Week 7 Thur. 2/20	Architcture II contd: Modularization		Data Banker Interface Specification example
Week 8 Tue. 2/25	Architecture III: Design examples, class exercise Slides in PDF:download		Due: minimal subset (iteration 1 of code)
Week 8, Thur. 2/27	Quality Assurance: Role of QA in controlling development; Reviews download		QA Plan Examples: DataMining Project and Cyclone Project (longer)
Week 9, Tue. 3/4	Quality Assurance II: Testing and test planning: download		Due: second code increment
Week 9, Thur. 3/6	Industry Guest Lecture: Lloyd Madden, Fabtrol
Week 10, Tue. 3/11	Final lecture and review of course concepts
Week 10, Thur. 3/13	Project 2 demos.		Project 2 code is due (projects should be completed by Thur. 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)
	Final exam: