Assignment+6+-+FINAL+REPORT

FINAL REPORT division of work

MEET AT 9am THURS, JUNE 16 to prepare for our presentation ATTENTION: PLEASE! dress code: look professional - a little better than when you normally come to class in We are presenting like we are an actual company presenting to potential clients Thanks :)

Katrina - Methods - Recommendation - conclusion

Vania - Timeline -within Katrina's file for Future Work

Camille - Executive summary (from ass3) - Introduction - Requirements (from ass3) - Appendix

Kai & Calvin - Design --- Photoshop page has the final prototype and website - Results of testing

Vania (heuristic analysis) --Kai (heuristic analysis) --Calvin(heuristic evaluation) --Katrina (heuristic analysis)

--Group

What to do for heuristic analysis (for Calvin and Kai): the procedure for heuristic analysis is this: Have several evaluators (each member) use the nine heuristics to identify problems with the interface, analyzing either a prototype or a paper description of the design. Each evaluator should do the analysis alone. **Then combine the problems identified by the individual evaluators into a single list.**

Table: Nielsen and Molich's Nine Heuristics
 * **Simple and natural dialog ** - Simple means no irrelevant or rarely used information. Natural means an order that matches the task.
 * **Speak the user's language ** - Use words and concepts from the user's world. Don't use system-specific engineering terms.
 * **Minimize user memory load ** - Don't make the user remember things from one action to the next. Leave information on the screen until it's not needed.
 * **Be consistent ** - Users should be able to learn an action sequence in one part of the system and apply it again to get similar results in other places.
 * **Provide feedback ** - Let users know what effect their actions have on the system.
 * **Provide clearly marked exits ** - If users get into part of the system that doesn't interest them, they should always be able to get out quickly without damaging anything.
 * **Provide shortcuts ** - Shortcuts can help experienced users avoid lengthy dialogs and informational messages that they don't need.
 * **<span style="font-family: 'Times New Roman','serif'; font-size: 16px;">Good error messages **<span style="font-family: 'Times New Roman','serif'; font-size: 16px;"> - Good error messages let the user know what the problem is and how to correct it.
 * **<span style="font-family: 'Times New Roman','serif'; font-size: 16px;">Prevent errors **<span style="font-family: 'Times New Roman','serif'; font-size: 16px;"> - Whenever you write an error message you should also ask, can this error be avoided?

--- Camille will put it all together because she has all our personas/scenarios from ass4 (we have to provide her with our lo-fi prototypes again like ass4

ALSO, we have to print out the powerpoint slides to hand in with our final report

PLEASE EMAIL/POST ON WIKI YOUR WORK BY 12 MIDNIGHT TONIGHT SO CAMILLE CAN PUT IT ALL TOGETHER AND PRINT IT OUT.