...
10. Frequency of use: before and at the end of each period.
Lilia: BELLA and RECEP, i have corrected point 7 and 8, according to Merja's comments. I have put below the next steps we have to do,these are the copy-paste from the slides. In two words, we have to interview some users and then describe the interview (very shortly) and
then to create a persona. I have done the part with usability aspects, any corrections-suggestions and additions are welcome. I ill be off next lesson and lab, but then will be back.
NEXT STEPS TO DO:
Interview:
Interview technique: ask your interview subject to recall a specific event and describe to the best of their recollection how that event took place. Ask them to describe their experience when e.g. they tried to find an apartment for rent...
§Where were they?
§How long did it take?
§What computer equipment or software was used?
§What did they most enjoy about the experience?
§What was most annoying about the experience?
Built a simple persona from your data profile:
Include:
§Name
§A role or job title
§Quotes in the personas language
§Relevant demographics
§Descriptions that reveals goals, motivations, pain points
§Descriptions that describe primary activities this user type will engage in, where and in which social relations
Important usability aspects:
...
- accuracy and relevancy (data presented in the application, should be reliable and up-to-date).
Bella Lilia: BELLA and Recep, i have wrote below some ideas for Planning Report, suggestions are more than welcome.
TASK 2
Planning Report:
| Wiki Markup |
|---|
A test plan should be written down before the start of the test and it should address the following issues \[Nielsen 1993\]: |
• The goal of the test: to research usability aspects of WinhaWille student page,dentify problems and benefits:
Since WihnaWille is strictly educational assistance tool, we will not be covering attractiveness and visualization of the application, we will concentrate on the following tasks:
- to define if the structure of the menu is clear and the titles are understandable
- do the users able to successfully complete the task
- to detect if information represented is clear and understandable
- to detect if data is reliable and accurant
- to identify the most relevant/important parts of application, as well as missing and unnecessary ones, usefull and not
- to reveal general lareas for improvement
• Where and when will the test take place:Metropolia University, Leppävaara unit• How long is each test session expected to take:30-40 min per each user• What computer support will be needed for the test: computer with active internet connection• What software needs to be ready for the test:none• What should the state of the system be at the start of the test: computer is on, browser is pointed to a home page, such as google, or metropolia
.• What should the system/network load and What should the system/network load and response times be? (not too fast or too slow);did not get the question
• Who will serve as experimenters for the test: Bella, Lilia and Recep• Who are the users going to be and how are we going to get hold of them: users are Metropolia students, second part of question is not clear
• How many users are needed: 10 ---?
• What test tasks will the users be asked to perform:
- to find link/to go to WinhaWille (to understand if user knows it by heart, or needs to first log in to metropolia/tuubi page)
- to give an explaination of each submenu, what does each title means without browsing through it (to understand depth of knowledge of the application, to identify comprehension of submenu titles)
- to enroll to a study year
- to find and enroll to courses
- to check study progress
- to show the most common area of usage
- to show the less common area of usage
- to give a feedback on improvement
• What criteria will be used to determine when the users have finished each of the test tasks correctly:mistake absence, quick actions, correct answers• What user aids will be made available to the test users (manuals, online help, etc): no help• To what extend will the experimenter be allowed to help the users during the test: at a very minimum level• What data is going to be collected and how will it be analysed:
DATA:
- Talk alowd records: to gather immediate feedback on interacting with the system
- Interview or questionnaire results
- Observation: to collect verbal and nonverbal reactions (interjections, gestures, facial expression and etc) will be used as an addition to main research
METHODS:
analyzing quatitive data:
- calculation of frequency of successful performance
- time to complete the task
analyzing qualititive data:
- interview interpretation
- questionnare analysis
- heuretical analysisRECEP, i have also started Task2 in a separate wikipage, you can find the link in the page Tasks