Date	Topic and Notes	Assignments	Reading For This Class
W 01/19/22	What is Software Engineering? [overview]	Some homeworks are posted. Start early! HW0 Specification. HW0 is optional, but students have reported in previous semesters that they have to create a Virtual Machine anyway for HW1 through HW5. HW0 walks you through it. HW0 also contains a video tutorial on terminals/bash. HW1 Specification. HW6 Specification is worth reading early (trust me, you will regret if you don't read it early).	(none; first day of class)
M 01/24/22	Process, Risk and Scheduling [overview]		Wikipedia's Software Development Process Buse and Zimmermann's Information Needs for Software Development Analytics (if you are low on time, read only Sections I-V) [Microsoft] HW1 Specification Optional: "How well do real companies plan and estimate effort?" Find out in: Anda et al.'s Variability and Reproducibility in Software Engineering: A Study of Four Companies that Developed the Same System [Simula]
W 01/26/21	Measurement [overview]	HW0 due	Begel and Zimmermann's Analyze This! 145 Questions for Data Scientists in Software Engineering [Microsoft] Optional: "How does measurement bias relate to software?" Find out in: Mytkowicz et al.'s Producing Wrong Data Without Doing Anything Obviously Wrong!" [IBM] Optional: Don't want to read the Mytkowicz paper? Watch the video instead!
M 01/31/22	Quality Assurance and Testing [qa]	HW1a due	Sections 2.0 to 2.5 of Henderson's Software Engineering at Google [Google] Wikipedia's Quality Assurance Wikipedia's Software Testing Optional: "How does Google test each change to all of its software?" Find out in: Memon et al.'s Taming Google-Scale Continuous Testing [Google]
W 02/02/22	Test Suite Quality Metrics [qa]		Wikipedia's Code Coverage Wikipedia's Mutation Testing Optional: "How did mutation testing improve code review feedback by over 60% for over 10,000 code authors at Google?" Find out in: Petrovic and Ivankovic's State of Mutation Testing at Google [Google] Optional: "Do coverage metrics really help with critical projects?" Find out in: Dupuy and Leveson's An Empirical Evaluation of the MC/DC Coverage Criterion on the HETE-2 Satellite Software [Alcatel]
M 02/07/22	Test Inputs, Oracles and Generation [qa]	HW1b,c,d due	Wikipedia's Test Data Generation Read up to, but not including, "Program Specific Checkers" in Zeller's Fuzzing: Breaking Things with Random Inputs Tillmann and de Halleux's Pex — White Box Test Generation for .NET [Microsoft] Optional: "What's the state of the art in test oracles?" Find out in: Barr et al.'s The Oracle Problem in Software Testing: A Survey Optional: "Can fuzz testing find security bugs?" Find out in: Godefroid et al.'s Automated Whitebox Fuzz Testing [Microsoft]
W 02/09/22	Code Inspection and Review [qa]		Wikipedia's Code Review Bacchelli and Bird's Expectations, outcomes, and challenges of modern code review [Microsoft] HW2 Specification Optional: "How does gender relate to GitHub pull requests?" Find out in: Terrell et al.'s Gender differences and bias in open source: pull request acceptance of women versus men Optional: "Where do invariants come from?" Find out in: Ernst et al.'s The Daikon system for dynamic detection of likely invariants
M 02/14/22	Dynamic Analysis Tools [qa]		Wikipedia's Dynamic Program Analysis Musuvathi et al.'s Finding and Reproducing Heisenbugs in Concurrent Programs [Microsoft] Optional: "How can we detect locking bugs?" Find out in: Savage et al.'s Eraser: A Dynamic Data Race Detector for Multithreaded Programs [Digital]
W 02/16/22	Pair Programming and Skill Interviews [coding]		Wikipedia's Pair Programming Cockburn and Williams' The Costs and Benefits of Pair Programming Dean Jackson's The Google Technical Interview [Google] Section 4.1 of Henderson's Software Engineering at Google [Google] Optional: "What did a survey of over 46,000 comments find out about modern technical interviews?" Find out in: Behroozi et al.'s Hiring is Broken: What Do Developers SayAbout Technical Interviews? [Microsoft] Optional: "What can go wrong in pair programming?" Find out in: Lewis and Shah's How Equity and Inequity Can Emerge in Pair Programming
02/20/22	(None; this is a sunday)	HW2 due
M 02/21/22	Static & Dataflow Analysis (1/2) [qa]	HW3 is due after Exam1. However, leaving much work of HW3 until after the exam typically works poorly for students!	Wikipedia's Static Program Analysis Ayewah et al.'s Experiences Using Static Analysis to Find Bugs [Google] HW3 Specification Optional: "How does Microsoft find bugs in critical device drivers?" Find out in: Ball et al.'s A Decade of Software Model Checking with SLAM [Microsoft] Optional: "What are deployment challenges for static analysis?" Find out in: Bessey et al.'s A Few Billion Lines of Code Later: Using Static Analysis to Find Bugs in the Real World [Coverity]
W 02/23/22	Static & Dataflow Analysis (2/2) [qa]		Wikipedia's Basic Block Wikipedia's Data-flow Analysis
M 02/28/22	Defect Reporting and Triage [bugs]		Wikipedia's Bug tracking system Bettenburg et al.'s What Makes a Good Bug Report? [Apache, Eclipse, Mozilla] Optional: "Are testers more neurotic than developers?" Find out in Smith et al.'s Beliefs, Practices, and Personalities of Software Engineers: A Survey in a Large Software Company [Microsoft]
W 03/02/22	Exam 1.	Exam Example, Key for Exam Example
03/06/22	(None; this is a Sunday)	HW3 due
03/07/22	Spring Break
03/09/22	Spring Break
M 03/14/22	Fault Localization and Profiling [bugs]		Wikipedia's Profiling Parnin and Orso's Are Automated Debugging Techniques Actually Helping Programmers? Graham et al.'s gprof: a Call Graph Execution Profiler HW4 Specification Optional: "How can we collect per-path information?" Find out in: Ball and Larus's Efficient Path Profiling [Microsoft] Optional: "What other fault localization techniques exist?" Find out in: Wong and Debroy's A Survey of Software Fault Localization
W 03/16/22	Debugging as Hypothesis Testing [bugs]		Sections 2.7 to 2.10 of Henderson's Software Engineering at Google [Google] Andreas Zeller's Automated Debugging: Are We Close? Optional: For more information on this project, visit: Zeller's Delta Debugging: from automated testing to automated debugging Optional: For an entire on-line course on this topic, visit: Udacity's Software Debugging: Automating the Boring Tasks
03/20/22	(None; this is a Sunday)	HW4 due
M 03/21/22	Debugging as Hypothesis Testing (cont.) + Exam1 Discussion [bugs]
W 03/23/22	Requirements and Specifications [design]		Wikipedia's Requirements Elicitation Spolsky's How To Be A Program Manager [Stack Overflow] Zowghi and Coulin's Requirements Elicitation: A Survey of Techniques, Approaches and Tools HW5 Specification
M 03/28/22	Guest Lecture, Dr. Denae Ford Senior Researcher, Microsoft Research Note: This lecture will be a remote lecture over Zoom. Zoom link will be emailed to students before the lecture.	The Next Generation of Software Developers (slides)
W 03/30/22	Elicitation, Validation and Risk [design]		Abstract, Section 1 and Section 2 of Bjarnason et al.'s Challenges and practices in aligning requirements with verification and validation: a case study of six companies (first 5.5 pages only) Sinofsky's PM at Microsoft (cached copy) (original) [Microsoft] Wikipedia's Fault Tree Analysis
M 04/04/22	Designing for Maintainability [design]	HW5 due	Up to and including Section II-B of Liu et al.'s Automatic Generation of Pull Request Descriptions (the rest is optional) Malkwai's The art of software systems development: Reliability, Availability, Maintainability, Performance (RAMP) Spolsky's Things You Should Never Do, Part 1 [Stack Overflow]
W 04/06/22	Guest Lecture, Adam Brady Google Note: This lecture will be a remote lecture over Zoom. Zoom link will be emailed to students before the lecture.	SRE, Service Levels, and Error Budgets
M 04/11/22	Patterns and Anti-Patterns [design]	HW6a due	Wikipedia's Software Design Pattern HW6 Specification Optional: "How do design patterns work in industry?" Find out in: Beck et al.'s Industrial Experience with Design Patterns [AT&T, Motorola, Siemens, IBM]
W 04/13/21	Code Inspection and the Brain [coding, qa]		Floyd et al.'s Decoding the representation of code in the brain: An fMRI study of code review and expertise Krueger et al.'s Neurological divide: an fMRI study of prose and code writing.
M 04/18/21	Productivity [coding] (this lecture includes a participation component; you will need a coding laptop/environment)		See special reading instructions
W 04/20/22	Guest Lecture, Dr. Chad Spensky Note: This lecture will be a remote lecture over Zoom. Zoom link will be emailed to students before the lecture.	Lecture SlidesM 04/25/22	Automatic Program Repair [overview]		Marginean et al.'s SapFix: Automated End-to-End Repair at Scale [Facebook] Monperrus et al.'s Repairnator patches programs automatically Optional: "Can smaller companies use automated repair?" Find out in: Haraldsson et al.'s Fixing Bugs in Your Sleep: How Genetic Improvement Became an Overnight Success [Janus] Optional: "How does mutation relate to automated repair?" Find out in: Le Goues et al.'s A Systematic Study of Automated Program Repair: Fixing 55 out of 105 Bugs for $8 Each
W 04/27/22	Bonus Lecture: Human Factors in SE, AI4SE, SE4AI TBA
F 05/06/22	Final Exam (Exam2). Online	Exam2 example (key included) HW6b due — Note that there are absolutely no extensions on HW6b. It is already extended as long as possible. The late policy does not apply. Please plan accordingly.