Changes

''Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.''

'''[WORK IN PROGRESS: This post will be updated once I gather all of my thoughts. Stay tuned...]'''

Based on the papers on delta debugging that I've sifted through (with [http://www.infosun.fmi.uni-passau.de/st/papers/computer2000/computer.pdf ''From Automated Testing to Automated Debugging''] by Andreas Zeller being the most understandable to non-math wizards, and [http://www.infosun.fmi.uni-passau.de/st/papers/tr-99-01/esec99.pdf ''Yesterday, my program worked. Today, it does not. Why?''] also by Andreas Zeller probably being the most relevant to our project), here is an outline of my understanding of delta debugging, a summary of the concepts that must be taken into account while working on the delta debugging framework project, and an outline of the conceptual stages of developing the delta debugging framework.

### The test case fails. We know that the failure-inducing change(s) are not exclusively in the change(s) that were removed. I say not exclusively because of the concept of Interference (described above).

### The test case is indeterminate. There were some inconsistencies.