This part of your documentation defines the project,
the user requirements, and the respective evaluation criteria.
Keep in mind that this document must be short and concise,
not a long treatment full of arcane details and lengthy deliberations
on marginal issues. Each of the sections below should not be
longer than two or three paragraphs. You may use diagrams
or pictures to illustrate important aspects of your system.
<------------------- cut here ------------------>
COMP 675 Winter 2000: [Project Name[: Part 1 -- Requirements
COMP 675 Winter 2000: [Project Name]: Part 1 -- Requirements
Development Team
Team name
email link
Member name
email link
Member name
email link
Member name
email link
Member name
email link
Project Overview
In one or two paragraphs, describe your chosen application.
Point out why it is interesting, identify the task it is
supposed to support, list some advantages over existing
systems, and describe the target users.
Existing Systems
The goal of your project is to devise a system that helps
the user perform your chosen task more easily than existing
systems. Give a brief descriptions of existing systems
(not necessarily computer-based), point out why they
are attractive to users, and identify weaknesses
which your system can overcome. Restrict yourself to
two or three examples, and three to five criteria.
User Requirements
Identify three to five critical aspects of your system from a user's
perspective. If possible, ask potential users what they
would consider important in such a system; otherwise,
put yourself in the user's shoes. Be careful not to
get into technology euphoria, assuming that the latest
hot technology will be automatically desirable for the user.
Evaluation Criteria
Define three to five criteria against which you want your
system to be evaluated. For this class, concentrate on
user interface design and usability aspects, especially
considering that most likely your prototype will not
be a fully functional product. It is important that
all your criteria are measurable or observable;
"easy to use" is certainly not sufficient.
You may use criteria which in principle are measurable,
but within the constraints of this term project may
not be practical. Use the textbooks, e.g. [Dix et al., Chapter 4]
for suggestions on such criteria.
Team email
Last modified: [modification date & time]
<------------------- cut here ------------------>
Franz Kurfess
Last modified: Tue Jan 4 20:07:29 EST 2000
