Project Phase 5 – CS 3724

Redesign and final report

Purpose: To redesign your system based on the results of the evaluation in phase 4, and to summarize your project in a final report.

Deadline: December 4, 11:59 PM

Your tasks:

In the last phase, you ended by developing a list of redesign recommendations based on the results of your formative evaluation. Your first task in this phase is to realize those design changes by modifying your prototypes. Update each of the prototypes you used in your evaluation to reflect the new state of your activity, information, and interaction design.

Although it is not required, you may elect to briefly re-evaluate your redesigned system using the updated prototypes. This would allow you to demonstrate that your changes had the desired effect on usability.

Finally, you need to write a final report for your project. Details are below.

Deliverables:

Your deliverable will be an extension to the set of web pages (HTML) you developed in the earlier phases. For this phase, your site must include, but is not limited to, the following:

• A main page for phase 5 of the project, with links to each of the pages described in the following bullets.
• A redesigned prototypes page, where you present your updated prototypes (sketches, screenshots, working demos, videos, etc.) and show how they were updated to match the redesign recommendations you developed.
• An evaluation page (if applicable), where you describe the re-evaluation of your system and discuss its results, if you chose to perform this step.
• A final report page, where you present a well-written, professional summary of your project. The idea of the report is that it is an executive summary of your entire project that can stand on its own, allowing the reader to understand the most important aspects of your project and its results. The text for this page should be written in complete sentences and paragraphs, and it should be designed to be read from top to bottom, just like a formal report. The page should include pictures, diagrams, and links to other pages on your website as necessary. The report should have at least the following sections (with suggested approximate length in parentheses):
1. Problem domain and root concept (2-4 paragraphs): summarize the problem your group was trying to address and discuss the root concept of your system.
2. Requirements analysis (2-4 paragraphs): summarize the methods you used to gather requirements, and present your most important findings.
3. User interface design (3-6 paragraphs): summarize the most important design choices you made for your system (activity, information, and interaction design).
4. Evaluation and redesign (4-6 paragraphs): summarize the methods you used to evaluate the usability of your system, present your most important findings, and describe the most important changes you made to the design as a result. Also discuss additional evaluation and prototyping you would like to do if given more time.
5. Reflection on the product (3-5 paragraphs): Reflect on the final system design produced in your project. How well do you think it addressed the original problems? How closely does it reflect your original root concept? How usable do you think your system would be in real-world use? How useful do you think your system would be in real-world use? Are there any major barriers to the adoption of the system you have designed?
6. Reflection on the process (3-5 paragraphs): Reflect on the scenario-based design process you used for your project. How closely do you think you followed the process; where did you deviate from the process? How useful did you find important elements like scenario writing and claims analysis? Would you use this process or a version of this process if you were given a system design or usability engineering task at your job? Why or why not? Do you think that the use of this process resulted in a better product as opposed to the use of an ad hoc process?

Post your website using VT filebox, or other web space you may have access to. By 11:59 PM on December 4, send the link to your HTML submission to the TA.