If your goal is to create a successful product, then you must take into consideration your users` needs and wishes. A usability testing report is a highly important document that will help you to get an insight into your audience`s demands and frustrations. The report is created in the process of usability testing, that is intended to identify the flaws and positive features as well.
Every usability testing report should include the following sections:
· Background summary. In this part you briefly describe the object under test, provide details concerning date and location, participants and research team. Mention the equipment you used and also outline the tasks that were completed.
· Identify the method you applied. Tell how you conducted the test step by step, including the information about the test sessions and task scenarios. Provide some data concerning the participants, but avoid including full names.
· Analyze test results. Provide a comprehensive explanation of all the completed tasks, define the most successful ones and tasks with the lowest completion rate as well.
· List your findings and recommendations based on data. Keep in mind, that usability testing report is not only about problems, but you can also mention positive features you detected during the test.
These pieces of advice are likely to help you write a good usability testing report.
Read the full article
Is Fedora ready for the average human yet? Let's find out.
As a human who uses a computer I want to install an OS, use a usable desktop, connect to network storage, burn CDs, remote desktop into it, that sort of thing. I should be able to do that without resorting to a commandline, right?
Booting from the DVD the installer all looked good, select free disk area to create partitions in: error. Much fiddling about and playing with manual options: still a non-explanatory error. After some Googling this turned out to be because Fedora doesn't completely support UEFI yet. Cue panic, consider rooting around in BIOS wildly disabling anything that mentions UEFI and enabling anything that says 'legacy' and breaking Windows7's boot in the process. But it's actually an easy fix - in BIOS there are two entries for the DVD drive, a UEFI one and a legacy one. Switch the boot priority around and the installer's fine. But that wasted a couple of hours.
The installer didn't default the swap partition size correctly. I don't care about swap (I have enough RAM IMO) but I do care about hibernate, hibernate uses the swap partition and if you're using more RAM than that a spurious error flashes by and it doesn't hibernate.
I'm not sure why LVM is regarded so highly that it's the default. It DOESN'T make things easier if you have a one-disk setup and want to resize partitions. gparted does that just fine - shrinks filesystems and moves stuff about like PartitionMagic. At best LVM confuses things. Does gparted support it fully, as in can it shrink a filesystem on an LVM volume just as it could if there was no LVM? If not then LVM fails as Joe User needs to use the commandline and type in numbers - one mistake and that's a filesystem chopped in half.
I've had a root about for a GUI that will do this. system-config-lvm 'might' do it, or it might just resize the LV and chop the filesystem off, it's not clear from the documentation or its GUI text and the internet has more questions than answers. And it's not maintained any more so isn't in Fedora20's repos.
For more complex disk setups LVM has its place but not here.
Of course Fedora doesn't come with exciting non-free things like mp3 decoding - a Google for 'things to do after fedora install' explains how to add the rpmfusion repos and install all those sorts of things. I think we'll have to live with that one.
nVidia drivers are as painless as nVidia can make them given that they don't want to give the source away... click - download - ./run, but actually it's not painless on Fedora because the open-source nVidia drivers - nouveau - are in the way and need to be disabled first. That's not as simple as uninstalling a package, or even editing x11.conf (eugh), they're in the kernel and initrd. Some Googling suggests rebuilding the initrd. Sounds like a bit of a kerfuffle. More Googling found a 'temporary' solution: add 'rdblacklist=nouveau' to the kernel boot line. To make it slightly more permanent you need to edit grub's configuration, that's changed since last we met but now you need to edit /etc/default/grub and add rdblacklist=nouveau to the end of the GRUB_CMDLINE_LINUX line. Then you need to run grub2-mkconfig.
KDE on the whole has been lovely. I'd quite like a user-friendly way to 'map network drive' like on Windows. Dolphin happily browses the shares but files can only be opened in other KDE (kioslave) apps, mounting is better. A root around found 'Smb4k' which is working great.
I can't seem to burn a CD image. Right-clicking the .iso suggests k3b. k3b looks nice, it's about to start burning then gives a permission error.
Running k3b as root I am met with the helpful 'cdrecord returned an unknown error (code 255)'.
GnomeBaker is a little more helpful and says that it can't get an exclusive lock on /dev/sr0. lsof and fuser don't show anything locking it.
When remote-desktoping from a netbook using Splashtop on Windows it resizes the Windows desktop to fit the netbook's screen. So far VNC on linux (using an existing desktop session) is having none of it. There's a resolution-switching applet for the system tray but there's no resolution in the list that matches my netbook's. I can change to that resolution with the nVidia control panel but then it sticks at that resolution forever, doesn't just add it to the list.
Skype can't send the ringing/alert sounds to the speakers whilst sending voice to the USB headset. It seems it used to as there are settings for it but they all go to 'pulseaudio' and in pulse they show up as one source. You can direct them to any sink you like but there's no way to split them.
