\documentclass[11pt,twoside]{article}

\usepackage{latexsym}
\usepackage{code}
\usepackage{proof}
\usepackage{fancyhdr}
\usepackage{lecnotes}

\lhead{\fancyplain{}{\bfseries TITLE}}
\chead{}
\rhead{\fancyplain{}{\bfseries \thepage}}
\lfoot{{\small\scshape Project Proposal}}
\cfoot{}
\rfoot{{\small\scshape \today}}

\title{{\large 15-819K: Logic Programming}\\
       {\large Project Proposal}\\
       {TITLE}}
\author{AUTHORS}
\date{\today}

\begin{document}

\maketitle

\begin{abstract}
A short abstract summarizing the proposed project, 200 words or
fewer.  The proposal, excluding the references, must be at most
10 pages and must conform to this format.  If there is additional
supporting material, say, more examples or a partial
implementation, please provide a URL and sketch what is there.
The firm deadline for handing in the proposal is \textbf{Tuesday,
November 21}.  Proposals will be graded.
\end{abstract}

\section{Introduction}

The introduction should provide motivation, clear problem
statement, and review of the most relevant prior work with
citations.  The introduction should be accessible to anyone in
the class, including me, so do not expect too much background
knowledge.  This is especially true if the proposal applies logic
programming in your own area of research.

\section{Project Description}

Describe the proposed research.  This may include additional
background, examples of the problem and proposed solutions, and
partial results obtained so far.  Be explicit about how you plan
to approach the problem and what is novel about it compared to
prior work.  If you have conjectures or plan to prove certain
theorems, state them as clearly as possible.  If you plan an
implementation, sketch its functionality and justify your
implementation language.  If you propose a language design,
sketch the properties you expect to hold (even if you do not plan
to prove them) and the kind of programs you would like to
express.  Examples are a useful device in illustrating what you
propose; use them liberally.

\section{Expected Outcome}

Detail the expect outcome of the project.  Summarize here any
theoretical results, language designs, implementations, or other
artifacts you intend to produce.  It is important to delineate
the scope of the proposed project, so you should also explicitly
mention what you do not plan to address.  For example, you might
state that you wish to produce a design but not an
implementation, or an implementation but not a correctness proof
for it.

You should also explain how you would assess the outcome of
your project.  For example, you might measure speed improvements
in compiled code, or consider the range of algorithms
your language can express, or the kind of programs that
your analysis can certify.

A proposal is not a binding contract, and research is
unpredictable by nature, so this section should represent your
best guess.  If there are contingencies they should be spelled
out to the extent you can anticipate them.

A project report is a required outcome for every group.  If you
believe that a paper might result from the work, give some
potential publication venues.

\section{Conclusion}

Summarize the proposed project, now that its technical basis has
been explained, and point to some potential future work (even if
you do not plan on carrying it out yourself).

\section{References}

Give the references in the usual BibTeX format.

\bibliographystyle{plain}
% \bibliography{lp}

\end{document}
