Date	Topic and Notes	Assignments	Reading For This Class
T May 05	What is Software Engineering? [overview]	Some homeworks are posted. Start early!	You should read the HW6 Specification so you can think about it early!
W May 06	Process, Risk and Scheduling [overview]		HW1 Specification 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]
R May 07	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!
F May 08	HW 1a (Test Coverage) Due
M May 11	Quality Assurance and Testing [qa]		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 May 12	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]
W May 13	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]
R May 14	Code Inspection and Review [qa]		HW2 Specification 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
F May 15	HW 1b, 1c and 1d (Test Coverage) Due
M May 18	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 May 19	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]
W May 20	Static & Dataflow Analysis (2/2) [qa]		HW3 Specification Wikipedia's Basic Block Wikipedia's Data-flow Analysis
R May 21	Exam Review. Notes; 2-slide QA on DF and Invariants	Exam 1 Released -- DOWNLOAD -- UPLOAD	Previous Exams
F May 22	HW 2 (Test Automation) Due
M May 25	No class (Memorial Day)
T May 26	Software Engineering through the eyes of a hacker, academic, employee, and CEO Chad Spensky, PhD ABD Allthenticate [guest]	Exam 1 Due at Noon Eastern!
W May 27	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]
R May 28	Fault Localization and Profiling [bugs]		HW4 Specification 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
F May 29	HW 3 (Mutation Testing) Due
M Jun 01	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 Jun 02	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
W Jun 03	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 [Microsoft] Wikipedia's Fault Tree Analysis
R Jun 04	Designing for Maintainability [design]		Malkwai's The art of software systems development: Reliability, Availability, Maintainability, Performance (RAMP)
F Jun 05	HW 4 (Defect Detection) Due HW 6a (Contribution) Due (HW6a can be turned in by Noon Eastern on Monday, June 8 without penalty)
M Jun 08	Patterns and Anti-Patterns [design]		HW5 Specification 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]
T Jun 09	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 Neural Divide: An fMRI Study of Prose and Code Writing 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? Optional: YouTube Coverage: Summary of Neurological Divide...
W Jun 10	Industry Guest Lecture (Research-based startups) Dr. Jack Wadden Sequal, Inc. [guest]		Optional: "How do software testing techniques help hardware?" Find out in: Mahmoud et al.'s Minotaur: Adapting Software Testing Techniquesfor Hardware Errors
R Jun 11	Productivity (bring a coding laptop!) [coding]		See special reading instructions
F Jun 12	HW 5 (Debugging Automation) Due Don't forget about HW 6!
M Jun 15	Multi-Language Projects [coding]		Wikipedia's Java Native Interface Python's Extending Python with C or C++
T Jun 16	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
W Jun 17	Automatic Program Repair [overview]		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]
R Jun 18	Exam 2 Review	Exam 2 Released
M Jun 22	Career Development and Failure	Exam 2 Due at Noon Eastern!	This is the last lecture according to the Academic calendar.
T Jun 23	Bonus Lecture! Software Engineering Research!
W Jun 24	(no lecture)
R Jun 25	(no lecture)	HW 6b (Contribution) Due All Course Materials Due