There was a task to evaluate the ease of use of the program, and not just "difficult-simple", but more objectively ... Maybe there are some evaluation systems that give a specific number that evaluates simplicity, say on a 10-point scale or something like that. I would be grateful for the help. (I apologize for the off-top, did not know what tags to specify :))
- ru.wikipedia.org/wiki/USABILITY - andreycha
- Since this is a very subjective assessment, it is difficult to lead to functional tests. However, you can always take some basic metrics, for example, the number of user actions to achieve a specific page, and compare them with competitors. Ideally, you should collect statistics on the use of the application, and starting from it build and test hypotheses; without this, you will never know that a third of regular users visit a page every day that you do not pay attention to, considering it unnecessary. - etki
|
1 answer
To objectively evaluate the ease of use of the program , put a user behind it who sees it for the first time. Give the user a task (or several), which he must perform on his own using this program. Measure the lead time. This will be an objective assessment of the ease of use of the program .
- Measurement is a completely correct approach. But it is impossible to focus only on the absolute beginner in the general case. For example: one program provides the ability to record scripts, and the other does not. If a task is given to repeat some script for multiple files of the same type, sooner or later the software with the ability to create scripts will win: that is, one software can be "easier" for processing one file, if you see it for the first time, but for identical processing every day a new file other software can be much easier (even if it requires some initial training). - jfs
- Similarly, the user must have basic subject-matter literacy and similar software. - Kromster
- @jfs Ease of use - this is exactly how quickly the user will figure out the interface. For this you need a beginner. This is exactly what the author of the question asks. - a-bobkov
- @ a-bobkov: criterion in response: "Measure the execution time". Submit the task: "check broken links on the site" (option a) go through the browser (option b) write / find a ready script that will check the links - if a small site check once, the browser check may take less time, the larger the site, the more often you need to check it, the more likely that using / writing the script will win (it will take less time), even if you have to teach the user to use Google in the process, command line skills rammirovaniya. - jfs
|