<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<!--Converted with jLaTeX2HTML 2002-2-1 (1.70) JA patch-2.0
patched version by:  Kenshi Muto, Debian Project.
* modified by:  Shige TAKENO
LaTeX2HTML 2002-2-1 (1.70),
original version by:  Nikos Drakos, CBLU, University of Leeds
* revised and updated by:  Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
  Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>Project Option</TITLE>
<META NAME="description" CONTENT="Project Option">
<META NAME="keywords" CONTENT="handbook">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">

<META NAME="Generator" CONTENT="jLaTeX2HTML v2002-2-1 JA patch-2.0">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="handbook.css">

<LINK REL="next" HREF="node25.html">
<LINK REL="previous" HREF="node23.html">
<LINK REL="up" HREF="node22.html">
<LINK REL="next" HREF="node25.html">
</HEAD>

<BODY >
<!--Navigation Panel-->
<A NAME="tex2html384"
  HREF="node25.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
 SRC="file:/usr/share/latex2html/icons/next.png"></A> 
<A NAME="tex2html380"
  HREF="node22.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
 SRC="file:/usr/share/latex2html/icons/up.png"></A> 
<A NAME="tex2html374"
  HREF="node23.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
 SRC="file:/usr/share/latex2html/icons/prev.png"></A> 
<A NAME="tex2html382"
  HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents"
 SRC="file:/usr/share/latex2html/icons/contents.png"></A>  
<BR>
<B> Next:</B> <A NAME="tex2html385"
  HREF="node25.html">Course Work Option</A>
<B> Up:</B> <A NAME="tex2html381"
  HREF="node22.html">Degree Requirements</A>
<B> Previous:</B> <A NAME="tex2html375"
  HREF="node23.html">Thesis Option</A>
 &nbsp; <B>  <A NAME="tex2html383"
  HREF="node1.html">Contents</A></B> 
<BR>
<BR>
<!--End of Navigation Panel-->

<H3><A NAME="SECTION00042200000000000000"></A> 
<A NAME="sec:ProjectOption"></A>
<BR>
Project Option
</H3>

<P>
The project option allows up to 3 of the 30 hours of credit required for graduation to be in
CS5990. In addition to completing the 30 hours of credit in approved courses (including
CS5990 and up to 3 hours of CS5999 credit, An Example Course Plan), a student
following the project option is expected to: present a project plan at a department-wide
seminar, and both written and oral project reports at the conclusion of the project. Thus,
the student should 

<P>

<OL>
<LI>Prepare a written project plan which describes any background work necessary for
     completion of the project and a project plan. 
</LI>
<LI>Defend the project plan in an oral seminar presentation. 
</LI>
<LI>Prepare a final report at the conclusion of the project. 
</LI>
<LI>Defend the project/report in an oral seminar presentation. 
</LI>
</OL>

<P>
Unlike a thesis, a project might not attempt to extend boundaries of computer science
theory and/or practice but may well be focused on completion of some large
programming effort needed to support a research effort in progress at MTU. 

<P>
The project plan presentation is somewhat like a thesis proposal in that the student
presents background material about the project and outlines the basic project plan. As in
the thesis option, the entire faculty is invited to participate in the closed session after the
presentation where faculty will provide suggestions and air concerns regarding the
proposed project. The student and his/her advisor will decide the appropriate action given
this input. 

<P>
At the completion of the project the student will prepare a project report which will
provide the basis for the oral examination. As with a thesis, the final project report needs
to be in the hands of the entire committee no later than two weeks prior to the oral
defense. The project report may take any of several different formats, depending upon
the individual project itself and the desires of the student and committee. The report may
be (but is not limited to) one of the following 

<P>

<UL>
<LI>a description of some constructed software, possibly including personal insights
     into lessons learned during implementation,
</LI>
<LI>a bibliographic essay evaluating the current state of some area within computer
     science, or
</LI>
<LI>a detailed design document and implementation plan for a significant future project
     which would include several grad students in an ongoing implementation study. 
</LI>
</UL>

<P>
Given the goal that students be able to finish a masters with a project option in two
academic years (aiming to finish in May of year 2) the department recommends the
following time-table for the milestones along the way to a project masters. This timetable
is aimed towards students pursuing full-time studies while working half-time as a
supported graduate assistant. Experience indicates that failure to reach these milestones
decreases the likelihood of a student finishing a project masters in two years. (Note: items
marked with a `+' are milestones; items marked with a `*' are `requirements'.) 

<P>
<DL>
<DT><STRONG>+</STRONG></DT>
<DD>A student should find a major advisor during the first year in the program. 
     
</DD>
<DT><STRONG>+</STRONG></DT>
<DD>A student should present a project plan by the end of the 4th term in residence
     (not counting summers). 
     
</DD>
<DT><STRONG>*</STRONG></DT>
<DD>No later than one week prior to the project plan presentation, each CS faculty
     member will be provided with a final version of the written project plan. 
     
</DD>
<DT><STRONG>*</STRONG></DT>
<DD>The entire committee is expected to be chosen no later than two weeks after the
     project plan is accepted. The extent to which non-advisor committee members
     contribute to the development of the project plan, and to the development of the
     final project report will be left to the individual project committees. 
     
</DD>
<DT><STRONG>*</STRONG></DT>
<DD>A ``defendable'' project report needs to be in the hands of the entire committee no
     later than two weeks prior to the oral defense. A  ``defendable
report'' is one that the
     student/advisor feel is ready for defense.  In addition to providing a copy to each
     committee member the student is to provide a copy to each faculty member in CS no
     later than one-week prior to the defense and to make a copy available in the CS
     main office from other interested parties may make a copy. 
     
</DD>
<DT><STRONG>*</STRONG></DT>
<DD>The project defense will include a public description of the student's project
     followed by two question and answer sessions: the first consists of both students
     and faculty; the second being closed to the general audience consists of faculty
     only. 
</DD>
</DL>

<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html384"
  HREF="node25.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
 SRC="file:/usr/share/latex2html/icons/next.png"></A> 
<A NAME="tex2html380"
  HREF="node22.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
 SRC="file:/usr/share/latex2html/icons/up.png"></A> 
<A NAME="tex2html374"
  HREF="node23.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
 SRC="file:/usr/share/latex2html/icons/prev.png"></A> 
<A NAME="tex2html382"
  HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents"
 SRC="file:/usr/share/latex2html/icons/contents.png"></A>  
<BR>
<B> Next:</B> <A NAME="tex2html385"
  HREF="node25.html">Course Work Option</A>
<B> Up:</B> <A NAME="tex2html381"
  HREF="node22.html">Degree Requirements</A>
<B> Previous:</B> <A NAME="tex2html375"
  HREF="node23.html">Thesis Option</A>
 &nbsp; <B>  <A NAME="tex2html383"
  HREF="node1.html">Contents</A></B> 
<!--End of Navigation Panel-->
<ADDRESS>
Steven M. Carr
2006-08-29
</ADDRESS>
</BODY>
</HTML>
