The title says it all.
Project was submitted and presented during week 10
Wednesday, May 13, 2009
Friday, May 8, 2009
Week 9 Status Report
Week 9 Status Report
Tasks completed:
-Compiled user testing data from week 8 testing (Pat, James : 90 minutes)
-Built PowerPoint presentation for Monday's demo (team : 120 minutes)
-Polished off application for submission (Pat, James : 60 minutes)
Next week's tasks:
-Submit project (team)
-Presentation
Problems:
Still going well, no serious problems.
Tasks completed:
-Compiled user testing data from week 8 testing (Pat, James : 90 minutes)
-Built PowerPoint presentation for Monday's demo (team : 120 minutes)
-Polished off application for submission (Pat, James : 60 minutes)
Next week's tasks:
-Submit project (team)
-Presentation
Problems:
Still going well, no serious problems.
Saturday, May 2, 2009
Week 8 Status Report
Week 8 Status Report
Tasks completed:
-Built user walkthrough surveys and scripts (1.5 hours) Pat, Adim, James
-Performed 10 walkthroughs (3 hours) Pat, Adim, James
Next week's tasks:
-Submit project (team)
Problems:
Still going well, no serious problems.
Tasks completed:
-Built user walkthrough surveys and scripts (1.5 hours) Pat, Adim, James
-Performed 10 walkthroughs (3 hours) Pat, Adim, James
Next week's tasks:
-Submit project (team)
Problems:
Still going well, no serious problems.
Friday, April 24, 2009
Week 7 Status Report
Week 7 Status Report
Tasks completed:
-Heuristic evaluations during Wednesday's class time (45 minutes)
-Prototype completed (Team) ~4 total hours
Next week's tasks:
-Begin user testing (team)
-Work on Assignment 4 (individual projects)
Problems:
Still going well, no serious problems.
Tasks completed:
-Heuristic evaluations during Wednesday's class time (45 minutes)
-Prototype completed (Team) ~4 total hours
Next week's tasks:
-Begin user testing (team)
-Work on Assignment 4 (individual projects)
Problems:
Still going well, no serious problems.
Saturday, April 18, 2009
Week 6 Status Report
Week 6 Status Report
Tasks completed:
Tasks completed:
- Test Plan Document prep work (~1-2 hrs a piece):
Jimmy - Usability evaluations goals / Schedule
Adim - Concerns / Data collection methodology
Pat - Target audience background / Subject selection background
Matt - Logistics / Materials design
- Most of this week was spent working on Assignment 3 deliverables, so
in turn it was a rather light week on our project.
Next week's tasks:
- Assignment 3 continuation (individual)
- Assignment 3 continuation (individual)
- Heuristic Evaluation
- Deliverable 3 for Friday
Problems:
Still going well, no serious problems.
Thursday, April 9, 2009
Week 5 Status Report
Week 5 Status Report
Tasks completed:
-Built Design document (Written by Pat, with feedback by team, 2 hours)
-Interface design patterns (Jimmy, Pat, Adim, 1 hour)
Next week's tasks:
-Assignment 3 (Broken teams)
-Prep for exam (Individual)
-Begin looking into testing planning (Matt, 1 hour)
Problems:
None so far!
Tasks completed:
-Built Design document (Written by Pat, with feedback by team, 2 hours)
-Interface design patterns (Jimmy, Pat, Adim, 1 hour)
Next week's tasks:
-Assignment 3 (Broken teams)
-Prep for exam (Individual)
-Begin looking into testing planning (Matt, 1 hour)
Problems:
None so far!
Monday, April 6, 2009
User Feedback
From our interaction with user walkthroughs in class last week, we got the following feedback:
Our current mouse layout is a little confusing. The previous layout had a single arrow for minimal mouse movement, and an arrow with a bar for larger movement. Users thought the arrow with bar implied the mouse would be moved to the edge of the screen. This was replaced with something like this:
> >> >|
Now you can have minimal movement, larger movement, and then jumps to the edge of the screen. This should alleviate any user confusion. These changes were reflected in Pat Day's assignment 2.
Our current mouse layout is a little confusing. The previous layout had a single arrow for minimal mouse movement, and an arrow with a bar for larger movement. Users thought the arrow with bar implied the mouse would be moved to the edge of the screen. This was replaced with something like this:
> >> >|
Now you can have minimal movement, larger movement, and then jumps to the edge of the screen. This should alleviate any user confusion. These changes were reflected in Pat Day's assignment 2.
Thursday, April 2, 2009
Week 4 Status Report
Tasks completed:
-Went over SRS feedback (Team, 30 minutes)
-Decided on using tango icon library for remote icons. This will allow for easy -recognition by the user (Suggested by Matt Broadstone)
-Went through user walk through of our prototype. Got some good feedback (James / Adim, 30 minutes)
Next week's tasks:
-Design Document (Pat will start the doc, team will complete, ~2 hours)
-Build on existing prototype (James, 2 hours)
-Work on mobile web interface (Adim, 1 hour)
Problems:
None so far!
-Went over SRS feedback (Team, 30 minutes)
-Decided on using tango icon library for remote icons. This will allow for easy -recognition by the user (Suggested by Matt Broadstone)
-Went through user walk through of our prototype. Got some good feedback (James / Adim, 30 minutes)
Next week's tasks:
-Design Document (Pat will start the doc, team will complete, ~2 hours)
-Build on existing prototype (James, 2 hours)
-Work on mobile web interface (Adim, 1 hour)
Problems:
None so far!
Wednesday, April 1, 2009
Tango Icon Library
We decided as a team to use the Tango Icon Library for as many icons as we can. Tango is an open source icon library.
http://tango.freedesktop.org/Tango_Icon_Library
http://tango.freedesktop.org/Tango_Icon_Library
Friday, March 27, 2009
Weekly Update 2
Tasks completed:
Blog entry (Matt, 15min)
Initial HTA's in class (all members, ~30min)
SRS Document (all members, 2 hours)
Throwaway prototype (James 1.5 hours)
Next week's tasks:
Blog update (Adim, 15min)
Design Document (all members, ~2 hours)
Begin formal prototype (all members, ~2 hours)
Problems:
None so far!
Blog entry (Matt, 15min)
Initial HTA's in class (all members, ~30min)
SRS Document (all members, 2 hours)
Throwaway prototype (James 1.5 hours)
Next week's tasks:
Blog update (Adim, 15min)
Design Document (all members, ~2 hours)
Begin formal prototype (all members, ~2 hours)
Problems:
None so far!
Wednesday, March 25, 2009
SRS Progressing
The SRS is progressing nicely. Still need to complete our HTA and prototype images. User profiles are also being built. We will be meeting on Friday to polish off the document before submitting
Monday, March 16, 2009
Project Selected
Our project has been selected. We will be implementing the remote control interface for a computer. This will be easy to implement in C#, and we will most likely take that approach.
We will begin to fill out our SRS document this weekend
We will begin to fill out our SRS document this weekend
Sunday, March 15, 2009
Proposed 3 projects
Here are our three proposed projects for selection:
a. This is an application that was prototyped by Matt which creates a carousel type overlay on a browser for navigating through tabs. We would want to build on top of this, and possibly make it a plugin for a browser. The user moves the mouse to the top corner of the screen, which launches the overlay of rotating tabbed pages
2. Remote control interface for computer
a. The idea behind this is to have a web page for operating basic controls of another computer (such as mouse movement, volume, etc)
b. A variety of mobile versions of the webpage would be available (for iPhone, NetBooks, etc).
3. Fussball game tracking software
a. This software would be designed to be implemented on a computer that is mounted on a fussball table.
b. The application would track a fussball game and report statistics, game progress, and game results to social networks (i.e. twitter, facebook, myspace, etc…).
1. Browser tab carousel
a. This is an application that was prototyped by Matt which creates a carousel type overlay on a browser for navigating through tabs. We would want to build on top of this, and possibly make it a plugin for a browser. The user moves the mouse to the top corner of the screen, which launches the overlay of rotating tabbed pages
2. Remote control interface for computer
a. The idea behind this is to have a web page for operating basic controls of another computer (such as mouse movement, volume, etc)
b. A variety of mobile versions of the webpage would be available (for iPhone, NetBooks, etc).
3. Fussball game tracking software
a. This software would be designed to be implemented on a computer that is mounted on a fussball table.
b. The application would track a fussball game and report statistics, game progress, and game results to social networks (i.e. twitter, facebook, myspace, etc…).
Saturday, March 14, 2009
Initial Setup
This is the setup of team 4's blog for Software Usability 444
Team proposed projects to come...
Team proposed projects to come...
Subscribe to:
Posts (Atom)