Saturday, October 31, 2009

Weekly Status Report 10/25 - 10/31

Task/Features Completed:

Usability Testing

Prep: Cleanup Test Plan Errors [Jason] 1 hour

Meeting 1 [Jason, Kevin, Jeff] 4.5 hours total

· Date: Tuesday

· Time: 12pm – 1:30pm

Meeting 2 [Kevin, Jason, Jeff] 3 hours total

· Date: Thursday

· Time: 12pm - 1pm

Meeting 3 [Robert, Jeff, Zach] 3 hours total

· Date: Friday

· Time: 12pm - 1pm

Quality Assurance Iteration R2

· Status Message does not appear on program startup [Kevin] 0.25 hours

· Staff note and finger remain highlighted when incorrect key is selected [Jason] 0.25 hours

· JSlider labels are not shown [Robert] 0.25 hours

· Spelling error on keyboard test label [Kevin] 0.1 hours

· Load Song Dialog needs to highlight song immediately on import [Jeff] 0.25 hours

Focus for next week:

Quality Assurance Iteration R2

· End of quiz and test does not return to freeplay mode correctly [Zach] 0.25 – 0.5 hours

· Basic Piano Quiz acts differently via keyboard then clicking keyboard [Jeff] 0.25 – 0.5 hours

· Mode identification cleanup [Kevin] 0.25 – 0.5 hours

· Text feedback for user errors cleanup [Robert] 0.25 – 0.5 hours

· On creation, current part of beginner tutorial is not shown [Kevin] 0.1 – 0.2 hours

Data Analysis

· Take all data collected during usability tests and create graphs of the data [Robert] 1 – 2 hours

Planned team meeting [All] 5 hours total

· Project Status Check

· Discuss presentation plans for final presentation

Issues/Challenges this week:

None

Saturday, October 24, 2009

Weekly Status Report 10/18 - 10/24

Task/Features Completed:

Test Plan Deliverables

  • Data Collection Methodology [Jason] 0.5 hours
  • Document Integration [Jason] 4 hours
  • Logistics [Zach] 0.2 hours
  • Schedule [Robert] 1 hour
  • Target Audience [Zach] 1 hour
  • Usability Evaluation Goals [Kevin] 2 hours
  • Concerns [Kevin] 0.5 hours
  • Pre-Test Survey [Jeff] 1 hour
  • Post-Test Survey [Jeff] 1 hour
  • Task Cards (6 HTAs) and Consent Form [Robert] 0.5 hours

Development Iteration 1

  • Model Stubs [Jason] 1.5 hours
  • Controller Stubs [Jason] 1.5 hours
  • Staff UI [Zach] 4 hours
  • Keyboard UI [Robert] 4 hours
  • Hand-Positioning UI [Kevin] 4 hours
  • Main Screen UI [Jeff] 3 hours
  • Demo Toolbar UI [Jeff] 1 hour
  • Keyboard Setup UI [Jeff] 2 hours
  • Chords Tutorial UI [Jason] 2 hours
  • Beginner Tutorial UI [Jason] 3.5 hours

Development Iteration 2

  • NoteCollection Implementation [Jason] 1 hour
  • Note Implementation [Jason] 0.5 hours
  • Modes Implementation [Jason] 1 hour
  • Control Command Implementation [Jason] 1 hour
  • MainScreenUI Integration [Jason, Zach, Jeff] 9 hours
  • DemoToolbarUI Integration [Jason, Jeff, Zach, Robert] 4 hours
  • Staff Integration [Zach, Jason] 8 hours
  • Keyboard Integration [Jason, Robert] 10 hours
  • Hand-Positioning Integration [Jason] 1.5 hours
  • KeyboardSetupUI Integration [Jason, Jeff] 6 hours
  • BeginnerTutorialUI Integration [Jason, Jeff] 8 hours
  • Update Handling for Keyboard [Jason, Robert, Zach] 9 hours
  • Update Handling for Staff [Jason, Robert, Zach] 9 hours
  • Update Handling for Hand-Positioning [Jason] 0.5 hours
  • DemoThread Implementation [Jason] 1.5 hours
  • SongLoader Implementation [Jason, Jeff] 2 hours

Quality Assurance Iteration

· Add text to clarify timing bar in demo toolbar [Robert] 0.5 hours

· Add status messages on main screen [Robert, Zach] 1.5 hours

· Make mode differentiation more obvious [Zach, Jeff] 1 hour

· Add keyboard red highlighting for notes not shown in freeplay mode [Robert, Jason] 1 hour

· Refactor Keyboard UI into octave panels [Jason] 2 hours

Focus for next week:

Usability Testing

Prep: Cleanup Test Plan Errors [Jason] 1 hour

Meeting 1 [Jason, Kevin, Jeff] 6 hours total

· Date: Tuesday

· Time: 12pm - 2pm

Meeting 2 [Kevin, Jason, Zach] 6 hours total

· Date: Thursday

· Time: 10am - 12pm

Meeting 3 [Robert, Jeff, Zach] 6 hours total

· Date: Friday

· Time: 11am - 1pm

Issues/Challenges this week:

Chords HTA was incomplete: Did not get to completing it because we wanted to aim for decent quality with 5 HTAs over bad quality with 6 HTAs.

Workload Overload: Team took on way too much this week due to a late start on implementation.

System Re-design lead to project delays: Team had to redesign parts of the system since the original design was either hard to use or did not support a certain feature.

Friday, October 16, 2009

Meeting Minutes 10/11 - 10/17

Task/Features Completed:

Plan Project Implementation [0.5 hours per person = 2.5 hours total]
  • Planned and assigned test plan deliverables
  • Planned and assigned development iteration 1 deliverables
Learning Python: Jeff and Zach [6 hours total]

Focus for next week:

Test Plan Deliverables
  • Data Collection Methodology [Jason] 0.75 - 1.25 hours
  • Document Integration [Jason] 3 - 4 hours
  • Logistics [Zach] 0.1 - 0.2 hours
  • Schedule [Robert] 1.5 - 2.5 hours
  • Target Audience [Zach] 1 - 1.5 hours
  • Usability Evaluation Goals [Kevin] 1.5 - 2.5 hours
  • Concerns [Kevin] 0.5 - 1 hours
  • Pre-Test Survey [Jeff] 1 - 2 hours
  • Post-Test Survey [Jeff] 1 - 2 hours
  • Task Cards (6 HTAs) and Consent Form [Robert] 1 - 1.5 hours
Development Iteration 1
  • Model Stubs [Jason] 0.5 - 0.75 hours
  • Controller Stubs [Jason] 0.5 - 0.75 hours
  • Staff UI [Zach] 4 - 6 hours
  • Keyboard UI [Robert] 4 - 6 hours
  • Hand-Positioning UI [Kevin] 3 - 5 hours
  • Main Screen UI [Jeff] 1 - 1.5 hours
  • Demo Toolbar UI [Jeff] 2 - 2.5 hours
  • Keyboard Setup UI [Kevin] 2 - 4 hours
  • Chords Tutorial UI [Robert] 2 - 4 hours
  • Beginner Tutorial UI [Jason] 3 - 5 hours
Issues/challenges for this week:

Large workload with other classes may lead to incomplete deliverables (or poor quality).

Image overlay with UI may lead to project deliverable delays.

Learning Python and wxPython may slow down development of project.

Friday, October 9, 2009

Weekly Status Report 10/4 - 10/10

Tasks/Features Completed:

Cognitive Walkthrough [1 hour per person = 5 hours total]
* Stepped 2 sample users through the following HTAs on our interfaces:
* Play a Demo
* Beginner Tutorial
* USB Keyboard Setup
* Chords Tutorial

In-class Team Meeting [1.25 hours per person = 1.25 hours total]

* Planned deliverables for each person outside of prototypes.
* Jason: System UML, 1/2 Component Descriptions
* Jeff: UI Design Section 2.1 with 4 HTAs
* Kevin: 1/2 Component Descriptions
* Robert: UI Standards and Library Choices
* Zach: UI Design Section 2.1 with 2 HTAs

Out of class Team Meeting [1 hour per person = 5 hours total]

* Reviewed prototypes and design document sections.
* Discussed barriers to completing document sections.

High-Fidelity Prototypes with Descriptions:

* Keyboard Screen [Robert] 0 hours: No modifications to interface was necessary
* Staff Screen [Zach] 0 hours: No modifications to interface was necessary
* Hand-Positioning Screen [Kevin] 0 hours: No modifications to interface was necessary
* Main Screen [Jeff] 1.5 hours
* Chords Tutorial [Zach] 0.75 hours
* Keyboard Setup [Robert] 1 hour
* Demo Screen [Jeff] 0.5 hours
* Beginner Tutorial [Jason] 1 hour

Design Document Written Sections:

* System UML [Jason] 1 hour
* Component Descriptions [Jason, Kevin] 3 hours
* UI Design Section 2.1 [Jeff, Zach] 3 hours
* UI Standards [Robert] 1 hour
* Technology Choices [Robert] 0.5 hours
* Document Integration [Jason] 5 hours

Focus for next week:

Plan Project Implementation [0.25 - 0.5 hours per person = 1.25 - 2.5 hours total]
* Details TBA until feedback is given on completed design document

Issues/challenges for this week:

Workload Overload: Team is concerned about of work overload for assignments outside the project that may lead to delays on project deliverables (Studying for the test, Assignment 3).

UI Modes: Team is concerned that overuse of modes in UI made lead to Usability flaws in our interfaces.

Saturday, October 3, 2009

Weekly Status Report 9/27-10/3

Tasks/Features Completed:

Complete SRS Document by Sunday at Midnight:

  • Task Analysis [Kevin] 0.5 hours
  • Cleanup Graphical HTAs [Kevin] 0.5 hours
  • Document Integration [Jason] 2 hours

High-Fidelity Prototypes:

  • Keyboard [Robert] 0.75 hours
  • Staff [Zach] 1 hour
  • Finger-Positioning [Kevin] 0.5 hours

Out-of-Class Team Meeting [Everyone] (1 hour per person = 5 hours total)

  • Analyzed Keyboard, Staff, and Finger-Positioning Prototypes
  • Stated that freeplay mode, beginner tutorial, play a demo, and USB keyboard setup would be the 4 HTAs supported in deliverable 2
  • Assigned high-fidelity prototype roles for deliverable 2

Focus for the next week:

Plan Design Document [0.25 - 0.5 hours per person = 1.25 - 2.5 hours total]

  • Details TBA until design document template is released

High-Fidelity Prototypes with support of four HTAs:

  • Keyboard Screen [Robert] 0.75 – 1 hours
  • Staff Screen [Zach] 1 - 1.25 hours
  • Hand-Positioning Screen [Kevin] 0.5 - 0.75 hours
  • Main Screen [Jeff] 1 - 1.5 hours
  • Chords Tutorial [Zach] 0.75 - 1 hours
  • Keyboard Setup [Robert] 1 - 1.25 hours
  • Demo Screen [Kevin] 1 - 1.5 hours
  • Beginner Tutorial [Jason] 1 - 1.5 hours

Issues/challenges for this week:

Confusion on Deliverable 2: Team is confused on project specification for “medium fidelity in breadth and depth.” We are unsure if this feature implies that implementation is required or if multiple images of GUI progression through a HTA is acceptable.

Friday, October 2, 2009

Meeting Minutes 10/2/2009

Prototypes Presented:





Deliverable 2 Features to be shown:
- Beginner Tutorial [Jeff, Jason]
- Freeplay Mode [Jeff, Zach, Robert, Kevin]
- Play a Demo [Jeff, Kevin, Zach, Robert]
- USB Keyboard Setup [Jeff, Robert]

Note: Features list multiple people because they affect ownership on main interfaces stated below.

Deliverable UI Mockups Required:
- Keyboard Screen [Robert]
- Staff Screen [Zach]
- Hand-Positioning Screen [Kevin]
- Main Screen [Jeff]
- Chords Tutorial [Zach]
- Keyboard Setup [Robert]
- Demo Screen [Kevin]
- Beginner Tutorial [Jason]

Note: Since Jeff and I have a lighter load for the user interface requirements, we will take a larger load of work for the design document.