CSCI 3366 (Introduction to Parallel and Distributed Processing), Spring 2001:
Guidelines and Requirements for Projects


Contents

Overview

One of the requirements for this course is completion of a project. The project will count as 100 points of your total grade; i.e., it counts as much as an exam and about 2.5 times as much as a homework. Students may work individually or in groups of two. A project can consist of writing a non-trivial parallel program, or performing a set of experiments exploring some aspect of parallel programming, or anything else relevant to the course and approved by the instructor. It should be something about 2.5 times as ambitious as one of the 40-point homeworks, and if two people work together, the project should be about twice as ambitious as a solo project. All projects must be approved in advance by the instructor, who will be the final arbiter of whether the topic and level of difficulty are appropriate.

Suggestions for topics

Possible project topics include, but are not limited to, the following. If your project involves writing code, you may use any language/library that can be run on the department's network of lab machines.

Parallel applications

Your project can be the design and implementation of a non-trivial parallel application. There are many, many possibilities here; see the problems at the end of each chapter in the textbook for ideas. You should plan to collect and analyze at least minimal performance data for your application.

Performance experiments

Your project can consist of a set of experiments designed to measure something about a parallel-programming platform or platforms, such as one of the following.

What to turn in and when

Project proposal

What:

A brief description of your project topic, no more than a paragraph, in the form of a short e-mail to the instructor. (Plain text is preferred over proprietary word-processor formats.)

When due:

April 10 at 5pm.

Points:

5 points.

Project plan

What:

A more detailed description of your project, up to a page, again in the form of an e-mail to the instructor. (Plain text is preferred over proprietary word-processor formats.) If you are writing an application, describe what problem you are solving and the design of your parallel algorithm. If you are conducting performance experiments, describe what you are trying to measure and the experiments you will use to measure it.

When due:

April 19 at 5pm.

Points:

5 points.

Final oral presentation

What:

An oral presentation, up to 5 minutes, about your project. In this presentation, you should:

When due:

During the time slot reserved for this course's final exam (May 8, 2:30pm - 5:30pm).

Points:

20 points.

Final written report

What:

A brief report (no more than five pages should be required, and two or three will suffice for many projects) describing your project's goals and outcome, in hard-copy form. This should be an expanded version of your oral presentation, describing your project's goals, design, and results. It should include bibliographic references as appropriate.

When due:

May 8 at 2:30pm. Not accepted late.

Points:

35 points.

Source code

What:

Complete working source code for any program(s) you wrote as part of your project, submitted electronically as for homework. Be sure your code is readable and well-documented.

When due:

May 8 at 2:30pm. Not accepted late.

Points:

35 points.



Berna Massingill
2001-03-29