• None! (First class.)

• 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]

• 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!

• 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]

• 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]

• 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]

• 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

• 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]

• 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]

• Wikipedia's Basic Block
• Wikipedia's Data-flow Analysis
• HW3 Specification

• 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]

• 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

• HW4 Specification

• 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

• 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

• 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

• Malkwai's The art of software systems development: Reliability, Availability, Maintainability, Performance (RAMP)

• Wikipedia's Software Design Pattern
• HW5 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]

• 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?

ITS Teaching and Learning Projects for HW6 (10 minutes)
Zhen Qian and Matt Jones, Application Development, UM ITS.

Medium-Scale Software Engineering (70 minutes)
Dr. Kevin Leach, Senior Research Scientist, Clinc.

• HW6 Specification

• See special reading instructions

• Wikipedia's Java Native Interface
• Python's Extending Python with C or C++

• 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]

• Le Goues et al.'s A Systematic Study of Automated Program Repair: Fixing 55 out of 105 Bugs for $8 Each
• Jia et al.'s Finding and fixing software bugs automatically with SapFix and Sapienz [Facebook]


• 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]