From CS160: User Interface Design Sp12
- Contributed to the paper prototype, filming, and mission statement.
- Constructed paper prototype parts, discussed the video prototype.
- Edited / Shot video, provided prototype materials and shooting space.
- Constructed paper prototype parts, wrote Prototype section of writeup.
The path to obtaining a driver's license can be very difficult. For a small group of learning drivers, the driving test evokes a great sense of fear because of the highway driving portion. These drivers lack coordination, good reaction times, and driving sense required for highway travel. Our mission is to provide an environment for these learning drivers to practice highway driving skills without being afraid of crashing. This will help ease the transition into highway driving, rather than the experience being a 'dive into action' ordeal. Our goal will be satisfied if drivers who previously stalled on getting their license because of fear become more motivated to get their license.
Use right hand as a cursor. Choose start to view 3 different tasks, or choose help for a tutorial Select an item by hovering over it (hover over start)
Sub Main Menu
Here we have 3 different tasks that simulate a highway environment. Hover over each task to see a description (hover over)
In the easy task, the user has a car interface. In the top left is a video of the user, on the bottom right is a speedometer, and on the bottom left is a steering wheel. In this simulation, user need to brake as soon as possible when the car in front of you makes a sudden stop. Start with right foot up, and put foot down in a braking motion to brake when the car in front of user stops.
In this simulation user will practice merging onto the highway. Make sure to merge at the proper time and not hit any cars! When the lane is free, use hands as a steering wheel to merge.
In this simulation user will practice changing lanes. Raise and lower his or her left hand to signal, and steer with both hands. Move his or her right foot forward to accelerate and bring it back to stop accelerating. Stomp his or her foot to brake. he or she have to quickly swerve out of the lane by turning his or her hands when an obstacle presents itself.
3 Other Choices:
when the both of the user's hands up, the Paused screen shows up and paused the game. In this paused screen, the user is able to adjust the volume and either back to game or exit game.
Passed the task
This screen shows up when user pass the current task, tell the user that " You successfully completed this task." and the user can either choose to back to main menu or start next task.
Fail the task
This screen shows up when user fail the current task, tell the user that " You did not successfully completed this task." and the user can either choose to back to main menu or try this task again.
Though hover is used to select buttons in the Kinect interface, tapping with wire pointers is used in the paper prototype.
Tiny version uploaded to the wiki: Media:fatal_exception_proto_video.wmv
Youtube Version: here
Discussion of Video Prototyping
In our group meeting, we brainstormed three tasks of different difficulties for our users to do in our interface. Then we drafted a diagram of our application showing how views were connected to each other. Afterwards we constructed all the different elements of our UI on pieces of paper. Afterwards, we came up with a background story for a typical user that would use our interface. We then shot a video of this fictitious user using our interface while we manually animated the paper elements of our interface. This resulted in a very good demo of what our interface should do.
In the process of making our paper prototype, we found new interesting ways of displaying our driving 'dashboard.' For example, we added a rear view mirror that would actually display a video of the user. We found that viewing the road from a driver's perspective was much more useful than viewing it from the top, and the driver's seat view makes the program more realistic.
We found difficulty in creating a psuedo 3d interface using paper. We had to draw in perspective to create an adequate simulation. Also we found coordinating the prototype to get all the parts working difficult. It required all 4 of us simultaneously to simulate some of our activities. Writing a good script took some practice because we didn't want to be too verbose; at the same time, we wanted to describe as much of our application as possible.
Using a rod with a hand picture on it worked well to simulate the kinect cursor. To give viewers more of an idea of how the user would interact with the paper prototype, we showed cuts of Wenjie actually performing the gestures. Making the paper prototype modular was great because if we ever wanted to switch an element out, we could just cut out another module and place it on top of our 'base' module. Having a base module also helped with the consistency across our prototype.