Date	Topic and Notes	Assignments	Reading For This Class
Wed Jan 03	What is Software Engineering? [overview]	Some homeworks are posted. Start early!	None! (First class.)
Mon Jan 08	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] 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]
Wed Jan 10	Measurement [overview]		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!
Mon Jan 15 MLK Day	—	—	—
Wed Jan 17	Quality Assurance and Testing James Perretta, UMich [qa, guest]		Wikipedia's Quality Assurance Wikipedia's Software Testing Optional: "How does Google test each change to all of its software?" Found out in: Memon et al.'s Taming Google-Scale Continuous Testing [Google]
Mon Jan 22	Test Suite Quality Metrics [qa]	HW 1a (Test Coverage) Due	Wikipedia's Code Coverage Wikipedia's Mutation Testing 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]
Wed Jan 24	Test Inputs, Oracles and Generation [qa]		Wikipedia's Test Data Generation 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] Optional: Play an interactive coding duel puzzle based on this technology. (Good interview practice.) [Microsoft]
Mon Jan 29	Code Inspection and Review [qa]	HW 1b, 1c and 1d (Test Coverage) Due	Wikipedia's Code Review Bacchelli and Bird's Expectations, outcomes, and challenges of modern code review [Microsoft] 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
Wed Jan 31	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]
Mon Feb 05	Static & Dataflow Analysis (1/2) [qa]		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]
Wed Feb 07	Static & Dataflow Analysis (2/2) [qa]	HW 2 (Test Automation) Due	Wikipedia's Basic Block Wikipedia's Data-flow Analysis
Mon Feb 12	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]
Wed Feb 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 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
Mon Feb 19	Debugging as Hypothesis Testing [bugs]		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
Wed Feb 21	In-Class Exam #1 [exam]	HW 3 (Mutation Testing) Due	(no Discussion Sections on Friday the 23rd)
Mon Feb 26 Vacation	—	—	—
Wed Feb 28 Vacation	—	—	—
Mon Mar 05	Requirements and Specifications [design]		Wikipedia's Requirements Elicitation Zowghi and Coulin's Requirements Elicitation: A Survey of Techniques, Approaches and Tools
Wed Mar 07	Elicitation, Validation and Risk [design]		Wikipedia's Software Verification and Validation Wikipedia's Fault Tree Analysis
Mon Mar 12	Patterns and Anti-Patterns James Perretta, UMich [design, guest]	HW 4 (Defect Detection) Due	Wikipedia's Software Design Pattern 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]
Wed Mar 14	Refactoring and Search-Based Software Engineering Marouane Kessentini, UMich [guest]		Wikipedia's Code Refactoring Wikipedia's Search-Based Software Engineering Video of In-Class Demo 1 Video of In-Class Demo 2
Mon Mar 19	Designing for Maintainability [design]		Malkwai's The art of software systems development: Reliability, Availability, Maintainability, Performance (RAMP)
Wed Mar 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 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?
Mon Mar 26	Productivity (bring a coding laptop!) [coding]	HW 5 (Debugging Automation) Due	See special reading instructions
Wed Mar 28	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]
Mon Apr 02	Software Reliability Engineering at Google Adam Brady, Google [guest]	HW 6a (Contribution) Due
Wed Apr 04	Software Engineering at a Startup Jason Mars, Clinc. [guest]
Mon Apr 09	Multi-Language Projects [coding]		Wikipedia's Java Native Interface Python's Extending Python with C or C++
Wed Apr 11	In-Class Exam #2 [exam]		(no Discussion Sections on Friday the 13th)
Mon Apr 16	Automatic Program Repair [overview]	HW 6b (Contribution) Due	Le Goues et al.'s A Systematic Study of Automated Program Repair: Fixing 55 out of 105 Bugs for $8 Each Optional: "What happened when a real company tried this?" Find out in: Haraldsson et al.'s Fixing Bugs in Your Sleep: How Genetic Improvement Became an Overnight Success [Janus]