\documentclass[11pt]{article}

\title{Course Project}
\author{15-819O: Program Analysis \\
        Jonathan Aldrich ({\tt aldrich@cs.cmu.edu})}
\date{
Project Proposals due Friday, March 22 at 11:59pm \\
Milestone 1 Report due Monday, April 8 at 11:59pm \\
Milestone 2 Report due Monday, April 22 at 11:59pm \\
Project Presentations due Monday, May 6 at 10:00am \\
Final Deliverables due Monday, May 13 at 11:59pm \\
500 points total
}

\begin{document}
\begin{sloppypar}

\maketitle

The goal of the course project is to become deeply familiar with
a subarea of program analysis research and to make a research or
engineering contribution to the state of the art.  The expected
scope of the project is about 40 hours, spread out over the last
half of the course.

\textbf{Groups.}  Students may work on this project in groups.  Group
projects will be given a single grade, with exceptions only in
extraordinary circumstances (e.g. if someone is clearly not pulling
his or her weight).  You are free to choose your own groups.
Expectations for the project will be scaled (within reason) to the
size of the group.


\section{Project Presentations (150 points)}

Prepare a presentation 15-20 minutes in length.  Describe the problem you are solving and why it is important; give any background not already provided in the class; explain how you solved the problem, and show your results or give a short demo, depending on the contribution of your project.  Include a retrospective criticizing your work and considering future extensions that could come out of it.

\section{Project Deliverables (200 points)}

Turn in any visuals you used in your project presentation.  In addition, turn in any additional information necessary to describe and reproduce what you did and your results.  This may take the form of a paper if there are significant technical details not covered in the presentation.  All scientific results, as well as input data, should be included or referenced.  Source code and instructions for building and running it should be included if your project involved implementation.  You need not duplicate information that is already clear in the presentation visuals, but the information provided across all deliverables should be complete and easy to find.

In a Ph.D. course of this form, it is unusual to see significant inequity in contributions to a course project, but if such a case arises, please bring it to the instructor's attention.

%If you worked in a group, each member of the group should turn in a 360 degree peer evaluation. For each team member (including yourself), estimate the percent contribution that team member made to the overall project. If you wish, you may also provide feedback to team members other than yourself on their strengths and areas for improvement.  I will pass on the feedback (which will naturally not be anonymous in a group of two) but not the percentages.  The percentages will be used, in the unlikely case that it is necessary, to ensure that 

\end{sloppypar}
\end{document}
