Continue: Is There A Problem Here?: Continue

Showing posts with label Continue. Show all posts

Showing posts with label Continue. Show all posts

20110914

Problem ID: 3220180634139034707
Entered by: Ben Simo

You will return

I am not sure I understand what will happen. Generally, I like verb buttons that describe what happens when I click them, but this dialog asks a question. Actually it asks two questions, and gives me three options: Close, Continue, and Cancel Request. Does Cancel Request cancel my request to cancel, or does it cancel something I requested before I requested to cancel?

I'm confused. What happens if I just close this dialog?

20100120

Problem ID: 2814613558044667286
Entered by: Ben Simo

Please insert disk into hard drive

@karlprosser: interesting reoccuring #win7 error, wanting me to insert my HD (that is actually there)

Insert a hard disk into what? Can one Continue without a disk?

20100115

Problem ID: 7501688042513587620
Entered by: Ben Simo

Context, Context, Context.

@jacksri: This error message might be slightly better than useless if I knew which app generated it.

Error messages that don't specify to what they apply aren't very helpful.

If I have to click Cancel to ignore, I'm not really ignoring it. Am I?

What is the difference between Yes and Cancel?

20100112

Problem ID: 9069110056659713566
Entered by: Ben Simo

Undefined is null or not an object

@scottpatton: an IE script error on an atm? tha makes me feel "safe". NOT!!!!!!

Nothing increases confidence in banking technology like Internet Explorer script errors on ATM machines. ;)

20100111

Problem ID: 4952556985203976302
Entered by: Ben Simo

Learn to spell

@eavb: My favourite #Word error message: "There are too many spelling or grammatical errors in ... to continue displ ...

I've often thought this when testing software or evaluating students' work. There too many error to continue reportin em. ;)

20100108

Problem ID: 8987970906880734407
Entered by: Ben Simo

Files in Use

I tell the CLUpdater program that it can install a patch and it tells me I have to close the CLUpdater program.

Are users expected to use task manager to install an update? Why do I have to manually kill the process that started the install that demands I kill the process that started the install process?

20100107

Problem ID: 6727666932465205914
Entered by: Ben Simo

Press F1 to continue towards potential imminet failure

“Anyone have a fix to this? Only started since I installed Windows 7.” - @johnpauldickie

Are SMART failures anything like SMART objectives?

20100106

Problem ID: 4641287961754946557
Entered by: Ben Simo

To update, please quit the update before continuing with the update

martinbtt: Today's comedy error message

And what if I don't want to continue? I see no cancel option.

Problem ID: 6071256249941685545
Entered by: Ben Simo

Version 10.6.2 is less than 10.4.9?

Epic #fail for Microsoft Office for Mac 2008 SP1 update” - @rickmur

20100104

Problem ID: 7833546389463736254
Entered by: Ben Simo

The Bios does not be installed

Jive Bios Error Win!!! - @doctorclark

So is there something even more basic than the BIOS (Basic Input/Output System) that displays this message?

Problem ID: 1902941907168843340
Entered by: Ben Simo

Are you sure?

@bradmccall: UX of dialogs like this bug me. They ask a question, but don't have a button with the right answer. "Yes, Del ...

I like verb dialog buttons that describe actions. However, I do think they should match the question.

20100102

Problem ID: 1042780665742798085
Entered by: Ben Simo

Might Not?

Tweeted by @MichaelJKraemer

Might not? Out of paper? Out of ink? Paper jam?

Is it more likely to print a receipt or not?

20091231

Problem ID: 3139063843505527385
Entered by: Ben Simo

Wait or select OK?

“Windows media center is grumpy today” - @antidale

Wait while files are added or select okay to continue using the system. Does pressing OK to continue cancel the adding of media files?

20091230

Problem ID: 6819519032120321687
Entered by: Ben Simo

All picture settings will be resetted

“Please don't turn to your new tv for grammar lessons... LG #fail” - @racheleason

20091229

Problem ID: 1894344649291859848
Entered by: Ben Simo

Name calling

“If that error were any less specific, it'd say "Your script has an error".” - @zac352

20090311

Problem ID: 2285206137094479470
Entered by: Ben Simo

WARNING: Others might see what you publish on the Internet

I just clicked the PUBLISH POST button. I expect others to be able to see the information.

20090308

Problem ID: 8314546944735734347
Entered by: Ben Simo

The object is not responding

Tweeted by @bp

Yeap, it's still possible to bust Word and Excel with, basically, Copy and Paste. The clincher is this error message (Where's the "Cancel"?!)

Where is the cancel? And click OK to wait?

20090305

Problem ID: 395351408566211859
Entered by: Ben Simo

Not located in the usual place

Tweeted by @Alcedine

"What does this even mean???

I think a restart is definitely in order...

So long Photoshop CS4 ; ;"

20090224

Problem ID: 1607020405161482464
Entered by: Ben Simo

Where's OK?

I'd like to click OK, but where's the button? Clicking OK in the text has no effect.

20090214

Problem ID: 3921017845468176155
Entered by: Ben Simo

Can I give an unspecified response?

Whatever Microsoft developer thought this was okay should suffer some unspecified unpleasantness.

Software testing tools: Heuristics for recognizing problems.

Usability Heuristics

from Jakob Nielsen

• 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

from James Bach
and Michael Bolton

-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

from Ben Simo

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

the OWASP Top 10

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.