Your thesis is not your dissertation. Neither is it a one liner about what you are doing. Your thesis is "a position or proposition that a person (as a candidate for scholastic honors) advances and offers to maintain by argument." [Webster's 7th New Collegiate Dictionary]. "I looked at how people play chess" is not a thesis; " people adapt memories of old games to play new games" is. Similarly, "I wrote a program to play chess" is not a thesis; "playing chess requires a database of actual games" is. A thesis has to claim something. There are many kinds of theses, especially in computer science, but most of them can be lumped into one of the following classes: 1. process X is a feasible way to do task Y
2. process X is a better way to do task Y than any previously known method 3. task Y requires process X
4. people use process X to do task Y
5. process X is a terrible way to do Y
6. people don't use process X
Feel free to substitute "process X" with "memory organization X" or what ever else might make one theory different from another. Make sure you clearly specify the class of tasks Y to which your thesis applies.Besides being a proposition, a thesis has to have another property: it must say something new. "Understanding natural language requires context" is not a thesis (except maybe in a linguistics department); "process X is a feasible mechanism for adding context sensitivity to natural language understanders" is, as is "context is not required for visual understanding. What is a defense?
A defense presents evidence for a thesis. What kind of evidence is apprpropriate depends on what kind of thesis is being defended. Thesis: process X is a feasible way to do task Y
One defense for this kind of claim is an analysis of the complexity, or completeness, or whatever, of the theoretical algorithm. In computer science, the more common defense is based on empirical results from running an experiment. A good defense here means more than one example, and answers to questions such as the following. What are the capabilities and limits of your experiment? How often do the things that your experiment does come up in the real world? What's involved in extending it? If it's easy to extend, why haven't you? If your example is a piece of a larger system, how realistic are your assumptions about input and output? Thesis: process X is a better way to do task Y than any previously known method The same kind of defense applies here as in the previous case, but now serious comparisons with previous systems are required. Can your result do the same examples the previous results did, or can you make them do yours? Can you prove they couldn't do your examples? If you claim to be more efficient, what are you measuring? Thesis: task Y requires process X
This is usually defended by a logical argument. It is usually very tough to do, even if the argument doesn't have to be formalized. Thesis: people use process X to do task Y
Many students make the mistake of picking this kind of thesis to defend. It requires serious experimental evidence to defend, unless your real thesis is of the previous form, i.e., only process X is possible. Selected excerpts from protocols and surveys of your officemates are not psychological evidence, no matter how much they might have inspired your work. Thesis: process X is a terrible way to do Y, or people don't use process X This is a reasonable thesis if process X is a serious contender. The defense would be an analysis of the limits of process X, i.e., things it can't do, or things it does wrong, along with evidence that those things matter. I have lots of theses in my dissertation. Which one should I pick for my defense? Defending a real thesis is hard. If you think you have a lot of theses, you probably just have a bunch of undefended claims. One good thesis, or two so-so theses, with adequate description and defense, is more than enough to fill up a dissertation. I...