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 ------------------>
CSC 481 Winter 2002: [Project Name]: Documentation Part 1
CSC 481 Winter 2002: [Project Name]: Documentation Part 1
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.
If your system is completely novel, describe why
you believe it is appealing to potential users,
and why the needs of those users are not addressed
by current systems.
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.
