Purpose
- To choose an application or problem for which you will design
a user interface.
- To get even more writing practice; this time writing a
project request memo for your "boss."
What To Do 1. Think of some possible projects. The project should be defined in terms of a problem to be solved,
not in terms of a solution or technology. Usually this will
mean saying that you want to enable some specified user population
to better carry out some specified task or activity. (See further
discussion of this point under 3 below.) For ideas: think about the CHI videos we watched, and look at examples
of prior projects I will provide. You are encouraged to discuss your ideas in disCourse, with me
via email, or in office hours to get early feedback on viability.
Students sometimes worry about whether they can "finish"
(by which they mean implement) the project in one short semester.
You will not be required to program a finished software product.
You will only be required to complete enough of a prototype
that basic usability testing can be done on a portion of the
interface design and interactive functionality. The prototype
could be implemented in any interactive technology (e.g., flash,
web pages, or traditional programming language).
Don't get too
ambitious with programming. It always takes longer than you
think, and will detract you from the point of this course.
2. Propose projects to others and form groups.
I recommend (but do not require) that you do projects in groups
of 2-3 people.
Contact class members you know, or use the Assignment 4 discussion
of disCourse to "advertise" your project idea and
seek collaborators.
Try to match complementary skills, e.g., a technical person,
a designer, and a "people person" -- but make sure everyone commits
to being involved in all aspects of the project to some extent!
I will request confidential peer-evaluations of participation
effort at the end of the semester.
3. Write a memo to your "boss" Write a one-page description of the project, written as a
memo to your boss requesting permission to undertake the project.
Focus on what problem is to be solved, for whom and
why: who are the users, what is their task or activity to
be supported, and what improvement will the software make? Do
not talk about the "how" -- do not tell me what
the software will look like, what tools you might use to program
it, or other aspects of the implementation. This would be premature
because we are only at the phase of defining the project requirements
and have yet to go through the process of designing it.
Also mention in the memo that you will be following a user-centered
methodology, and say why. (See my first lecture, or read ahead
in Chapter 9.)
The memo should indicate who else is on the project team,
so that I can form groups in disCourse. Please also give the project
a brief name that we can use for the group.
Every member of the proposed project groups must write and submit
their own request memo. This is because I want to know that
you have each agreed to be on the project, and I want you each to
have practice writing. (Needless to say, this will be graded in
part on your writing quality.)
Post the memo on your web site and submit the URL as your submission
to Assignment4 in disCourse.
Some Ideas Here are some ideas in general ...
- A collaborative application for cell phones or PDAs (small displays
on portable devices).
- Attaching annotations to arbitrary objects in the world, so
you can have discussions with others interested in those objects.
- Web interface for a large shared repository of digital images.
(Some already exists, but I can give you requirements for something
different.)
- Work managment system for a moderately sized software project
(e.g., several students). Be able to post work required on the
software, including development of functionality, testing, bug
reports. Web accessible.
- Improved web-based online discussion tools, for synchronous
or asynchronous discussion,
Here are some ideas from ICS 463 a few years ago. (Unfortunately
most projects from that class are no longer on the web.) Can you
improve on them?
- A program for practicing Japanese
- An interactive kiosk-based directory/map for the ICS department.
- Improved displays and controls for your automobile.
Here are some projects from my ICS 667, a graduate level course
that focused entirely on design, comparing two different approaches.
(Your projects don't need to be as extensive.)
Pau |