Review Your Design

After your walkthrough, you should meet with your client, instructors, and user experience experts (graduate students), and review the HU4628 students’ heuristic evaluations to gather feedback on your design. After meeting with your client, user experience experts, and instructors, you should list your design changes in a document.

Feedback from Client (Scientist)

As soon as you can schedule it, your team should meet with your client (scientist) to discuss the design changes suggested by the cognitive walkthrough. The purpose of the meeting is for the scientist to give you feedback on your design and to indicate any missing component or content.

Before the meeting, email the following documents to the scientist for their review:

• hand-drawn or software drawn sketches of your application design and navigational framework
• list of data that the app will store
• details of the instructional and other content for the app

You may explain the application to the scientist by reading your nominal use scenario, especially if the scientist did not attend the cognitive walkthrough.

During the meeting, tell the scientist about your team website. You should have them visit your team website during the meeting and tell them that you will post updates and more information on the website.

Record your meeting notes with the client (scientists) and post them on your team website.

Feedback from User Experience Experts (Graduate Students)

After you receive the heuristic evaluation from the graduate students , your team should meet with the graduate students who performed the heuristic evaluation of your app. The purpose of the meeting is for the graduate students to give you feedback on your design resulting from the heuristic evaluation. All members of your team should have read the heuristic evaluation before meeting with the graduate student. You should also have accessible during the meeting your paper prototype used for the cognitive walkthrough.

At least one member of your team should record notes during the meeting. The meeting notes should be posted on your team website immediately after the meeting.

Feedback from HU4628 Heuristic Evaluation

The HU4628 students will also conduct heuristic evaluations related to the app. This assignment is designated Project Assignment 3B. These results should be referenced in your team’s cognitive walkthrough and should be read and understood by the entire team.

At least one member of your team should record notes during the meeting. The meeting notes should be posted on your team website immediately after the meeting.

Feedback from Instructors

The week after your Cognitive Walkthrough, you will meet with your instructors. See Project Assignment 4 – Design Review assignment description for details about the meeting.

At least one member of your team should record notes during the meeting. The meeting notes should be posted on your team website immediately after the meeting.

Design Change Documents

You should decide if the design changes proposed by your client (scientist), user experience experts (graduate students), the HU4628 heuristic evaluations and instructors are appropriate. In addition you can derive your own additional design changes. The design changes you plan to implement should be organized and listed in a Design Change Document. For each design change you should give a reason or rationale for the design change, so you will know why you made the change. Like all documents that your team generates, the Design Change Document should be dated just below the title. Your team will generate several design change documents during the semester so they should be dated and numbered in the title of the document. Post them in order on your team website.

Post the Design Change Documents on your website as soon as they are generated.

Updated Burndown Chart

When you created your burndown chart at the beginning of the semester, you did not have enough information to specify the implementation tasks for your project. But now that I have defined the scope of your app during the design review, you should have a complete vision of the app and should be able to specify the implementation tasks in your burndown chart. 

You should refine your burndown table by adding implementation tasks in the “Product Backlog Inventory” below the “Project Assignment 6 – Implementation Requirements” task. Try to give a complete delineration of the tasks required to complete the implementation of your app and then give your best estimate for the effort of each tasks in the cells for week 7 by entering a negative number.  You probably want to correct the effort that you gave for “Project Assignment 6” task when you created the burndown chart. You can do this by entering the “initial estimated effort” in the week 7 cell for the “Project Assignment 6” task. The table will make clear the refinements that you made to update the burndown chart. Do not forget to post the updated graph on your team website, and to keep it updated.

CS4760 & HU4628 Students Collaborating

Recall that the HU4628 students are responsible for ensuring that the burndown chart is current and posted on the team website. Throughout the implementation of your app, the CS4760 students should inform the HU4628 students of their progress, so that they can update the burndown chart.

Submit on Canvas

After you have posted your Design Change Documents and updated your burndown chart on your team website, submit the URL to your design changes on canvas.