Standard Requirements for Individual Study under Dr. Newman

1. Develop an annoted bibliography (including those papers you have
        already read).  Each entry should include the full bibliographic
        information (as in journal reference lists).  Please send a sample
        of each kind of entry asap so that I can make sure we are on the
        same page on this.  Annotations should include both a sketch of
        the paper (not necessarily their abstract - it may include more or
        less than that, but at least should include any keywords and names
        of systems that were mentioned or explained in the paper - this is
        for easy location later when you write a paper or thesis on the
        topic).
        Annotated bibliography updates should be sent with each report
        (see below).
	The bibliographic entries should be kept in bibtex format, and the 
	annotated version should be in latex, with citations to the .bib
	file.  See www.cise.ufl.edu/~nemo/papers/example.bib and
	www.cise.ufl.edu/~nemo/papers/ex-annotated.tex
	The annotated bibliography should be compiled using latex, then
	the bibliographic entries compiled into a .bbl file using bibtex,
	then latex run a couple more times to resolve references.
	Use xdvi to view the .dvi file, dvips and dvipdf to produce
	postscript and PDF formats, respectively.
	EXAMPLE:
$ latex ex-annotated.tex 
This is TeX, Version 3.14159 (Web2C 7.4.5)
(./ex-annotated.tex
LaTeX2e <2001/06/01>
(/usr/local/share/texmf2/texmf/tex/latex/base/article.cls
Document Class: article 2001/04/21 v1.4e Standard LaTeX document class
... snip ....
No file ex-annotated.aux.

LaTeX Warning: Citation `jpeg' on page 1 undefined on input line 27.
... snip (lots more warnings of undefined citations) ...
(see the transcript file for additional information)
Output written on ex-annotated.dvi (2 pages, 5852 bytes).
Transcript written on ex-annotated.log.

$ bibtex ex-annotated
This is BibTeX, Version 0.99c (Web2C 7.4.5)
The top-level auxiliary file: ex-annotated.aux
The style file: plain.bst
Database file #1: example.bib

$ latex ex-annotated
... snip ... (pretty much the same output as before)....

$ latex ex-annotated
... snip ... (same except there should be no citation warnings)...
(./ex-annotated.bbl [2] [3] [4]) [5] (./ex-annotated.aux) )
(see the transcript file for additional information)
Output written on ex-annotated.dvi (5 pages, 14420 bytes).
Transcript written on ex-annotated.log.

$ xdvi ex-annotated &
$ dvips -f ex-annotated.dvi > ex-annotated.ps
This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com)
' TeX output 2004.04.22:1757' -> 
<texc.pro><f7b6d320.enc><74afc74c.enc><texps.pro>. <cmti10.pfb><cmbx12.pfb>
<cmr10.pfb><cmr17.pfb>[1] [2] [3] [4] [5] 

$ dvipdf ex-annotated.dvi > ex-annotated.pdf
$
	Bibliography should be updated and submitted as .tex, .bib, and
	.pdf files regularly.  You may also develop a web page indexing
	websites and copies of PDF and/or postscript copies of papers
	in the bibliography.

2. Develop a study/project plan.  This may be for a term paper, for a
        protocol design, simulation, or software code, or some combination
        of these.  For each deliverable, there is a different decomposition
        of it into subgoals (e.g., researching and writing up the various
        background technologies for a paper, researching and evaluating
        existing technology choices/protocols for development projects,
        planning requirements, architecture, etc. for simulation or for
        software).  The plan elements should have planned dates of
        completion associated with them, and any dependencies noted.
3. Produce biweekly progress reports.  These should refer to the plan
        (in the first such report) and where you are one each of the main
        plan elements (as an overview).  This is easy - just include a
        copy of the list with a status column and edit the status column.
        It should also include specifics on the recently accomplished
        goals and be specific about the goals for the next reporting
        period (e.g., I have read and annotated the papers listed below
        with their annotations, I have attached the revised section 2 of
        my paper, and I have refined the simulation architecture - see
        the third attachment below.  Next I plan to develop detailed
        design for the simulation, learn how to use simulation tool ns,
        and read the following papers ....).
        Any finished artifacts should be included (e.g., design documents,
	bibliography updates, reasonably complete and rewritten sections
	of papers you are writing, completed code or simulations, etc.).
	Email your reports to me.
4. Produce a final report.  This should include final paper, code, 
	simlulation, simulation results, etc.  This must be submitted 
	two weeks before the end of classes in order for me to grade it.
	If you want a chance to revise it after comment, then submit a
	draft at least three weeks before the end of classes.