Read one of the stories referenced in the three recent issues of ACM TechNews mentioned above, or any more-recent issue. Pick a story that nobody else in your section is covering; coordinate with your T.A. to make sure you are avoiding duplicates. Write a brief review of the story. Your review should cover the main idea and give your reaction to it, focusing on possible applications. In your review, when possible refer to related work, which you discovered using Google Scholar or one of the other references mentioned above. A suggested length is 300 to 1200 words per topic. Tables, graphs, and images are welcome; the key point is to summarize the meat of the topic for a computer science expert who may not know this particular topic in detail.
For each citation in your review, please submit a working link to a freely-readable copy if available, and also submit a working link to a URL based on Digital Object Identifiers (DOIs) if available, as shown in How to find a DOI and create permanent links to online articles. Here is an example using Vancouver system format (although you need not use this style, you should be consistent about your citation style):
The citation's title hyperlinks to a freely-readable resource <http://faculty.washington.edu/ajko/papers/Ko2011EndUserSoftwareEngineering.pdf>. Unfortunately, these versions are often ephemeral or are preliminary versions, so it's better to also include a DOI to the final, stable version even if it's not freely readable. The DOI reference in the above citation hyperlinks to <http://dx.doi.org/10.1145/1922649.1922658>. If your report uses an active format such as PDF or HTML, URLs should be clickable.
Prepare a brief presentation of your review, and present it to the rest of the class. Coordinate with your T.A. about scheduling your presentation.
Submit the following files.
It may also help to submit the original versions of your work (e.g., review.odt) in case there are problems with the PDF versions.