|
|
|
Assignment
5 |
CSCI-588: Specification
and Design of User Interface Software |
Fall 2004 |
| Due:
6.30 pm. PDT, October 19, 2004 |
| Your
team is required to submit two hardcopies of your project
status review (1 for the Professor, 1 for the T.A). The approximate
number of pages (slides) in presentation format for each
part is listed on "Project Status Reviews I and II Agenda
for October 19 and 26, 2004". When you generate the
slides, previous assignments will be the references and may
even be included, as needed. Remember to consider any homework
comments received from the Grader, T.A. or Professor. Those
comments will definitely help your team to improve your project.
To clarify, the content of your Assignment 1, Project Description,
is your Topic Explanation. |
| Address
any assumptions you make for building your system. Also,
refer to previous grading criteria (and your v, v-, or v+
grades) to ensure the other assignments were complete. For
User Analysis Discussion, a Data Flow Diagram of tasks being
performed by your system should be added this time. You only
have to list what you've done so far. |
| Completion
of the whole system is not required now. Use about 10 pages
for your screen prototypes. Please write some explanation
for the screen designs and navigation. Sequence your slides
following sample path(s) through your system. Try to create
an example of how the system would work when the user is
interacting with the system. Write comments, issues, complaints,
assumptions, tool(s) used, lessons learned and plans for
the rest of the semester. |
| It is
expected that you will be copying or repeating portions of
your previously completed homework. The reason for the homework
is an incremental development of your class project and to
solicit/obtain feedback as an iterative development. |
| You
must include one cover page in the hard copies. You have
to list your team number, team member names, and your team
location (write "Campus" or off-site location). |
| Plan
for a 10-minute presentation, showing the background information
briefly, but emphasizing the screens designed and the comments/issues
lessons learned chart. |
V+ Followed
outline explicitly, addressing each item. It is taken into
account who presents on 10/19/04 vs. 10/26/04 in terms of
preparation time allowed. Entire team presents project, each
doing a portion. Team addresses screen designs factoring
in issues and guidelines discussed in class. Teams illustrate
corrections of design and decision made based on feedback
of doing homework, class discussion, team discussion, etc.
Written explanations of screen designs and navigation included
in hardcopy handed in, not just screen dumps. Team presentations
were rehearsed so that they are conducted smoothly in class.
V Interim capability demonstrated, but, there is a lot of
more work to do. Team only follows general topic areas on
outline, but does not address everything requested. Only
1 person of 2 or 3 person team presents team project.
V- Team presents screens drawn using drawing tools in PowerPoint
or handwritten (low fidelity prototype), with only a small
subset of the eventual design. Any sections missing from
the outline will result in a V-, so, double check that each
item is addressed. Lack of team cooperation is apparent.
No presentation of material as scheduled (i.e. just the hardcopy
was handed in, but the presenters were absent). Did not follow
outline in "Project Status Reviews I and II" handout. |
|
