Tag Info

This is in fact your decision. You must define the usability goals for the project in the usability specification. They are usually formulated just like you suggest: "n% of the users accomplished the task in less that n minutes". A couple of "standard measurement" have evolved during the last decades. Measures like time-on-task, success-rate, ...

Here is my theory: Its about the ROI. Its not that there is a good reason for the passive ui for help sections, by all rights every part of a system should have an excellent and active ui. But we tend to focus harder on the core customer experience, because that's where the money is. And just tack on documentation / help sections. The effort that help ...

what do you think are the main differences in methodology between "Requirements Engineering" and "Usability Engineering" Personally, I would not separate these out. I spend a lot of time acting as a business analyst for projects, and whenever possible I make sure that usability is part of the main requirements gathering effort. They may be listed in a ...

We have developed over the last few years our own SWE BOK in our company, and there we see the two disciplines like that: Requirements engineering is the first of the disciplines which looks at the problem of the customer (only). It has to ignore completely the solution (even if you think you know it). Usability engineering has to think about how to make ...

I don't see any disconnect at all between the two. Most people will have a faster response to objects on the right side of their visual field. So that applies to moving balls; tigers that want to eat you; etc. It is about a tiny increase in visual perception. This has nothing to do with learned importance. Reading from left to right has taught us that ...

I would say No, not entirely. There is of course the System Usability Scale which measures: effectiveness (can users successfully achieve their objectives) efficiency (how much effort and resource is expended in achieving those objectives) satisfaction (was the experience satisfactory) The measurement coming closest to your question would be ...

I hit this question constantly and almost always have to make adjustments during testing sessions. The post is correct that if the product isn't usable or accessible, then there is no product since it'd be a digital rock. Though the argument I think is flawed a little bit. Looking at the argument a different way...the user doesn't care what happens at a ...

I read the two replies by mliebelt and Gray a couple of times. I partially agree with both. It sounds correct to me to define UE as solution-oriented and RE as problem-oriented, but the current studies aim to focus on their intersection. If we take a look at the recent reference in RE (e.g Alan M. Davi's book: JERM), we see that taking product/solution into ...

I already have seen different kinds of interactive help at multiple websites. However, it were always used in context with a guided tour to introduce the features of a system to a novice user. One example is an online route planner - the tour can be started immediately after the page is loaded. Furthermore, facebook usually makes a short interactive tour ...

In simple terms no. Task complexity can be determined through user testing, preferably using an approach such as contextual enquiry. All scales will be based upon interpreting the user feedback and if a user can successfully carry out a task. Common 'scales' are series of grades ranging from everyone completes the task with no problems through to tasks ...

Here's one way to do it, assuming that permissions are the same for each object group. (ie If User01 can edit an object under group X, then he can also edit the 500 other objects in group X). Rather than defining role as a group of users, define the role as a group of permissions. For example: Role 1 (admin) can edit, delete, and view Role 2 (author) can ...

Don't forget that depending on the situation, better usability actually yields more security: If the security mechanisms are too complicated to use, users will often choose not to use it at all. (To put it bluntly: Why is Blackberry less used than iPhone?) If bad usability hinders the understanding what the security mechanism protects, the user will find a ...