Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

HCI and Swing Final Review Sheet for Summer 2005 Session 1, Exams of Computer Science

A review sheet for the final exam of the human-computer interaction (hci) and swing course during the summer 2005 session 1. It covers the material that has been taught since the midterm, including chapters 7-10 of shneiderman's book and swing topics such as memory management, threading, custom components, menus, toolbars, and actions.

Typology: Exams

Pre 2010

Uploaded on 08/18/2009

koofers-user-75y
koofers-user-75y 🇺🇸

10 documents

1 / 1

Toggle sidebar

Related documents


Partial preview of the text

Download HCI and Swing Final Review Sheet for Summer 2005 Session 1 and more Exams Computer Science in PDF only on Docsity! C M S I 6 9 8 / 5 9 8 I N T R O D U C T I O N T O H U M A N - C O M P U T E R I N T E R A C T I O N ( H C I ) Summer 2005 Session 1 Final Review Sheet The final is cumulative, and so this review sheet extends the previous sheet’s material. This is what we’ve covered since the midterm: • In-depth HCI material consists of Shneiderman chapter 7 — yes, amazingly, there has been only one full “theory” session since our midterm, and so we have managed to only cover this chapter. Of course, this is in addition to the previous in-depth material from the beginning of the summer session (and described in the Midterm Review Sheet). • Material from this evening’s smorgasbord is also fair game, but not in-depth (“fair game, but not in-depth” carries the same definition that it did in the midterm). This material covers Shneider- man Chapters 8–10. • For Swing, we have covered memory management, threading, custom components, and menus/toolbars/actions. As with the midterm, these are all fair game for the final (as well as all other prior Swing topics) — you will not be asked to do any extensive programming, but you may be asked to write out little fragments of code, critique some code, or outline/diagram a pro- gram. Questions will not test your knowledge of the API per se, but your knowledge of how to use it properly. You can think of the midterm as a set of sample questions; the tone and perspective of the final will be the same. I can tell you that since we will have more time allocated for the final, we won’t have an easy gimme question like the midterm’s #1, and I will feel more comfortable asking a question that takes more time to answer well, like the “create an OAI model” variety. Have fun!
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved