Home

Topic Paper - Michigan Technological University

image

Contents

1. consider show before whether tapping the thought it information would lead to that have the real entered instructions into data but those are section much further assumed down could edit and change content as well as do other features to record and analyse my daily total Materials that Types of The Home page Measuring Could be Tap app might be hooks used measuring could use tree visuals buttons clarified by to hang instructions more because visual bucket or the tap graphics there is Knots in rope instructions none for measuring number of taps per tree Examples of There are no Records tab don t misleading or visuals is understan complex misleading d why the visuals and forecast is provides no necessary info Best if on the the name home the tree page in data there entry could bea separate visual for that Other A help tab Lots of problems with should be text Could design of present in h more documentatio each organized n section to provide asses tab in 32 each function of the application Anything that could create legal or cross cultural problems Also add temperature in Celsius The measurement s are all English the rest of the world uses metric Alternative ways of making document easier Shorten the early instructions and add an intro Better home page log out Better grap
2. present a tool for first the users For app Feedback on Yes basic Sorta the yes Looks Did notlike The basic structure of layout labels make good it no structure is design intuitive sense and lead Makes good just to the right sense to need to areas me separate trees per saved data with 24 amount of taps gallon S Feedback on Button fine Everything is Yes should Bigger data It was Help buttons and page seems readable and be more entry fields readable button is font almost too fine organized font size and large too large plain good but then the weather data to the right was small Feedback on No had Yes but The record Not really No some Same as data logging assumed certain fields and data clear if it of the spots comment 1 process that each were missing entry wants plot weren t plot would like diameter sectionisa dataor clear on be able to bit individual what was handle confusing tree data supposed multiple to be tree inputs entered where Feedback on Page didn t Not right now yes Yes easily No could Need data display work viewed and not find button to makes where to view edit sense view data data logged in Efficiency of would edit had to The help When the When was Overall design enter data reenter the section screen was reading the great page Think plot name should be landscape help it design if more excel each tim
3. should be with the more unknowing practical of tree tappings the help info is spot on Anything P did Tree It was all was not The rope Never Little not tapping understandabl sure about for explains confused understand on number 3 e where to go determinin why the between first reading Wording is to startthe g the diameter of difference awkward tutorial number of the tree is of tap app expected taps was important help the app to confusing it just says catchy knowl was at first until it is names anew user it was though and tutorial explained guide me to further help or farther readable down page Anything P N A Nothing Records Nothing Nothing N A couldn t section understand at all Expressions N A The measuring No it was No The help is N A that seemed instructions expressed a bit wordy wordy The tools list in a good should only amount of have words explanations for things people don t recognize like tap spile etc 21 Other It is a very Some Need more Everything visuals N A problems with straight instructions color looks great style forward are wordy Needs a aesthetic some aren t it theme style which could be more is easy to even and easy navigate to read and find information Anything that Everything The tools list You should The tap No N A is out of order seems well should come add more number organized after an i
4. 11 Scenario 2 user centeredness of maple app Test Goals To test the extent to which app can help first time users tap maple syrup easily and quickly To assess how user can download and install app easily and quickly To assess how user can identify and use the key tools quickly and easily To assess how efficient and learnable the app is To improve user s perception of the quality of the app s interface To assess how easy users can remember the system To reduce the number of errors users make when they use the app Quantitative measurement State the number of commands or features you did not use State the number of commands or features you utilized State the number of times you expressed frustration Record the time you took to complete your task Record the number of errors you committed How long did it take you to recover from errors How frequent did you use the manual State the number of times you referred to it How frequent did the manual help you to solve your problem Strike a ratio between the number of times you were successful using the app and the number of errors you committed How many times did the system divert your attention from the main task 12 Scenario description am a maple syrup enthusiast love to tap maple trees for fun and sometimes make some few dollars from the sale of the syrup am so excited that got a smart phone that has an app that can help me tap trees calculate the
5. Each one focusing specifics on records enter data to help weather add more appea 41 The tree tapping should really be things to consider before tapping I thought it would lead to the real instructi OMISSIONS The instructions say to have a thermometer but it is not listed Overview or intro no Not when you use the feature for the first time you have to navigate to the help sector first No warnings it should state when and where you are able to tap a tree Never explains why the diameter of the tree is important it just says it is Types of hooks used to hang bucket Knots in rope for measuring number of taps per tree A help tab should be present in each section to provide asses tab in each function of the application Also add temperature in Celsius WORDINESS The measurement instructions They take up as much space as the rest of the guide Most people would know how tc The help is a bit wordy Some instructions are wordy some aren t it could be more even and easy to read Need more color Needs a theme Shorten the early instructions and add an intro Lots of text Could be more organized MOBILE APP LOOKS GOOD MAKES SENSE The basic structure is good Yes Basic layout intuitive The labels make sense and lead to the right areas 42 READABLE Everything is readable and fine It was readable and large NOT CLEAR CONFUSING FRUSTRATING had assumed that each plot would be able to handle multiple tree inputs The rec
6. believe instructions little be located should be They take up unnecessar ina better smaller as much y ifthe user place due to the space as the is using a simplicity rest of the measuring of the guide Most tape application people would know how to measure a tree Any gaps in The It was a bit Info could Display full information instructions staggered be more amount of saytohavea Could have effective if information thermometer flowed or visuals but it is not transitioned were used listed better Inaccurate Sunniest information side of tree could be misleading during an overcast day Should read 29 sunniest side of tree typically south Title brief Overview or Not when Not unless overview intro no you use the you go to feature for app help the first time you have to navigate to the help sector first Cautions No warnings Not really No it No No None that warnings should should be state when needed and where you are able to tap a tree Any other Not pre Other than problems mapping of for some about content the buttons people with should be the more unknowing practical of tree tappings the help info is spot on Anything P did Tree tapping was not The rope Never Little not number 3 sure about for explains confused understand on Wording is where to go determinin why the between first reading awkward tostart th
7. have apps There will be one participant at each testing time and testing time will not exceed sixty minutes The participant will test the app by using it to accomplish tasks Participant will be required to answer some questions about the app and its documentation 17 Pre test questions 1 How many years have you used a smart phone 2 Please indicate your level of agreement to the follow statement am very interest in the testing of this android application 1 Strongly agree 2 Agree 3 Neutral 4 Disagree 5 Strongly disagree 18 Computer User Interface Usability Testing You are being invited to participate in a research study to determine the usefulness and usability of computer user interfaces This study is being conducted by Dr Robert Pastel of Michigan Technological University Computer Science Department and students in Dr Pastel s Human Computer Interaction HCI courses The students are performing the usability tests as part of their project and to fulfill the HCI course requirements There are no known risks if you decide to participate in this research study There are no costs to you for participating in the study The information you provide and tasks that you will perform will determine the usefulness and usability of user interfaces The questionnaires and the tasks should take less than an hour to complete The information collected may not benefit you directly but the information learned in this st
8. many times did you call for help What number of commands or instructions didn t you use How many steps did you have to go through in order to complete a task Scenario description You are a maple syrup enthusiast and you have sought for ways you can tap trees in an easy and enjoyable manner You also wished you could keep track of your tapings when is it appropriate to tap what supplies are necessary to carry along Fortunately you bought a smart phone that has an app that can help solve most of the problems you are pondering over But how can you use the app on the smart phone You found yourself in the midst of a lot of trees in a cold spring day in Northern part of United States You are definitely sure maple sugarbushes are close to where you are You turned to your smart phone and you realized that the mobile app can help you identify the trees and help you tap You don t do this often but you turned to the documentation section to view the user manual that contained instructions that can help you navigate your way through the app Task list Use the documentation manual to Find where you can enter information about your tap Find how you can enter information about the tap Find out how you can save information for later use Find out the steps you will go through in order to tap maple tree Tap maple tree with ease Identify the appropriate moment to tap Access the calculator and use it to calculate aspects of syrup yiel
9. A isoutoforder seems well organized Problems The N A organization organizatio pose n is pretty easy to follow Any headings All headings None None missing are straight confusing forward Materials that might be clarified by visual Examples of misleading or complex visuals Other None N A None N A problems with design of documentatio n 27 Anything that None Nothing N A could create seems legal or cross misleading cultural problems Alternative Was very ways of easy to use making document easier For app P1 P2 P3 PA P5 P6 Feedback on Yes Basic The labels yes Looks good The basic structure of layout make sense Makes sense structure is design intuitive and lead to to me good just the right need to areas separate trees per saved data with amount of taps gallons Feedback on Everything is It was buttons and readable readable font and fine and large but then the weather data to the right was small Feedback on data logging process Feedback on yes Yes easily data display viewed and 28 makes sense Efficiency of Overall design great design if the view flaws get worked on Negative findings For documentation P1 P2 P3 P4 P5 P6 Any irrelevant The Measuring Weatheris The help information measuremen using meter relevant button t stick is a but could
10. Usability test report of maple app designed by GoggleFox For Professor Robert Pastel Michigan Technological University Computer Science Department By Isidore Kafui Dorpenyo Michigan Technological University Department of Humanities Contents Description of UI test goals and test oruinn r r AE ANINA A ATA NEA AENA 3 POSE PIE aona AA AA A ene 5 Results 5x aet Arcam a A RR A AE E A S T oe Te teres 20 Conclusion and suggestions aperies ra EEEN NATA TETAAN 36 Appendix A BUg reports o ne E E E E T S E E E sea eee 38 APpendixsiB Excelisheet x5 e e raaa ada 41 Description of UI test goals and test Group GoogleFox successfully completed a usability testing of the maple syrup app designed to among other things aid independent maple syrup producers in their tasks while gathering information for the USDA to use on independent maple syrup production The group has been tasked to design an app that can help calculate the economic value generated by maple syrup enthusiasts GoggleFox is required to design a mobile app where people could self report their production levels days with good sap flow total number of trees tapped etc would facilitate this data collection The app consists of tools that can help users to check temperature data number of taps records of taps the tree that is tapped and yield calculator will help gather data on key production numbers and using those numbers to calculate production stat
11. application was easy to perform the task 1 Strongly agree 2 Agree 3 Neutral 4 Disagree 5 Strongly disagree 2 Please indicate your level of agreement to the follow statement enjoy using this android application 1 Very much 2 A little bit 3 Neutral 4 Not very much 5 Not at all 3 Please indicate your level of agreement to the follow statement would use this android application again 1 Strongly agree 2 Agree 3 Neutral 4 Disagree 5 Strongly disagree 15 Bug report form Name of experimenter Isidore Kafui Dorpenyo Name of participant Time Date Bug number Bug name Location Description 16 Test set up details The testing will take place in the usability testing center at Rekhi hall It is a quiet room that is set up for usability testing Present in the room is a camera that records the process The room is large enough so participants can position and reposition themselves At each point of the test there will be about four students in the room three undergraduate students and one graduate student One undergraduate student a SC major preferably will be available to explain the functionality of the app Other undergraduate students present will observe and take notes keep time or offer help to participants The graduate student will mostly serve as the test administrator Participants will be served with mobile phones that
12. ation measurement information using meter relevant button instructions was concise stick is a but could believe They take up and good little belocated should be as much space unnecessar ina better smaller due as the rest of y if the user place to the the guide is using a simplicity Most people measuring of the would know tape application how to measure a tree Any gaps in Clear The It wasa bit No Info could Display full information thought instructions staggered be more amount of flow well say to have a Could have effective if informatio organized thermometer flowed or visuals n but it is not transitione were used listed d better Inaccurate None Not as far as They was to Sunniest None N A information know use records side of feature tree could be misleading during an overcast day Should read sunniest side of tree typically south Title brief Includes a Title yes yes Not when yes Not unless Yes overview title Overview or you use the you go to introduction intro no feature for app help other the first definitions time you and tools have to navigate to 20 the help sector first Cautions No warnings Not really No it No No None that warnings should should be state when needed and where you are able to tap a tree Any other none none Not pre none None that Other than problems mapping of noticed for some about content the buttons people
13. d Qualitative measurement How easy were you able to use the document 1 2 3 45 67 8 9 10 Did you find it easy to navigate through the document 1 2 3 4 5 67 8 9 10 To what extent was the document useful and usable 12 3 4 5 67 8 9 10 What positive features about the documentation can you recall How easy were you able to learn the document 12 3 4 5 67 8 9 10 How useful was the document 12 3 4 5 67 8 9 10 How motivated are you to use the app 12 3 4 5 67 8 9 10 e How motivated are you to recommend the app to others 12 3 4 5 67 8 9 10 Post scenario interview or questionnaire Evaluate the content Identify any irrelevant information Do you see any gaps in the information Indicate What information is inaccurate Does the documentation include a title a brief overview or introduction Does the document contain cautions warnings and dangers of using the app What other problems does the content present Evaluate the style Identify anything that you did not understand on first reading What couldn t you understand at all Could you identify expressions that seem wordy inexact or too complex List other problems with the style Evaluate the organization Is there anything that is out of order or hard to locate or follow State those things What problems does the organization pose Evaluate the design Indicate any headings that are missing confusing or excessive Give examples of mate
14. e g the diameter difference tutorial number of of the tree of tap app expected taps was is help catchy the app to confusing important names know was at first until it just says though a new user it was itis and tutorial explained guide meto further help or farther readable down page 30 Anything P Records couldn t section understand at all Expressions N A The The help is that seemed measuring a bit wordy instructions wordy The tools list should only have explanations for things people don t recognize like tap spile etc Other Some Need more problems with instructions color style are wordy Needs a some aren t theme it could be more even and easy to read Anything that The tools list Youshould The tap is out of order should come add more number after an intro sections rope could of some kind Each one be At first focusing explained thought the specifics on ina instructions records different came from enter data order figuring out to help how the tools weather all fit together add more appealing graphic design Problems might not Creativities Just organization have known design confusing pose the real should add at first instructions more colors were there if hadn t looked Any headings The tree When using missing tapping the records confusing should really feature it be things to does not 31
15. e if set in main oriented would have the view sheet had multiple page couldn t been nice flaws get trees on the find the for visuals worked on same plot I d submit have to do it button multiple times Next drew two tables one negative responses representing positive responses and the next representing 25 Positive findings For documentation P1 P2 P3 P4 P5 P6 Any irrelevant Informatio information n was concise and good Any gaps in Clear No information thought flow well organized Inaccurate None Not as far as None N A information know Title brief Includes a Title yes yes yes yes overview title Overview or introduction intro no other definitions and tools Cautions warnings Any other None none none None that Other than problems noticed for some about content people with the unknowin g of tree tappings the help info is spot on Anything P did It was all not understandabl understand on first reading Anything P N A Nothing Records Nothing Nothing N A couldn t section understand at all 26 Expressions N A It was No N A that seemed expressed wordy in a good amount of words Other It is a very Everythin N A problems with straight g looks style forward great aesthetic style which is easy to navigate and find information Anything that Everything No N
16. g the number of taps was confusing at first until it was explained further farther down Little confused between difference of tap app help catchy names though The tap number rope could be explained in a different order I might not have known the real instructions were there if I hadn t looked Just confusing at first Records tab is misleading and provides no info Best if the name the tree in data entry EASY CLEAR UNDERSTANDABLE WRONG LOCATION information was concise and good Clear thought flow well organized Includes a title introduction other definitions and tools It was all understandable Other than for some people with the unknowing of tree tappings the help info is spot on it was expressed in a good amount of words It is a very straight forward aesthetic style which is easy to navigate and find information Weather is relevant but could be located in a better place Not unless you go to app help The tools list should come after an intro of some kind At first I thought the instructions came from figuring out how UNNECESSARY INFORMATION SOLUTIONS Measuring using meter stick is a little unnecessary if the user is using a measuring tape The measuring instructions The tools list should only have explanations for things people don t recognize like tap I don t Sunniest side of tree could be misleading during an overcast day Should read sunniest side of tree typically sout You should add more sections
17. hic design with more colors More options for wealth how to s and setting Auto fill information used by gaps and wealth applications Provides help in each sub application to help users understand how to fill or use each feature or present a tool for first the users Ability for the user to change text size Design would help like said before maybe some more visuals based on directions Also have categories Maybe make a small video when you open the app of a cheesy cartoon figure tapping a tree Pretty cool app though 33 For app Feedback on The basic structure of structure is design good just need to separate trees per saved data with amount of taps gallon S Feedback on Button fine Yes should Bigger data It was Help button buttons and page seems be more entry readable is too large font almost too organized fields font and large plain size good but then the weather data to the right was small Feedback on No had Yes but The record Not really No some Same as data logging assumed certain fields and data clear if it of the comment 1 process that each were missing entry wants plot spots plot would like diameter sectionisa data or weren t be able to bit individual clear on handle confusing tree data what was multiple tree supposed inputs to be entered where Feedback on Page didn t No could Need data disp
18. istics The app provides a simple how to guide and helps users to tap maple trees with ease Having completed designing the app and its documentation we set to conduct a usability test We had two main purposes to evaluate the content organization style and design of the documentation and to assess the extent to which app can help first time users tap maple syrup easily and quickly With these goals in mind we set apart three days for the test Monday April 14 Tuesday April 15 and Thursday April 17 We conducted two tests on Monday three on Tuesday and one on Thursday Each testing time lasted an hour or less We fell short of one participant because she could not make it to the testing place due to extreme weather conditions The original plan to test seven participants was not met Therefore results of analysis will be based on responses from six participants Gender representation was not balanced as we had five males and one female The test followed a simple procedure Testers present welcomed the participants to the testing center One of the humanities students briefed the participants on expectations This was meant to keep the participant at ease In most of the cases the person doing the briefing assured the participants that test was not conducted on them but on the app and its documentation The facilitator issued consent form and pre test questions for participants to fill out After forms and other necessary documents were fil
19. lay work not find button to where to view edit view data data logged in Efficiency of would edit had to The help When the When Overall design enter data reenter the section screen was was great page Think plot name should be landscape reading design if more excel each time ifl setinmain oriented the helpit the view sheet had multiple page couldn t would flaws get trees on the find the have been worked on same plot I d submit nice for have to do it button visuals multiple times 34 After had finished organizing under various tables reread the collated results in order to identify reoccurring ideas and issues grouped issues and recurring ideas into categories and labels came out with seven different categories that captured the content of the responses for documentation and five for app Categories for documentation are Unclear confusing Easy clear understandable Wrong location Unnecessary information Solutions Omissions Wordiness And categories for app are Looks good makes sense Readable Missing omissions Not clear confusing frustrating Miscellaneous In an excel sheet grouped responses under the various categories Check appendix B 35 Conclusion and suggestions Based on responses provided would say that documentation and app met the needs of the participants Almost all 6 participants found app and documentation very intuitive and easy t
20. led out participants were presented with various testing materials http www csl mtu edu classes cs4760 www projects group5 www http cs4760 csl mtu edu 2014 scientists and applications HScientist5 3 We conducted two different tests on each participant First we issued out the scenario for documentation or help manual This scenario asked that participant to use the tapping guide to tap a tree for the first time Participants were asked to read the tapping manual in order to produce a step by step explanation of how to tap a tree After completion of tasks participants were asked to answer some questions Here we combined questions from Brandon s scenario and mine scenario since both scenario s aimed at testing the usability of the documentation After the completion of task 1 we proceeded to the second task Here we tested the app proper Participants were asked to enter specific data into app and check if data was saved Participants were asked to fill out post test questionnaires and interview questions Bugs were taken note of Overview of presentation schedule Monday 2 00 3 00 pm first participant tested 3 30 4 30pm second participant tested Tuesday 11 00 am 12 00 first participant tested 1 00pm 2 00pm second participant tested 3 00pm 4 00pm third participant tested Thursday 11 00 am 12 00 noon participant could not show up 1 00pm 2 00pm second participant tested Our testing was not without prob
21. lems On the first day we were forced to perform the firs usability testing in the computer lab at Rekhi because a group was testing their app in the room that we scheduled to use The second test for the day was performed in the atrium at Rekhi I believe strongly that it did not affect our results For the purpose of a smooth run of test we used Brandon Perelman s scenario 2 Check appendix A for bug reports Test plans Even though present my original test plan below must say that we did not strictly adhere to our test plans We wanted to make room for our scenarios to be tested within the stipulated time so we merged sections for instance merged the post test questionnaire of my second test scenario with that of my Brandon s We also used his scenario and questionnaires to test the app Scenario 1 documention guide test Test Goals To evaluate the content organization style and design of the documentation To assess how usable the document is To test the clarity brevity and syntactic quality of user documentation To determine the ease of use of the documentation To assess the simplicity or difficulty of the documentation To assess how document can help you learn how to tap trees record information and produce sugar and syrup Quantitative measurement list How long did it take you to identify the information you need How much task were you able to accomplish with the help of the documentation How
22. ment where appropriate e Font size and data entry size must be increased where appropriate e Users should be allowed to aggregate multiple trees entered individually into single plots And for documentation we recommend e Conciseness in wording and sentence construction e That if it is necessary visuals should be used to explain steps or procedures e Clarity in sentence construction 36 These suggestions and comments should be attended to by both app developers and documentation experts Improvements should be tested again 37 Appendix A Bug reports Gap pee S MS sam Ep a an Bug Report Form Experimenter Name reso Date Af Bug Number Bug Name o Bug Location ras Bug Descrintion Lying om a tard elo epo chal bein tora Procedure for Replicating the Problem Qe cov Ay Chie kk A fi LLord i 38 Bu rt Fo xperimenter Name MEC orm Date Y pena 2 Bug Name Jw bee Bug Location Entes Papa A chants Procedure for Replicating the Problem LAA Pafe Syren MAS 39 Bug Description Whaea posses Suba ap iption Procedure for Replicating the Problem LaS pees 4 Ims dals Gallons 40 Appendix B Excel sheet UNCLEAR CONFUSING DOCUMENATATION Tree tapping number 3 Wording is awkward I was not sure about where to go to start the tutorial I expected the app to know I was a new user and tutorial guide 1 The rope for determinin
23. nd complex misleading why the visuals and forecast is provides no necessary info Best if on the the name home page the tree there could in data bea entry separate visual for that Other None N A A help tab none Lots of text N A problems with should be Could be design of present in more documentatio each organized n section to provide asses tab in each function of the application Anything that Also add The don t see None Nothing N A could create temperatur measurements any legal seems legal or cross e in Celsius are all English problem as misleading cultural the rest of the long as the problems world uses app does metric not tell personal info on what you have logged 23 in the records Alternative Was very Shorten the Better Ability for Design Maybe ways of easy touse early home page the userto would help make a making instructions log out change text like said small video document and add an Better size before when you easier intro graphic maybe open the design with some more appofa more visuals cheesy colors based on cartoon More directions figure options for Also have tapping a wealth how categories tree Pretty to s and cool app setting though Auto fill information used by gaps and wealth applications Provides help in each sub application to help users understand how to fill or use each feature or
24. ntro sections rope could of some kind Each one be At first focusing explained thought the specifics on ina instructions records different came from enter data order figuring out to help how the tools weather all fit together add more appealing graphic design Problems might not Creativities Just The N A organization have known design confusing organizatio pose the real should add at first n is pretty instructions more colors easy to were there if follow hadn t looked Any headings All headings The tree When using None None Just the missing are straight tapping the records tap app confusing forward should really feature it help be things to does not buttons consider show before whether tapping the thought it information would lead to that I have the real entered instructions into data but those are section much further assumed down could edit and change content as well as do other 22 features to record and analyze my daily total Materials that Types of The measuring Home page Measuring Could be Tap app might be hooks used instructions or could use tree visuals buttons clarified by to hang the tap more because visual bucket instructions graphics there is Knots in none rope for measuring number of taps per tree Examples of N A There are no Records tab none don t N A misleading or visuals is understa
25. number of taps and record information on taps You found yourself in the midst of a lot of trees in a cold spring day in Northern part of United States You are definitely sure maple sugarbushes are close to where you are You are definitely sure maple trees are close to where you are You turned to your smart phone and you realized that the mobile app can help you identify the trees and help you tap Now you have to find out how to navigate the system 13 Task list Main task is to use the app to produce maple syrup Sign up and use app Use the app to select a site Use the app to look for maple tree and tap Log data into application Save data and continue Qualitative measurement To what degree do you agree or disagree with the following statements about the system It was very easy to learn how to use the system 1 2 3 45 67 8 9 10 Using this system was a frustrating experience 1 2 3 45 67 8 9 10 feel that this system allows me to achieve very high productivity 1 2 3 45 67 8 9 10 worry that many of the things did with this system may have been wrong 1 2 3 45 67 8 9 10 This system can help me achieve all the tasks want to accomplish 1 2 3 45 67 8 9 10 The system is very pleasant to work with 1 2 3 45 67 8 9 10 Icons are easy to identify and understand 1 2 3 45 67 8 9 10 14 Post scenario interview or questionnaire 1 Please indicate your level of agreement to the follow statement Overall this android
26. o use However participants expressed some concerns that need to be addressed First is the app Designers should consider working on clarifying data logging process since all six participants expressed negative comments According to participants the data logging process is not clear Most of the participants were confused with regard to what plot wanted Some also did not find where to view data or edit data logged in and others want designers to increase font size and data entry field Documentation needs to be improved as well The most recurring issues about documentation center around confused or unclear instructions wordiness omission of important information and unnecessary information For instance some of the participants said that the documentation is confusing at first look or not sure about where to go to start the tutorial expected the app to know was a new user and tutorial guide me to help or readable page others also stated that weather is relevant but could be located in a different place or The tools list should come after an intro of some kind At first thought the instructions came from figuring out how the tools all fit together some also stated that the measurement instruction take up as much space as the rest of the guide or documentation developers should shorten the early instructions and add an intro For the app we recommend that e All data fields must contain units of measure
27. ord and data entry section is a bit confusing No some of the spots weren t clear on what was supposed to be entered where had to reenter the plot name each time if had multiple trees on the same plot l d have to do it multiple times When the screen was landscape oriented couldn t find the submit button EDITING TOOLS Need button to view edit data logged for MISSING OMISSIONS Yes but certain fields were missing like diameter Home page could use more graphics 43 Appendix C Attendance sheet Session Day Time Location Undergraduate student present 04 14 2014 2 00 3 00 1 Estafania Borns 2 David Nyakundi 3 Travis Foster 4 Theresa Tran 5 Quincy Howe 04 14 2014 3 30 4 30 1 Estafania Borns 2 Theresa Tran 3 David Nyakundi 4 Travis Foster 5 Quincy Howe 04 15 2014 11 00 12 00 HCI lab 1 Ann Dahlquist 04 15 2014 1 00 2 00 HCI lab 1 Estafania Borns 2 Thomas Black 3 Ann Dahlquist 04 15 2014 3 00 4 00 HCI lab 2 Ann Dahlquist 44 04 17 2014 11 00 12 00 HCI lab 1 Ann Dahlquist 04 17 2014 1 00 2 00 HCI lab 1 Estafania Borns 2 Thomas Black 45
28. rial that might be clarified by a visual Give examples of misleading or overly complex visuals List other problems with design of documentation Identify anything that seems misleading or that could create legal problems or cross cultural misunderstanding Kindly suggest alternative ways of making this document easier to use Bug report form Name of experimenter Isidore Kafui Dorpenyo Name of participant Bug number Bug name Location Description 10 Test set up details The testing will take place in the usability testing center at Rekhi hall It is a quiet room that is set up for usability testing Present in the room is a camera that records the process At each point of the test there will be about four students in the room three undergraduate students and one graduate student One undergraduate student a SC major preferably will be available to explain the functionality of the app Other undergraduate students present will observe and take notes keep time or offer help to participants The graduate student will mostly serve as the test administrator Participants will be served with mobile phones that have apps There will be one participant at each testing time and testing time will not exceed sixty minutes The participant will test the app by using it to accomplish tasks Participant will be required to answer some questions about the app and its documentation
29. udy should provide more general benefits The questionnaires and test are anonymous Do not write your name on the survey No one will be able to identify you or your answers and no one will know whether or not you participated in the study except for the instructor of the class that is giving you credit for participating Should the data be published no individual information will be disclosed Your participation in this study is voluntary By completing the questionnaires and performing the tasks you are voluntarily agreeing to participate You are free to decline to answer any particular question you do not wish to answer or not to perform a task for any reason If you have any questions about the study please contact Dr Robert Pastel Assistant Professor Computer Science Department Michigan Technological University Houghton MI 49931 The MTU Institutional Review Board has reviewed my request to conduct this project If you have any concerns about your rights in this study please contact Joanne Polzien of the MTU IRB at 906 487 2902 or email jpolzien mtu edu Participant signature and date 19 Results This section details the results and process of analysis for both the documentation and the app First collated all the responses in a word document This was organized in a table Results for documentation P1 P2 P3 P4 PS P6 Any irrelevant The No Measuring Weatheris The help inform

Download Pdf Manuals

image

Related Search

Related Contents

Admiral Craft SG-811E/F Owner's Manual    Gefen GTV-WHD-1080P-SR-EU  warning  PDF - Les automatismes appliqués  Netgear WG102 Reference Manual  

Copyright © All rights reserved.
Failed to retrieve file