Abstract Requirements
Abstracts should come from solid computer science journals,
NOT
trade magazines.
Example journals:
IEEE Computer,
IEEE Micro,
Communications of the ACM,
IEEE Transactions on Computers,
Software Practice and Experience,
ACM Transactions on Programming Languages and Systems,
ACM SigOPS,
ACM SigArch,
OS Readings (on Library Reserve),
etc.
Web publications are also ok,
e.g., Sun has numerous white papers available.
Be sure to list the URL on your abstract.
There are also good references in the course text books.
The CS Conference room (Beckman 100) has numerous
journals and conference proceedings.
These come from faculty, so they are not always the most current.
Finally, the terminal room, Beckman 102, usually has some conference
proceedings in the North/East book shelves.
The main idea of the abstract is
to summarize
and
to review
computer science technical literature -
NOT just to
summarize .
Each abstract should be one to two pages
using some sort of text formatter:
LaTeX,
troff, Frame, html, etc.
The abstract should include a short description of the
major points that you found in the article
(demonstrating your understanding of the content).
The abstract should then include
YOUR
analysis of the article:
information content, presentation approach, etc.
Abstract Header Format
The following information
must be in the abstract header:
Course: CS110
Name: John Doe
Abstract Due Date: 1/21/93
Date: 1/21/93
Article Title: OS is fun
Journal Ref: SigOPS, 1/1/1, pg. 92-95, or a URL
Formatter: troff
Due
Due at 6:00pm on Wednesdays.
Where to Turn in
To the plastic bins outside mike's office.
Examples
Abstract Example 1
Abstract Example 2
Last modified August 28, 1999 by mike@cs.hmc.edu