forked from Gabxi/StoryAlive
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathweek7.html
262 lines (231 loc) · 14 KB
/
week7.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>CS247 StoryAlive</title>
<meta name="description" content="CS247 Final Project: StoryAlive">
<meta name="author" content="Cindy Chang Jessica Kung Adam Raudonis Gavin Kho">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="">
<meta name="author" content="">
<!-- Le styles -->
<link href="css/bootstrap.css" rel="stylesheet">
<link href="css/custom.css" rel="stylesheet">
<link href='http://fonts.googleapis.com/css?family=Open+Sans:400,300' rel='stylesheet' type='text/css'>
<style type="text/css">
body {
padding-top: 60px;
padding-bottom: 40px;
}
.sidebar-nav {
padding: 9px 0;
}
@media (max-width: 980px) {
/* Enable use of floated navbar text */
.navbar-text.pull-right {
float: none;
padding-left: 5px;
padding-right: 5px;
}
}
</style>
<!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
<!--[if lt IE 9]>
<script src="../assets/js/html5shiv.js"></script>
<![endif]-->
<!-- Fav and touch icons -->
<link rel="apple-touch-icon-precomposed" sizes="144x144" href="../assets/ico/apple-touch-icon-144-precomposed.png">
<link rel="apple-touch-icon-precomposed" sizes="114x114" href="../assets/ico/apple-touch-icon-114-precomposed.png">
<link rel="apple-touch-icon-precomposed" sizes="72x72" href="../assets/ico/apple-touch-icon-72-precomposed.png">
<link rel="apple-touch-icon-precomposed" href="../assets/ico/apple-touch-icon-57-precomposed.png">
<link rel="shortcut icon" href="../assets/ico/favicon.png">
</head>
<body>
<div class="navbar navbar-inverse navbar-fixed-top">
<div class="navbar-inner">
<div class="container-fluid">
<button type="button" class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="brand" href="./index.html">StoryAlive</a>
<div class="nav-collapse collapse">
<p class="navbar-text pull-right">
CS247 Final Project Winter 2013
</p>
<ul class="nav">
<li><a href="./team.html">Team</a></li>
<li><a href="./week5.html">Week 5</a></li>
<li><a href="./week6.html">Week 6</a></li>
<li class="active"><a href="./week7.html">Week 7</a></li>
<li><a href="./week8.html">Week 8</a></li>
<li><a href="./week9.html">Week 9</a></li>
<li><a href="./week10.html">Week 10</a></li>
</ul>
</div><!--/.nav-collapse -->
</div>
</div>
</div>
<div class="container-fluid">
<h1>Milestone 3: Functional Prototype 1</h1>
<br />
<h3>What happened this week</h3>
<div class="row-fluid">
<div class="span8 columns">
<p>Based on our Wizard of Oz prototyping session last week, we came into class on Tuesday still feeling very not
completely satisfied with our idea and during class talked about pivoting to a new idea about creating an application
that would allow fencers to practice by using the Leap to track the angles and positions of their wrist and in turn,
show the user a computer generated wrist of an opponent fencer, thereby training the user to deflect jabs of the
opponent by observing the movements and positions of the opponent's wrist. After agreeing on this idea after class,
we started to implement the functional prototype for Thursday.</p>
<p>Since our coach didn't show during the coach meet-and-greet a few weeks ago, we finally had the chance to meet
with Rob Ryan, our mentor, on Wednesday night. We explained our situation to Rob and he led us back to square one
in terms of brainstorming ideas and designing to solve needs. This turned into a massive 3.5 hour brainstorm and
work session. We went through a lot of whiteboarding of ideas. At first, we honed in on the application area of
travel, specifically traveling to Asia, and a few problem areas that arose there were: something to do with
dirty squat toilets in Asia, haggling, communicating over the language barrier, and jaywalking.</p>
<br />
<p>Images of our first brainstorm session about travel</p>
<a href="img/week7_1.jpg" class="thumbnail" target="_blank"><img src="img/week7_1.jpg"></a>
<a href="img/week7_2.jpg" class="thumbnail" target="_blank"><img src="img/week7_2.jpg"></a>
<a href="img/week7_3.jpg" class="thumbnail" target="_blank"><img src="img/week7_3.jpg"></a>
<br />
<p>However, in generating possible solutions to solve these problems above, again really focusing on the
need aspect of the design, we got stuck again. The problems in the area of toilets and bathrooms in Asia resonated
deeply with us, but the biggest problems we sas were simply: the toilets were dirty, smelled bad, and unhygenic,
which were not problems we could see the Leap helping to solve. Other problems, like haggling, were found to have
knowledge at the center. For example, we thought of an application that could help sellers and customers agree
on a price by having them move their hand up or down in correspondence with the price of the sale, such that agreeing
would mean their hands were on the same level. However, we went deeper and realized that that was not the main problem
of haggling--the main problem is not knowing if you (the buyer) is getting ripped off or not due to being a foreigner.
This problem was not one we saw gestures being very useful for. </p>
<br />
<p>Images of our second brainstorm session about payments, acting out the experience</p>
<a href="img/week7_4.jpg" class="thumbnail" target="_blank"><img src="img/week7_4.jpg"></a>
<a href="img/week7_5.jpg" class="thumbnail" target="_blank"><img src="img/week7_5.JPG"></a>
<a href="img/week7_6.jpg" class="thumbnail" target="_blank"><img src="img/week7_6.JPG"></a>
<a href="img/week7_acting.jpg" class="thumbnail" target="_blank"><img src="img/week7_acting.jpg"></a>
<br />
<p>Thus, we went back to brainstorming again. We finally came to talking about the problem of losing and keeping
receipts, losing track of your purchases. From there, we started to bond over how signing receipts in stores
doesn't really do anything - it seems like signatures would be used for identity confirmation, but they are never
checked. We started to talk about environmental issues as well, and speculated how many trees could be saved by
simply not printing out receipts at the end of every transaction and instead making the experience purely digital.
Having each known and talked to people who have had their credit card numbers stolen, we also converged on the need to improve
security in making purchases. This being a particularly bad flu season, we also talked about the need to
prevent the spreading of illnesses in public spaces or publicly used items, such as the pens people use to sign
their receipts in busy supermarkets or stores.</p>
<div>
</div>
<h3>Our final idea and Looking Forward</h3>
<div class="row-fluid">
<div class="span8 columns">
<p>Our final idea is a simpler, more secure, and gesture/digital-based point of sale system. This system
would let customers digitally sign their receipts by signing in the air and would be more secure by incorporating
photographic elements and actually checking the signature against the buyer's other signatures in the past.
This system, using just a laptop and LEAP, could potentially replace very expensive payment machines and systems
already in large stores, and could be very useful for small businesses who don't have a lot of money to spend on
their payment systems.</p>
<p>Feature choices with Rationale</p>
<ol>
<li >Credit Card Detection</li>
<ul>
<li>Rationale:</li>
<p>While you could hand over your credit card to the
cashier to swipe and process the payment, there is still the hygienic issue
of someone else touching your credit card. With our system, we want to eliminate the need
to hand over your credit card (minimizing the possibility of even the cashier stealing
your identity or overcharging you), so simply scanning your card into our system
would be safe and clean. </p>
</ul>
<li >Photo Authentication</li>
<ul>
<li>Rationale:</li>
<p>Sometimes stores don't check your photo ID upon purchase with a credit card, which makes
it easier for theft to occur. Our system would compare your photo ID on record with the way
you look now in the store by leveraging the web cam of the laptop.</p>
</ul>
<li >Visual receipt</li>
<ul>
<li>Rationale:</li>
<p>Receipts are sometimes hard to read and check over for items simply because each item is
described in a way that's foreign to the customer, for example, a pair of skinny blue jeans
with flower patterns down the side of the leg could just be
called "JEANS BDCDT" on the receipt, which doesn't meet the customer's mental model toward the
jeans. Instead, a visual receipt will allow users to quickly scan and check their purchases because
users can quickly match the image on the receipt with the real item. This matching activity is
more efficient and accurate than having to translate and then match
obscure text labels of objects assigned by
the store to the objects users have bought.</p>
</ul>
<li >Digital Signature (with confirmation of signature authenticity)</li>
<ul>
<li>Rationale:</li>
<p>Stores don't verify your signature. Several of the people we talked to had actually experimented
with signing differently on receipts just to see if anything would happen (for example, signing
upside down, just writing a line or drawing a circle, etc.) This makes theft
easier and seems counterintuitive - a signature
should help to increase security. By having the customer sign and approve their
purchase with the LEAP and then verifying it digitally, we add a layer of security to the buying
process. The virtual in-air signature that uses gestures is better than the current system of just
having a pen and a machine to sign on because it is more hygienic as well.
</p>
</ul>
<li >Creating and curating a storage space for digital receipts</li>
<ul>
<li>Rationale:</li>
<p>From <a href="http://blog.softwareadvice.com/articles/retail/please-kill-the-paper-receipt-102310/">
this website</a> we gather that the environmental footprint due to creating paper receipts is
HUGE. According to the website, receipt paper demands in the US are 640,000 tons per year, which
equates to 9,600,000 millions trees cut down each year just to produce paper receipts. From there, there is
even more damage done with the amount of water, oil, and CO2 used and emitted. Thus, there really is a
need to move from paper receipts to digital ones. By keeping receipts digitally in one place,
we prevent customers from losing physical receipts as well, which saves them from stress and
makes it easier to verify their purchases when they have to pay off their credit cards. </p>
</ul>
</ol>
<p>Implementation Progress: Because we struggled so much with music early on in the process of this project and
then started to implement the fencing app idea on Tuesday, only to pivot to this final idea, we have unfortunately
not been able to create our first functional prototype in time for class today. However, we have prototyped the system
by acting it out ourselves and will come to class on Thursday with a
<a href="https://docs.google.com/presentation/d/1dyFljgcJx67YeoqYbvnzv6AhRlbe5tBEJ7K2WRSpiO0/edit?usp=sharing">wizard of oz</a>
instead to still collect feedback
and test out the idea/get feedback from our peers and the course staff before implementation. We will definitely
catch up to the milestone on user testing for next week--but our delayed progress this week is
simply due to a delayed first meeting with our mentor and pivoting from our initial idea.</p>
<p>Prioritized To-Do in Implementation and Design</p>
<ol>
<li >Thursday 2/21: Email around campus to ask if we can set up system in real environment to test</li>
<li >Thursday 2/21 and Friday 2/22: Do more wizard of oz testing and crummy trials</li>
<li >Friday 2/22 - Sunday 2/24: Work on signature detection, recording, confirmation</li>
<li >Saturday 2/23: Work on credit card detection and photo authentication</li>
<li >Monday 2/25: Work on visual receipt and figuring out how to store receipts as PDFs</li>
<li >By Tues 2/26 First functional prototype done, test in Tresidder or real world situation</li>
</ol>
<p>Preliminary Thoughts for User Testing</p>
<ol>
<li >Fake check out line experience</li>
<li >Ask a booth in Tresidder to try it with real clients</li>
<li >Test on students, elderly, moms - people likely to have lots going on and potentially lose lots of receipts</li>
<li >Test in bookstore</li>
</ol>
<div>
</div>
<hr>
<div class="row-fluid">
<footer>
<p>by <a href="./team.html">Cindy Chang</a>,
<a href="./team.html">Jessica Kung</a>,
<a href="./team.html"> Adam Raudonis</a>, and
<a href="./team.html">Gavin Kho</a></p>
</footer>
</div>
</div><!--/.fluid-container-->
<!-- Le javascript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<script src="js/jquery.js"></script>
<script src="js/bootstrap.js"></script>
</body>
</html>