Assignments

Date Due Date Assigned Assignment Description
9.12 now extended to 9.14 9.5 1. Complete a 1500 word analysis.
Pick one software application to examine. Write an analysis of the product using your readings from this week and the next. Consider the questions: Is the software polite? How is the information designed (or is it a question of process rather than design)? Rather than just detailing what you did or didn't like, spend time describing the effective or ineffective design and offer solutions to fix it. Include at least two screenshots to bolster your claims. Your writing skills will also be assessed, so compose carefully.

Submit this to the teacher folder prior to class on 9/12. Please submit in either MS Word or HTML format.
9.16/9.19 9.12 2. Summarize your analysis from assignment # 1 in two paragraphs or less. Complete summary and send to class mailing list by 11 pm on 9.16.01.
In addition, mail at least one message to the class list explaining whether you agree or disagree with another's assessment. Complete this by 6 pm on 9.19.01.
9.26 9.19 3. Complete analysis of Journyx download pages and come up with a business idea.

Finish the analysis and heuristic review begun in class. Compose analysis of web download experience. List the following:

  1. The primary goals of the company (what are they trying to do?)
  2. The nature of their audience (who is their target?)
  3. Compare their product download experience to at least 2 other companies with similar products (easier? harder? how?)
This should be at least 500 words and include at least one screenshot illustrating your points.

Read through the tutorial, come up with a possible business idea and be prepared to come up with a business plan in class in a small group.

10.3 9.26 4. Revise your first assignment.
Submit this with "_revised" added to the name to the teacher folder prior to class on 10.3. Please submit in either MS Word or HTML format.
10.14 (midnight) 10.10 5. Complete first piece of analysis. This is due by Sunday, so I can post relevant material (and web pages) to the site.

Group tasks for 10.10:

  1. Do a GOMS calculation (using Raskin's model) for a) Logging into TimeSheet and b) Logging out (once inside the product).
  2. Create an HTML page that contains your group information. If you do not have someone in your group who can author HTML, let me know.
  3. Observe your Admin person (have them use the Thinking Aloud Protocol, where "you ask the participant to vocalize his or her thoughts, feelings, and opinions while interacting with the product") create the group to represent your company and edit your individual roles. Log this data. Have a member of the group take notes on the Admin experience. The Admin is also required to create his or her own log.
  4. Create one task scenario for your role. This document should include your user persona. We will use this for next week's activity (Where you walk through the scenario "in character" in the Timesheet application and keep a log of your activities).
  5. Each person evaluate the satisfaction survey. Email your comments to me (I will review your suggestions and post one form everyone will use so we can collect consistent data). I'm only looking for a couple of sentences here.
  6. You may email me your materials but you must put a copy into your group project folder by next class. Make sure to put your name on forms that are individually completed.
10.31 Midterm Midterm group assignment

Your group can create one page or a small site.

All groups will be required to publish pages that contain the following:

  1. Header information (course, group members, assigned tasks)
  2. Description of the fictional company
  3. Summation of initial download process on the Journyx Site
  4. Summary of admin experience
  5. User persona descriptions
  6. Listing of task scenarios for each persona
  7. Results of scenario testing
  8. Results of surveys
  9. Formal documentation of results and recommendations for Journyx (with a minimum of 5 screenshots), this may include appendix information, such as your GOMS analysis

Each member of the group will be asked to assess their work as well as the contributions of the other members. Formal presentations will take place on 10.31.01.
12.5 Final Final exam assignment

Redesign an Existing GUI or Design Your Own GUI

You may either work in groups (of no more than 3) or individually. All individuals will be required to deliver the following items and a working prototype GUI. Groups will also be required to deliver the following, presented in one package. The only additional requirement for group work will be an evaluation of the members.

  1. If you are redesigning a UI, you must provide explanatory material and screenshots of the current design
  2. Address goals of UI
    • The primary goals of the product (what are you trying to do?)
    • The nature of your audience (who is your target?)
    • Potential implementation issues (how will you reach them?)
  3. Formal description of users/participants
    • User personas
  4. Storyboards
    • Digitized images of your storyboards inserted into the document
  5. High level design document
    • Abstracted model of either the flow or interaction design
  6. Formal requirements
    • Goals
    • Description of product
    • Platform
    • Software
    • Language
    • Type of interaction
    • Feature List
  7. Walkthrough results
  8. Place the following data in a subfolder called "LASTNAME_final" in your student directory: Formal documentation of the process and a working prototype in either a Flash, HTML or Director format. Other formats subject to approval. A soft copy (preferably in MS Word) and hard copy of your formal documentation must be turned in at the time of presentation. A separate soft copy of your prototype must be turned in at the same time.

Formal presentations will take place on 12.5.01.

Policy Statement | Syllabus | Student Projects | Assignments | Home