Inspection

Preview this template

INSPECTION INSTRUCTIONS

Please read the instruction before you start inspecting the application.

[The Instruction can be found here]

xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:st1="urn:schemas-microsoft-com:office:smarttags"
xmlns="http://www.w3.org/TR/REC-html40">

You will be given several questions based on the ‘Specific Context’ and<br/>‘Transformation process’ [e
name="place"/>
name="PlaceName"/>
name="PlaceType"/>

SECTION
1: INSPECTION OF DATA TRANSFORMATION

style='color:red'>[If you are not reading the instruction yet, it can be found
here]

The
questions in this section are ONLY related to ‘Data Transformation Process’.
Therefore, you are required to step through and give full attention particularly
on tasks and data states in the Data Transformation of the diagram. Please
consider the questions and try to construct any possible failure stories that could
influence the usability of the application. From the stories, list out the problems
or anomalies that may hinder the effective, efficient and satisfying use of the
application.

style='color:red'>

IMPORTANT

WHAT YOU SHOULD DO?lang=EN-GB style='color:black'>

[Please remember these steps as you
need to do the same thing for all of the questions]style='color:black'>

style='color:black'>

style='color:black'>You will be given several questions based on the ‘specific
context’ and the ‘type of transformation process’.

style='mso-bidi-font-style:normal'>E.g.style='mso-bidi-font-style:normal'>

style='mso-bidi-font-style:normal'>Contextstyle='mso-tab-count:2'> : Users [Perceptual
System]

style='mso-bidi-font-style:normal'>Transformationstyle='mso-tab-count:1'> : Acoustic Parameters Transformation

style='mso-bidi-font-style:normal'>Questionstyle='mso-tab-count:1'> : Do you think
the users can perceive that there are two different levels of pitching?style='color:black'>

lang=EN-GB style='color:black'>

FOR EVERY QUESTION, YOU ARE
REQUIRED TO;

style='margin-left:21.0pt;border-collapse:collapse;border:none;mso-border-alt:
solid windowtext .5pt;mso-yfti-tbllook:480;mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-border-insideh:.5pt solid windowtext;mso-border-insidev:.5pt solid windowtext'>

style='mso-bidi-font-weight:normal'>STEP
1: style='color:black'>

lang=EN-GB style='color:blue'>By using the w:st="on">Task-Data State
Diagram, step through and focus at each ‘task’ and ‘data state’ of the
application;

lang=EN-GB style='color:black'>[You may need to give more attention to the
tasks and the data states of the specific transformation. The transformation
to focus on is dependent on the question you are currently referring to]

lang=EN-GB style='color:blue'>

lang=EN-GB style='color:blue'>STEP 2: style='color:black'>

lang=EN-GB style='color:blue'>While stepping through the design, use the
question and its related information in the Context of Use Descriptions (attachment 4) as your guideline to;

style='mso-bidi-font-weight:normal'> style='mso-list:Ignore'>1.
lang=EN-GB style='color:blue'>look for any possible failure stories that influence
the usability of the application;

style='mso-bidi-font-weight:normal'> style='mso-list:Ignore'>2.
lang=EN-GB style='color:blue'>identify and detect any possible problems
or anomalies from the stories that may hinder the effective, efficient and satisfying use of
the application (you may write with the solution if you have one); lang=EN-GB style='color:black'>

lang=EN-GB style='color:black'>[Some questions might require you to refer to
other documents. For instance, you might need to refer to the list of users’
previous experiences in the Context of Use Descriptions if the questions were
asking about the affect of users’ previous experience. You may also report
usability problems that not covered by given questions] style='mso-bidi-font-weight:normal'>.

lang=EN-GB style='color:blue'>STEP 3: style='color:black'>

lang=EN-GB style='color:blue'>For every problem you have found, rate its
‘level of severity’ by writing them in the correct given text box. lang=EN-GB>

lang=EN-GB>[Please write in point form if more than one problem] style='mso-bidi-font-weight:normal'>.

lang=EN-GB>

The Levels include:-

style='font-size:11.0pt;color:black;mso-ansi-language:EN-GB'> style='mso-spacerun:yes'> style='mso-spacerun:yes'> Level 1 style='font-size:11.0pt;color:black'> = cosmetic problem - only needs to be
fixed if extra time is available on project

Level 2 = minor usability
problem – fixing this should be given low priority

Level 3 = major usability
problem – important to fix, so should be given high priority

Level 4 = usability
catastrophe – imperative to fix this before it goes for development

Question.1.1: Can any user move handphone joystick to any contact points correctly using their thumb? Do you see any problem in terms of age, gender, physical capabilities and limitation

Question 1.2: Can any user move the handphone joystick to the same direction as in predefined list? Do you see any problem in terms of age gender physical capability and limitation etc?

Question 1.3: Can any user accept that handphone joystick can be used to write a normal shape of roman alphanumeric characters? Do you see any problem in terms of age, gender, physical capability and limitation etc?

Write your Failure Stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question.2.1: Do you think the users’ experiences can help them to move joystick to the correct contact point?

Question 2.2: Do you think the users’ experiences can influence them on how they write and follow the ‘shape of predefined alphanumeric characters’?

Question 2.3: Do you think users’ experiences such as a handwriting experience can influence the way they write characters or alphanumeric using joystick?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question.3.1: Do you think the users’ previous knowledge can affect the way they move and use the proposed joystick (with nine contact points) to the correct point or direction?

Question 3.2: Do you think the users' prior knowledge can help them to match correctly between the “moving path of joystick” and the “writing path of predefined alphanumeric character”?

Question 3.3: Do you think the users can apply their knowledge to write successfully any alphanumeric characters using joystick without always referring to predefined list?

Write you failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question.4.1: Do you think the users need skills and training to move or push the joystick into eight directions precisely from the center using their thumb?

Question 4.2: Do you think the skill in operating and moving joystick can help the user to match correctly between the ‘joystick movements' and the ‘shape of predefined alphanumeric characters’?

Question 4.3: Do you think without a proper training the user can move the joystick and follow the path of predefined alphanumeric characters?

Question 4.4: Do you think the users need skills and training to memorize and write alphanumeric character using joystick without always referring to the predefined list?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 5.1: Do you think the users can perceive whether or not their joystick is in the right points?

Question 5.2: Do you think the user can perceive and map between the ‘9 joystick contact points' and the ‘9 black dots writing path of predefined alphanumeric character’ as the same?

Question 5.3: Do you find any other possibilities for the user to get wrong perceptions when they try to match the joystick movement with what in the predefined list?

Question 5.4: Is it important for the user to perceive the shape of predefined alphanumeric character as a normal way writes normal Roman alphanumeric characters?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question.6.1: Do you think that more number of joystick contact points can create more possibilities of movement which eventually affect memorability, accuracy etc?

Question 6.2: Do you think it is significant for the user to know whether or not the direction has contact points to hit?

Question 6.3: In your opinion, do you think it is significant for the user to match exactly the same between the ‘joystick contacts points' and the ‘dots in the shape of predefined alphanumeric character’?

Question 6.4:Do you think the definition of ‘matching’ is flexible? (i.e. Must be exactly the same)

Question 6.5: Do you think that it is significantly important for the text writing by using joystick to be as closed as possible with normal writing of Roman Alphanumeric Characters?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question.7.1: By looking at the joystick, do you think the user can recognize it as a joystick with 9 different contact points (as most of handphone joystick can only be moved into 4 different directions including ‘up’, ‘down’, ‘left’ and ‘right’)?

Question 7.2: Do you think a reference is required on how to move the joystick?

Question 7.3: By looking at the joystick, do you think it can be easily used to follow the direction of the shape of predefined alphanumeric character?

Question 7.4:By looking at the joystick, do you think it can be used to write alphanumeric characters smoothly as writing a normal roman alphanumeric characters?

Question 7.5: Are there any reference materials available on how to write the predefined alphanumeric characters? Can it easily be referred and accessed?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question.8.1: Do you think the 9 contact points are sufficient to allow flexible movements of joystick?

Question 8.2: Do you think the predefined shape of alphanumeric character is easier to be created using the limited 9 joystick contact points?

Question 8.3: Do you think anyone can understand the shape of predefined alphanumeric characters?

Question 8.4: Do you think the nine joystick contact points are sufficient to represent alphanumeric characters?

Question 8.5: Do you think the characters in the predefined list can be perceived as real alphanumeric character?

Question 8.6: Are the list of predefined alphanumeric characters memorable?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question.9.1: Do you think the points are suitable to be transformed into acoustic parameters?

Question 9.2: Do you think the list of joystick contact points are suitable to be transformed into acoustic parameters?

Question 9.3: Do you think that the list of joystick contact points is enough to represent an alphanumeric character with acoustic parameters?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 10.1: Do you think the physical environment can influence the user on how they move the joystick into different directions exactly?

Question 10.2: Do you think the physical environment can influence the user from matching the ‘joystick movements’ with what in the ‘predefined list correctly’?

Question 10.3: Do you see any physical environment problems that can influence the user in creating any alphanumeric characters?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 11.1: Are there any possibilities for the users to select the wrong point? Are there anyway for them to avoid this?

Question 11.2: By looking at the steps/actions in the diagram, do you see any problems and difficulty for the user to move the joystick?

Question 11.3: How do you find the steps to move joystick according to the directions and shape of predefined alphanumeric characters?

Question 11.4: Do you think it is important for the joystick movement to be as flexible as writing using pen on paper?

Question 11.5: Do you see any problems of the predefined alphanumeric characters to be created using joystick?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

[This application is purposely for the situation where the user's eyes need to focus on other things eg. During walking]

Question 12.1: This application has no graphical interfaces; however, do you recognize the importance of incorporating graphical user interface into this application that might improve and influence the user in moving the joystick into varied directions correctly?

Question 12.2: This application has no graphical interfaces; however, do you recognize the importance of incorporating graphical user interface into this application for instance, to show the character being created to help them to match with the predefined list

Question 12.3: This application has no graphical interfaces; however, do you recognize the importance of incorporating graphical user interface into this application that might helps the user to learn faster and creates alphanumeric characters without frequently referring to the predefined list?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

SECTION
2: INSPECTION OF ACOUSTIC PARAMETERS TRANSFORMATION

style='color:red'>[If you are not reading the instruction yet, it can be found
here]

The
questions in this section are ONLY related to ‘Acoustic Parameters Transformation
Process’. Therefore, you are required to step through and give full attention particularly
on tasks and data states in the Acoustic Parameters Transformation of the
diagram. Please consider the questions and try to construct any possible
failure stories that could influence the usability of the application. From the
stories, list out the problems or anomalies that may hinder the effective,
efficient and satisfying use of the application.

style='color:red'>

IMPORTANT

WHAT YOU SHOULD DO?lang=EN-GB style='color:black'>

[Please remember these steps as you
need to do the same thing for all of the questions]style='color:black'>

style='color:black'>

style='color:black'>You will be given several questions based on the ‘specific
context’ and the ‘type of transformation process’.

style='mso-bidi-font-style:normal'>E.g.style='mso-bidi-font-style:normal'>

style='mso-bidi-font-style:normal'>Contextstyle='mso-tab-count:2'> : Users [Perceptual
System]

style='mso-bidi-font-style:normal'>Transformationstyle='mso-tab-count:1'> : Acoustic Parameters Transformation

style='mso-bidi-font-style:normal'>Questionstyle='mso-tab-count:1'> : Do you think
the users can perceive that there are two different levels of pitching?style='color:black'>

lang=EN-GB style='color:black'>

FOR EVERY QUESTION, YOU ARE
REQUIRED TO;

style='mso-bidi-font-weight:normal'>STEP
1: style='color:black'>

lang=EN-GB style='color:blue'>By using the w:st="on">Task-Data State
Diagram, step through and focus at each ‘task’ and ‘data state’ of the
application;

lang=EN-GB style='color:blue'>

lang=EN-GB style='color:blue'>STEP 2: style='color:black'>

lang=EN-GB style='color:blue'>While stepping through the design, use the
question and its related information in the Context of Use Descriptions (Attachment 4) as your guideline to;

style='mso-bidi-font-weight:normal'> style='mso-list:Ignore'>1.
lang=EN-GB style='color:blue'>look for any possible failure stories that influence
the usability of the application;

style='mso-bidi-font-weight:normal'> style='mso-list:Ignore'>2.
lang=EN-GB style='color:blue'>identify and detect any possible problems
or anomaliesfrom the stories that may hinder the effective, efficient and satisfying use of
the application (you may write with the solution if you have one); lang=EN-GB style='color:black'>

lang=EN-GB style='color:blue'>STEP 3: style='color:black'>

lang=EN-GB style='color:blue'>For every problem you have found, rate its
‘level of severity’ by writing them in the correct given text box. lang=EN-GB>

lang=EN-GB>[Please write in point form if more than one problem] style='mso-bidi-font-weight:normal'>.

lang=EN-GB>

The Levels include:-

Level 2 = minor usability
problem – fixing this should be given low priority

Level 3 = major usability
problem – important to fix, so should be given high priority

Level 4 = usability
catastrophe – imperative to fix this before it goes for development

Question 1.1: Do you think any users can detect and differentiate different levels of pitching and different degrees of panning? Do you see any problems in terms of age, gender, physical capabilities and limitation

Question 1.2: Do you think any users can judge the position of sound through different level of pitching and degree of panning? Do you see any problems in terms of age, gender, physical capabilities and limitation

Question 1.3: Do you think anyone can detect nine positions of sounds through the three levels of pitching and three degrees of panning? Do you see any problems in terms of age, gender, physical capabilities and limitation

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 2.1: Do you recognize any other user's experiences that might influence the user in differentiating the levels of pitching and degrees of panning?

Question 2.2: Do you think the users’ experiences can influence the way they predict different positions of ‘joystick contact point’ through the different combination of ‘pitching levels’ and ‘degrees of panning’? Can it be learned?

Question 2.3: Do you think the users’ previous experience can influence the users in identifying the nine coordinate of sound (from three levels of pitching and three degrees of panning)?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 3.1: Do you see any users’ previous knowledge that might influence or require by the user to be able to differentiate the pitching levels and different degrees of panning?

Question 3.2: Do you think the user can memorize the levels of pitching as well as degrees of panning?

Question 3.3: Do you see any other previous users' knowledge that might influence them in predicting and judging the sound position correctly based on different levels of pitching and degrees of panning?

Question 3.4: Do you see any previous users' knowledge that might influence them in identifying the nine coordinates of sound correctly?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 4.1: Do you think the users’ skill such as ‘sound listening’, ‘input device (e.g. joystick)’, or any other skills can influence the user in differentiating the levels of pitching as well as degrees of panning?

Question 4.2: Do you see any training requirement for the user to improve their detecting skill on pitching and degrees of panning?

Question 4.3: Do you think the users’ previous skills such as ‘sound listening’, input device (e.g. joystick) or any other skills can influence the ability of users to predict and judge the position (based on different pitches and degree of panning) correctly? Do you think the skill can be developed? How long does it take to develop the skill? Is it a reasonable period if time?

Question 4.4: Do you think the skill to detect nine coordinates of sound can be developed (e.g. through training)? How long does it take to develop the skill? Is it a reasonable period if time?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 5.1: Do you think the user can clearly perceive the different for both levels of pitching and degrees of panning even if they were played at the same time?

Question 5.2: Let’s assume that the array of pitching is {low, mid, high, mid, low}. Do you think the second ‘low‘is perceived as the same as the first ‘low'?

Question 5.3: Do you think the user can perceive the combination of both ‘pitching' and ‘degree of panning' as ‘sound at any positions'?

Question 5.4:Do you think different users perceive the same position for a sound with the same level of pitching and the same degree of panning? Lets assume that the user turns the volume down; do you think they can perceive the same position?

Question 5.5: If three levels of pitching are combined with three degrees of panning; do you think the user perceives both as 2-dimension with nine (9) coordinates representation?

Question 5.6: Without listening to any previous levels of pitching or degrees of panning; do you think the user can identify the coordinate of the sound (points)?

Write your failure stories:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 6.1: Is it important for the user to be able to differentiate levels of pitching and degrees of panning?

Question 6.2: Is it important for the user to be able to predict and judge the sound positions correctly?

Question 6.3: Do you think it is important for the user to know that the pitching parameter is representing horizontal coordinate and degree of panning parameter is representing vertical coordinate?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 7.1: Do you think the use can differentiate levels of pitching and degrees of panning only through stereo earphone?

Question 7.2: Do you think the user can predict the sound position only (pitching and panning) through stereo earphone?

Question 7.3: Do you think the user can identify the nine coordinates through stereo earphone? Is it important to have reference on how to identify these coordinates?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 8.1: Do you think the input of the acoustic parameters transformation (Matrix of Joystick contact points) are suitable to be mapped with three different levels of pitching and three different degrees of panning?

Question 8.2: Do you think the position of joystick contact points can be easily determine through sound by mapping them with different levels of pitching and different degrees of panning?

Question 8.3: Do you think the coordinate of 9 joystick contact points which are located in a matrix (3 x 3) can be represented by 3 levels of pitching (as vertical axis) and three degrees of panning (as horizontal axis)?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 9.1: Do you think the three levels of pitching and three degrees of panning are sufficient and suitable to represent the nine joystick contact points uniquely?

Question 9.2: Do you think the combination of different levels of pitching and different degrees of panning can create different sound locations or positions?

Question 9.3: Do you think the combination of three levels of pitching (low, mid, high) and three degree of panning (-90, 0, 90) can be used to create a 2-dimensional space eg. (low,-90) is the lower left point and (mid, 0) is the center point?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 10.1: Do you think the user can detect different levels of pitching and degrees of panning in all kind of environment eg. Noisy, restaurant, airport etc?

Question 10.2: Without really focusing on the sound such as while walking or driving; do you think the user can detect different levels of pitching and different degrees of panning?

Question 10.3: Do you see any other environments or situation (such as observing people during walking) that might influence the user in predicting and judging the position of joystick contact points through different levels of pitching and degrees of panning?

Question 10.4: Do you see any other environments or situation that might influence the user in identifying the coordinate of sound?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 11.1: Do you think the movement of joystick can help the user to differentiate levels of pitching and degrees of panning?

Question 11.2: Do you think the user interaction with joystick can influence them in predicting and judging the position of sound (represented by three levels of pitching and three degrees of panning)?

Question 11.3: Do you think the interaction with and position of joystick can influence how the user identifies the sound coordinates?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

[This application is purposely for the situation where the user's eyes need to focus on other things eg. during walking]

Question 12.1: No graphical interface provided. However, Do you see any important graphical user interface that will help the user to differentiate levels of pitching and degrees of panning?

Question 12.2: No graphical interface provided. However, do you see any important graphical user interface that will help the user to predict different position based on different combination of pitching and degree of panning?

Question 12.3: No graphical interface provided. However, do you see any important graphical user interface that might be able to help the user to identify those coordinate in space?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

SECTION
3: INSPECTION OF FINAL SOUND TRANSFORMATION

style='color:red'>[If you are not reading the instruction yet, it can be found
here]

The
questions in this section are ONLY related to ‘Final Sound Transformation
Process’. Therefore, you are required to step through and give full attention particularly
on tasks and data states in the Final Sound Transformation of the diagram.
Please consider the questions and try to construct any possible failure stories
that could influence the usability of the application. From the stories, list
out the problems or anomalies that may hinder the effective, efficient and
satisfying use of the application.

style='color:red'>

IMPORTANT

WHAT YOU SHOULD DO?lang=EN-GB style='color:black'>

[Please remember these steps as you
need to do the same thing for all of the questions]style='color:black'>

style='color:black'>

style='color:black'>You will be given several questions based on the ‘specific
context’ and the ‘type of transformation process’.

style='mso-bidi-font-style:normal'>E.g.style='mso-bidi-font-style:normal'>

style='mso-bidi-font-style:normal'>Contextstyle='mso-tab-count:2'> : Users [Perceptual
System]

style='mso-bidi-font-style:normal'>Transformationstyle='mso-tab-count:1'> : Acoustic Parameters Transformation

style='mso-bidi-font-style:normal'>Questionstyle='mso-tab-count:1'> : Do you think
the users can perceive that there are two different levels of pitching?style='color:black'>

lang=EN-GB style='color:black'>

FOR EVERY QUESTION, YOU ARE
REQUIRED TO;

style='mso-bidi-font-weight:normal'>STEP
1: style='color:black'>

lang=EN-GB style='color:blue'>By using the w:st="on">Task-Data State
Diagram, step through and focus at each ‘task’ and ‘data state’ of the
application;

lang=EN-GB style='color:blue'>

lang=EN-GB style='color:blue'>STEP 2: style='color:black'>

lang=EN-GB style='color:blue'>While stepping through the design, use the
question and its related information in the Context of Use Descriptions (Attachment 4) as your guideline to;

style='mso-bidi-font-weight:normal'> style='mso-list:Ignore'>1.
lang=EN-GB style='color:blue'>look for any possible failure stories that influence
the usability of the application;

lang=EN-GB style='color:blue'>STEP 3: style='color:black'>

lang=EN-GB style='color:blue'>For every problem you have found, rate its
‘level of severity’ by writing them in the correct given text box. lang=EN-GB>

lang=EN-GB>[Please write in point form if more than one problem] style='mso-bidi-font-weight:normal'>.

lang=EN-GB>

The Levels include:-

Level 2 = minor usability
problem – fixing this should be given low priority

Level 3 = major usability
problem – important to fix, so should be given high priority

Level 4 = usability
catastrophe – imperative to fix this before it goes for development

Question 1.1: Do you think any user can pay attention onto every single sound in a group? Do you see any problem in terms of age, gender, physical capabilities and limitation etc.

Question 1.2: Do you think any user can predict the position and follow the direction of all single sounds which are played in sequence as a group? Do you see any problem in terms of age, gender, physical capabilities and limitation etc.

Question 1.3: Do you think any user can conceptualize alphanumeric shape through a group of positions and directions of sounds? Do you see any problem in terms of age, gender, physical capabilities and limitation etc.

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 2.1: Do you see any users’ previous experience that can influence them in focusing on both level of pitching and degree of panning in every single sound in a group?

Question 2.2: Do you see any other previous experiences that can influence the users in predicting correctly sound directions of all separate sounds in a group if they were played in sequence?

Question 2.3: Do you see any other previous experiences that can influence users in conceptualizing the shape of predefined alphanumeric characters?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 3.1: Do you think the knowledge in music or sound can influence the user in recognizing and differentiating all levels of pitching and degrees of panning if they were played in sequence?

Question 3.2: Do you think the user needs to memorize the previous sound pitch to predict the next one? Or do you recognize any other knowledge that will help the user to focus on both level of pitching and degree of panning in every separate sound in a group

Question 3.3: Do you think the knowledge in music or sound can influence the user in predicting the directions of every single sound in a group if they were played in sequence?

Question 3.4: Do you think the user needs to memorize the previous pitching level (or degree of panning) of the sound as a reference in order to predict the position of the next sound?

Question 3.5: Do you see any previous users’ knowledge that might influence them in conceptualizing the position and direction of sounds as any shape of correct alphanumeric characters?

Question 3.6: Do you think the user can conceptualize a correct alphanumeric character without any knowledge about the predefined list? OR do you think the user MUST memorize all the alphanumeric characters in the predefined list in order for them to conceptualize its shape correctly?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 4.1: Do you see any users’ skills that can influence them in focusing on every level of pitching and degree of panning of sound in its group?

Question 4.2: If training was required, how long do you think it will take to learn and improve the skill in recognizing and differentiating all levels of pitching and degrees of panning of every single sound?

Question 4.3: In order to predict the position and direction correctly; do you think the users need any specific training? If training is required, how long does it take to learn?

Question 4.4: Do you see any users’ skills that can influence the users in predicting correctly the directions of all single sounds in a group?

Question 4.5: Do you think the users’ previous skills such as input device (joystick) or any other skills can influence them in conceptualizing a correct shape of alphanumeric character?

Question 4.6: Do you think the user can conceptualize the shape of alphanumeric characters without training?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 5.1: Do you think the user can focus on every single sound and perceive them as a group?

Question 5.2: Do you think the user can perceive the direction of sounds correctly if more than one single sound were played in sequence?

Question 5.3: Do you think the user can perceive the combination of different positions and directions of sounds as a shape of alphanumeric character?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 6.1: Is it important for the user to be able to focus on every single sound in a sound group?

Question 6.2: Is it important for the user to judge and predict correctly the position and direction of all single sounds in a group? Can this be achieved by playing all the single sounds in sequence?

Question 6.3: Do you think by allowing the user to finish creating alphanumeric character using joystick before playing its sounds output will improve the way they predict the position or directions?

Question 6.4: Do you think the shape of alphanumeric character is easier to be conceptualized by listening and interpreting the sound positions and directions?

Question 6.5: Do you think by allowing the user to finish creating alphanumeric character using joystick before playing its sound output will improve on how they conceptualize the shape of alphanumeric character being created?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 7.1: Do you think that the user MUST be using stereo earphone in order to focus every single sound in its group?

Question 7.2: Do you think that the user MUST be using stereo earphone in order to predict the sound positions and directions correctly?

Question 7.3: Do you think the user will still be able to conceptualize a shape of alphanumeric character if the sounds were played throughout different output device other than stereo earphone, for instance through a built in handphone stereo speaker?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 8.1: Do you think the level of pitching and degree of panning for every single value in a group can be easily detected?

Question 8.2: Do you think the combination of different levels of pitching and different degrees of panning can be played in sequence to create moving sound in space?

Question 8.3: Do you think the position and direction of sounds can help the user in conceptualizing the shape of predefined alphanumeric characters?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 9.1: Do you think by playing the sound in sequence and giving silent gap in between for about 0.25s will help the user to recognize both acoustic parameters (pitches and degree of panning)?

Question 9.2: Do you think the first sound can be recognized the first sound of the overall sounds in a group?

Question 9.3: Do you think by playing every single sound in sequence with at least 0.25 second gap in between will help to clarify and improve the prediction of sounds positions and directions?

Question 9.4: Do you think the whole sequence of sounds can be used as a feedback of users’ joystick movements where they can learn on how to create alphanumeric characters correctly?

Question 9.5: Do you think the predefined list of alphanumeric characters can be easily conceptualized through sounds representation in this application?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 10.1: Do you see any other environments or situations that can influence the user in focusing every single sound in its group?

Question 10.2: Do you see any other environments or situations (such as observing people during walking) that can influence the user in predicting correctly the directions of all single sounds in a group?

Question 10.3: Do you see any other environments or situations (such as observing people during walking) that can influence the user in conceptualizing the shape of the sounds?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

Question 11.1: Do you see any problems for the user to focus and differentiate all levels of pitching and degrees of panning if the sounds were played only after the user create or move the joystick.

Question 11.2: Do you think the interaction joystick can help the user to focus and recognize the level of pitching and degree of panning of all single sound in a group?

Question 11.3: Do you think the interaction with handphone joystick can influence the users on how they predict the position and direction of all single sounds? If yes, would it be any difference if the sounds were only played after the interaction?

Question 11.4: Do you think the interaction with handphone joystick can influence the users on how they conceptualize the shape of alphanumeric characters? If yes, would it be any difference if the sounds were only played after the interaction?

Question 11.5: Do you think the users can detect problems or errors throughout the sounds if they have created a wrong movement?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

[This application is purposely for the situation where the user's eyes need to focus on other things eg. during walking]

Question 12.1: Do you see any important graphical interface that will help the user to recognize and differentiate all pitches and degree of panning of every single sound in its group?

Question 12.2: Do you see any important graphical interface that will help the user to predict correctly the position and direction of all single sounds in a group?

Question 12.3: Do you see any important graphical interface that will help the user to improve on their way of conceptualizing a correct alphanumeric character?

Write your failure stories here:

Level 1 = cosmetic problem - only needs to be fixed if extra time is available on project

Level 2 = minor usability problem – fixing this should be given low priority

Level 3 = major usability problem – important to fix, so should be given high priority

Level 4 = usability catastrophe – imperative to fix this before product can be released

use this free template

Inspection

Related templates and questionnaires

QuestionPro in your language

Awards & certificates

The Experience Journal