<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Notes and Such &#187; guide</title>
	<atom:link href="http://blog.mmhkay.de/tag/guide/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mmhkay.de</link>
	<description>A weblog</description>
	<lastBuildDate>Thu, 19 Nov 2009 22:08:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>PhD approaches &#8211; overview of some literature</title>
		<link>http://blog.mmhkay.de/2009/11/phd-research-approaches-overview-of-some-literature/</link>
		<comments>http://blog.mmhkay.de/2009/11/phd-research-approaches-overview-of-some-literature/#comments</comments>
		<pubDate>Thu, 19 Nov 2009 22:06:33 +0000</pubDate>
		<dc:creator>soeren</dc:creator>
				<category><![CDATA[PhD]]></category>
		<category><![CDATA[book review]]></category>
		<category><![CDATA[guide]]></category>
		<category><![CDATA[methodology]]></category>
		<category><![CDATA[research]]></category>

		<guid isPermaLink="false">http://blog.mmhkay.de/?p=160</guid>
		<description><![CDATA[Much too late did I realize that the molding of a Ph.D. topic and the preparation of the proposal is something rather independent from the subject of study (software engineering, in my case) and can be taught and learned. The trigger for this insight was a writing course at the University of Leipzig where the [...]]]></description>
			<content:encoded><![CDATA[<p>Much too late did I realize that the molding of a Ph.D. topic and the preparation of the proposal is something rather independent from the subject of study (software engineering, in my case) and can be taught and learned. The trigger for this insight was a <a href="http://www.schreibzentrum-leipzig.de/wissen_fr.htm">writing course</a> at the University of Leipzig where the instructor demonstrated with a few simple exercises that she had to offer something for the variety of subjects and fields the participants were working in.</p>
<p>This experience lead me to reflect on the whole process: what made it so erratic, why would it take longer than expected and why would it be so frustrating? I came up with the following explanations for myself:</p>
<ol>
<li>unspecific guidance: everybody has heard of a &#8220;proposal&#8221; and you know that it is meant to be written before the actual thesis. But how to even get there? How to start, what to do in the middle? The time from start to proposal can easily cover a year and requires particular activities and techniques &#8211; find them out and name them</li>
<li>The deliverables are not clearly defined: so you look up some literature, how to structure it? What about these ominous research questions, how do they look like? What is a topic and when do I know that I have found one? At least for me it is very hard to try to reach an unclear goal.</li>
<li>Heuristics / strategies / quality gates: How to decide between alternatives? How to judge their feasibility? Again, if you have no clue what to look for, how do you know when you found it?</li>
</ol>
<p>To find out more about this I went through a number of books and articles and for the most relevant sources I want to share  what I consider most useful about them.</p>
<h2>The sources</h2>
<p>I have reviewed several books and online articles. Some focussing on academic writing project in general, some focussing on the early stages (up to a research) proposal for computer scientists.</p>
<p>The books</p>
<ul>
<li>Booth, W. C.; Colomb, G. G. &amp; Williams, J. M. (2003), <em>The Craft of Research</em>, The University of Chicago Press.</li>
<li>Davis, G. B. &amp; Parker, C. A. (1997), <em>Writing the doctoral dissertation: a systematic approach</em>, Barrons&#8217; Educational Series, Inc..</li>
<li>Kruse, O. (1999), <em>Keine Angst vor dem leeren Blatt, </em>Campus Verlag.</li>
</ul>
<p>and the online articles</p>
<ul>
<li>Lauer, H. (1975), &#8216;Discussion on Ph.D. thesis proposals in computing science&#8217;, <em>The Computer Journal</em> <strong>18</strong>(3).</li>
<li>Levine, J. S. (2004),&#8217;Writing and Presenting Your Thesis or Dissertation&#8217;, eBook, http://www.lulu.com/product/e-book-download/writing-and-presenting-your-thesis-or-dissertation-%28ebook%29/96916. (Also available at: <a href="http://www.learnerassociates.net/dissthes/index.htm">http://www.learnerassociates.net/dissthes/index.htm</a>)</li>
</ul>
<h2>The process of writing a proposal</h2>
<p>All sources except Davis and Parker discuss the writing process at least up until the proposal itself. They all more or less assume that there are the following steps</p>
<ul>
<li>an orientation phase</li>
<li>a literature research phase</li>
<li>a selection or refinement phase</li>
<li>the write-up of the proposal</li>
</ul>
<p>Kruse describes the orientation in much detail, he discusses particular questions that any research should ask him/herself when starting a new, big project, how to narrow a subject down, what types of projects there are and much more.  The book looks at all of this from a &#8220;writing&#8221; point of view, where the act and skill of writing is the vehicle to generate and order thoughts and bring them into a shape that can be used to inform others. Lauer takes the opposite approach and looks at the PhD process as a project and gives appropriate advice on how to manage the different stages.</p>
<p>The literature research phase is presented similarly in all the four sources. The literature review for a proposal is supposed to be comprehensive but not exhaustive (which it needs to be in the thesis itself). Kruse recommends to do a very superficial but broad literature &#8220;scan&#8221; in the orientation phase (including just reading headlines and abstracts), in order to get a feeling for topics and questions, the amount of potentially relevant material and an idea about who are names to remember in the field.</p>
<h2>Deliverables and Gates</h2>
<p>Even more important (at least for me) than information about the process were specific and concrete deliverables Ican work towards and &#8220;gates&#8221; at which I get feedback on how my creations are so far.</p>
<p>One of the most crucial self-assessment seems to be having a concise research question that reflects the current research. Only with a specific question can the available literature and the necessary research work be narrowed down sufficiently to actually get done. Booth, Colomb and Williams offering a short fill-in-the-blanks pattern for this purpose, that basically asks four questions:</p>
<ul>
<li>What are you studying? (Topic)</li>
<li>What do you want to find out? (Question)</li>
<li>What for? (&#8220;Cost of Research&#8221;)</li>
<li>What benefit does it have for the reader? (Practical application)</li>
</ul>
<p>A beginner&#8217;s mistake (count me in) is to stop narrowing down with just a topic. With an actual question, it becomes clear, what <em>your</em> interest in the topic is. This makes it more concise and relevant to you. Unfortunately, you are not researching for yourself, but for a community of researchers. The third part describes what value this research has to them, or conversely, what cost it comes with if it remains unanswered. Finally, especially if you are in applied research, the questions is: what are the implications outside the research community, in every day life.</p>
<p>Once one is a little deeper into any particular question, the &#8220;topic analysis&#8221; sheet from Davis and Parker might come in handy. They suggest to fill out a questionnaire with six questions, before starting to write the actual proposal. This questionnaire requires you to name a questions, but it also includes a short summary on related work, theories, research approach and possible outcomes. The idea is that you can fill out more than one questionnaire with reasonable effort. If you have more than one topic or several variants on one you can get into them deep enough to know what they are about and so decide which alternative is best, all before you write the actual proposal.</p>
<p>Lauer offers some advice on what should be in the proposal, which goes pretty much along the lines of Davis and Parker. His notion of checking the quality of a proposal leads to idea that this should be a circular or iterative process. He discusses what could go wrong at early versions of a proposal and what is necessary to fix these problems.</p>
<h2>Summing it up</h2>
<p>Hopefully, this little overview of my small library of research aproach sources has given you some hints as to whether or not this is usefull for you. I am sure there is a ton of different literature, but it appears to me that I am approaching &#8220;<a href="http://books.google.com/books?id=yPU0ubJkpXcC&amp;pg=PA153&amp;lpg=PA153&amp;dq=theoretical+saturation&amp;source=bl&amp;ots=ydfx2o9qBY&amp;sig=LwpNeKpRZGTHaTip2odAJCDESe8&amp;hl=de&amp;ei=k7sFS-nIDZWsmwOWvtHHCg&amp;sa=X&amp;oi=book_result&amp;ct=result&amp;resnum=6&amp;ved=0CCkQ6AEwBQ#v=onepage&amp;q=theoretical%20saturation&amp;f=false">theoretical saturation</a>&#8220;, the point at which reading new books on the same topic tell me almost nothing new. Yet there might be stuff that is better written, more compact or more specialized to one or the other discipline. I would love for you to share in the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mmhkay.de/2009/11/phd-research-approaches-overview-of-some-literature/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
