Project 4d : Submission

Due Saturday at 5:00 PM MST

There are four steps to completing Project 4. We are on step 'D'

  1. Working Prototype
  2. Code Complete
  3. Visual Freeze
  4. Submission

The final stage of the project is to tidy up any last-minute changes and turn in the project.

Fixing Bugs

Before the product reaches the customer, all the quirks and glitches have been worked out. Make sure to give yourself a couple days to do this. You might want to let a roomate or friend play with your project for a few minutes to teese out a few bugs.

Submission

Your assignment is simply to implement the design presented in your spec. However, it is understood that the design will change during the implementation phase due to the realities of the technology and other engineering constraints. Therefore, the spec itself will change. Please include:

  1. An updated copy of the spec. There needs to be some feature in the spec allowing the reader to know what changed since the last time he read it.
  2. The working product. Upload to I-Learn an executable, installer, link to a web site, or whatever else is necessary for someone to evaluate your project.

To turn in project 4, please create a new post in the "Project Submission" discusson board. This post will have at least two components: your updated spec and your project. Since we cannot add attachments to I-Learn, you will need to host it somewhere (such as an Office 365 document or a Google Document) and provide a link. Make sure everyone has permissions to access this file and make sure the document has your name on it.

Grading

  Exceptional
100%
Good
90%
Acceptable
70%
Developing
50%
Missing
0%
Fully Implemented
20%
Every control works as the user expects All the features in the spec are implemented One feature does not work as the user expects or as the spec describes One feature described in the spec is missing More than one feature is missing
No Defects
20%
No bugs can be found One or more minor bugs exist that the average user would probably not find One obvious defect A bug exists that severely impacts a common user scenario There are many glaring bugs
Application of Standards
20%
There is no room for improvement in the use of color, typography, and layout as well as applicable web, mobile, or desktop standards The design follows all relevant layout, color, and typography guidelines One aspect of the design does not adhere to the standards One obvious or gross violation of a standard seriously degrading the overall quality of the design No knowledge of applicable standards is demonstrated in the product
Overall Impact
40%
Stunning The target user is likely to be “pleased” with the design and all their needs will be met One aspect of the design distracts from the overall visual impact The quality of the visuals presents usability issues The design is difficult to look at

In addition to the above criteria, a penalty of 10% will be added for a missing updated spec.