CVA Seminar
CVA Report Preparation
Last Update: 22 March 2011
Note:
or
material is highlighted
|
Oral Reports (to be given during last meeting)
Please prepare an oral presentation of your work this semester.
It should not be longer than 20 minutes.
Outline:
- The role of your task in the overall project, e.g., which passage
you're working on, what you're trying to do with it, etc.
- What you have accomplished, including:
- a report on any human protocols you ran
- your demos
- What the immediate next steps in your part of the project are
- i.e., what you would have done had you had another week or
so to work on it
- What longer-term future steps need to be taken
- i.e., a recommendation to whomever continues your
project about what they should do.
Written Reports
At the end of the semester, you will be expected to hand in a
conference-style report
describing the project you worked on this semester.
It should:
- be on 8.5 x 11-inch paper
- be bound in the upper left-hand corner using a staple or binder
clip
- Do not use folders or covers,
unless your report is too thick to be stapled or binder-clipped.
- have your own title page (not the printer's cover page!)
- The title page should include the following information:
- descriptive title (not: "CVA Project")
- your name
- course number and/or name (if applicable)
- date completed (e.g., 10 May 2011, or whatever).
- followed by the abstract (see below)
- followed immediately by the body of
your paper (which does not have to start on a new page).
I strongly suggest that you
learn to use LaTeX and ispell.
- A LaTeX template is available
here.
The intended audience is the person who will be continuing your
project next semester.
Therefore, the report should be self-contained and
detailed enough to tell that (possibly hypothetical) person exactly:
- what
has been done
- why it was done
- what problems were faced
- how you solved
them
- what needs to be done next
- and how to get started doing it.
In the real world, you will be expected to write papers, either for
presentation at conferences, publication in journals, or presentation to
your boss or co-workers.
Users and other people want to read about
the program, what it
does, how it works, etc., and to see it in action. Consequently, the
main product of your work is the paper
(including, but not limited to, the demo)!
In the paper,
you should say what you have done, and say (in English summary, not in
programming detail) how you have done it. It should also include
your annotated demo.
You should read Goldfain,
Albert (2003),
"Computationally Defining 'harbinger' via Contextual
Vocabulary Acquisition" [PDF], to see an example of a such a paper
or browse through the
"Progress Reports" section of the CVA website.
Thus, each report must consist of the following components:
- abstract of the project (a 1-paragraph summary), consisting
of brief, 1-or-2-sentence summaries of each of the
following points (2a-g, below)
- This is the sort of information you might find yourself having to
give, extemporaneously, in a job interview, in an informal discussion at
a conference or convention, or even in a "real" job when your boss sees you
in the hall or even in the mall :-)
- The abstract should be completely self-contained; i.e., it should be
understandable by someone who is not familiar with our CVA project, as
well as by someone who does not bother to read the rest of your paper!
- And your paper should not assume that the reader has read the abstract!
- Consequently, your paper should includeand probably begin
withany important information from the abstract.
- description of the project (the body of the paper), including:
- brief descriptions of the CVA project and SNePS
- the role of your task in the overall project, e.g., which passage
you're working on, what you're trying to do with it, etc.
- what you have accomplished, including:
- a report on any human protocols you ran
- an annotated transcript of your demos
including commented SNePS representations of the sentence and prior
knowledge.
- the syntax and semantics of new SNePS case frames,
- full explanation of any SNePS networks.
- what the immediate next steps in your part of the project are
- i.e., what you would have done had you had another week or so to
work on it
- what longer-term future steps need to be taken
- list of references (if appropriate)
- Such lists should cite all and only documents that you
explicitly mention in the body of the report.
- Please be sure to cite only published materials (or
unpublished papers from websites).
- Do not cite websites unless there is
a very good reason to do so. If in doubt, ask me.
Please prepare all documents using a word processor (preferably
LaTeX), and hand in hard copy to me on or before the due date announced
in the syllabus.
For inclusion on the CVA website, I would also like online
versions of:
- your complete report, with all appendices (preferably in PDF
format)
- your demo file (plain ASCII text, not .doc)
- a transcript of your demo (plain ASCII text, not .doc)
For further information on how to prepare your report, as
well as pointers on grammar, etc., see my webpage
"How to Write".
Copyright © 2004–2011 by
William J. Rapaport
(rapaport@buffalo.edu)
http://www.cse.buffalo.edu/~rapaport/717cva/reports.html-20110322