Schedule

Week	Tuesday Lecture	Thursday Lecture	Friday Discussion
1  Mar. 28 - Apr. 1	Introduction to Software Engineering; elephants to do: sign up with Piazza	What is Software Engineering? readings: 1.1, 1.2, 1.3, 2.1, 3.1, 3.2. No Silver Bullet (Brooks)	Failing big see below for readings
2  Apr. 4 - 8	Requirements Engineering readings: 6.1, 6.2, 6.3	Customer Interview	Use Cases overheads
3  Apr. 11 - 15	Hw 1 draft due Monday, 11:55pm Customer Interview	Requirements Engineering	Requirements Engineering
4  Apr. 18 - 22	Hw 1 final due Monday, 11:55pm Software Process Models readings: 4.1, 4.2	Midterm 1	No discussions
5  Apr. 25 - Apr. 29	Software Process Models; Testing readings: 5.1, 5.2, 5.3.1, 10.1, 10.2, 10.3 to the middle of p. 207, where 10.3.2 starts. The Mythical Man Month (Brooks)	Testing	Return midterms; Mythical Man Month
6  May 2 - 6	Testing	Other Quality Assurance Approaches readings: 10.5, 10.6, 10.7 Automated Testing for League of Legends	UML Class Diagrams overheads
7  May 9 - 13	Testing Mythical Man-Month Design and UML Class Diagrams	Agile Software Processes readings: 5.1, 5.2, 5.3.1, 7.3.3 (just "Class Design and Class Diagrams")	Midterm Review overheads
8  May 16 - 20	Midterm 2	Version Control Software Architecture Hw 2 due Friday, 11:55pm	Return midterms; Git
9  May 23 - 27	Software Architecture readings: 5.3.5, 7.1, 7.2	Software Architecture Cognitive Surplus Hw 3A due at 11:55pm	No discussions
10  May 30 - June 3	Lecture	Lecture Hw 3B and 3C due at 11:55pm	Review
Finals  June 6 - 10		Thursday, June 9 Final Exam, 8:00am - 10:00am

Reading Assignments

• Before class on March 31: Sections 1.1, 1.2, 1.3, 2.1, 3.1, 3.2. No Silver Bullet - Essence and Accident in Software Engineering, by Frederick P. Brooks, Jr. (and see my errata)
• Before discussion on April 1: California payroll system fiasco
  • 12/21/12 Overhaul of California government payroll system at risk of collapse (L. A. Times)
  • 2/8/13 California Kills $90 Million Contract With SAP (Government Technology)
  • 3/11/15 The big reason California state computer projects fail (Sacramento Bee)
• Before class on April 5: Sections 6.1, 6.2, 6.3.
• Before class on April 19: Sections 4.1, 4.2.
• Before class on April 26: Sections 5.1, 5.2, 5.3.1, 10.1, 10.2, 10.3 to the middle of p. 207, where 10.3.2 starts. The Mythical Man Month (and see my errata)
• Before class on May 5: Sections 10.5, 10.6, 10.7, Automated Testing for League of Legends
• Before class on May 12: Sections 5.1, 5.2, 5.3.1, and the "Class Design and Class Diagrams" part of 7.3.3
• Before class on May 24: Sections 5.3.5 (I should have assigned this earlier in the quarter), 7.1, 7.2.

Homeworks

Homework 3

Homework 2 - Template - Testing Matrix

Homework 1 - Template - Scan of Appendix B, Example 4
Several examples of requirements specifications:

• Four examples in the Homework 1 format, written by Readers from last year and this year: Sample 1, Sample 2, Sample 5, Sample 6.
• WhatTimeIsIt from Joel on Software
• Ambulance Dispatch System by Rohleder, Smith, and Dix
• Claw Design Bible (At the Computer Game Design Conference on May 6, 1998, there was a panel on design docs. Moderator Alex Dunne referenced a game design document which was submitted by panelist John Jack, a producer at Monolith. This design doc was from the company's computer game, "Claw".)

Lecture Notes, Overheads, Videos, and Links

Midterm 1 questions list and Midterm 1 from Spring, 2015

Midterm 2 questions list and Midterm 2 from Spring, 2015

Final Exam from Spring, 2015

Handy list of videos we watched in lecture

• J. B. Rainsberger, 7 minutes, 26 seconds (May 12)
• Nordstrom Innovation Lab (May 24)
• Clay Shirky, Cognitive Surplus (part 1; we also watched part 2) (May 26)