Changes
no edit summary
This can be used for testing out wiki markup. Enjoy.
----
Project proposal
==Target User Group (3 pts)==
The target user group is all users of cell phones. In addition, the product makes the most sense for users who are frequently on the go and cannot devote a significant amount of their time to looking at, or providing tactile/visual inputs to, their phones. While equally useful to both novice and advanced cell phone users, it would probably be a more fitting product for the intermediate-to-advanced user.
The most specific group outlined above, those frequently on the go, cannot devote a significant amount of time to providing inputs to their phones to accomplish a certain task. These users know what the want to do, but do not have the time or desire to go through 5 menu levels to get to what they are trying to accomplish. In addition, they might not have the ability to look at their phone while attempting to perform a specific action, such as the case with drivers, who need to keep their eyes on the road. These users need a way to perform actions on the phone without looking at it or pressing a lot of keys.
==Problem Description (3 pts)==
Today's phones contain a myriad
==Problem Context and Forces (3 pts)==
The analysis section should give more background for the problem. What aspects of the situation might influence the problem solution? Think about location, time, environmental factors etc. Then think about aspects of the user group, their education, available time, motivation, values etc., What related or complementary solutions exist already?
==Solution Sketch (3 pts)==
Give a very brief sketch (outline) of the kind of solution(s) you are considering. Since your problem has barely been specified and you haven’t done any user interviews, you probably don’t have enough information to make many design choices. So your solution sketch should be very general. This is an excellent place to make use of real sketches (drawings) as well as text.
