Extracted Content: Kenneth Blais: Okay.
  David Looper: Okay everyone's ready.
  Jonathan Kelly: Hello.
  David Looper: So we are here uh for uh functional design. Okay? So we are here for the functional design meeting mm so first I will show the agenda so we will uh I will take notes during this meeting so I will try to summarise it and put that summary in the shared folder if you want to look at it afterwards so then uh each of you will uh lead a presentation on the task that has been required last time so user requirement specification, technical design and Then I will uh present you some new project requirements I received from uh the management board. Then we will take uh the decision on on the remote control uh needed functions and then I will assign you the task for the next part of the meeting. Of the of the process. So uh who want to start the the presentation of what they did?
  Kenneth Blais: F do you want to start
  Jonathan Kelly: Make a start yeah.
  David Looper: You can start.
  Jonathan Kelly: So Cable, camera.
  David Looper: You have uh PowerPoint?
  Jonathan Kelly: Should be in my in their folder no?
  David Looper: Ah yeah maybe there.
  Jonathan Kelly: Up.
  David Looper: Okay. Who are you?
  Jonathan Kelly: Um at three I think. No? Mm.
  David Looper: Ouch. And
  Kenneth Blais: Okay.
  David Looper: We have a technical problem uh.
  Jonathan Kelly: Do we think w s in the in the wrong folder maybe? It is possible.
  David Looper: You put
  Kenneth Blais: No.
  David Looper: it on
  Jonathan Kelly: It was somewhere in something like this. I don't remember the name actually must be something like messenger AMI or something.
  Kenneth Blais: What do you have in short cut?
  Jonathan Kelly: Go up.
  Kenneth Blais: Participant two.
  Jonathan Kelly: Yeah go up.
  David Looper: Yeah.
  Jonathan Kelly: Again. No. Go back.
  David Looper: You have no
  Jonathan Kelly: Uh maybe messenger Messenger.
  David Looper: Over. Okay.
  Jonathan Kelly: No. There is nothing.
  David Looper: There's no We have a
  Jonathan Kelly: Let's
  David Looper: technical
  Jonathan Kelly: go and check.
  David Looper: problem.
  Kenneth Blais: Yeah.
  Jonathan Kelly: I'll
  Kenneth Blais: Otherwise,
  Jonathan Kelly: go and check.
  Kenneth Blais: could you just describe by hand?
  Jonathan Kelly: Okay.
  Kenneth Blais: With the the whiteboard?
  Jonathan Kelly: Yeah.
  David Looper: If you remember yeah
  Jonathan Kelly: Yeah.
  David Looper: but
  Jonathan Kelly: So
  David Looper: that's
  Jonathan Kelly: uh. Basically what we want here is a remote control right.
  David Looper: Yeah.
  Jonathan Kelly: So um the question well first of all what to control. So most people want to have a a remote for their hi-fi and T_V_ and stuff like that.
  Kenneth Blais: Mm-hmm.
  Jonathan Kelly: And but other people want th also remotes for controlling uh and toys like robotic pets and
  Kenneth Blais: Mm-hmm.
  Jonathan Kelly: little robots and stuff and other people also want to have remotes for controlling um whole house.
  Kenneth Blais: Mm-hmm.
  David Looper: Yeah.
  Jonathan Kelly: Yeah, so there's a project I think called X_ house or something like that that does that, uh you can integrate your remote with uh computers stuff.
  Kenneth Blais: Mm-hmm.
  Jonathan Kelly: So there is one that is one thing. The other is the the finder feature yeah by whistling or whatever. Uh
  Kenneth Blais: Okay.
  Jonathan Kelly: if you have the finder feature then you can also have uh at the same time as and general voice commands if you want yeah.
  Kenneth Blais: Mm-hmm.
  Jonathan Kelly: So I think it should be a package in that case. Uh so the user interface will consist of two parts. One is the voice command part and on one is the actual buttons part. Uh and th the buttons part would be uh a set of buttons for choosing devices,
  Kenneth Blais: Mm-hmm.
  Jonathan Kelly: a set of buttons for special navigation in space,
  Kenneth Blais: Mm-hmm.
  Jonathan Kelly: a set of buttons for linear access of medium and a set of buttons for random access.
  David Looper: Okay.
  Jonathan Kelly: Yeah?
  Kenneth Blais: What do you mean by linear access then?
  Jonathan Kelly: Like a video tape goes forward, backwards,
  Kenneth Blais: Ah.
  Jonathan Kelly: uh fast and stuff yeah. Um.
  David Looper: Okay so special navigation, linear access, random access and there's a fourth one no?
  Jonathan Kelly: Mm?
  David Looper: So the better now for special navigation?
  Jonathan Kelly: Yeah. For special navigation for example you might have a T_V_ in the menu and you going to
  David Looper: Okay.
  Jonathan Kelly: change yeah?
  David Looper: Then linear
  Jonathan Kelly: Uh.
  David Looper: access then
  Jonathan Kelly: Mm.
  David Looper: random access.
  Jonathan Kelly: Yeah and also parameter
  David Looper: Ah yeah
  Jonathan Kelly: changing.
  David Looper: parameter okay.
  Jonathan Kelly: So if there are common parameters maybe we should put special buttons for that
  David Looper: Okay.
  Jonathan Kelly: um or maybe we could have everything uh generic but uh there are a lot of uh remotes on the market right now
  David Looper: Okay.
  Jonathan Kelly: and basically this is most of the almost everybody has this stuff.
  David Looper: Okay and and voice command did you uh
  Jonathan Kelly: Voice command w we could specify anything. We could assign
  David Looper: Okay.
  Jonathan Kelly: any button a command to any button,
  David Looper: Okay.
  Jonathan Kelly: if we have enough processing power, I guess so. Yeah.
  David Looper: Okay.
  Jonathan Kelly: Yeah.
  David Looper: So that's uh that close your investigations?
  Jonathan Kelly: Yeah. Uh
  David Looper: Okay.
  Jonathan Kelly: yeah I think so. Not so far.
  David Looper: Okay. Maybe we can have a look at the user requirements with
  Kevin Crouch: Yeah. Um I dunno if you open
  David Looper: I dunno if
  Kevin Crouch: the
  David Looper: I can open
  Kevin Crouch: uh
  David Looper: it. Maybe you
  Kevin Crouch: m
  David Looper: can
  Kevin Crouch: is
  David Looper: s
  Kevin Crouch: not here.
  David Looper: It's
  Kevin Crouch: Uh in yeah okay.
  David Looper: Messenger
  Kevin Crouch: No.
  David Looper: no?
  Kevin Crouch: In document. Mm computer yeah.
  David Looper: In which folder?
  Jonathan Kelly: Where did you put it?
  Kevin Crouch: Here. Here.
  David Looper: Short-cut to
  Jonathan Kelly: mm.
  David Looper: AMI
  Kevin Crouch: But it's
  David Looper: shared
  Kevin Crouch: not
  David Looper: folder?
  Kevin Crouch: Um.
  David Looper: Maybe you can send it to Kevin Crouch by email. Just to participant one. At AMI.
  Kevin Crouch: Mm-hmm. Yeah, I can do that.
  David Looper: I will try to show it to everyone, that would be more comfortable.
  Kevin Crouch: Okay. Um.
  David Looper: You send it?
  Kevin Crouch: It's participant one?
  David Looper: Yeah. Uh this is this email.
  Jonathan Kelly: I'm designing the user interface.
  Kevin Crouch: Okay. You can uh.
  David Looper: Okay. So maybe I can switch slides when you
  Kevin Crouch: Yeah.
  David Looper: whenever you ask, that will be more convenient. So okay,
  Kevin Crouch: Okay
  David Looper: functional
  Kevin Crouch: so
  David Looper: requirements.
  Kevin Crouch: you can you can go. Okay so in our usability lab we observed the remote control use among one hundred subjects
  David Looper: Mm. Yeah.
  Kevin Crouch: okay? And here I have the results so you can see that um seventy five per cent of users find most remote controls ugly so we have to find something to make them more more nice, more kind. Eighty per cents of users would spend more money when the remote control would look fancy. Eighty hundred per cent of users would spend more money when the remote control would look oh to it's not good. So okay. So
  David Looper: We
  Kevin Crouch: it's
  David Looper: can
  Kevin Crouch: not
  David Looper: just
  Kevin Crouch: in
  David Looper: keep
  Kevin Crouch: theory
  David Looper: doing
  Kevin Crouch: but
  David Looper: that?
  Kevin Crouch: I I can I can say yeah.
  David Looper: Yeah.
  Kevin Crouch: Fifty f uh seventy five per cent of users say they s zap a lot. So mm we have to have a remote control uh very um out for that. Uh the buttons have are to be um uh uh like you say resist resisting to to shocks.
  David Looper: Okay.
  Kevin Crouch: Um and fifty per cents of users say they only use uh ten per cents of but of the buttons in the
  David Looper: Okay.
  Kevin Crouch: in the remote control. So all the buttons we we have to put are have to to have um a use a real use and not
  David Looper: Okay.
  Kevin Crouch: only or
  David Looper: Okay, so fewer buttons maybe
  Kevin Crouch: Yeah.
  David Looper: would be
  Kevin Crouch: F
  David Looper: good?
  Kevin Crouch: not many buttons, and uh and uh uh u useable buttons.
  David Looper: Okay.
  Jonathan Kelly: But what kind of remote controls did you look at?
  Kevin Crouch: Sorry?
  Jonathan Kelly: What kind of task was it? It was a T_V_?
  Kevin Crouch: Yeah. Uh
  David Looper: Yeah.
  Kevin Crouch: most for most is T_V_.
  David Looper: Yeah but in fact we it it seems that we are going to make a T_V_ remote control according
  Jonathan Kelly: Huh.
  David Looper: to new requirements I received from the management
  Jonathan Kelly: Uh-huh.
  David Looper: bo I will present them in the following.
  Jonathan Kelly: Ah! Good.
  David Looper: Okay.
  Kevin Crouch: 'Kay you can go so. So there are other frustrations expressed by users, so they said uh they lost uh often the remote control in in the
  David Looper: Yeah.
  Kevin Crouch: room so they want to have a way to to
  David Looper: To find
  Kevin Crouch: to
  David Looper: it.
  Kevin Crouch: find it.
  David Looper: Yeah.
  Kevin Crouch: Um and um lot of the time they it takes too much time to learn how to use
  David Looper: Yeah.
  Kevin Crouch: a new remote control. So they want something s
  Kenneth Blais: Mm-hmm.
  Kevin Crouch: really very simple and uh
  David Looper: Okay.
  Kevin Crouch: easy to use. And uh remote controls are bad for
  David Looper: What
  Kevin Crouch: R_S_I_
  David Looper: is her other side?
  Kevin Crouch: um I
  Jonathan Kelly: Other
  Kevin Crouch: dunno.
  Jonathan Kelly: side yeah, yo wa your wrist. It i can become painful you can have tendonditis.
  David Looper: Oh yeah?
  Jonathan Kelly: Yeah.
  David Looper: I did not knew that.
  Jonathan Kelly: If you also up on a computer in a strange position.
  David Looper: Okay so you we have to make it uh more
  Jonathan Kelly: Ergonomic.
  David Looper: ergonomic yeah.
  Jonathan Kelly: But uh. Have
  Kevin Crouch: Yeah.
  Jonathan Kelly: to say ha ha.
  David Looper: It's your job Oh.
  Kevin Crouch: Uh.
  David Looper: Uh sorry got a message from Microsoft.
  Kevin Crouch: Okay um before that I I have some some some thing
  David Looper: Yeah.
  Kevin Crouch: uh to say before
  David Looper: Yeah yeah.
  Kevin Crouch: um We know that uh the user use uh a lot their um remote control um to to change channel.
  David Looper: Yeah.
  Kevin Crouch: Um and um to to change uh volume selection of
  David Looper: Okay.
  Kevin Crouch: the and uh and not uh a lot for setting for
  David Looper: Yeah.
  Kevin Crouch: setting the the channels and uh
  Kenneth Blais: Mm-hmm.
  Kevin Crouch: thing things like that.
  Jonathan Kelly: Mm-hmm.
  David Looper: Okay.
  Kevin Crouch: So it's better to put uh uh uh something very easy to set and uh
  David Looper: Yeah.
  Kevin Crouch: and
  David Looper: This function should be very
  Kevin Crouch: Very
  David Looper: uh accessible.
  Kevin Crouch: accessible yes.
  David Looper: Yeah, okay.
  Kevin Crouch: That's right.
  David Looper: This is the main function okay.
  Kevin Crouch: So then we asked some questions to them and
  David Looper: Yeah.
  Kevin Crouch: um we asked this question if
  David Looper: Yeah.
  Kevin Crouch: they prefer an L_C_D_ screen or on their remultific function remotes control and if they mm pay more for speech recognition in remote control
  David Looper: Yeah.
  Kevin Crouch: and you can go we have here the results of
  Jonathan Kelly: The first question.
  Kevin Crouch: of the questions. So you know that um for the younger it's very important
  David Looper: To have L_C_D_
  Kevin Crouch: to have
  David Looper: and
  Kevin Crouch: the
  David Looper: voice.
  Kevin Crouch: s yes and speech recognition. And uh and the others is not so important but uh we know that uh uh people between fifteen and twenty five are people who watch a lot T_V_ and uh who who wh can use a lot this uh.
  David Looper: Okay.
  Kevin Crouch: So maybe we we can have a speech
  David Looper: Yeah maybe
  Kevin Crouch: recognition
  David Looper: this this
  Kevin Crouch: in.
  David Looper: is important.
  Kevin Crouch: Yeah.
  David Looper: Moreover th maybe those uh like those teenager customer could advice their parents to buy this equipment and
  Jonathan Kelly: Mm.
  David Looper: so we can we have to take care of that point of view I think or so.
  Kevin Crouch: Mm.
  David Looper: Yeah.
  Kevin Crouch: Okay and if there is th the conclusion now. So as we say before, I think uh um a remote control lightening in the dark it's it's a good thing.
  David Looper: Okay.
  Kevin Crouch: Uh not to many mud buttons like we we said before, e
  David Looper: Yeah.
  Kevin Crouch: easy to use uh a way to find it easily in the room and uh uh resistant to to shock and to
  Kenneth Blais: Mm-hmm.
  Kevin Crouch: to
  David Looper: Okay.
  Kevin Crouch: An I s no,
  David Looper: Okay
  Kevin Crouch: yeah.
  David Looper: these are the user
  Kevin Crouch: I dunno
  David Looper: requi
  Kevin Crouch: if you see something else important or
  Kenneth Blais: I'm just thinking of some thing.
  Kevin Crouch: Mm.
  David Looper: Yeah.
  Kenneth Blais: Um We want to have a no, I know if a idea. We want to have a a general remote control for everything.
  David Looper: No no no. We w it seems that we no want to have a T_V_ remote control.
  Kenneth Blais: Okay.
  David Looper: From
  Jonathan Kelly: Mm.
  David Looper: the management board I receive
  Kenneth Blais: Yeah.
  David Looper: an email. Cos it would be costly uh and and also it it would take more time to develop to
  Kenneth Blais: Yeah.
  David Looper: have
  Kenneth Blais: Yeah
  David Looper: a
  Kenneth Blais: yeah.
  David Looper: a general generic remote
  Kenneth Blais: Yeah.
  David Looper: control.
  Jonathan Kelly: Mm I it's not true I think. The
  Kenneth Blais: No no.
  Jonathan Kelly: the second claim that you put.
  David Looper: That it would be too long to
  Jonathan Kelly: Yeah.
  David Looper: develop.
  Jonathan Kelly: I think that should be the same.
  David Looper: Oh yeah. Because I received that email from management board and they seems to tell that that if we want to be on the market as early as possible we should uh focus on T_V_ more where it seems that the market is more important. So maybe it's a good decision. I dunno. What's your
  Jonathan Kelly: I have
  David Looper: opinion?
  Jonathan Kelly: uh I've no idea I mean I should know a bit more about how fast we can uh design it. I don't think Uh yeah.
  Kenneth Blais: Finish tonight.
  Jonathan Kelly: Yeah. Okay.
  Kenneth Blais: But basically yeah
  Jonathan Kelly: Yeah.
  Kenneth Blais: maybe I can continue with my presentation, it would be
  David Looper: Okay.
  Kenneth Blais: al
  Kevin Crouch: Yeah.
  Kenneth Blais: you
  Jonathan Kelly: Yeah.
  Kenneth Blais: you but I think we have some technical problem or so. So I'm just going to describe briefly what we do in the remote control.
  David Looper: Maybe
  Kenneth Blais: If
  David Looper: you can
  Kenneth Blais: fact
  David Looper: go to the whiteboard if you have some drawings to do I
  Kenneth Blais: Yeah
  David Looper: don't
  Kevin Crouch: Mm.
  David Looper: know.
  Kenneth Blais: but Do I have oh yeah. Now I have enough cables.
  Jonathan Kelly: Like a you feel a bit like a dog with this stuff.
  Kenneth Blais: Okay so I'm just going to describe in fact for for a remote control this is quite easy. We just have sorry, I'm going
  David Looper: Okay. Are you okay?
  Kenneth Blais: Like that. I'm just going to describe. Basically we have a a battery a power supply here. After that we just have um user interface. Let's say that um something like that, which could be um a L_C_D_ let's say or um an array of push button, something like that. Push button or a L_C_D_. After that we we feed that into um uh an electronic chip. So I say U_C_ and I feed that to uh L_E_D_ which is uh infrared um which is a an infrared um component. And so what we for for myself this for for us this is quite easy.
  David Looper: U_C_ is the central unit?
  Kenneth Blais: Yeah.
  David Looper: Okay
  Kenneth Blais: Y
  David Looper: yeah.
  Kenneth Blais: it's a it's this just a chip which does all the um numerical
  David Looper: Computation.
  Kenneth Blais: numerical computation
  David Looper: Okay.
  Kenneth Blais: according to your display. And so for us uh this is quite easy. We just need to take to define what we want to do when the user interface um wants something and after that we just do the coding to s and send that to to to the not the to the television.
  David Looper: Okay.
  Kenneth Blais: So for us this is quite easy.
  David Looper: Okay so this is quite easy.
  Kenneth Blais: Yeah. Um
  David Looper: There is not that much
  Kenneth Blais: we just
  David Looper: constraints.
  Kenneth Blais: have to define the processing power that we need uh especially if we want to do some uh speech recognition, in that case that mean that we are going to use more
  Jonathan Kelly: This
  Kenneth Blais: for simple
  Jonathan Kelly: will think this will take more time to develop
  Kenneth Blais: Yeah
  Jonathan Kelly: also.
  Kenneth Blais: of course of
  Jonathan Kelly: Yeah.
  Kenneth Blais: course. And um but for a standard one this is really easy. It's a question of one
  Jonathan Kelly: Soon.
  Kenneth Blais: month and so
  David Looper: To
  Kenneth Blais: on
  David Looper: have a
  Kenneth Blais: s
  David Looper: you s you speak about with voi voice control?
  Kenneth Blais: No no no no, I say
  David Looper: Standard button one.
  Kenneth Blais: yeah standard uh standard remote control takes maybe uh one month to to do that.
  Jonathan Kelly: Yeah. So the only time problem is the sp voice recognition.
  Kenneth Blais: Yeah.
  Jonathan Kelly: Yeah.
  Kenneth Blais: Definitely.
  Jonathan Kelly: Yeah.
  David Looper: So do you have any idea of how long it would take to have voice recognition now?
  Kenneth Blais: I would say.
  Jonathan Kelly: Ten years.
  Kenneth Blais: I would say uh about eight months to have the first results.
  David Looper: Okay so i it's a bit long yeah.
  Kenneth Blais: Yeah. I can Um.
  David Looper: One month for the standard one with button.
  Kenneth Blais: Yeah.
  David Looper: Even if we have a L_C_D_ display?
  Kenneth Blais: Yeah even. I mean that this is really standard devices now. Um eight. For uh speech recognition.
  David Looper: Okay yeah. Okay so we can take this into account. So who think it would be good to go for uh like speech recognition?
  Jonathan Kelly: But we don't have time to market.
  Kenneth Blais: And also
  David Looper: Yeah it
  Kenneth Blais: how
  David Looper: will.
  Kenneth Blais: much uh I think
  Jonathan Kelly: I think we should contact
  Kenneth Blais: during
  Jonathan Kelly: management.
  Kenneth Blais: the kickoff meeting you say that we we shouldn't we shouldn't go up to twelve point five Euro
  David Looper: Euros.
  Kenneth Blais: per
  David Looper: Yeah,
  Kenneth Blais: unit
  David Looper: yeah.
  Kenneth Blais: so how many units should we sell to have a
  Jonathan Kelly: Well.
  David Looper: Well
  Jonathan Kelly: Uh
  David Looper: each unit is is sell uh twenty five Euros.
  Kenneth Blais: Yeah but how many yeah.
  Jonathan Kelly: How muc how much do you get how much do you if you buy one million units h no, one hundred thousand units. Eh chips. We're gonna need chips right.
  Kenneth Blais: Yeah.
  Jonathan Kelly: Yeah. How much will it cost for one hundred thousand?
  Kenneth Blais: Usually this is less tha at two dollars per chip.
  Jonathan Kelly: Okay.
  David Looper: Because
  Jonathan Kelly: So
  David Looper: we
  Jonathan Kelly: you
  David Looper: are
  Jonathan Kelly: have any idea for a powerful one that has uh good enough for do speech recognition.
  Kenneth Blais: Yeah,
  Jonathan Kelly: Yeah? Okay.
  Kenneth Blais: we can
  Jonathan Kelly: So. No
  David Looper: It
  Jonathan Kelly: it
  David Looper: seems
  Jonathan Kelly: doesn't.
  David Looper: that that we want to sell like four million units from the
  Kenneth Blais: Mm-hmm.
  David Looper: first meeting.
  Jonathan Kelly: Okay. Four million.
  David Looper: Okay.
  Kevin Crouch: Mm.
  Kenneth Blais: Um I just had a question uh do you want to continue with your presenta?
  David Looper: Yeah
  Kenneth Blais: Is
  David Looper: I
  Kenneth Blais: it
  David Looper: I will continue. Well ask your question if you want.
  Kenneth Blais: Um you say that I don't remember by heart but thirty per cent
  Kevin Crouch: Mm?
  Kenneth Blais: of the tested people say that's it's quite difficult to to to use the remote control.
  Kevin Crouch: Yeah.
  Kenneth Blais: Do they say that this is difficult but for the same reason or do they have other reason?
  Kevin Crouch: Oh.
  Kenneth Blais: To to
  Kevin Crouch: Would j
  Kenneth Blais: maybe to keep in mind maybe to access to that menu you should do something like
  Kevin Crouch: Uh
  Kenneth Blais: that.
  Kevin Crouch: yeah w I I think they they say that it's uh difficult to learn how to use it
  Kenneth Blais: Mm-hmm.
  Kevin Crouch: but i when you know how to use it,
  Kenneth Blais: Mm-hmm.
  Kevin Crouch: it's it's
  David Looper: Okay.
  Kevin Crouch: okay.
  Kenneth Blais: And
  Kevin Crouch: But
  David Looper: It's not intuitive first.
  Kevin Crouch: Yeah.
  Kenneth Blais: But yeah maybe and what about if we design a remote control which can be configure as you want? You say that I want, I have six
  Jonathan Kelly: Mh-hmm.
  Kenneth Blais: button
  Jonathan Kelly: A a lot of people are uh if you have the L_C_D_ screen
  Kenneth Blais: Yeah.
  Jonathan Kelly: if you can
  David Looper: Yeah.
  Jonathan Kelly: do it completely the way you want because the buttons also look
  Kenneth Blais: Yeah.
  Jonathan Kelly: the way
  David Looper: But,
  Jonathan Kelly: you want them
  David Looper: but also
  Jonathan Kelly: but
  David Looper: it seems
  Jonathan Kelly: it will be
  David Looper: that
  Jonathan Kelly: hard to configure I mean imagine
  Kenneth Blais: Yeah.
  David Looper: Yeah.
  Jonathan Kelly: i uh so it's really something for the expert user.
  Kenneth Blais: Okay.
  Jonathan Kelly: So I mean there are markets and markets. I think the young people are th uh are uh Christine here said uh
  Kenneth Blais: Yeah.
  Jonathan Kelly: you have a
  David Looper: Yeah.
  Jonathan Kelly: uh it is yeah. So for our young people uh it will be cool, they can be able to use it. Th maybe their parents will not but they will configure it. I guess.
  David Looper: Yeah.
  Kenneth Blais: Mm-hmm.
  David Looper: Maybe it would be more complex to
  Kevin Crouch: Mm.
  David Looper: configure it
  Kenneth Blais: Yeah. Yeah.
  David Looper: to be simple
  Kenneth Blais: Yeah.
  Jonathan Kelly: Mm.
  David Looper: than
  Kevin Crouch: Mm.
  David Looper: creating a simple product.
  Jonathan Kelly: And there
  Kenneth Blais: Yeah.
  Jonathan Kelly: are another thing is that if we make something that's simple and easy to use that's bas to use immediately that means that it will be exactly the same as everything else.
  Kenneth Blais: Yeah.
  Jonathan Kelly: All right?
  Kenneth Blais: Yeah.
  Jonathan Kelly: Otherwise, if it's different then of course everybody has somebody has to learn to use it first.
  Kenneth Blais: Yeah.
  David Looper: Yeah. But also we we see that that most people find it find remote controls too complex because they have too many buttons and they mainly use only channels
  Kevin Crouch: Mm.
  David Looper: and
  Jonathan Kelly: Mm-hmm.
  David Looper: volume buttons. So we may just uh make a very easy to use remote control with mainly those buttons
  Jonathan Kelly: Yeah.
  David Looper: and maybe also um some lightning stuff too because most people find also hard to to find the remote control. Losed
  Jonathan Kelly: Mm-hmm.
  David Looper: lose it etcetera. These these are these two points are the main frustrations so maybe if we design something very simple and easy to uh find when lost it will uh add uh a serious competitive advantage without
  Kevin Crouch: Mm.
  David Looper: making something too complex and too long to develop.
  Jonathan Kelly: Mm-hmm.
  David Looper: So but le let us see first the new requirement. So we don't have to so this this uh is uh is um in the this is in the same direction as we were speaking so we don't have to make a very complex remote controls to access teletext and stuff like that
  Jonathan Kelly: But teletext is just one button.
  David Looper: Yeah but then you have to you have to define the buttons to surf
  Jonathan Kelly: You
  David Looper: amongst
  Jonathan Kelly: you
  David Looper: pages
  Jonathan Kelly: just write
  David Looper: and stuff.
  Jonathan Kelly: the write the numbers.
  David Looper: Yeah. So
  Jonathan Kelly: So will
  David Looper: well
  Jonathan Kelly: you add with the channel keys, right?
  David Looper: Yeah.
  Jonathan Kelly: So.
  David Looper: So anyway we don't have to include this feature because it's it's not used any more by users, they prefer to s
  Jonathan Kelly: I am. I'm sure that uh it don't like but uh I don't see just one button.
  David Looper: Yeah.
  Jonathan Kelly: So.
  David Looper: I dunno. If i one button is still one more button. If if if we want to make it very simple we have to reduce number of buttons compared to th to our competitors.
  Jonathan Kelly: Mm-hmm.
  David Looper: Well anyway I have this point. We can discuss. Also um so as as I told before uh it would be better if it's only for the T_V_ um because we want to be quick on on the market. And then also we have to make very uh uh clear that this uh this remote control is is part of of our products and show our corporate uh logo and and colours on the on the design as well so that uh they identify it as one of our product. So this is the the key point. So before uh finishing we can uh define uh what would be the characteristic of the o th of the control of the remote control and which button do we need which function do we want etcetera.
  Jonathan Kelly: Capital.
  Kevin Crouch: Mm.
  David Looper: So do you um so so from from the Kevin Crouch I think a key aspect is the easy to use aspect, it should be
  Kevin Crouch: Mm.
  David Looper: very simple and most button are never used only ten per cent of the button are are used often so I think we have to do something very simple and I think we all agree on that point,
  Kenneth Blais: Mm-hmm.
  David Looper: no?
  Kevin Crouch: Mm.
  Jonathan Kelly: Well if it is going to be just a T_V_ remote control it is going to be very simple.
  David Looper: Yeah okay. So yeah the key point here is simple. Maybe. So few buttons, channel, volume control and what el what function do you see
  Jonathan Kelly: Well if it's
  David Looper: in addition
  Jonathan Kelly: going to
  David Looper: to
  Jonathan Kelly: be
  David Looper: that?
  Jonathan Kelly: as simple as possible then just have the remote control, there is no other function that I can see really.
  David Looper: Yeah. Maybe switch T_V_ on and off
  Jonathan Kelly: Uh no you want to keep television on so that the advertising can revenue can come back to us. Or
  David Looper: Yeah.
  Jonathan Kelly: something.
  David Looper: Yeah. Volume, maybe a mute button, and then
  Kenneth Blais: Mm.
  David Looper: on off button. And that's all?
  Kenneth Blais: Uh I know that som you say that many people are doing plenty of a lot of zapping.
  Kevin Crouch: Mm-hmm.
  David Looper: Mm.
  Kenneth Blais: I know tha I discovered that when I did a quick look, uh they do now som they do something which is quite nice now,
  Jonathan Kelly: It's
  Kenneth Blais: you have a
  Jonathan Kelly: a
  Kenneth Blais: button,
  Jonathan Kelly: memory,
  Kenneth Blais: you
  Jonathan Kelly: yeah.
  Kenneth Blais: you press it, and this is uh the previous channel which
  David Looper: Okay.
  Kenneth Blais: has come back.
  David Looper: Yeah this is cool. Maybe we can include that also. Previous previous channel button. So we have like channel button, the previous channel button, the
  Kenneth Blais: Mm-hmm.
  David Looper: volume button, plus a mute button,
  Kenneth Blais: Mm-hmm.
  David Looper: and uh just the the traditional on off
  Kenneth Blais: Mm-hmm.
  David Looper: button.
  Jonathan Kelly: And uh and of course the channel changing buttons.
  David Looper: Yeah. I I talk
  Jonathan Kelly: How
  David Looper: about that,
  Jonathan Kelly: should they
  David Looper: yeah?
  Jonathan Kelly: how should we implement that? Because uh could be numerical only or could be also incremental.
  David Looper: Yeah. Incremental definitely because zapping you you switch
  Jonathan Kelly: Mm-hmm.
  David Looper: them.
  Kenneth Blais: Let's say that we can do something like that. This is uh incremental, but once you press it for a long time, you go five by five.
  David Looper: We go
  Kenneth Blais: To
  David Looper: faster?
  Kenneth Blais: go fa to go faster.
  David Looper: Mm.
  Jonathan Kelly: Mm. It's an interesting idea, that if you press it for a long time it does something else, in general. So if you you have your ten buttons for the for the numeric the numerical buttons and you have instead of having just one memory
  Kenneth Blais: Yeah.
  Jonathan Kelly: you have if you press them for a long time No. Doesn't work does it.
  David Looper: Maybe we should have also a digit
  Jonathan Kelly: Maybe
  David Looper: button
  Jonathan Kelly: we should have a complete keyboard and just type console commands.
  David Looper: Yeah.
  Jonathan Kelly: Change channel to eight. No.
  David Looper: Maybe we have also to have digits or only incremental. I dunno bec because
  Jonathan Kelly: Well
  David Looper: if
  Jonathan Kelly: if
  David Looper: you
  Jonathan Kelly: it's
  David Looper: have the
  Jonathan Kelly: useful like if if you want to change between three channels for example then you h
  David Looper: Uh.
  Jonathan Kelly: you cannot you cannot cannot work with just memory being incremental.
  David Looper: Yeah. Because you have your previous channel button if you have incremental only it's
  Kenneth Blais: Yeah.
  David Looper: not uh it isn't worth it because the previous channel is eith either minus one or plus one.
  Jonathan Kelly: Yeah. Yeah.
  David Looper: So I think we need also digits.
  Kenneth Blais: Okay.
  David Looper: Maybe we we can make very obvious the channel and volume button button and smaller button down there with the the digits.
  Jonathan Kelly: Yeah when you zap usually you will have to press the same button all the time
  David Looper: Yeah.
  Jonathan Kelly: and
  Kenneth Blais: Or we can do something like that. We can
  Jonathan Kelly: Yeah.
  Kenneth Blais: design the remote control to have access. You know some remote control have uh protection
  Jonathan Kelly: Mm-hmm.
  Kenneth Blais: and so you you y
  David Looper: Yeah.
  Jonathan Kelly: Hey
  Kenneth Blais: You
  Jonathan Kelly: I just thought this thing there is a I mean you know there is are some with a wheel like this. Instead of having the up down buttons for
  David Looper: Yeah.
  Jonathan Kelly: uh
  Kenneth Blais: Yeah,
  Jonathan Kelly: you can have
  Kenneth Blais: a kind
  Jonathan Kelly: the wheel.
  Kenneth Blais: of joystick.
  Jonathan Kelly: Yeah.
  David Looper: Yeah. Maybe we can have a wheel for incremental.
  Jonathan Kelly: Yeah.
  David Looper: Okay. So have a wheel for incremental, have the digits uh on the lower side that can be closed so as
  Kenneth Blais: Mm-hmm.
  David Looper: you say protected,
  Jonathan Kelly: Mm-hmm.
  David Looper: and uh yeah I think this is
  Jonathan Kelly: On
  David Looper: the
  Jonathan Kelly: the lower
  David Looper: basi
  Jonathan Kelly: side I think it you have to turn it. No?
  David Looper: And do
  Jonathan Kelly: If
  David Looper: we
  Jonathan Kelly: we do
  David Looper: do
  Jonathan Kelly: that.
  David Looper: we have a
  Kenneth Blais: Or a or a ball, yeah, not a a wheel but a ball, and you say uh
  David Looper: No, a wheel is
  Jonathan Kelly: Yeah.
  Kenneth Blais: to
  David Looper: better. I would say the wheel is better.
  Jonathan Kelly: Because
  David Looper: What
  Jonathan Kelly: of
  David Looper: is
  Jonathan Kelly: that
  David Looper: the expert of uh
  Kenneth Blais: Yeah.
  Jonathan Kelly: Because it's uh it's it's not like a volume which is smooth yeah? The channels change one by one.
  Kenneth Blais: Yeah.
  Jonathan Kelly: So you have to the user has to like to should feel the the
  Kenneth Blais: Yeah,
  Jonathan Kelly: the discrete
  Kenneth Blais: the yeah.
  David Looper: Okay.
  Jonathan Kelly: sense a bit.
  David Looper: Yeah.
  Jonathan Kelly: Yeah.
  David Looper: That's a good idea. Well also we have to decide uh so it should be lightening in the dark I think because most people lost their remote
  Kenneth Blais: 'S quite
  David Looper: control.
  Kenneth Blais: it's quite easy we do
  David Looper: Okay.
  Kenneth Blais: that w with back light on
  Jonathan Kelly: Yeah.
  Kenneth Blais: the
  Jonathan Kelly: Even
  Kenneth Blais: on
  Jonathan Kelly: if
  Kenneth Blais: the
  Jonathan Kelly: i
  Kenneth Blais: wheel.
  Jonathan Kelly: L_E_D_ uh or a if if it's the L_C_D_
  Kenneth Blais: A blue
  Jonathan Kelly: feature uh
  Kenneth Blais: a blue L_E_D_
  Jonathan Kelly: whatever,
  Kenneth Blais: and
  Jonathan Kelly: yeah.
  David Looper: Yeah,
  Kenneth Blais: we sell that
  David Looper: and
  Kenneth Blais: um.
  David Looper: do we put
  Jonathan Kelly: Yeah.
  David Looper: an L_C_D_ display? Because it was important for young customers if you remember.
  Jonathan Kelly: I think it's only put on if cou have multi function.
  Kenneth Blais: Yeah.
  Jonathan Kelly: If you do not multi function then there is no p point in having L_C_D_. Just increase the cost.
  David Looper: Okay.
  Jonathan Kelly: The user does not have an advantage really.
  David Looper: So no L_C_D_?
  Kenneth Blais: Mm-hmm.
  Kevin Crouch: Hmm.
  David Looper: And so no speech as well because it w it would delay too much the
  Kenneth Blais: Okay.
  David Looper: development
  Jonathan Kelly: Well if it's going
  David Looper: process.
  Jonathan Kelly: to delay yeah but uh it will be cool. It would. Because a user could say C_N_N_ for example and it would go
  Kevin Crouch: Mm-hmm.
  Jonathan Kelly: C_N_N_. Mm.
  David Looper: Yeah. That would be cool. But
  Jonathan Kelly: Yeah.
  David Looper: eight months is really long and Maybe we can just uh
  Kenneth Blais: Ten years
  David Looper: Okay. So um I I will uh I will so I we will move to next meeting so in after the lunch break
  Kenneth Blais: Mm-hmm.
  David Looper: uh here are the individual uh action uh you are required to do but you will be uh recalled to the actions by uh email I think but you can take notes if you if you want but well the instruction will be sent. So thank you for uh your
  Kenneth Blais: Okay.
  David Looper: suggestion and I I will make a summary of that meeting that I will put in the shared folder you
  Kenneth Blais: Okay.
  David Looper: can't see
  Kenneth Blais: Okay.
  David Looper: and uh and then you will um you will be able to to see what has been uh has been said on on this meeting and and what has been decided. Uh maybe for next meeting uh send Kevin Crouch your presentation before by email so that we can see them uh altogether.
  Jonathan Kelly: Yeah.
  David Looper: That
  Kevin Crouch: Mm.
  David Looper: would be easier.
  Jonathan Kelly: What is the folder that you put yours in? And did it it did work?
  Kevin Crouch: No.
  David Looper: No it did
  Kevin Crouch: No
  David Looper: not
  Kevin Crouch: no.
  David Looper: work. She send
  Jonathan Kelly: Ah
  David Looper: it
  Jonathan Kelly: yeah.
  Kevin Crouch: I dunno,
  David Looper: to Kevin Crouch by
  Jonathan Kelly: Mm.
  David Looper: email.
  Kevin Crouch: I dunno it.
  Jonathan Kelly: Okay.
  David Looper: So maybe this is better, to send it by email.
  Jonathan Kelly: Okay what
  David Looper: Okay?
  Jonathan Kelly: is your email?
  David Looper: So yeah I I'm it's in the first uh email so I'm participant one
  Jonathan Kelly: At participant
  David Looper: at AMI
  Jonathan Kelly: one. Okay.
  David Looper: uh where is that, it's here. Participant one at AMI. Okay. So see you after lunch break.
  Kevin Crouch: 'Kay
  Jonathan Kelly: Well
  Kevin Crouch: thank
  Jonathan Kelly: during
  Kevin Crouch: you.
  Jonathan Kelly: lunch break actually.
  Jonathan Kelly: So next time we should have a fight. How about uh management or something. Who happens to be your friend.
Updated Content: Jonathan Kelly presented the major components of the interface design, dividing the interface into two parts: voice commands and buttons. Kevin Crouch went over users' requirements as seen in a company study and showed that the major complaint was that remotes were too difficult to use. She also showed that users want fancier and more ergonomic designs, shock protection, voice recognition, and LCD screens. David Looper announced a new requirement to the group, that the remote is only to control televisions. Kenneth Blais gave a layout of the internal functions of the device and showed that a standard chip, instead of a larger one that would accomodate voice recognition, would be the most feasible. David Looper announced also that the group was not to include a teletext function and that they should integrate the company logo into the external design. The group decided on what button functions should be included and decided to eliminate the LCD screen and voice recognition from the design due to time and cost restraints.