Report

Table of contents
1. General description of application ..........................................................................4

1.1 The use of the program .................................................................................4
1.2 General commands and behaviour of the program.........................................4
2. Dialogue structure ..................................................................................................5

2.1. General dialogue structure ...............................................................................5
2.2 Dialogue structure of Registration ....................................................................6
2.3 Dialogue structure quit menu ............................................................................6
2.3 Dialogue structure payment menu.....................................................................7
2.4 Dialogue structure new bill menu .....................................................................7
2.5 Dialogue structure payment form menu ............................................................8
3. Grammars ..............................................................................................................8
3.1 Registration ......................................................................................................8
3.2 Main menu .......................................................................................................8
3.3 Checking the key code......................................................................................8
3.4 Payment menu ..................................................................................................8
3.5 Checking the bills that are under payment.........................................................9
3.6 New payment ...................................................................................................9
3.7 Payment form.................................................................................................11
3.8 Quitting the program ......................................................................................12
4. System prompts....................................................................................................12
4.1 At the beginning .............................................................................................12
4.2 Registration ....................................................................................................12
4.3 Main menu .....................................................................................................13
4.4 Checking the key code....................................................................................13
4.5 Payment menu ................................................................................................13
4.6 Checking the bills that are under payment.......................................................14
4.7 New payment .................................................................................................14
4.8 Payment form.................................................................................................15
4.9 Quitting the program ......................................................................................15
5. The files ...............................................................................................................15
6. User profiles and other information ......................................................................16
7. General description of program code ....................................................................16

7.1 At the beginning and general variables ...........................................................16
7.2 Registration menu...........................................................................................16
7.3 Main menu .....................................................................................................16
7.4 New payment menu ........................................................................................16
7.5 Payment form menu .......................................................................................17
8. Usability test report ..............................................................................................17

8.1. Test procedures and tasks ..............................................................................17
8.1.1 Test tasks.................................................................................................18
8.2. Results and the problems ...............................................................................19
8.2.1 Problems in grammars .............................................................................19
8.2.2 Problems in prompts................................................................................19
8.2.3 Other problems ........................................................................................19
8.3. Improving the problematic areas....................................................................20
8.3.1 Grammars................................................................................................20
8.3.2 Prompts ...................................................................................................20
8.3.3 Other .......................................................................................................20
8.4. The subjects’ opinions ...................................................................................21
8.4.1 Subject 1..................................................................................................21
8.4.2 Subject 2..................................................................................................21
8.4.3 Subject 3..................................................................................................21
9. User guide............................................................................................................21
1. General description of application
Easy Bank is a banking application that is used by a speech user interface. It is
designed especially for blind people and is meant to be used by a computer in a
private area, such as users home, where it is safe for the user to say out loud private
information, e.g. user ID’s and passwords. Easy Bank can be used only for paying
bills and checking bills that are under the payment, because other bank services are
not included in this version.
This version of Easy Bank is just a prototype of the application, and can be used only
with the material that was prepared for the tests, because it wasn’t possible to build a
database that is needed for this kind of applications.
1.1 The use of the program

As in all bank applications, the user must first register into the system with an user ID
and a password. The user ID and password consists of four numbers. If the user says
his user ID or password wrong two times, the numbers will be asked from him
number by number. If the user still doesn’t get them right, the program will be shut
because of security reasons.
After registration the user is asked if he wants to hear general information about the
program. In the general information -section the user hears e.g. commands what he
can say in the program. After that the user gets to the main menu. In the main menu
the user can go to the payments menu or quit the program. When quitting the
program, the user is confirmed if that is what he really wants to do.
When the user goes to the payment menu for the first time in the session, he will be
asked to give a keycode that corresponds to the certain number. If the user gives the
wrong keycode three times, the program will be shut for security reasons. Keycodes
consists of two digits, and must be said separately, not as a figure.
In the payments menu the user can select a new payment, payment form or check bills
that are under the payment. The new payment –section is for paying a new bill. The
user is asked to give all the information from the bill. After that the user can still
change some items or accept the bill. In the payment form –section there are payment
forms for certain recipients, that the user can use. The user can change all the items in
the bills, except the recipient information. The bills under payment –section contains
information of all the bills that are about to be payed. The user can eye the
information of the bills and delete them.
1.2 General commands and behaviour of the program

The user can go back in the program by saying back, return to the main menu by
saying menu and get some help by saying help. Those three commands are available
almost everywhere in the program. The help-message is different in every main
section and contains the most common commands of that section and other helpful
information. Only in the registration-section the user can’t use them.
Every time when the user interrupts doing something e.g. paying a bill or wants to go
to the main menu, the program confirms that the user really wants to do that. In cases,
when the program misunderstands the user, that prevents the unwanted transition to
happen.
If the program doesn’t understand what the user is saying, it asks the question again
three times. For every prompt, there are two help-prompts, which are said in these
cases. After that if the user still isn’t understood, the program will be shut.
This application doesn’t support barge-in, so the user can’t interrupt the program by
saying something. The user must listen the question to the end before he can answer
to it or say a command.
2. Dialogue structure
All the dialogues contain the help prompts and some confirms when leaving, but they
are not represented in the pictures. The pictures are also quite simple from the original
dialogues
2.1. General dialogue structure
Welcome
Registration
Main menu
Payments
Quit
New payment Payment form Bills under the payment

Two-headed arrow: something went wrong. Error prompt and new recognition.
One-headed arrow: too many wrong values, quit.
2.2 Dialogue structure of Registration
user ID?
Wrong1 Wrong2
user ID
Quit
Password?
Wrong1 Wrong2
Password Quit
Main menu
2.3 Dialogue structure quit menu
Main menu
Payment menu
Quit?
Yes No
Quit
2.3 Dialogue structure payment menu
Payment menu
New bill menu Payment form menu Bills under payment
More? Remove one bill?
Remove bill1 Remove bill2 Remove bill3
2.4 Dialogue structure new bill menu
New bill
Recipient’s name? Euros? Date?
Account number? Cents? Message?
Bill is… Is it OK?
Yes Change one item…
Yes
Payment menu No Change more?
2.5 Dialogue structure payment form menu
Payment form
Select recipient
Change one item?
Yes
Yes Change other item?
No
Payment menu
3. Grammars
3.1 Registration
Grammar for prompt 2, 3, 4, 6, 7 and 8
$digit = one | two | three | four | six | seven | eight | nine;
$sep = *sil%% [*any%%] *sil%%;
$grammar = [$sep] < $digit [$sep] > [$sep];
3.2 Main menu

Grammar for prompt 12
$menu = forward | next | pass | no | menu | main;
$yes = yes | information | general;
$help = help;
$payments = (pay | payments | bill | bills | settlements);
$quit = (quit | exit | shut | end);
$help = help;
$back = back;
3.3 Checking the key code

Grammar for prompt 16, 17 and 18
$digit = zero | one | two | three | four | five | six | seven | eight | nine;
$sep = *sil%% [*any%%] *sil%%;
$grammar = [$sep] < $digit [$sep] > [$sep];
3.4 Payment menu

$start = [I'd%% | would%%] like%% | I%% want%% | I%% need%% [to%%
pay%%] [a%%];
$end = please%%;
$new = [$start][new] (bill | settlement)[$end];
$form = [$start][bill] form[$end];
$under = [$start][bills] under the%% payment%%[$end];
$menu = (menu | back| quit);
$help = help;
3.5 Checking the bills that are under payment

$yes = (yes | yeah | remove);
$no = (no | noup | nou | back);
$menu = (menu | main );
$help = help;
$one = one | first;
$two = two | second;
$three = three | third;
$menu = menu | back;
$help = help;
$yes = (yes | yeah | jes | jep | ok);
$no = (no | noup | nou);
$back = back;
Grammar for prompts 26, 27 and 28
$no = no;
$yes = yes;
3.6 New payment

$persons = Jack Daniels | James Bond | Madonna;
$companies = hospital;
$names = [$persons]|[$companies];
$menu = (menu | main | quit);
$help = help;
$digit = seven | four | two | six;
$back = back;
$menu = (menu | main |quit);
$help = help;
$digit = fifty | twenty four | seventy two | fourty eight;
$back = back;
$help = help;
$digit = thirty | sixty | none;
$back = back;
$help = help;
$digit = twenty six | seventeen | four | ten;
$back = back;
$help = help;
$months = october | april | january | december;
$back = back;
$help = help;
$messages = hospital care | debt | loan | protection;
$back = back;
$help = help;
Grammar for prompt 38, 56 and 58
$yes = (yes | yeah );
$no = (no | noup | nou | change);
$yes = (yes);
$payments = (pay | payments | bill | bills | back);
$quit = (quit | exit | shut | menu);
$help = help;
$no = (no);
$no = no;
$yes = yes;
$menu = menu | main | back | quit;
$sum = sum;
$messa = message;
$date = date;
$rec = recipient;
$acc = account;
$back = back;
$help = help;
$digit = fifty | twenty four | seventy two | fourty eight;
$back = back;
$help = help;
$cent = thirty | sixty | none;
$back = back;
$help = help
$mes = loan | hospital care | protection | debt;
$back = back;
$help = help
$digit = seventeen | four | twenty six | ten;
$back = back;
$help = help
$months = october | april | january | december;
$back = back;
$help = help
$persons = Jack Daniels | James Bond | Madonna;
$companies = hospital;
$names = [$persons]|[$companies];
$back = back;
$help = help
$digit = four | two | six | seven [*sil%% [*any%%] *sil%%];
$back = back;
$help = help
3.7 Payment form

$form = Winnie the%% pooh%%;
$poke = pokemon;
$mick = Mickey mouse%%;
$spid = spider man%%;
$back = back | menu | main | quit;
$help = help;
$accept = yes | yeah | jes | accept;
$item = reference | sum | message | date | account | recipient | change;
$menu = menu | main | quit;
$back = back;
$help = help;
$yes = yes;
$no = no;
$back = back;
$help = help;
$yes = (yes);
$payments = (pay | payments | bill | bills | back);
$quit = (quit | exit | shut | menu);
$help = help;
$no = (no);
$sum = sum;
$mess = message;
$date = date;
$back = back;
$menu = menu | quit;
$help = help;
$mess = rent | restaurant | loan;
$back = back;
$help = help;
$digit = fifty two | sixty five| four hundred | eighteen;
$back = back;
$help = help;
$digit = seventy | fourty | fifty | none;
$back = back;
$digit = twenty nineth | tenth | seventh | twelveth;
$back = back;
$help = help;
$month = april | may | june;
$back = back;
$help = help;
Grammar for prompt 75 and 77
$yes = yes;
$no = no;
3.8 Quitting the program

$yes = yes;
$no = no;
$back = back;
$help = help;
$yes = yes;
$back = back | no;
$help = help;
4. System prompts
4.1 At the beginning
1.Welcome to Easy Bank
4.2 Registration
2. Please, give your user I D.
If the user ID is not correct: 3. Given user I D +userID+ not found. Please repeat your
user I D
If the user ID is still not correct: 4. Given user I D +userID+ not found. Please give
your four numbered user ID number by number.
Then the user will be asked to give the numbers number by number.
If the user ID is said wrong three times: 5. Too many wrong user I Ds. The program
will be shut. Goodbye.
When the user ID is said correct: 6. Hi +users name+. Please give your password
If the password is not correct: 7. Given password +password+ not found. Please
repeat your password.
If the password is still not correct: 8. Given password +password+ not found. Please
give your four numbered password number by number.
Then the user will be asked to give the numbers number by number.
If the password is said wrong three times: 9. Too many wrong passwords. The
program will be shut. Goodbye.
If the given user ID an password don’t match: 10. The given user ID and password
don't match
4.3 Main menu

11. Your registration was successful!
12. Do you want to hear general information or go to the main menu?
13. You are in the main menu. You can say for example pay or quit. What do you want
to do?
If the user wants to hear general information: 14. You can now pay bills or quit. If you
want to go backwards, just say back. You can return to the main menu saying menu.
You get help saying help.
If the user asks for help: 15. You asked for help. You are now in the main menu. You
can go to the payments or quit the program. When you use the program, you can
always go back by saying back. Later you can return to this menu by saying menu.
You can say for example payments, bill, quit, or back.
4.4 Checking the key code

16. Say the key code that corresponds to number +keynumber+.
If the key code is not correct: 17. The key code +keycode+ was not correct.
If the key code is still not correct: 18. The key code +keycode+ was not correct.
Please check the key code of +keynumber+ and say the first number.
Then the user is asked to give the second number.
If the key code is said wrong three times: 19. You gave too many wrong key code
numbers. The program will be shut. Goodbye.
4.5 Payment menu

20. You are in the payment menu.
21. What do you want to do? You can say new bills, payment form or bills under the
payment.
If the user asks for help: 21. You asked for help. You are about to pay bills or
checking your bills under payment. You can return to main menu by saying menu or
go back by saying back. You can say for example payment form, new payment, bills
under payment, back or menu.
4.6 Checking the bills that are under payment
22. You are about to check bills, which are under the payment. You have following
bills.
Then the information about the bills is told to the user.
23. Do you want to remove one of these bills?
24. Say the number of the bill you want to remove.
25. You chose the following bill, recipients name: +recipients name+, sum: +sum+,
date: +date+. Do you want to delete it?
The user wants to delete the bill: 26. The bill has been deleted. Do you want to delete
another bill?
The user doesn’t want to delete the bill: 27. The bill is not deleted. Do you want to
delete another bill?
If the user wants to go to the main menu: 28. Do you want to leave to main menu?
29. Now you return to the main menu.
4.7 New payment

30. You chose a new payment.
31. Please, say the name of the recipient or quit.
32. Please say the account number.
33.Please, give the euros.
34. Please, give the cents or say none.
35. Please, give the day.
36. And the month.
37. Please give the message.
38. Recipient: +recipients name+, account number: +account number+, sum:
+euros+ euros and +cents+ cents, date: +day+ of +month+ and the message:
+message+. Do you want to change the bill or accept it?
The user accepts the bill: 39. The bill is accepted. Now you return to the payments
menu.
40. You finished paying a new bill. Do you want to pay more bills?
The user wants to change the bill: 41. You really want to change the bill?
42. The bill is not accepted. You can change recipient, account number, date, sum or
message.
43. What do you want to change?
44. Please, give the euros.
46. The new sum is +euros+ euros and +cents+ cents.
47. Please, give a new message.
48. The new message is +message+.
49. Please, give a new day.
50. Please say the month.
51. The new date is +day+ of +month+.
52. Please, say the name of the recipient.
53. The new recipient is +recipients name+.
54. Please say the account number.
55. The new account number is +account number+.
56. Do you want to change anything else?
If the user wants to go to the main menu: 57.You are about to leaving from creating a
new payment. 58. Do you really want to leave?
59. Now you return to the payments menu
If the user asks for help: 60. You asked for help. You are now in the new payment
menu. You can pay a bill by giving the account number and name of the recipient,
message, sum and date. You can always go backwards saying back and to main menu
saying menu. You can say for example payments, recipient, account number,
message, sum, date, quit, back or menu.
4.8 Payment form

61. You chose a payment form. You have a payment form to following recipients:
+recipient1+, +recipient2+, +recipient3+, +recipient4+.
62. Please, give the recipient.
63. Recipient: +recipients name+, sum: +sum+, date: +date+ and the message:
+message+
64. Do you want to change the bill or accept it?
The user accepts the bill: 65. The bill is Recipient: +recipients name+, sum: +euros+
euros and +cents+ cents, date: +day+ of +month+ and the message: +message+. Do
you accept it?
66. The bill is accepted. Now you return to the payments menu.
67. You finished paying a new bill. Do you want to pay more bills?
The user wants to change the bill: 68. You are about to change the bill.
69. What do you want to change?
70. Please, give a new message.
71. Please, give the euros.
73. Please, give a new day.
74. Please say the month.
75. Do you want to change anything else?
76. You are about to change items again.
If the user wants to go to the main menu: 77. Are you sure you want to interrupt using
payment form?
78. Now you return to the payments menu
If the user asks for help: 79. You asked for help. You are about to pay a bill with the
payment form. You can say the name of the recipient and then change the items of the
previous saved bill form. I tell the information about the bill and afterwards you can
change the wrong items or accept the bill. You can change the recipient, sum,
message or date. You can always go backwards saying back and to main menu saying
menu. You can say for example recipient, quit, back or menu.
4.9 Quitting the program

80. Would you like to quit the program?
81. Are you sure you want to quit?
If the user doesn’t want to quit: 82. You didn't quit the program.
If the user wants to quit: 83. Thank you for using Easy bank. Welcome again.
5. The files
This application contains three files, which one must have to use it well. Two of them
are real application files: htyo.rad and htyo2Repair.rad. The last file is needed when
testing the program. The user must have “the bills” and other information. These can
be found from the information.doc
6. User profiles and other information
There are four user profiles made for this program, which can be found from the
information.doc –file. It isn’t possible to create new ones with the program. User IDs
and passwords for each user profile, keynumbers and –codes and all the possible bills
and payment form –bills that can be paid with this program, are also found from the
information.doc –file.
7. General description of program code

We have used code few times. All the variables are listed below.
7.1 At the beginning and general variables

• start, counts the times starting the application
• keycounter, all most the same as previous
• kohta, this variable is used in many places. It’s named badly in finish. We
need it because we need to know the prompt where to go from the help-menu.
It gets a number value.
• help1, the first help-prompt, when the recogniser don’t understand the value
• help2, the second help-prompt, when the recogniser still don’t understand the
given value
7.2 Registration menu

Variables and the code:
• muuttuja, gets the user’s user ID. We named this terribly and in finish J. It is
changed when the user ID is recognised badly and asked again.
• counter, counts how many times the user ID has been asked. This kind of
counter has been used in many places with conditional tool.
• first, sec, thi and fou, these four variables get the values of user ID when
asked number by number.
• passw, gets the user’s password. It is changed when the password is
recognised badly and asked again.
• passcounter, counts how many times the password has been asked. Like
counter.
• firs, se, th and fo, these four variables get the values of password when asked
number by number..
The variable muuttuja is used as seen below while greeting:

if { [string compare $muuttuja "seven eight nine two"] == 0 } {
tts "Hi Harry Potter"
}
7.3 Main menu

• key, gets the keycode. It is changed when the keycode is recognised badly and
asked again.
• first and second, these two variables get the values of keycode when asked
number by number.
7.4 New payment menu

These variables are only for getting the values of the paid bill. The values can be
changes later, if the recogniser has been missed the real value.
• name, recipient’s name
• account, recipient’s account number
• euro, euros of the sum
• cent, cents of the sum
• day, the day of the due date
• month, the month of the due day
• messag, message to the recipient
The variable cent is used as seen below while there are no cents given:
if { [string compare $cents(recog) "none"] == 0 } {
set cent "no"
}
7.5 Payment form menu

• euro, euros of the sum
• cent, cents of the sum. Like above when there are no cents.
• day, the day of the due date
• month, the month of the due day
• message, message to the recipient
8. Usability test report

8.1. Test procedures and tasks
The tests were held in TAUCHI testing laboratory on 22nd of April. We had three
subjects, which all are quite experienced computer users. Their native language is
Finnish and they all are under 25 years old. We think that they present well the users,
who would use this kind of application. They have a talent to speak and understand
English and they are eager to try new ways of doing things. The tests were
videotaped, but all subjects refused to give a permission to further spread. They shied
their pronunciations. The subjects did not know anything about application
beforehand and they had never used speech applications.
Before the test we told them some things about our application. We told that it would
be the application, which works only with speech and it is a banking application,
which they would use easily for example at home. We gave them a little grammar,
which might help them to use Easy Bank. We explained only the most difficult words
or phrases. We compared it to the internet bank applications to produce some kind of
metafora from our application beforehand.
We described also the ways of using our speech application, e.g. how close it would
be good to keep the microphone while speaking and how they were supposed to
speak. Before the test we trained few minutes with the toolkit’s example application,
pizza.rad. We also said them that the application cannot be interrupted while it is
speaking.
Before the real test the subjects selected their new identity, which they used in the
application. At that time they got a user ID and a password, which they need when
registering to the system. They also selected one bill and two payment forms, which
they then would pay during a test. They were also given a list, which contains the
keycodes.
The subjects managed to finish all the tasks given and it took 20-30 minutes to do the
test depending on the subject. We made few changes after the first test session and
that improved recognition and so subjects 2 and 3 were little quicker.
8.1.1 Test tasks

The test tasks were given in Finnish so that the subjects would not feel the test all too
difficult to use when their native language is different than the one the application
uses. Below are the translated tasks:
1. Register to the application and quit the program after registration.

At the first time the subject started to use the application he had to register into it.
In the later tasks we just skip the registration, so that when the subject started to
do the new task, he started it from the main menu. We thought that it is not
necessary to do the registration but once because it is always the same.
So with this task we only wanted to see, how the registration works. User IDs and
passwords were four-numbered digits, so we thought that the recognition might be
difficult. We also tested that the subject would understand the way of ending the
program.
2. Eye on the bills, which are under the payment, and remove the bill you
want. Finally return to the main menu.
This task was supposed to test the ‘Bills under the payment’ section. Before the
subject can pay a bill, he has to give a keycode. The keycode is needed when the
user goes to the payment section at the first time. In tasks three and four the
keycode is not asked anymore.
The task was supposed to check how well-designed ‘Bills under the payment’
section is and how the user selects the removed bill. Finally we wanted to see, that
the subject understands, which is the main menu, where he can start all again if
necessary.
3. Pay a new bill you selected. Finally return to the main menu.
This task checks how the subject manage to pay a new bill. The subject had to
give all the items which were needed for paying a bill correctly. We wanted also
to see how the user would recover from error situations and recognition misses.
4. Pay the bills you selected using a payment form. Change only the items
which are bolded. Finally return to the main menu.
This is very much the same as the task three. At this time the subject only uses a
payment form instead of a plain bill form and he has to change some of the items
on the form. We wanted to test how the subject manages to change those items
when the order of the items is not strict.
8.2. Results and the problems
The usability tests were successful, because they brought up a few quite remarkable
usability problems that we hadn’t noticed ourselves. Most of the problems had
something to do with the grammars. Usually something was missing from them, or
they were made too inaccurately. Also the speech recogniser caused some problems.
8.2.1 Problems in grammars

The biggest problems in the application were grammars in yes-no –dialogues, where
the program is expecting the user to say yes or no. For some reason, the program
didn’t understand what the subject was saying in these kinds of prompts, and in one
case the program was even shut because of this. We hadn’t made actual grammars for
these kind of prompts, just added ”yes” and ”no” to the ports, because there were only
those two words to be recognised. So, that probably caused the problems in
recognition.
Other problem in the grammars was, that there were in some points missing the
grammars for ”quit” and ”menu”. The subjects tried to say those words in such points
were they were missing, and were confused because the program didn’t understand
their command. We hadn’t added those words to all of the grammars, because we
thought that they aren’t needed everywhere. Anyway, now we noticed that they
should be added in those other grammars too.
The subjects also tried to say other commands that what we had put in the grammars.
For example when the program asked the user ”Do you want to remove one of these
bills?”, the subject answered ”remove” instead of ”yes” or ”no” that we had thought
he would say. Also some other commands came up, that showed us that some words
should be added to the grammars.
8.2.2 Problems in prompts

There were also some problems with the prompts. In some points there were prompts
that said only the question and the possible answers or commands were said in the
previous prompt. That caused problems when the subject didn’t say anything or the
program didn’t understand him. In that case only the question was repeated and not
the possible answers. That confused the subject and he didn’t remember anymore the
alternatives what he can say. Also the programs pronunciation of some words was a
little confusing for some of the subjects. They weren’t sure in all points, what the
program is trying to say.
8.2.3 Other problems

The speech recogniser caused also quite a lot of problems. There were many cases,
where the user seemed to say his command very clearly but still the program didn’t
understand him or understand him wrong. The subjects were very frustrated in these
points, especially when the program did something that they didn’t want it to do.
Numbers and how to say them were one problem. User ID, password, account and
keycode numbers were meant to say one number at a time (e.g. two six) and the
numbers that represent a sum were meant to say as a figure (e.g. twenty-six). Subjects
gave the user IDs, passwords and account numbers right, but all of them tried to say
keycodes as figures. Some of them weren’t sure how to say the sums.
8.3. Improving the problematic areas
The usability tests gave us quite a lot of ideas how to make this application better and
more usable. Areas that need improvement seemed clearly to be grammars and some
prompts. The structure of this program seems to work fine without improvements.
8.3.1 Grammars
The first thing to do is to build proper grammars for all of the yes-no –prompts. The
speech recognition seems to work much better with them. Proper grammars should
also be added to every point, where they still are missing. Also words ”quit” and
”menu” should be added to every point, where the user might need them. The
registration-section is an exception, because that must be cleared properly before the
user can use the program.
Other things that can be done to the grammars is to add more possible words to them.
If the program is tested more, there may appear more words that the users like to use
and all of them should be in the grammars too. That however causes problems with
the recognition. We have noticed, that the more there are words in the grammars, the
more there are misrecognised words. Also if the words are much similar to each other,
the recognition gets harder and more inaccurate.
8.3.2 Prompts
There are few prompts that must be improved. The possible answer alternatives must
be added to those prompts that don’t have them. That way the user hears the
alternatives again when the prompt is repeated in error situations and he doesn’t have
to remember what was said in the previous prompt.
In some prompts there must also be changes in the word and sentence orders so that
the question part comes last. If the question is in the beginning, the user doesn’t
necessarily remember the form of the question that was asked and doesn’t know how
and what to answer to it.
8.3.3 Other
There are also few other things that need some improvement, but there are things that
we can’t change. Mainly that is the speech recogniser, which works sometimes very
inaccurately. We have already changed the CSLU’s settings many times to improve
the recognition, but still it feels that it’s not accurate enough. The subjects wondered
often what was going on when the recogniser misses and leads them to the wrong
place. We don’t think that that is a real usability problem, which we can’t improve
anymore.
8.4. The subjects’ opinions
After the test we asked the subjects to fill out an enquiry and we interviewed them. In
the enquiry we asked their opinions about using the program and what was good and
bad in its features. Above there is listed some of the comments that we received.
The subjects thought that the language (English) was not the key problem when error
situations happened. However, they said that some basic words were recognised all
too often wrong, like ‘Yes’ and ’No’. They had a good picture of applications
structure and they managed to finish the tasks finally well. All of them thought that
next time it would be pretty easy to use such an application.
8.4.1 Subject 1
”At first it was difficult to navigate, but soon the menu seems to be quite logic and
clear. Some instructions wouldn’t be needed, but otherwise the program was running
smoothly. It didn’t understand my ‘No’-word and sometimes ‘Back’- or ‘Quit’-words.
That was a little bit annoying. Structure of the application was easy to understand.”
8.4.2 Subject 2
”The program jumped few times to unexpected places without telling where it went.
Otherwise it was clear enough. Sometimes it was unclear what I can say, for example
pay, payment or payment menu. It would be easier to use, if there would be only one
possible choice. It didn’t understand my ‘No’.”
8.4.3 Subject 3
”At the beginning it was quite annoying to follow what the program did, but after
learning the program it was much more easier. I would suggest some kind of ‘skip’ to
the program so that you don’t need to listen all the long prompts again if it
misrecognises or something.. It would be also nicer to use if it would speak more
naturally and understand better my speech.”
9. User guide
We think that this application doesn’t need any user guide, but we thought that this is
the place, where the user checks the most important things. We have few comments
on using this application properly:
• Use only one of the given user profiles and its user ID and password.
• Before start using the application, select the bills you want to “pay”. Bill X
means a new bill, which can be paid in a section ‘New payment’. Form X is
the bill, which can be paid in a section ‘Payment form’.
• The application works properly only with the test tasks.
1. Identities (needed in the task 1)
U = user ID
P = password
Mr. Bush
U: 4312
P: 4719
--
Jyrgen
U: 2742
P: 2616
--
Princess Diana
U: 6473
P: 6915
--
Harry Potter
U: 7892
P: 7214
2. Keycodes (needed in the task 2)
3963 28
4241 82
4729 26
5282 91
8203 66
3. Bills (needed in the task 3, select one)
Bill 1
Recipient: Jack Daniels
Account number: 4234
Sum: 24€ 60cents
Date: 4th of January
Message: Debt
--
Bill 2
Recipient: James Bond
Sum: 72€
Date: 17th of October
Message: Protection payment
--
Bill 3
Recipient: Madonna
Sum: 48€ 30cents
Date: 26th of December
Message: Loan
--
Bill 4
Recipient: Hospital
Sum: 500€
Date: 10th of April
Message: Hospital care
4. Forms (needed in the task 4, select 1 or 2 and 3 or 4)
Form 1
recipient: Winnie the Pooh
sum: 65 € 50 cents
message : loan
date : 10th of April
--
Form 2
recipient: Pokemon
message : rent
date : 12th of May
--
Form 3
recipient: Mickey Mouse
message : restaurant
date : 7th of June
--
Form 4
recipient: Spider Man
sum: 400 €
message : rent
date : 29th of May

Report

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Report

Uploaded by

Copyright:

Available Formats

Table of contents

1. General description of application ..........................................................................4

2. Dialogue structure ..................................................................................................5

5. The files ...............................................................................................................15

6. User profiles and other information ......................................................................16

7. General description of program code ....................................................................16

8. Usability test report ..............................................................................................17

1.1 The use of the program

1.2 General commands and behaviour of the program

2.1. General dialogue structure

New payment Payment form Bills under the payment

2.2 Dialogue structure of Registration

2.3 Dialogue structure quit menu

New bill menu Payment form menu Bills under payment

More? Remove one bill?

Remove bill1 Remove bill2 Remove bill3

2.4 Dialogue structure new bill menu

Recipient’s name? Euros? Date?

Account number? Cents? Message?

Bill is… Is it OK?

Yes Change one item…

Change one item?

Yes Change other item?

3.2 Main menu

3.3 Checking the key code

3.4 Payment menu

3.5 Checking the bills that are under payment

3.6 New payment

3.7 Payment form

3.8 Quitting the program

4.3 Main menu

4.4 Checking the key code

4.5 Payment menu

4.7 New payment

4.8 Payment form

4.9 Quitting the program

7. General description of program code

7.1 At the beginning and general variables

7.2 Registration menu

The variable muuttuja is used as seen below while greeting:

7.3 Main menu

7.4 New payment menu

7.5 Payment form menu

8. Usability test report

8.1.1 Test tasks

1. Register to the application and quit the program after registration.

8.2.1 Problems in grammars

8.2.2 Problems in prompts

8.2.3 Other problems

8.3. Improving the problematic areas

2. Keycodes (needed in the task 2)

3. Bills (needed in the task 3, select one)

4. Forms (needed in the task 4, select 1 or 2 and 3 or 4)

You might also like