Date	Topic and Notes	Assignments	Reading For This Class
T Aug 31	What is Software Engineering? [overview]	Some homeworks are posted. Start early!	Read the HW6 Specification so you can think about it early!
R Sep 02	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]
T Sep 07	Measurement [overview]	HW 0 (Dev Setup) 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!
R Sep 09	Quality Assurance and Testing [qa]	HW 1a (Test Coverage) 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]
T Sep 14	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]
R Sep 16	Test Inputs, Oracles and Generation [qa]	HW 1b, 1c and 1d (Test Coverage) 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]
T Sep 21	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
R Sep 23	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]
T Sep 28	Pair Programming and Skill Interviews [coding]	HW 2 (Test Automation) Due	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 Say About 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
R Sep 30	Static & Dataflow Analysis (1/2) [qa]	(putting off HW 3 typically works poorly for students)	Wikipedia's Static Program Analysis Ayewah et al.'s Experiences Using Static Analysis to Find Bugs [Google] 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]
T Oct 05	Static & Dataflow Analysis (2/2) [qa]		Wikipedia's Basic Block Wikipedia's Data-flow Analysis HW3 Specification
R Oct 07	— (optional "Bonus" lecture: World Building)	Exam #1 Due (you pick a 2-hour window within this 24-hour day)
T Oct 12	Defect Reporting and Triage [bugs]	HW 3 (Mutation Testing) Due	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]
R Oct 14	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
T Oct 19 (break)	—	—	—
R Oct 21	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
T Oct 26	Requirements and Specifications [design]	HW 4 (Defect Detection) Due	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
R Oct 28	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
T Nov 02	Designing for Maintainability [design]		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]
R Nov 04	Patterns and Anti-Patterns [design]	HW 5 (Debugging Automation) 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]
T Nov 09	Dr. Kevin J. Leach, Vanderbilt University [guest]
R Nov 11	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 Siegmund et al.'s Measuring Neural Efficiency of Program Comprehension [Microsoft] Optional: "What did reddit think of this?" Find out in: Does the brain interact with programming languages like it does with natural languages?
T Nov 16	Productivity (bring a coding laptop!) [coding]	HW 6a (Contribution) Due	See special reading instructions
R Nov 18	Multi-Language Projects [coding]		Wikipedia's Java Native Interface Python's Extending Python with C or C++
T Nov 23	Guest Lecture Dr. Ciera Jaspan, Google [guest]		Jaspan et al.'s "Enabling the Study of Software Development Behavior with Cross-Tool Logs" [Google]
R Nov 25 (break)	—	—	—
T Nov 30	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
R Dec 02	Game Theory [other]		Optional: How can game theory be used to find concurrency bugs in safet-critical systems? Find out in: Henzinger's Games, Time, and Probability: Graph Models for System Design and Analysis. Optional: For more information, visit Wikipedia's Nim.
T Dec 07	Security and Software Engineering [other]		Optional: For more information on buffer overflows, which this lecture assumes you have seen previously, visit Wikipedia's Buffer overflow.
R Dec 09	Quantum Computing and Romance Novels [other]	You Should Pretend HW 6b (Contribution) is Due (see below about no late submissions)
T Dec 14	—	Exam #2 Due (you pick a 2-hour window within this 24-hour day)
R Dec 16	—	HW 6b (Contribution) Due (cannot be accepted later than this, please plan accordingly) All Course Materials Due