Project Option

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

1. Prepare a written project plan which describes any background work necessary for completion of the project and a project plan.

2. Defend the project plan in an oral seminar presentation or meet with the advisory committee to discuss the project plan. Complete the departmental Project Plan Approval form.

3. Prepare a final report at the conclusion of the project.
4. Defend the project/report in an oral seminar presentation.

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.

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.

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

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

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'.)

+

A student should find a major advisor during the first year in the program.

+

A student should present a project plan by the end of the 3rd term in residence (not counting summers).

*

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.

*

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.