Do Not: Is There A Problem Here?: Do Not

Showing posts with label Do Not. Show all posts

20101221

Problem ID: 7675816213204665797
Entered by: Ben Simo

Sorry, you do not have any Data Details

If you are going to add $190.70 in data usage fees on top of my unlimited plan fees, the least you can do is provide details as to how you calculated that amount.

Edit

20100610

Problem ID: 5400827394047272246
Entered by: Anonymous

Expired

Seth Eliot reports:

If you are having trouble with a Medical Device and want to let the FDA know about it at www.accessdata.fda.gov/scripts/medwatch/medwatch-online.htm, then the FDA only wants to know if you are using expired goods. Expiration Dates in the future are not allowed.

Edit

20100129

Problem ID: 8850985081123597231
Entered by: Ben Simo

Do not honour

@DanielTome: another #ux fail when trying to pay a fine online. What does "do not honour" mean in this case?

Edit

Problem ID: 2468276484710077844
Entered by: Ben Simo

Ambiguous authentication

osma: updating my computer. apparently one of many updates has an issue, but which one? #packagekit #fail

Security features like this can be useful in protecting computers from malware but ONLY IF the user is given sufficient information to make intelligent decisions.

Edit

20100120

Problem ID: 6094243198307575241
Entered by: Ben Simo

Do not turn the power off

“Whyyyyyyy Wiiii, Whyyyy nowwwww do you want to do a system update!!! FAIL!” - @iRx

What happens if the power goes out?

Edit

20100114

Problem ID: 6281131783335824797
Entered by: Ben Simo

Your Kindle software is updating

“Kindle must have newest software, it doesn't get a choice in this decision. Sorry Man.” - @alanatpresent

I've got nothing about systems that update their own software. However, ones that force updates often do so at very inopportune times. Here's an idea: let users select when the update gets installed.

Edit

20100111

Problem ID: 4265546165042316998
Entered by: Ben Simo

Complexity

@LAKing: This form just keeps getting better. This is a form error page.

Do not enter a country when selecting a state for place of birth? I can't see the part of the form asking for place of birth, but if the instructions are as complex as what I see for entering a name, I'm surprised there aren't more errors being reported.

If you have no first name or middle name, select No First Name (NFN) or No Middle Name (NMN), as appropriate. If you only have initials in your name, enter the initial(s) (without the period) and select Initial Only (IO). If you are a "Jr.," "Sr.," "II," etc., enter this under Suffix.

How many new acronyms can users be introduced to in order to fill out a form? What if your middle name is a digit? What if you have more than three names? If they're going to spell out specific instructions with acronyms, they might as well deal with all the possibilities. Right? ;)

This has to be a government form made more confusing by a government software system.

Edit

20091231

Problem ID: 2969416042625759636
Entered by: Ben Simo

Installing...

“No video game should take 10 minutes to install.” - @rbieber

Back in the '80s, I often waited 10 minutes for games to load from floppy disk. :)

Edit

Usability Heuristics

• Visibility of system status Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

• Match between system and the real world Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

• User control and freedom User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

• Consistency and standards Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

• Error prevention Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

• Recognition rather than recall Recognition rather than recall: Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

• Flexibility and efficiency of use Flexibility and efficiency of use: Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

• Aesthetic and minimalist design Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

• Help users recognize, diagnose, and recover from errors Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

• Help and documentation Help and documentation: Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Consistency Heuristics

-F amiliar Familiar: The product is not consistent with the pattern of any familiar problem.

E xplainable Explainable: The product is explainable.

W orld World: The product is consistent with the real world.

H istory History: The present version of the product is consistent with past versions of it.

I mage Image: The product is consistent with an image that the organization wants to project.

C omparable Products Comparable Products: The product is consistent with comparable systems.

C laims Claims: The product is consistent with what important people say it’s supposed to be.

U ser Expectations User Expectations: The product is consistent with what users want.

P roduct Product: Each element of the product is consistent with comparable elements in the same system.

P urpose Purpose: The product is consistent with its purposes, both explicit and implicit.

S tatutes Statutes: The product is consistent with applicable laws.

FAILURE Heuristics

F unctional Functional: The error detecting, reporting, and handling functions properly.

A ppropriate Appropriate: Errors are reported at the appropriate time in an appropriate manner.

I mpact Impact: The impact of the failure is communicated to those impacted.

L og Log: The error is appropriately logged; or not logged.

U ser Interface User Interface: The error is reported in the user interface in terms that the user understands.

R ecovery Recovery: The user is informed of what they need to do to recover from the error.

E motions Emotions: The error handling and reporting has a positive influence on user emotions.

Security Vulnerabilities

1. Injection Injection: Injection flaws occur when untrusted data is sent to an interpreter as part of a command. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without authorization.

2. Broken authentication and session management Broken authentication and session management: Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.

3. Cross-Site Scripting Cross-Site Scripting (XSS): XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.

4. Insecure Direct Object References Insecure Direct Object References: A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to gain unauthorized access to data.

5. Security Misconfiguration Security Misconfiguration: Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.

6. Sensitive Data Exposure Sensitive Data Exposure: Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.

7. Missing Function Level Access Control Missing Function Level Access Control: Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.

8. Cross-Site Request Forgery Cross-Site Request Forgery (CSRF): A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.

9. Using Components with Known Vulnerabilities Using Components with Known Vulnerabilities: Running software components with known vulnerabilities can compromise the vulnerable components and anything those components can access -- undermining defenses.

10. Unvalidated Redirects and Forwards Unvalidated Redirects and Forwards: Using untrusted data, without validation, to determine the destination of redirects and forwards can enable attackers to redirect victims to phisihing or malware sites.

Is There A Problem Here?

20101221

Sorry, you do not have any Data Details

20100610

Expired

20100129

Do not honour

Ambiguous authentication

20100120

Do not turn the power off

20100114

Your Kindle software is updating

20100111

Complexity

20091231

Installing...

Problem or no problem?

Usability Heuristics

Consistency Heuristics

FAILURE Heuristics

Security Vulnerabilities

Popular

Recent Problems

Recent Comments