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 Computer Systems, ACM Transactions on Programming Languages and Systems, ACM Operating Systems Review (SIGOPS), ACM Computer Architecture News (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. Also, there are good references in the course text books.

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 markup-based text formatter: LaTeX, troff, HTML, etc. (MS-Word, StarOffice, and similar WYSIWYG formatters do not qualify.) 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, Section XX
Name:  John Doe
Abstract Due Date: 1/21/93
Date: 1/21/93
Article Title:  OS is fun
Author: A CS God
Journal Ref: SigOPS, 1/1/1, pg. 92-95, or a URL
Formatter: troff

Due

Due at 9:00PM on Wednesdays.

Where to Turn in

To the plastic bins outside Geoff's office.

Tips

Tips

Examples

Abstract Example 1
Abstract Example 2

Particular Abstracts

Abstract #1 Abstract #2
Abstract #3 Abstract #4
Abstract #5 Abstract #6
Abstract #7 Abstract #8
Abstract #9 Abstract #10
Abstract #11 Abstract #12
Abstract #13 Abstract #14

Last modified January 21, 2002 by geoff@cs.hmc.edu