| Date | Topic | Assignment |
|---|---|---|
| Jan 18 | Introduction & Software Process | [Project] Pre-proposal presentation date: Feb 22 |
| Jan 25 | Requirements Analysis & Software Design | |
| Feb 1 | Project Management & Software Testing | An Empirical Analysis of Flaky Tests (Presenter: Mostafa ) |
| An Empirical Study on Real Bug Fixes (Presenter: Will ) | ||
| [Critique] Due date: Feb 8 | ||
| Feb 8 | Empirical Study on Bugs | Change Distilling: Tree Differencing for Fine-Grained Source Code Change Extraction(Presenter: Ye ) |
| Fine-grained and Accurate Source Code Differencing(Presenter: Kijin ) | ||
| [Critique] Due date: Feb 15 | ||
| Feb 15 | Program Differencing | CCFinder: a multilinguistic token-based code clone detection system for large scale source code (Presenter: Tithi ) |
| Sourcerercc: scaling code clone detection to big-code (Presenter: Yin ) | ||
| [Critique] Due date: Mar 15 | ||
| Feb 22 | No class | The instructor is on sick leave |
| Mar 1 | Pre-proposal Presentation | [Project] 2-page proposal due date: Mar 15 |
| Mar 15 | Clone Detection | MUDABlue: An Automatic Categorization System for Open Source Repositories (Presenter: Grace ) |
| On automatically detecting similar Android apps (Presenter: Michelle ) | ||
| [Critique] Due date: Mar 22 | ||
| [Project] Midpoint presentation date: Apr 5 | ||
| Mar 22 | Similar Software Detection | Visualization of test information to assist fault localization (Presenter: Swapna ) |
| Where should the bugs be fixed? - more accurate information retrieval-based bug localization based on bug reports(Presenter: Chandani ) | ||
| [Critique] Due date: Mar 29 | ||
| Mar 29 | Fault Localization | Automatically finding patches using genetic programming(Presenter: Shengzhe ) |
| SemFix: program repair via semantic analysis(Presenter: Ye ) | ||
| [Critique] Due date: Apr 12 | ||
| Apr 5 | Midpoint Project Presentation | [Project] Final presentation date: May 3 |
| Apr 12 | Automatic Program Repair | Chianti: A Tool for Change Impact Analysis of Java Programs (Presenter: Andrej ) |
| Finding failure-inducing changes in java programs using change classification (Presenter: Tuna ) | ||
| [Critique] Due date: Apr 19 | ||
| Apr 19 | Change Impact Analysis | Systematic editing: generating program transformations from an example (Presenter: Breno [PPT]) |
| LASE: locating and applying systematic edits by learning from examples (Presenter: Madhusudan [PPT]) | ||
| [Critique] Due date: Apr 26 | ||
| Apr 26 | Systematic Editing | |
| May 3 | Final Project Presentation | [Project] Final project report due date: May 10 |