Week 8 Progress Report

Meetings (~2 hours)

We had a meeting to finalize our plan for the usability tests and discuss who would be coming in for the tests. We recruited on Facebook and by word of mouth and were able to find 8 volunteers, several of which are actually colorblind.

Tasks

• Set up meeting times with test volunteers
• Conduct 6 usability tests (5 on Thursday/Friday, 1 on Saturday) estimated to be 30 minutes each

Goals

Our goal for the next week is to do our final 2 usability tests on Sunday and then type up all of the data and compile it in a document that can be submitted for the deliverable on Monday. Moving forward we will also be analyzing the data to figure out what was and wasn't usable in our system.

Week 7 Progress Report

Meetings (~4 hours)

We had a long meeting Monday to iron out the details of our prototype design and determine individual tasks for the week. The primary focus this week was on development.

Heuristic evaluations were conducted in class on Wednesday and several changes have been made to our design. The buttons along the left side have been resized and given solid backgrounds to make them stand out and provide a consistent feel. Text has been added in several areas in the settings panel to indicate system status.

Tasks

• Update color selection mechanism to update faster and display color names (instead of just numeric values)
• Fix image display size (without using hard-coded values)
• Begin testing

Goals

Our goals for the week are development and testing related. There are a couple of features which need to be added or updated, and then we will begin testing.

Week 6 Progress Report

Meetings(~1 hour)
We had a meeting on Monday to determine what type of version control we would be using, and how we would divide up the coding tasks. We originally decided to use SVN since we were all familiar with it, but after having problems with the SVN repository host we were using we decided to switch to a mercurial repository hosted by BitBucket.

We also looked at our UML class diagram and tried to decide how we would split up the coding. We originally considered trying to complete all of the color highlighting strategies for the third deliverable but then we thought that might be unrealistic and that we should focus on the core functionality. We decided to wait to split up the coding until after we tried some Android tutorials on our own to see how things worked.

We also decided to plan for another meeting on next Monday to check the project status.

Tasks

• Set up the repository (Andrew)
• Connect to the repository (Lindsey, Ian, Thomas)
• Begin familiarizing selves with Android development

Goals for Next Week
Due to people having midterms, interviews, and other responsibilities during week 6 we are behind with our coding. We will be meeting on Monday where we will need to decide who's doing what parts of the code. We will also want to meet on Wednesday as well to verify whether or not we've caught up with the implementation and see if anyone is having problems with their portion of the implementation.

Progress Report (Week 5)

Design Document First Draft
Similarlyto how we handled the SRS document, we split up sections of the design document and delegated them to individual team members. We met throughout the week to check up on each other and get an idea of the overall progress.

Individual Tasks (1 hour per person):Everyone: Install Android SDK and Eclipse plugins if they haven't already
Andrew: Software Interface Description
Lindsey: Android Interface Guidelines
Thomas: External GUI Components/Frameworks
Ian: Native GUI Components


Meetings (~4 Hours)
For Monday, we each designed a UML class diagram of our system (30 minutes each) and met for 1 hour after class. We compared our diagrams and decided upon a new design that incorporated pieces from our individual designs. Andrew created a digital version of the new diagram.

For Wednesday we met for half an hour and delegated prototype responsibilities amongst the team (Andrew/Ian did a prototype of the settings view and Thomas/Lindsey did a prototype of the main view) and checked up on the individual tasks.

Saturday we met for 3 hours to combine our individual work into the design document and complete the remaining sections (i.e. user interface description, sub-component descriptions) as a group.

Goals for Next Week
Start working towards being ready for the 3rd deliverable (having a testable interface by the end of week 7). This means that we will need to decide on a type of version control and set up our repository. We will also need to begin the actual development and decide who will be coding which parts of the project.