Project phase II: Prototype Implementation (due July 16)
In this phase of the project you are asked to implement a high-fidelity
prototype
based on the designs of the previous phase.
for your assigned project for this phase. Your design needs to be based
on information collected during the requirements
gathering phase.
MAKE SURE YOU MAKE
THE CONNECTIONS BETWEEN
YOUR PROTOTYPE AND
THE DESIGN DOCUMENTS EXPLICIT & CLEAR.
Based on your votes there was no clear winner therefore you are allowed
to use and possibly mix design elements from all the design documents.
Make sure you indicate in your report the design documents you used
and how you used them.
You are not allowed to make your own design decisions unless you
document
thoroughly why you had to.
Your prototype should follow closely the design specifications. Any
deviations
must be well documented.
The main goal of the prototype is to illustrate the main aspects of
interaction with
the system. You are free to use
any programming environment, language you want
as long as you can demonstrate the system on demofest day (July
16).
THE PROTOTYPE HAS TO BE A WORKING COMPUTER PROGRAM.
For your report you will need to describe the programming environment
you used, any choices you had to make and provide ALL the source code you wrote as
part of your report. In addition you need to prepare a separate sheet with an informed
consent form and 3-5 questions you would like to ask potential users of
your system. These forms will be used during the demofest day (July
16).
Deliverable (July 16)
Your prototype implementation report will be in the form of webpages in
html format. Of course your prototype has to be an actual computer
program.
You can submit the report by email to gtzan@cs.uvic.ca
as a tar.gz file anytime before midnight of July 16. You can also
provide me with a url as long as you can ensure that the url
will be valid for the duration of the course.
Use the description above as
a guide on how to structure your report. I am willing to review
outlines and preliminary version of your report. Use the design
principles and guidelines we have learned to present the information in
your report effectively.
This part of the project is worth 33% of the project grade
(i.e 10% of the total grade).