prototype
PRACTICAL 3
Members:
Design Brief: Glance
Document typed and written by BJCJ in conjunction with AK and GK.
Step 1: Point of View
Brainstorming High-End Design Need
Knowing where others are (consumers and employees) so that you can be in the right place at the right time.
In order to maintain scheduled work, being ever conscious as to the whereabouts and actions of one’s associates.
In an attempt to reduce inefficiencies in scheduling, an individual must be constantly aware of the whereabouts, requirements and intentions of the individual’s associated entities.
conscious of, mindful of, informed about, acquainted with, familiar with, alive to, alert to; informal clued in to, wise to, in the know about, hip to; formal cognizant of;
Realtime
Associates
Perform jobs simultaneously
Chosen Topic: Tracking people’s location and intentions to maintain efficiency.
Step 2 - Storyboarding:
BJ’s Storyboard
G’s Storyboard
A’s
Step 3 - Paper Prototype:
Minutes of meeting:
Attending Members - G K, BJCJ, AK
Place: Library
Time: 5:45pm
Met at 5:45pm
Looked at G’s storyboard
Looked at BJ’s storyboard
Looked at As storyboard
Discussed the strengths and weaknesses of each storyboard
G’s Storyboard
Strengths |
Weaknesses |
|
Detailed |
Not sure how dashboard is used exactly |
|
Need identifiable |
Lots of writing |
|
Characters are obvious - Taxi driver and client |
|
|
Captions help with context |
|
Bj’s Storyboard
Strengths |
Weaknesses |
|
Needs identifiable |
Not sure on how to design interface |
|
Characters are obvious - lifeguards |
Not sure on dashboard itself |
|
Shows needs being solved |
Story a little disjointed |
A’s Storyboard
Strengths |
Weaknesses |
|
Clearly shows needs |
Not sure on characters |
|
Shows outcomes at the end of the day |
Lots of writing, a little too detailed |
|
Interesting storyline |
|
|
Detailed |
|
After much discussion decided on choosing G’s storyboard as the needs were simple and obvious, and the storyboard showed this clearly.
The need was identified as -
Client needs a taxi
Taxi needs to know exactly when the client is ready and where
Taxi tracks client until they pick them up, allows for them to do other jobs if the client is busy doing something else. Also allows for the client to tell the taxi if they don’t need it anymore, or if they will be late/busy.
Discussed meeting tomorrow, agreed upon having the paper prototype completed by 5pm Thursday, 17th March in the library.
Discussed different styles of interfaces and applications. Talked about how to do a paper prototype. Sent email to everyone with photos of storyboards and with the information in this document so far and time and place of meeting tomorrow.
Meeting finished at 6:40pm
Meeting Thursday 17th March 2010
Time: 5pm
Present: All members
A had unfortunately not been able to complete his prototype due to other commitments, but had some ideas and pictures with ideas to show. B had completed his client part of his project and G had completed his paper prototype. All members went through their paper prototypes.
Members discussed when they would be meeting next, however due to time commitments they couldn’t meet at all until the day of the presentation.
Things that need to be completed at the next meeting include:
· Taking video or photos of the paper prototypes
· Formatting this document
· Ensuring that all points have been covered
· A brief analysis of each paper prototype and which one we all think will work the best
· Finalise presentation for Monday
Discussion around the presentation:
It was agreed that each member would take about 20-30 seconds to show their prototype and another 20-30 seconds to show their storyboards. Any remaining time would be used to briefly introduce the brief, and to finish at the end.
Members agreed to do a quick run through of their presentation 15 minutes before class.
Finished at 6pm
Paper Prototype - AK
|
Slide 1 - Dashboard |
Slide 2 - Input |
Slide 3 - Location check |
|
Slide 4 - Sending Request |
Slide 5 - Date and Time for Pickup |
Slide 6 - Cannot book Taxi more than 1 week in advance |
|
Slide 7 - My Bookings, track your booking |
Slide 8 - My bookings, map |
Slide 9 - Edit booking |
|
Slide 10 - Contact Driver |
Slide 11 - Taxi Arrived |
Paper Prototype - BJCJ
Slide
1 - Home Screen
Slide 2 - Ordering a Taxi
Slide 3 - Update screen
Slide 4 - Settin
gs screen, can change default language, default cars, skins for the application etc...
Slide 5 - Taxi has arrived, allows the user to contact the taxi, ask where it is, refuse taking the taxi or to tell the taxi to wait
Paper Prototype
- GK
|
Slide 1 - Dashboard |
Slide 2 - Booking |
Slide 3 - Details |
|
Slide 4 - Processing Request |
Slide 5 - Booking confirmed |
Slide 6 - Canceling a booking |
|
Slide 7 - Cancellation Confirmed |
Slide 8 - Get Update |
Slide 9 - Map of route |
Reflection:
How was your decision process?
The decision process worked quite well, with a decision as to what the high-end design need was, being made within about an hour of the practical being issued. This was done through brainstorming and discussion, along with the use of Thesauruses and Google.
In regards to the decision about the story board was made after weighing up the strengths and weaknesses of each storyboard, and taking into account which would be the easiest and quickest to paper prototype.
What did you end up going with?
We ended up going with the Taxi system.
What is something you learned?
Something that we learned is that it is difficult to set goals and achieve them in short spaces of time, especially when we all do things differently. Also, that picking the easiest idea, although not always being the most fun or interesting, is often the best way to achieve something if time is a major factor.
What was most valuable?
The most valuable thing in this project was learning about paper prototyping, especially after reading the article by Snyder as it offered some really good and creative ideas for prototyping.