Weekly Status Report 9/20-9/26

Tasks/Features Completed:

SRS Document:

• System Summary [Jason] 0.5 hours
• User Classes [Zach] 2 hours
• Existing Competition [Jeff] 1.5 hours
• System Features [Jason] 2.5 hours
• Glossary [Jason] 0.25 hours
• HTA Cleanup [Zach] 0.25 hours
• Non-functional Requirements [Robert] 1 hour

In-class Team Meeting (0.5 hours per person = 2.5 hours total)

• Constructed horizontal, low-fidelity prototypes for the main screen, chords tutorial, beginner tutorial, keyboard setup, keyboard, staff, demo, and finger-positioning interfaces.

Planned Out-of-Class Team Meeting (0.75 hours per person = 3.75 hours total)

• Reviewed System Summary, User Classes, and System Features in the SRS document.
• Brainstormed ideas for existing competition, task analysis, and usability requirements.
• Planned remainder of SRS document:
• Glossary: Jason
• User Class Revisions: Zach
• Existing Competition: Jeff
• Last HTA: Kevin
• Clean up old HTAs: Everyone
• Prototypes for Kevin: Keyboard, Staff, and Finger-positioning interfaces
• Prototypes for Jason: Main Screen, Chords Tutorial, Beginner Tutorial, Keyboard Setup, and Demo toolbar interfaces

Focus for the next week:

Complete SRS Document by Sunday at Midnight:

• Task Analysis (1) [Kevin] 0.25 - 0.75 hours
• Document Integration [Jason] 1 – 1.5 hours

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

• Plan Design Document including brainstorming and deliverable assignments.
• Plan Prototype Development including deliverable assignments.

Issues/challenges for this week:

Deliverable Tardiness: Team members seem to be running into trouble completing deliverables in a timely manner.

Meeting Minutes 9/25

Reviews parts of the SRS:

- System Summary okay
- Existing Competition Initial Research and Discussion, final document to be completed on Saturday
- User Classes: Revisions: Remove Intermediate Learner. Add Independent Learner. Check user classes against system features. 4 classes decided on: Novice Learner with Teacher, Independent Learner, Piano Expert, Piano Teacher.
- System Features: Add Glossary in connection to System Features.
- Task Analysis: Clean up individual HTAs based on grades. Add 6th HTA on freeplay mode.
- Non-functional requirements: 5 parts of usability in connection to system, use "hard" numbers (5 seconds to complete feature). Include note to simulate piano setup without keyboard hookup.
- Prototypes: Translate whiteboard sketches into drawn sketches. Upload as images.

Assignments Due by Saturday Night:
- Existing Competition: Jeff
- User Classes Revisions: Zach
- Glossary: Jason
- Last HTA: Kevin
- Clean up old HTAs: Everyone
- Prototypes Kevin: Keyboard Interface, Staff Interface, Finger-Positioning Interface
- All other prototypes: Jason

Weekly Status Report 9/13-9/19

Tasks/Features Completed:

Individual HTAs:

• Zach: Stepping through the Beginner Tutorial to playing Piano (0.75 hours)
• Robert: Running through the Keyboard Setup Wizard (0.5 hours)
• Kevin: Importing Sheet Music (0.5 hours)
• Jeffrey: Playing a song demo (1 hour)
• Jason: Complete the C chord quiz (1 hour)

Out-of-class Team Meeting (1 hour per person = 5 hours total):

• Planned and distributed assignments for SRS document (1/2 hour per person)
• High-level overview of system with potential prototypes (1/2 hour per person)

In-class Team Meeting (0.25 hours per person = 1.25 hours total)

• Planned and distributed assignments for 5 HTAs (0.25 hours per person)

Focus for the next week:

Complete SRS Document:

• System Summary (1) [Jason] o.5-1 hours
• Existing Competition (1) [Jeff] 1-1.5 hours
• User Classes (3) [Zach, Kevin] 1 - 2 hours for Zach, 0.5 - 1 hours for kevin
• System Features (1) [Jason] 1.5-2.5 hours
• Task Analysis (1) [Kevin] 0.25 - 0.75 hours
• Usability Requirements (non-functional) [Robert] 1-2 hours

Planned Out-of-Class Team Meeting (1-1.5 hour per person = 5-7.5 hours total)

• Review SRS document outside of prototypes (1/3-1/2 hours per person)
• Review Interface Prototypes (1/3-1/2 hours per person)
• Plan Design Document and Computer-Generated Prototype (1/3-1/2 hours per person)

Issues/challenges for this week:

No current challenges.

Meeting Summary

Discussed responsibilities for SRS document.

• System Summary (1) [Jason]
• Existing Competition (1) [Jeff]
• User Classes (3) [Zach, Kevin]
• System Features (1) [Jason]
• Task Analysis (1) [Kevin]
• 6 HTAs (1 additional needed)
  
• Freeplay Mode to be done as 6th HTA
  
• Usability Requirements (non-functional) (1) [Robert]

Prototypes (>=1 per person, 7 total)
- Skeleton
- Specific interfaces and layouts finalized later

1. Musical Staff, with the ability to highlight individual notes.
2. View of keyboard with keys highlightable by the tutorial for lessons.
3. Chord tutorial screen, with the ability to present a chord quiz, demo chords, and choice of chord.
4. Will have panels for the speed and play-control of the current lesson.
5. Beginner tutorial
6. Overall screen (freestyle mode?)
7. Keyboard Setup

System Features list will be largely used as a basis for the other individual requirements.

Next meeting: 9/25 4pm-5pm

Meeting Minutes from 9/14

We analyzed the project concept that was selected: EasePiano to determine what tasks we could create HTAs for. The following categories were selected for HTAs:

- Robert: Keyboard Setup Wizard
- Jason: Scales Tutorial
- Kevin: Importing Sheet Music
- Jeff: Playing a song demo
- Zach: Beginner tutorial to playing piano

The next team meeting will be Friday, September 18th at 4pm - 5pm. We will be covering the following topics:

- SRS Planning
- Prototyping

Before the meeting, analyze competing products against the product we plan to develop. Examples include:

- TuxGuitar
- GuitarPro
- Learn & Master Piano
- Rocket Piano
- Piano is Fun!