Status Report: 03/31/2012

Tasks Accomplished:

• Team members compiled and reviewed SRS document (1 hour)
• Bill researched existing competition (2.5 hours)
• Doug compile the system summary based on what we've done so far ( 35 min.)
• Team members collaborated and created various user classifications (4.5 hours)
• Geoff compiled and elaborated on system features (1 hours)
• Each team member contributed at least one HTA for the app's basic functions (4 hours total)
• Boom compiled and expanded non-functional requirements (1.5 hours)
• Boom researched blind culture and photography for project reference (1.5 hours)
• Bill and Doug created and refined application prototypes (2 hours)

For next week:

• Members should continue familiarizing themselves with the Android development environment
• Team will begin structuring the application architecture and prepare it for implementation
• Members will begin to outline design document

Issues to Note:

• None at this time

Non-functional Requirements

Non-functional Requirements

• Photos can be taken by individuals with NLP (no light perception)
• Individuals with NLP must be able to compose the picture with the subject at one of the 5 possible points
• Use of voice and gesture controls
• Text-to-Speech settings
• Settings for Text-to-Speech speed (if possible from Android API)
• Vibration feedback

Status Report: 03/24/2012

Tasks Accomplished:

• Each group member created an HTA to be used in the SRS for different tasks that were agreed upon by the team
• Team members came up with two user classifications for the SRS
• Team members created a list of main system features to be implemented, as well as other features to consider
• All members began researching the user domain for our application, familiarizing themselves with various approaches to usability and accessibility for those with visual impairments.
• All members have been researching Android API's that may help in the implementation of our application.
• Doug, Boom, and Bill began prototyping the application's interface

For Next Week:

• Doug will focus on completing the System Summary section of the SRS document
• Geoff will focus on compiling the System Features section of the SRS document
• Bill will research some existing competition for leads and ideas
• Boom will compile a list of non-functional requirements
• Team will collectively create and decide on additional user classes
• Finalize SRS document and have it ready for submission
• Team members should look into the Android development process and familiarize themselves with how applications work

Issues to Note:

• Bill will be unavailable over the weekend and unable to contribute

Perspective

Being a person who has had clear vision his whole life, the idea of taking photos without looking at my subject is hard for me to comprehend.  This is not to say that it is not important, or that it does not happen, just that it is difficult for me to grasp.

With that in mind, and after reading through the paper that was posted yesterday, we here at Mistaken Umbrella are going to do our best to create an app for Android 4.0 that is designed to assist people take pictures, without being able to look at the screen.

Why Android 4.0?  Camera Face Recognition.  With Android 4.0's API we are able to identify faces from the camera, so we are able to provide feedback to users on how to better center their pictures, without having to take a picture first.

So far we've thought about using either the speakers, or the vibration system in order to provide feedback, but we're looking for suggestions.  If anyone can give us any ideas on other features that would be helpful we'd love to hear them.  If you could please leave them in the comments below we'd be happy to add them to our list of things we'd like to do.

Photography for the Blind

It's an interesting concept. Those who can't see being able to capture a scene with a camera. Is it possible? Certain researchers believe so and their results are promising. Take a look.

A Passing Thought of Usability

You've heard the word around, maybe from a conference, maybe a co-worker said it in passing, but it's left you wondering what is usability, and what does it mean to me?

To us usability is what people will like your app for.  If it's easy to use, nice to look at, using the latest interface options, or able to provide functionality where other apps can't, it's got usability at the core of it's design.

We hear at Mistaken Umbrella look to create Android applications designed around usability, in order to be able to provide best user experience possible to as many people as we can.