Project phase II: Design



In this phase of the project you are asked to come up with a design
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 DESIGN AND THE REQUIREMENTS EXPLICIT & CLEAR.

Based on your votes, the winning requirement gathering documents for each
project are:  (even though the winners won clearly the majority vote, other
reports received votes and in general all of you and me agree that the
quality of the reports was excellent. Good job)

  1. Just what you ordered (1_04 of previous phase)
  2. Student organizer        (2_02 of previous phase)
In your design you need to follow the requirements set by these winning reports.
However you are free to expand your decision based on information from
other reports but this step is optional.

The main goal of the design report is to be SPECIFIC. Essentially your design should be as complete and specific as possible leaving very little interpretation or ambiguity for the programmer who is going to implement it (for example: The "Save As" command should be the third command of the File menu which is the leftmost menu and should have as keyboard shortcat ctrl-o rather than the interface should have a "Save As" command.

The design phase of the project requires creativity and therefore I don't want
to impose any rigid structure. Some suggestions of things you might want to address in your design are: 1) what data is required ? 2) what conceptual model(s) is your design based on ? 3) are you using any interface metaphors ? 4) what widgets are you planning to use 5) what are the details such as colors/fonts/screen layout/command names 6) how are the requirements from the previous phase realized in your design

Essentially, your design report should contain everything required to send
the description to a software company and have them implement it
without having to ask you questions or make their own design decisions (as much
as possible).

How you convey this information is up to you but I strongly suggest that in
addition to text you create low-fidelity prototype screenshots of how
you envision your design. Programs such as Adobe PhotoShop or Gimp
can help you with this task.

Deliverable (June 20)

Your design report will be in the form of webpages in
html format. You can submit them by email to gtzan@cs.uvic.ca
as a url (preferable if you can ensure it will be valid
for the duration of the course) or a tar.gz file anytime before
midnight of June 20.

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).
Your grade will be broken up as follows:
5 points for showing how your design supports the requirements/scenarios/etc from phase I
3 points for the specification
2 points for creativity, aesthetics, presentation