00:49 |
# Good to see you all again. Let's see if that comes up.
|
00:58 |
This is our functional design meeting.
|
01:01 |
Um.
|
01:03 |
Just a sec while my PowerPoint comes up.
|
01:06 |
^Et voila^.
|
01:11 |
Okay. Mm um we put the fashion in electronics.
|
01:15 |
Let's start. Okay, our agenda today um - just check the time, it's twelve thirteen.
|
01:23 |
Um.
|
01:25 |
I'm gonna do an opening, talk about um - did you all get the minutes? I e-mailed them to you. I'm also putting 'em - them in the shared folder. So um then I - we'll talk about our general objectives and have your three presentations. Um I'll talk about the new project requirements I've just received, and then we have to make a decision on our remote control functions. Finally we'll just close. We're starting this meeting at approximately twelve thirteen and we have forty minutes. So -
|
01:29 |
Yep.
|
01:31 |
Right.
|
01:51 |
First of all the functional design objectives. Uh we need to keep in mind the user requirement specification, what needs and desires are to be fulfilled, the @ functions design, what effects the apparatus should have, and the working design, how the apparatus actually works to fulfil its function.
|
02:10 |
Okay, three presentations, um you can go in any order you choose um.
|
02:13 |
@
|
02:15 |
Mm shall we go in the order that you just did it?
|
02:18 |
Sure, please do.
|
02:19 |
I dunno.
|
02:22 |
How do I hook my screen up?
|
02:28 |
I think, you might have to disconnect Rose.
|
02:29 |
Yes I do.
|
02:41 |
Yeah.
|
02:48 |
Well there's a wee a wee plug just just that one there
|
02:49 |
Where does it go? Mm-hmm.
|
02:52 |
Hmm, I'm not supposed to move this, but -
|
02:54 |
$
|
02:57 |
Ah that's it, yep.
|
03:01 |
@
|
03:06 |
And then you have to press function F_ eight I think it is on your laptop.
|
03:09 |
Function, F_ eight, yeah.
|
03:13 |
Where's function?
|
03:13 |
The blue one, F_N_.
|
03:27 |
No signal.
|
03:29 |
Is it plugged in all the way and you screwed it in and -
|
03:32 |
Ah, wait, 's screw in.
|
03:32 |
Yeah.
|
03:35 |
I I think you just have to push it in really hard.
|
03:35 |
Push the screw.
|
03:40 |
That's it.
|
03:40 |
Oh, got it.
|
03:42 |
Mm 'kay. It's taking it a little bit -
|
03:42 |
Mm alright
|
03:45 |
I've never attached to anything.
|
03:47 |
Mm, neither have I.
|
03:49 |
'Kay there you go.
|
03:51 |
Alright, so, I don't know if you guys are able to get access to um the report that was online or if I'm the only one who is.
|
03:51 |
Alright.
|
04:01 |
But, I don't even know how to play this.
|
04:06 |
No.
|
04:07 |
Press the little presentation. It's the um - it looks like a Y_ kind of - over there above Draw.
|
04:14 |
There, that one, there you go.
|
04:16 |
Alright. So we're just gonna talk a little bit about the functional requirements that people specified when they were asked. Um I guess Real Reaction did some market research. They had a hundred subjects and their usability lab and they watched them watch T_V_ and recorded the frequency that they used particular buttons and the relevance that those buttons had.
|
04:45 |
What they found was they analysed people's desires and needs. Focusing on their desires, um people specifically said that they thought remotes were ugly $, seventy five per cent of the a hundred subjects noted that and that they - more importantly though, eighty per cent said that they would be willing to pay more for a fancier looking remote. I don't know anything beyond what fancy means, but that's particularly of use to us, I think. Um also they did some questions on voice recognition and found that the desire for voice recognition was inversely related to age, so younger people were more inclined to want something with voice recognition, whereas the older people in the like sixty and above segment or so did not really think that they would pay more money for voice recognitions.
|
05:06 |
Hmm.
|
05:37 |
'Kay.
|
05:37 |
Um people also had certain frustrations, that I think that we could try to take into consideration with
|
05:45 |
our design. That being people k- um frustrated with losing their remotes. I think, over fifty percent of the people mentioned that that was their biggest frustration. People are also frustrated with the difficulty it is to learn how to use a remote and I think that ties back to what you were saying before just that there's too many buttons, it just needs to be easy to use. It also mentioned something called R_S_I_ and I was hoping someone might be able to inform me as to what R_S_I_ is, because I don't know.
|
06:04 |
Hmm.
|
06:14 |
Repetitive strain injury.
|
06:16 |
What?
|
06:17 |
Repetitive strain injury.
|
06:17 |
@
|
06:18 |
Ah. There we go. Wow. People do not like that. So I guess sort of the carpal tunnel type thing, people do not like that, um the repetitive use, I guess, caused a strain. Um looking at the needs people specified, the problem right now is that people's remotes are not matching their operating behaviour. People are only using ten per cent of the buttons that they have offered to them on their remote.
|
06:20 |
So if you -
|
06:45 |
And what people do most often is changing the channel and changing the volume. People also zap like to change the channel, about um sixty five per cent during an hour of use. So we really just need to focus in on those volumes and channel changers rather than things like the audio settings, the screen settings and the channel settings, because they're used much more infrequently and probably just complicate what's going on.
|
07:15 |
So I think that some things that we might wanna think about, the idea of an L_C_D_ screen was brought up although they didn't have any details on
|
07:23 |
what people's preferences on that were, so I dunno know if that's coming to me later, or something like that. But something for us to consider also just the phenomenon that less is more when it comes to the buttons on the remote or what we wanna make easiest to use, make sure that, you know, something like an audio setting isn't given as much importance and visibility on the remote as something like channel changing that's used a lot more often. And basically in order for us to win over to the consumer we just need to focus on what it looks like, that it has a fancy appeal and that it's not ugly $ and that it feels like the way they're gonna use it, so it doesn't give them any hand injuries or things like that.
|
08:05 |
Hmm.
|
08:09 |
Thank you very much. That was that was great. Um # 's move on to the next presentation um on effects. Was that you? Great.
|
08:10 |
Mm 'kay.
|
08:17 |
Hmm.
|
08:21 |
Yeah, have I unscrewed it?
|
08:26 |
Push.
|
08:27 |
User interface, right.
|
08:28 |
User interface, right.
|
08:30 |
Interface.
|
08:36 |
Here we go.
|
08:38 |
Cheers.
|
08:38 |
Mm-hmm.
|
08:44 |
And I think that's in the shared, if I did it right, if anyone wants to look at it.
|
08:47 |
Mm 'kay, thank you.
|
08:48 |
Okay, great.
|
08:51 |
%
|
09:23 |
Okay.
|
09:24 |
Here we go.
|
09:29 |
Right so I'm gonna talk about the technical technical functions design of the remote control um.
|
09:38 |
We need to start by considering what a remote control actually is. It's a device that allows us to produce certain effects on our television, so i- it's basically a communication device. We we tell the remote control what we want to do, it sends a message to the television saying change the channel, change the volume, uh yeah, adjust these settings, adjust the brightness.
|
10:05 |
Um how do we actually go about designing a new television remote control?
|
10:10 |
First thing to do is to come up with the design specifications. We need to know what our final product is gonna be like, so we need a a clear idea of exactly what this product does, uh how it works, and what the end-user is gonna want from this product.
|
10:27 |
Um.
|
10:29 |
Oh, a way I'd suggest that we could go about this is by designing uh several different prototypes of user interfaces for this product, um and then uh trying to get some feedback uh about
|
10:43 |
%
|
10:44 |
h- how well these particular prototypes work, uh sorta find out what people think of 'em. Um using a remote control is is quite a subjective experience. Um,
|
10:55 |
Hmm.
|
10:57 |
and different different people sort of prefer different things.
|
11:01 |
Um we should remember that remote controls are a a fairly standard piece of equipment. When a users using a remote control, he or she expects the buttons to be in certain places. So in some sense we're gonna we're gonna have to aim for a device which is fairly conventional in design uh so that we're not completely shocking people. But I think within that there is also room for us to introduce novel ideas uh and to make something that's that's perhaps a little bit different, something that stands out.
|
11:33 |
Um also in in designing the user interface we need to consider practicalities. Uh the first of these is is technological ye- uh what can we do with the current state of technology as it is. The second is is economic, uh we need to find a balance between features and price. So as you mentioned things like voice recognition would would add to the price uh but it would also im- improve the design of the product.
|
11:55 |
Hmm.
|
11:59 |
So I had a look on the - on the web uh to see if I could find a few examples of existing television remote controls. In analysing these we can consider what what things - what's good about them, uh what things do they get right, what's bad about them, what's wrong with 'em, um how we can improve on the designs that that that I found and what can we do to make our product stand out from from the large majority of remote controls.
|
12:29 |
Here's two examples uh probably at the extreme ends of the spectrum. Um on the left here we've got uh an engineering-based design for a remote control, so it's one that's got lots of buttons, it's it's fully featured, everything you might possibly want to do is there, you know, it's got forward, backwards, up, down, channel numbers, volume, uh freeze frame. Yeah, it's it's fully featured and it might take a while to get to learn to use it, but once you've learned it you can - you can do whatever you want with your T_V_.
|
12:34 |
$
|
12:35 |
$
|
13:02 |
The one on the right is a lot more basic. It's just got the essential functions of the T_V_ changing the channel, play, stop, volume. It would be a lot quicker to learn to use it, but again th- it's it's swings and roundabouts. There are disadvantages, you can't use it say to to freeze the television picture. Uh there's a lot of features that are missing from that remote control. So we've got to to find our - find a way of striking a balance between the two.
|
13:29 |
Um as I said before, remote controls are subjective, different people want want different things. Um personally wa- what I want from a remote control is a device that's simple, it it's easy to use, uh it's got big buttons for doing the things I do most often, changing the volume, changing the channel. It it does everything that I need it to uh, as I said before, I'm quite lazy, I don't wanna walk across the room just to adjust my television. I also want something that that looks cool, um and that that feels good, that's ergonomically designed.
|
14:08 |
Mm 'kay. Thank you very much. That was very useful. $ It's funny to see the # drastic difference between those two remotes. # Um.
|
14:16 |
Hmm.
|
14:18 |
And neither of them were very pretty, you know?
|
14:19 |
No.
|
14:20 |
Yeah. I think that could be our selling point.
|
14:20 |
$
|
14:23 |
Mm.
|
14:23 |
A fashion fashion remote.
|
14:25 |
I think there's there's certainly a market for technology that looks cool. And I think that's that's why companies like Apple've 've 've made a lot of progress.
|
14:25 |
Right.
|
14:28 |
Mm.
|
14:29 |
Mm-hmm.
|
14:32 |
Hmm. Right, I really can't see what I'm doing, so does anyone have a -
|
14:32 |
Yeah.
|
14:38 |
You - there it is.
|
14:48 |
Ah-ha, look at that, showing up already.
|
14:52 |
Lovely.
|
14:52 |
So wait, did it let you go on the Internet or was that just what it let you see?
|
14:55 |
Uh that was just on the d- on the company web site, yeah.
|
14:57 |
Okay. 'Cause I was like googling* and then I'm like wait $ it won't let me google*. $
|
14:59 |
Hmm.
|
14:59 |
Yeah.
|
15:00 |
$
|
15:02 |
Alright um -
|
15:06 |
No, how do I play again?
|
15:09 |
Um the - it's right above Draw. There are three thingy- if - it's way at the bottom. Under three icons and it's the one that looks like a desk. Yeah, that one. There are Y_s @.
|
15:14 |
Ah.
|
15:19 |
Okay. So this is our working design presentation. Um I had a bit of - some issues with this, because I wasn't able to find everything I needed, but I guess that's - we're still in early stages. Um so, yeah, this is this. Though th- the thing about working design is the - what we're trying to do as a working design is figure out how the aparata- apparatus can fulfil its function.
|
15:45 |
Um one of the examples that kept coming up for me is that a coffee grinder. It works because it converts electrical energy to grinding the beans and then you put the bean through a filter and that filters out, and then you get coffee at the end that's nice and hot because of the combination of electrical energy and then the other things that are brought in to make it work. Don't know if I'm explaining that very well, but - how do I get to the next s- ah.
|
16:11 |
So h- the method as um working designers figure out what you need to make it fulfil this practical function, what what needs to be done and how do we convert all the elements to make that done. So wha- the easiest thing to do is to break down all the points
|
16:22 |
%
|
16:30 |
at which you need something to happen. So you make a schematic of the way that the the energy is converted
|
16:38 |
tsh- towards this practical function. And then I think the easiest thing to do is gonna be work on each task separately. So um -
|
16:48 |
Uh. Uh.
|
16:48 |
You just press - yeah, just click. That'll be fine.
|
16:50 |
So the findings that I got uh very - just very briefly is that you have a choice of the way that the information is projected to the receiver and in my opinion infra-red is the best way to do that 'cause you don't need a sight line. So that's one thing we're gonna work on. Um the user interface is critical here, because a lot of the things that happen in a remote control happen through the chip that controls - that converts the electrical energy into data, which then goes through the infra-red, so the the chip that uh I think Ian is designing, is gonna be crucial.
|
17:24 |
And really it all comes down to the to the user, because they're the one that's controlling most of the working design. So the components that we find here are the energy source, you know the battery or whatever that's gonna m- make it work, then the chip, which converts the data, the user that's controlling the chip, and the infra-red bulb that's gonna let us move the data to the receiver. So you have four main components and they are designed sort of like this. You have your energy source right there which then um brings
|
17:58 |
uh energy or information to the chip, which is also controlled by the users. You have energy going to the user who's controlling the chip - ooh 's not what I wanted to do uh uh.
|
18:11 |
Um yeah use that thing @ you can go back, previous.
|
18:15 |
Previous.
|
18:16 |
Sorry about that, guys.
|
18:17 |
% Pardon.
|
18:19 |
Oh.
|
18:21 |
Oh, well. Okay.
|
18:21 |
No, no, no, no, no. Okay, let's just get back to my schematic here.
|
18:25 |
Ye-
|
18:27 |
Double click on it.
|
18:29 |
With the right - with the left hand one.
|
18:30 |
W- yeah, yeah. I think it's frozen. Here. Don't show me that tip again. There we are. Sorry about this, guys. I'm kind of pathetic with things like this. Um alright. So you have your energy source, your user interface who's controlling the chip, the chip also uses the energy, and the chip through the use of the user interface is gonna control the switch which will work your infra-red bulb, which will then bring the data to the receiver. So hopefully that makes sense for everyone in my kind of garbled way. This is the the parts of the working design that need to be figured out. And $ personal preferences, besides the fact that I can't spell, we need a long-lasting energy source, people don't wanna be changing it a lot. We need a chip that works well with the user interface, that isn't too complicated.
|
18:35 |
$ There we are.
|
18:37 |
%
|
19:02 |
Mm-hmm.
|
19:21 |
We need a straightforward interface, like Ian was saying, simple, not overwhelming it with information and we need a reliable and clear infra-red signal, so that you're not waving your remote around and having to get frustrated and go do it by hands. So that's pretty much it for the working design.
|
19:32 |
Mm-hmm.
|
19:40 |
Excellent.
|
19:47 |
@
|
19:55 |
So, um.
|
20:03 |
Rose, do you think you can give me a hand with this?
|
20:04 |
Yes, absolutely.
|
20:15 |
Ah I can never tell which way to turn these things.
|
20:17 |
Yeah.
|
20:20 |
Lefty loosey*, righty tighty*, right? $ Lefty loosey*, righty tighty*.
|
20:22 |
Yeah.
|
20:22 |
$
|
20:24 |
What's up?
|
20:24 |
$
|
20:25 |
Lefty loosey*.
|
20:28 |
Uh. $ Never heard that before, that's good. $
|
20:28 |
$
|
20:30 |
# Oh yes.
|
20:33 |
%
|
20:37 |
I'll think of that every time now.
|
20:39 |
$
|
20:39 |
$
|
20:39 |
It's gonna stick in your head.
|
20:39 |
Yeah, that's a good one it'll stick with you.
|
20:47 |
Mm 'kay.
|
20:59 |
Um I have nothing on my screen.
|
21:03 |
Just a sec.
|
21:05 |
Mm.
|
21:05 |
Here we are.
|
21:07 |
Ooh, no signal.
|
21:07 |
Okay, yeah, it's fine.
|
21:10 |
Okay, requirements. We have a couple new requirements that I was just e-mailed right before the meeting and that we have to keep in in um in mind as we're creating this. We didn't bring it up yet, or at all in the meetings so far, but we're not gonna work with teletext because um - well it - that's been taken over by the internet, so we're not gonna worry about um - we're not gonna worry about that.
|
21:15 |
Okay.
|
21:29 |
What's teletext?
|
21:31 |
Uh, it's a British thing.
|
21:31 |
Um.
|
21:33 |
Oh. Oh, so -
|
21:34 |
You don't have it in the States?
|
21:35 |
No. $
|
21:35 |
It - no. W- d- could - would you care to explain it?
|
21:36 |
Oh, I didn't realise. Um yeah, it's like a -
|
21:41 |
I suppose it's kind of similar to a very very basic web browser. Um you have like you have uh numbers on your remote control, uh y- and you type in the page number you want, so like you type a hundred on your remote control and this this kind of index appears on the television screen with just some some text and some very blocky* looking graphics on it. And you just type numbers to go to different pages and it gives you information, mostly rather boring stuff like what's on T_V_ next and share prices and that kind of thing.
|
21:49 |
Mm-hmm.
|
22:07 |
@
|
22:09 |
S-
|
22:13 |
$ Lottery numbers and sport scores.
|
22:15 |
Yep, news headlines.
|
22:16 |
But if you ever see the T_V_ saying like go to page one sixty on Ceefax now, that's what they're talking about.
|
22:21 |
How?
|
22:22 |
Oh.
|
22:22 |
It's earl- it's pretty old technology. It's like nineteen eighties.
|
22:24 |
Okay.
|
22:25 |
That explains a lot.
|
22:26 |
I have no idea why we don't have it, but -
|
22:28 |
That's good.
|
22:29 |
$
|
22:30 |
Interesting. Okay um, well, we're not gonna - the management has decided we're not gonna work with that. Um -
|
22:35 |
$
|
22:43 |
Okay um and we're also gonna w- like your question earlier um whether this is going to be t- for television, video, or etcetera. Just for television. That's what we're focused on. Um otherwise becomes to complex, we wanna get this out um very quickly. We only have a a short amount of time.
|
22:50 |
Right.
|
22:59 |
'Kay.
|
22:59 |
Um and finally there's more marketing, I think, um, our corporate image* has to be recognisable. So while we're gonna make it look pretty we need to use our colour and our slogan i- in the new design.
|
23:06 |
Mm.
|
23:14 |
So what's our corporate image like? It's - It's kind of yellow colour with uh we put fashion in electronics.
|
23:18 |
Looks like, yeah, kind of a yellow and black and we have that - the emphasis on the R_s in um - mm-hmm.
|
23:22 |
It's like double R_.
|
23:24 |
Yeah.
|
23:25 |
But it's, yeah, we put the um
|
23:30 |
fashion in electronics. So we gotta keep that in that in mind.
|
23:33 |
$
|
23:33 |
$
|
23:34 |
Okay, so we want something that looks good
|
23:36 |
Yep. Yep.
|
23:37 |
and is yellow.
|
23:39 |
Yeah, or $ ha- maybe some buttons could be yellow. Like, we can we can play around with it a little bit.
|
23:41 |
Okay.
|
23:45 |
Um.
|
23:47 |
Okay, we need to talk about our functions and our target group. We need to decide who our target group is. You um in your analysis of different market um - of the marketing, you identified that different groups wanted different things or had certain preferences, for example that um that older people didn't really care for um voice recognition, but younger people did. Um and so who are we aiming this at?
|
23:56 |
Mm-hmm.
|
24:07 |
Mm-hmm.
|
24:15 |
Well if we're gonna say that function um fashion - we put the fashion in in electronics then you - automatically, I think, a sort of younger group that - that's - who's gonna be attracted to this.
|
24:23 |
%
|
24:29 |
Yes, I do think, who's gonna have the money to buy that also, that one?
|
24:32 |
Mm-hmm. It's gonna be twenty five Euro remember, so um it has to be avai- marketable to um whomever it is.
|
24:40 |
Mm-hmm.
|
24:41 |
Is it - is it something that's gonna be sold separately from the television or is it something that comes w- with a television? 'Cause that would affect the way that we market it.
|
24:50 |
Well at least right now what we're doing is um deciding on just the remote itself, so it will probably be sold separately, twenty five Euro by itself.
|
24:55 |
Right.
|
24:57 |
Right, okay.
|
25:00 |
The only break-down that I was given in terms of age was the voice activation and basically there's a big jump, after thirty five people don't really care if it has voice, so it's like basically fifteen to thirty five that think that that's a good idea. I dunno I'm gonna be given any other numbers broken down in terms of age later, but if that's sort of the only quality that we have that is divided into age then we would wanna stick between the fifteen and thirty five range.
|
25:12 |
Mm-hmm.
|
25:25 |
Yeah, that's probably uh a population w- quite a little bit of disposable income for use on technology anyway, so that might be a fairly good target group for us.
|
25:32 |
Yeah.
|
25:33 |
%
|
25:35 |
Now, those are - that's all specific for speech recognition. Are we gonna use that as one of our functions?
|
25:43 |
Um.
|
25:44 |
Mm.
|
25:46 |
I I would say no, because it's gonna add too much to the price.
|
25:50 |
Especially if we are marketing it as a separate product, people are gonna be paying uh, well, uh we've got a price limit of - was it twelve twelve and a half Euros for - to produce it? And I wonder if we can get voice recognition into that twelve and a half Euros without having to make too many other compromises.
|
25:53 |
Mm-hmm.
|
25:58 |
Mm.
|
26:01 |
To produce it, yeah.
|
26:01 |
To produce it, yes.
|
26:05 |
Mm.
|
26:09 |
But what else are we gonna put, I mean not that I'm really gung-ho about it, I don't know what else you can put in a remote to make it technologically advanced though. So like other than just making it look good, how is it - I mean it can look really great and still have the same up-n-down buttons and why's anyone gonna buy a new remote?
|
26:18 |
Yeah.
|
26:19 |
Hmm.
|
26:23 |
But - right.
|
26:26 |
Well but why are we why are we aiming for a technological advancement? Everything we're talking about is ease of use and simple and that doesn't necessarily mean more technology, in fact it could use - it could mean, not. If # - they might be overwhelmed with with remotes that have too many buttons and too much technology.
|
26:34 |
Mm-hmm.
|
26:36 |
That's a good thing to keep in mind.
|
26:45 |
If someone's looking to buy a new remote, don't they want like an upgrade? I dunno.
|
26:50 |
Upgrade? Well, we can look for - we can look at upgrade or we can look at um user-friendly.
|
26:54 |
Yeah, simplification. They could have a crap remote that came with their T_V_ that's just impossible to use, or maybe it broke, or maybe they're just missing it.
|
26:56 |
Yeah.
|
26:56 |
Mm-hmm.
|
26:56 |
Simplification, so -
|
27:02 |
Mm-hmm.
|
27:06 |
Uh-huh, mm.
|
27:08 |
And we also need to talk about if we're only gonna have the very simple ones or also have the other ones just separate somehow or -
|
27:15 |
Can you like - I mean this may be too complicated, but, I wish I had something to explain it, like if it was just a simple, either this way or this way, that had like the main buttons and then you could like pull something out, kind of and like you got the rest the buttons, but the rest of them like went in. Do you know what I'm saying?
|
27:15 |
Hmm.
|
27:15 |
Yeah.
|
27:26 |
Ooh.
|
27:29 |
The remote - There are remote controls like that, yeah. Like some T_V_s they have a sort of uh a sliding screen on the remote control of it that hides all the complicated buttons. So if you wanna do something complicated like programme your television or re-tune it, then you you open up this little hatch or or slide the screen down and there's all the - all the special buttons.
|
27:30 |
Kind of pull out of the side.
|
27:37 |
Mm.
|
27:39 |
Ooh.
|
27:47 |
Mm-hmm.
|
27:48 |
Mm-hmm.
|
27:50 |
'Cause then 's like people who don't wanna ever look at them, never even have to see them and if you like get the instruction manual that comes with it and you just don't even read it then you'll never even know that those things can pull out. And you're a happy person and everyone else doesn't have to have like two remotes, one that has the easy ones and one that has
|
27:53 |
Mm-hmm.
|
27:53 |
Mm-hmm.
|
27:54 |
Yeah.
|
28:00 |
Mm-hmm.
|
28:05 |
Yeah, that's a good idea.
|
28:05 |
more complicated ones, but 's all still in one.
|
28:05 |
Yeah.
|
28:06 |
Mm-hmm.
|
28:07 |
I think that's a good idea, yeah.
|
28:08 |
Mm.
|
28:10 |
Um we have to be careful that that that doesn't impede um the chip transmitting information, but um that's gonna be mostly technological thing. Um.
|
28:15 |
Yeah.
|
28:16 |
Good point. Yeah.
|
28:16 |
Yeah.
|
28:23 |
Okay um, so what are we emphasising?
|
28:28 |
I - what in this project?
|
28:29 |
Si- simplicity and fashion.
|
28:31 |
I think simplicity, fashion.
|
28:31 |
Simplicity and fashion.
|
28:32 |
Yeah mm.
|
28:34 |
Okay, those are very good goals, I think, um that we have to keep in mind in - with everything we do. Simplicity and fashion and, yeah, - or usability speci- however you wanna say that, which includes um an emphasis on making the infra-red very functional, so that you don't have to travel around a lot.
|
28:48 |
Mm-hmm.
|
28:49 |
Yeah.
|
28:50 |
Yeah.
|
28:55 |
Um.
|
28:55 |
What can you do to like make the infra-red more functional, like why would it not be? I'm just wondering.
|
29:01 |
I think it's a lot # to do with battery, but that's just my -
|
29:04 |
Okay.
|
29:05 |
The battery and that - I think that the chip takes the data and presents it well, without sort of scattering.
|
29:12 |
Mm-hmm.
|
29:12 |
So 's just the quality of the chip.
|
29:14 |
Yeah. I think so.
|
29:16 |
Okay.
|
29:17 |
The quality # uh quality of all the components really, I mean, we can't really do anything - shoddy work, 'cause it's
|
29:25 |
Yeah.
|
29:26 |
gonna be visible down the line.
|
29:29 |
So our target group, we're saying, fifteen to thirty five?
|
29:33 |
Well, I dunno how useful that number is if we're not doing -
|
29:35 |
S- voice recognition, which I kind of I kind of feel like voice recognition is not necessary in a remote control, like it might be necessary for a T_V_ but not for the remote c-, you know. Seems a little bit -
|
29:36 |
Yeah.
|
29:41 |
Yeah. I don't.
|
29:44 |
It's, yeah, it's pretty it's pretty high-tech.
|
29:44 |
Mm-mm.
|
29:47 |
Yeah.
|
29:47 |
Mm-hmm. Yeah, and it might be too expensive.
|
29:48 |
@
|
29:49 |
And if the whole idea is you're using a remote then why would you have voice, like you know what I mean and then it's like you wouldn't need a remote you'd just talk to your T_V_.
|
29:53 |
Mm-hmm.
|
29:56 |
Yeah. $
|
29:56 |
It's for, like, the ultimately lazy people, who can't even be bothered to pick up the remote.
|
29:57 |
Ooh.
|
29:59 |
$
|
29:59 |
$
|
30:01 |
Yeah.
|
30:02 |
Mm yeah. Maybe - I mean if I get m- more numbers, I'll e-mail you before the next meeting in terms of ages. But this doesn't divide up anything and there was only a hundred subjects also, which isn't, I mean, really isn't that representative, especially if it's a hundred subjects that th- they then can subdivide into age groups that means there's very few in each age group, so -
|
30:03 |
I-
|
30:13 |
Mm-hmm.
|
30:13 |
Mm-hmm.
|
30:23 |
Yeah, but I th- I think regardless we're we're aiming for the under sixty five or something.
|
30:23 |
@
|
30:28 |
Under sixty five, okay, that's a good start. Um.
|
30:29 |
Yep.
|
30:33 |
I'd say we're - uh can we narrow it down to maybe um
|
30:37 |
teenagers and families?
|
30:40 |
'Cause that would go up to like fifty?
|
30:40 |
Or like single professionals or something.
|
30:43 |
Twenty to like fifty five.
|
30:43 |
Okay, single -
|
30:47 |
I dunno.
|
30:47 |
Yeah.
|
30:49 |
It's it's hard to narrow it down.
|
30:50 |
It's really hard to figure out right now.
|
30:53 |
I think the product appeals across a quite a broad range of ages. I mean, we we said simplicity is is one of the features, so it's going to appeal to people, maybe people who have problems with technology, you know, people who get scared by having lots of buttons, and that might be older people, but then we've also got fashion, which is something that definitely appeals to younger people.
|
30:57 |
Mm-hmm.
|
31:08 |
Okay.
|
31:11 |
Mm-hmm.
|
31:14 |
Yeah.
|
31:15 |
Well maybe we don't have to defi- define the target group by the demographic of age, maybe we can define it by like the demographic of
|
31:18 |
Right.
|
31:22 |
like h- t- how much money they have to spend or something like that, like, well obviously it has to be someone who owns a television, and like how recently have they bought their television like that sort of thing.
|
31:24 |
Yeah. Yeah aim for a - an income group.
|
31:25 |
That's a good point.
|
31:25 |
Mm-hmm.
|
31:28 |
Mm-hmm.
|
31:28 |
Yeah.
|
31:32 |
Mm.
|
31:32 |
So maybe it's more useful to d- d- to define objectives like fashion and simplicity than to find specific target group as far as age is - because, yeah, things so different will appeal to different people, but -
|
31:36 |
Yeah, t- probably.
|
31:40 |
Yeah.
|
31:46 |
Okay. Um oh, there're a couple functions - do we want something so that - do we want some kind of thing to find it if it's lost?
|
31:56 |
Mm.
|
31:56 |
Yeah.
|
31:56 |
Like a button on a T_V_ you can press and it'll ring or something, I don't know like - or beep?
|
32:00 |
H-
|
32:02 |
I mean, like I said before, fifty per cent of of the fru- f- like frustration someone can have that was the biggest one and half the people said that happened and we all mentioned it before we knew about it.
|
32:11 |
Mm-hmm.
|
32:13 |
Yeah.
|
32:14 |
And if we're talking about making something easy that sort of goes along with it so it wouldn't be like a random thing to sort of add in. It would be relevant to like the overall goal I think, so -
|
32:21 |
Mm.
|
32:23 |
Mm.
|
32:23 |
Yeah, that'll probably be good.
|
32:25 |
Okay, we have to - we have about four minutes left to define our functions. So let's do that quickly. Um so we want something to keep it from getting lost.
|
32:33 |
Yep.
|
32:34 |
Yeah.
|
32:36 |
And # we want
|
32:40 |
um
|
32:42 |
we want large buttons for the essential things.
|
32:45 |
Yeah.
|
32:46 |
Yeah.
|
32:46 |
Large, accessible buttons for the essentials.
|
32:52 |
We want a possibility to um to get um
|
32:58 |
a possibility to get the extra functions.
|
33:02 |
Mm-hmm.
|
33:02 |
Yeah.
|
33:05 |
%
|
33:05 |
Which are kind of hidden away in some way or
|
33:09 |
well not hidden but they're uh
|
33:12 |
they're not as prominent as the main features.
|
33:14 |
Mm-hmm.
|
33:14 |
Hmm.
|
33:19 |
Um, yeah, hidden way.
|
33:22 |
And we also want it to be fashionable, which I'm not sure if that's a function so much as a um yeah -
|
33:30 |
@ on your coffee table, it's not like an eye sore, that kind of thing.
|
33:33 |
Mm-hmm.
|
33:33 |
Yeah.
|
33:38 |
Alright.
|
33:40 |
Okay, do it. Any other essential functions that we need?
|
33:44 |
Battery? Do we need a long-life battery?
|
33:46 |
Battery battery use. Yeah, but I think that goes in with simplicity and ease of use really.
|
33:49 |
Yeah.
|
33:52 |
But we might as well.
|
33:52 |
So you never have to change the battery.
|
33:54 |
Yeah.
|
33:58 |
We should maybe investigate whether it needs a battery at all.
|
34:01 |
I suspect the remote control does need a battery, but
|
34:04 |
Yeah.
|
34:04 |
Yeah, I would imagine. Just 'cause it is an electronic device, the -
|
34:05 |
I dunno if you can -
|
34:08 |
Yeah.
|
34:08 |
Mm. It - I think it does. I don't I don't think of a way you can operate a chip and convert that much data without without one. But you could maybe have it in a little charging station like a mobile phone, or like a little cradle for your iPod.
|
34:14 |
Yeah, without the energy, yeah.
|
34:22 |
Yeah, that's that's possible. Yeah.
|
34:23 |
You could - we could maybe do that instead. So you don't ha- you got like a rechargeable battery.
|
34:26 |
Charging.
|
34:28 |
Yeah.
|
34:29 |
I dunno, that might contribute to less people losing it too if it $ it stays in one place.
|
34:33 |
Mm-hmm.
|
34:35 |
Mm.
|
34:36 |
We have to think about um space in living-rooms, too, like 'cause they're - I mean, would you put it on top of the T_V_? I don't know, just think - okay, that's # that's a good idea, we'll keep it. Think it's -
|
34:40 |
Mm.
|
34:46 |
Yeah. That's just off the top of my head.
|
34:48 |
And maybe fun.
|
34:50 |
Okay. Um 'kay we're gonna conclude now, has everyone said their functions and - 'kay.
|
34:55 |
Yep.
|
34:57 |
Um after the meeting we're gonna each complete a sks- um a questionnaire and a summaries - summary. I don't know what summarisation. Um and then we'll have our lunch break. After that we have thirty minutes of individual work. Um I'll make sure to put up um the minutes and the project documentation and including these PowerPoint slides. If everyone could do that as well, that'd be great.
|
35:17 |
Um you each have individual actions, I_ um I_D_ Industrial Design you've your components concept, User Interface, the user interface concept, market trend wa- watching. And as as per last time you'll get specific incrat- instructions from your personal coach e-mailed to you. And hopefully, I hope, next time you'll be able to access more of the web site that they they seem to tell you that you could.
|
35:27 |
$
|
35:42 |
Yeah, who knows.
|
35:42 |
It's kinda frustrating, but um -
|
35:47 |
Be sure to note any frustrations or any um issues that come up in your um in your um summary.
|
35:56 |
Okay
|
35:58 |
Mm 'kay?
|
35:59 |
Sounds good.
|
36:00 |
Great seeing y'all.
|
36:02 |
# $
|
36:03 |
It's good.
|
36:04 |
$
|
36:05 |
$
|
36:06 |
Did you um - were you able to like put yours in the group folder? Okay.
|
36:09 |
Yes, I just did that. Hopefully it is there for people. Yeah?
|
36:13 |
Yep.
|
36:16 |
Looks like there are um - looks like there's a second one kind of of mine that's - that I didn't do, it's from like an earlier project, I think so um -
|
36:21 |
Yeah.
|
36:24 |
Okay.
|
36:26 |
Where is that? Yours is -
|
36:28 |
Under the shared folder, I don't know it might not even be under yours as well. Projects.
|
36:30 |
Technical. So in there we have technical functions presentation, working design presentation and the functional requirements. At least that's what I have in.
|
36:38 |
I only have three, I just have like our three. Yeah.
|
36:40 |
Yeah, that's what I have as well, R- Rose - So.
|
36:41 |
Okay. You don't have mine?
|
36:45 |
No, but that's 'cause I think yours is in the e-mail separate, like it's not on the server.
|
36:49 |
S-
|
36:50 |
Yeah.
|
36:55 |
Mm.
|
36:56 |
But if I open it and then save it, probably will be there. Oh wait, never mind you can't save it to the -
|
37:05 |
Okay. Well I'll figure that out in the meantime.
|
37:07 |
Okay.
|
37:08 |
Okay.
|
37:08 |
Okay.
|