Reading Assignments: Summaries and Technical Assumptions, Papers of Computer Science

Download Reading Assignments: Summaries and Technical Assumptions and more Papers Computer Science in PDF only on Docsity!

What’s that all about?

 Some weeks you’ll be asked to read and write about

 (^) Applications, implementations, technical architectures, approaches, interaction techniques, etc.

 Deliverables

 (^) Due in class the week after a reading is assigned  (^) One page summary  (^) 10 point font, 1.5 line spacing, times new roman font family  (^) Name, and GTID please!

 You’ll receive them back, with a numeric score

 (^) 3 points excellent, 2 points average, 1 point needs improvement

Summaries

 The summary is an exercise in being an analytic reader

 (^) Analysis of what the article has said, and why that matters

 A “C” grade summary

 (^) Vague  (^) Some spotty coverage of a few of the points in the paper

 A “B” grade summary

 (^) Tends to follow the paper structure, without much else  (^) Covers more of the points  (^) But is not analytic

Successful Summaries

 An “A” Summary will

 (^) Begin with a statement about the paper’s overall objectives  (^) Do not repeat what the author has said  (^) Provides context for the contributions of the paper  (^) Identifies the significance of the paper  (^) Covers the majority of the major points in the paper in succinct specifics

Technical Assumptions

 An “A” Grade paragraph

 (^) Gets at the architecture/assumptions of the system and why it matters  (^) Does the system’s architecture make it more/less suitable for certain environments or situations?  (^) Are there “flaws” (or unconsidered assumptions) that constitute a weakness of the system?  (^) Integrates discussion from class and paper (and other papers) together  (^) Sometimes resulting in a question or finding conflicting viewpoints