[Syllabus] [Schedule] [Homework] [Projects] [Resources] [Directory]
The following assignments are to be completed individually and posted to your individual course web page by the start of class on the week due.
Individual Homework
#1 – Project Brainstorming (due NEXT CLASS 9/12, NOT GRADED)
Administrative
Remdedial Java If you’re new to Java you should start working your way through the Sun Java tutorial Trails Covering the Basics. You should have a good grasp on this material by the 9/25 class.
Assignment Pick three different project ideas that you would be interested in working on, make a rough sketch of a user interface (a scanned or photographed sketch on paper is best) and write a 1 paragraph proposal for each, further fleshing out the idea. Post your write-ups and sketches on a web page in your order of preference (these will be used to help form project teams). For ideas, review recent years' CHI proceedings.
|
|
Individual Homework
#2 – UI Critique (due in 1 week, 9/19)
Find 2 examples of
good user interface design, and 2 examples of bad user interface design.
Your examples should be specific. It's very hard to find
a large interface that's completely good or completely bad, so don't try. Instead,
focus on a particular feature or aspect of a user interface that makes your
case. Avoid fuzzy words like “intuitive” and “user-friendly”. Find concrete
reasons for your judgment.
You aren't limited to desktop software. Web sites offer many great candidates for fame and shame. You aren't even limited to traditional computer interfaces. Feel free to go out into the real world, and consider consumer appliances, car dashboards, building entrances, traffic intersections, shower controls, etc. What to Post Your report should include 2 good examples and 2 bad examples.
For each example:
· describe the
purpose of the overall interface
· describe the particular aspect you find good or bad · explain why it's
good or bad
· if bad, speculate
why it might have been designed that way, and suggest a better design if
possible
· illustrate with
screenshots or photographs
|
|
I3 |
Individual Homework
#3 – Ethnography (due in 1.5 weeks, 9/28)
Northeastern has just hired you to make the student center more efficient and friendly. Pick a location and spend an hour people watching with a notebook and pencil. Spend some time watching the kinds of activities that people are engaged in, and think about how technology could help improve these activities. Pick one such activity to focus on and study. For your chosen activity watch several people perform the task and make detailed notes about the series of steps they go through, any objects (“artifacts”) they use, whether they interact with other people and, if so, the step-by-step details of this interaction. Conduct two or three unstructured interviews with your subjects. Some examples of activities (you can study one of these or, better yet, come up with your own):
What to Post Your report should include a one-paragraph summary of why you picked your particular activity to focus on, followed by an overview of the activity, the kinds of people you observed engaging in it, and a description of any artifacts they used. Describe the individuals you interviewed (not by name) and what you learned from the interviews. Following this, provide a detailed description of the activity and any variations you observed. Review the two papers assigned this class for examples of how to write your report. You can include sketches or photographs. Total report length should be 2-3 pages. |
I4 |
Individual Homework
#4 – SWING 1 – Rapid Prototyping in NetBeans (due in 1 week, 10/5)
Your mission in this exercise is to implement a Java application to provide online ordering for your favorite restaurant. The interface need not be functional, but the controls should be laid out on the page in such a way that it could actually work if completely implemented. Minimum requirements. Your interface need not implement the entire menu, but must contain at least the following:
here are step-by-step instructions (if you really, really don't want to use NetBeans, talk to the instructor) What to post: email a screen shot of your app running, along with a zip archive of your netbeans project directory, to is4300f16@ccs.neu.edu. |
I5 |
Individual Homework
#5 – SWING 2 – Event Handling (due in 1 week) Your mission in this exercise is to implement a very simple Java painting application. The JFrame app must support the following functions:
You should read through the Java Swing Tutorial on Writing Event Listeners first. For help on specific Swing components see How to… Some other tips to get you started:
Graphics
G=getGraphics(); G.setColor(Color.BLUE); G.drawRect(10,100,1,1);
public
void actionPerformed(ActionEvent e) { JComboBox cb=(JComboBox)e.getSource(); String
itemName=(String)cb.getSelectedItem(); … } What to post zip your netbeans project and email it to is4300f16@ccs.neu.edu.
|
I6 |
Individual Homework
#6 – SWING 3 – Constraint-Based Layout (1.5 weeks, due )
Your objective in this assignment is to get some experience with Frames, Dialogs and layout managers in Swing. Your mission is to create your own (ideally project-related) application with the following minimum requirements:
NOTE: You may not
use GridBagLayout, Free Design, Box, Overlay, Null or Absolute Layout anywhere in the project.
What to post Zip and email your netbeans project folder to is4300f16@ccs.neu.edu.
|
Individual Homework
#7 -Heuristic Evaluation (due in 1 week, 11/20)
In this individual assignment, you will do heuristic evaluation on three computer prototypes developed by your classmates.
The three interfaces you will be evaluating will be assigned in class. For each, go to the project team's webpage and review the P6 report for each project, which will give you instructions for running the prototype and background information about the project. This is not an anonymous evaluation, so feel free to contact a project group directly if you need more information than you were given. As soon as you receive your prototype assignments, try to download and run all prototypes. You don't have to do your heuristic evaluation right away, but poke around a bit and make sure the prototypes appear to work. We need to get logistical problems out of the way as early as possible, since everybody else is going to be working on heuristic evaluations too.
Follow the heuristic evaluation procedure to evaluate all interfaces carefully. Make a numbered list of usability problems and successes you find. For each problem or positive comment, you should:
You aren't required to recommend solutions for the problems, but any ideas you have would no doubt be appreciated.
Be thorough. You should have at least 12 useful comments (positive or negative) about each interface that you evaluate. Write your reports in a readable style. The usability of your report to its recipients will matter in your grade. Where possible, include screenshots to illustrate the problems you found. In general, make your report easy to read and understand.
What to Post You
should post three reports, one for each interface you evaluated, on
separate web pages. Email each relevant URL to the appropriate team
members, and also add them to your personal course webpage.
|