1. Pair Programming Assistant
Jeramy Zapotosky . Grace Uchida . Masis Nguyen . Sarah Lee . Michael Hart

2. Our Prototype Link: http://www.doanthangthien.org/inf132/
Student System:

3. Since last presentation...
Cognitive Walkthrough
Refined prototype based on CW
Usability studies 
Professor Jacobson
Professor Kay
Professor Thornton
Finalized prototype based on usability studies
Working on final report

4. Cognitive Walkthrough Refine Prototype Usability Testing
Project Progress
Create Prototype
Interviews
Cognitive Walkthrough   Refine Prototype Usability Testing
Refine Prototype
Final Report

5. Cognitive Walkthrough
Each member individually conducted a cognitive walk-through based on our previous list of tasks.
Each member noted problems he/she ran into and other HCI issues.
Met as a group and decided on appropriate changes to make prior to usability studies.
Refined the prototype based on the cognitive walk-through. 

6. Professor view
Student pairing should be changed so professors don't have to manually type in name. (More on this later!)
Migrated class settings from its own page to main page.
Page is reloaded and automatically scrolled to class settings when a Professor adds a new class.  
Project setup changed to a drop down menu for pairing deadline dates and automatic notifications rather than having several calendars.
Setup evaluation added to the settings window.
Back links passing proper information to previous pages to allow for easier web site navigation.
 Changed Manage to Projects. (Manage and settings were too similar.) Image

7. Professor view
Modified global navigation bar to have only "Home", "Help" and "Logout".  Initially we had place holders for other items we might want to add but this became confusing during usability testing.
Added warning messages throughout site to help correct input and navigation errors.

8. Evaluation Creation/ Submission Problems
Consistency - center and color all pages.
Evaluation Creator
Remove apply changes.  Just save and refresh.
Decided not to -> evaluate after US.
 Make title:"Evaluation Preview"
 Student View
Typing text should take away "evaluation saved."
 When student added -> "Request Pending."
Remove partner settings only allow adding of a single partner or solo.

9. Usability Studies Conducted in the professor's offices 15-20 minutes
5 tasks w/ different scenarios
Screen capture software to record the scenarios
Post-testing questions

10. Testing Problems Schedule conflict with Professor Pattis
Database reset during testing with Jacobson.
PC had performance issues during testing with Kay

11. Professor Jacobson Overview
 Couldn't find where to disable individual work
Went to Project Settings instead
 Evaluation setup link was hard to find. 
Looks like the page ends
Manual pairing 
ABC order
Double click
Would use this program is available

12. Professor Kay
Overview:
Spacing for add projects
Text box

13. Professor Thornton Overview:
Placeholders were confusing -> disregard for entire bar
No back button on Eval Creator page.
Integrate all features into one main area.
Windowing vs. Hide/Expand
There were many issues that were the same in both tests.

14. Student View
Selecting and pairing students did not act the way desired.

15. Apply Changes
Users all believed that apply changes meant that it saved the survey.

16. Calendars for Project Setup

17. Statistics Change "Project Info" button to "Statistics"
Although no professor actually had trouble finding it, Thornton said it was by process of elimination.

18. Changes Made Two ideas as solution to calendar problem. Idea 1 Idea 2
Changed 'Apply Changes' to 'Preview Changes'
Spaced the Add Project section. (Added two lines)
 Change the student view for pairing.
Double Click
Click and Drag
Multiple Select - implemented
Buttons
Remove all the placeholders.

19. Student Usability Testing
To be completed today with 4 ICS students (6pm ICS labs)
-Testing the student view of the system.
-Issues include:
How to deal with different pairing options (applying for solo work, 1 partner, 3 person group exception).
Evaluating 2 partners.

20. For Version 2.0
Use Javascript in order to allow a more fluid and client based user experience.  With C-Sharp, pages must be re-posted in order for changes to occur.  For example, selecting a date on a calendar requires a refresh for it to reflect the selected date and then another refresh to commit changes.
Develop more dynamic statistics.
Test two different versions of Project settings.
Find out feasibility of integration into checkmate or EEE.
Possibly develop a TA view.

21. Final Timeline
, Grace
, Jeramy