% Example LaTeX Document

% Preamble:  Sets up General Parameters which are Global
\documentclass[12pt]{article}
\usepackage{graphicx}
\usepackage{amsmath}
\usepackage{amssymb}
%\usepackage{doublespace, fullpage}

% Body:  Main Document
\begin{document}
\title{Title of Project\\TJHSST Senior Research Project\\Computer Systems Lab 2009-2010}
\author{Ann Smith - YOUR NAME}
\maketitle

\begin{abstract}
An abstract is a brief summarizing statement, usually between 75 and 150 words long. It gives the reader a synopsis of the problem, method, results, and conclusions of your document. The abstract takes the form of a paragraph, usually with 5-10 sentences. It appears atthe top of a journal 
article, just under the title, or on the page following the title page of a report. 
In the latter instance, the abstract appears on a page by itself.
\par
{\bf Keywords:} genetic algorithms, algorithmic composition
\end{abstract}

\section{Introduction}
 Problem Statement and Purpose
The introduction to your document should lead your readers into your paper and give them an 
idea of what to expect (also see Forecasting). It should not be simply a restatement of the abstract even 
though it will contain some of the same material.
\section{Background}
(from the Mayfield Handbook of Technical Writing) Provide enough information in a technical document
 to allow your reader to understand the specific problem being addressed and to provide a context 
for your own document. This background information may include (1) a historical summary of the 
problem being addressed; (2) a brief summary of previous work on the topic, including, if 
appropriate, relevant theory; and (3) the specific reasons the document is being written.
\par
In short documents, include background information in the introduction. In longer documents, however, 
putting some or all of the background information in a separate section with a heading may be more 
effective. Long and fairly complex reports, especially experimental reports where the purpose of 
the documentis to verify, evaluate, illustrate, or apply one or more theories, often include 
a separate theory section.
\section{Development}
\subsection{Theory}
(from the Mayfield Handbook of Technical Writing) In long and fairly complex reports and articles, especially theoretical and experimental reports 
where the purpose of the document is to apply, verify, or illustrate one or more theories, include 
a separate section presenting relevant theoretical formulae and the techniques by which any 
experimental results are predicted. When introducing equations, be sure to define all symbols used 
in them.
\subsection{Description of Project Work 1}
Write about what you are doing with your project.
\subsection{Description of Project Work 2}
Use subsections if necessary
\section{Tests or Analysis}
Describe how you are testing your project, and the types of analysis you are doing.
\section{Results}
(from the Mayfield Handbook of Technical Writing)
In the results section of a report, describe all appropriate information produced by the research 
procedures. Simply present data and estimates of their accuracy. Save the explanation and 
interpretation of these findings for the discussion section, which usually follows the results 
section. In short documents, however, the results and discussion sections may be combined into a 
single section.
\par 
Results sections make extensive use of graphs and figures to present data effectively. Order 
information by its importance to your audience's purpose in reading the document. State all 
significant findings in the text, referring to tables and graphs displaying all significant data. 
If the study has produced a large amount of raw data, do not present all of it in the results 
section. Instead, present only the information most appropriate to your audience's purpose in 
reading the document,summarizing other key information in graphs and figures. If appropriate, 
include your raw data in an appendix, referring to them within your text.
\par
Use images and visuals to portray information too.
\begin{figure}
%       \vskip-.6in   % OPTIONAL VERTICAL SKIP
       \center    %This figure is saved as "triceratops.jpg"  Leave off the ".jpg" here:
       \scalebox{1.5}[1.5]{\includegraphics*{triceratops}} % ADJUST THE SCALING
%       \hskip-.5in   % OPTIONAL HORIZONTAL SKIP
       \caption{Image of Triceratops building the ancient pyramids}             % OPTIONAL CAPTION
       \end{figure}

\subsection{Testing}
Include subsections if you need them.
\section{Discussion}
(from the Mayfield Handbook of Technical Writing)
\\
Explain in the discussion section of your document information presented in the results section, 
commenting on significant data produced by the study. In writing a discussion section, keep the 
following points in mind.
\begin{enumerate}
%\begin{itemize}
    \item Identify significant patterns in the data and relationships between variables. Offer tentative explanations for these patterns and relationships.

    \item Compare the actual data produced with any predictions or questions posed in the introduction or theory section of the document.

    \item If any of the results differ from the expected results, offer possible explanations for the discrepancies. Present the most probable explanations first and the least probable last.

    \item Consider how well the data answer any questions posed in the document's introduction. Do the results answer the questions completely? If not, explain what questions still need to be addressed and give possible explanations why the results may be inconclusive.

    \item Qualify the scope of your explanations, discussing in what cases your explanations apply and in what cases they may not.

    \item Organize your material in order of importance to your reader's purpose in using the document.
%\end{itemize}
\end{enumerate}
\section{Conclusion}
(from the Mayfield Handbook of Technical Writing)
Include a conclusion as the final part of the body of your document. This part of the document 
should summarize all essential information necessary for your audience's purpose. 
In your conclusion:
\begin{itemize}
\item Relate your findings to the general problem and any specific objectives posed in your introduction.
\item Summarize clearly what the report does and does not demonstrate.
\item Include specific recommendations for action or for further research. Sometimes these recommendations will constitute a separate section of a document.
\end{itemize}
\section{Recommendations}
(from the Mayfield Handbook of Technical Writing)
Many types of scientific and technical documents conclude by pointing to further action. Research
reports often recommend further studies to confirm tentative explanations or to answer questions 
presented in the discussion section. Feasibility and recommendation reports always have one or more 
specific recommendations as the principal aim of the document.
\\
Recommendations should always be specific and appropriate to the document's audience. Separate each 
specific recommendation. Often authors present recommendations in bulleted or numbered lists. 
Organize recommendations either in the order of importance or in the logical order of development.
\begin{thebibliography}{99}
\bibitem{Rosenfeld} R. Rosenfeld, ``Biological Modeling Language'',\newline http://www.cs.cmu.edu/\~blmt/, 2005.
\bibitem{BrogHodg} D. C. Brogan and J. K. Hodgins, ``Group behaviors for systems with significant dynamics'', {\it Autonomous Robots 4}, pp. 137-153, 1997.
\bibitem{BrogMet} D. C. Brogan, R. A. Metoyer, and J. K. Hodgins, ``Dynamically simulated characters in virtual environments'', {\it IEEE Computer Graphics \& Applications 18}, pp. 58-69, September/October 1998.
\underline{The World Wide Web Unleashed}, Sams Publishing, 1994.
\bibitem{Kopka} Helmut Kopka and Patrick W. Daly, \underline{A Guide
 to LATEX}, Addison-Wesley Publishing Co., Inc., 1993.
\bibitem{latex2html} Nikos Drakos and Ross Moore, \underline{LaTeX2HTML
Translator} Version 99.2 beta8(1.43), Macquarie University, Sydney, 1999.
\end{thebibliography}

\section{Appendices}
(from the Mayfield Handbook of Technical Writing)
In one or more appendixes, include materials that are not essential parts of your main text butthat will provide useful reference information to readersseeking more detail.
The following list presents some typical material that is often included in an appendix.
\begin{itemize}
\item Detailed explanations and elaborations too technical for the maintext
\item Additional diagrams
\item Additional tables summarizing data
\item Long lists
\item Experimental protocols or survey questions
\item Selected computer code directly relevant to discussions in the main body
\end{itemize}
\end{document}

