Practices
  Home arrow Practices arrow Page 7 - The Importance Of Interface Text (part...
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
PRACTICES

The Importance Of Interface Text (part 2)
By: Deepa L, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 3
    2003-03-26

    Table of Contents:
  • The Importance Of Interface Text (part 2)
  • Brass Tacks
  • The Screening Process
  • Playing The Field
  • When Things Go Bad...
  • Offering Instruction
  • Better Safe Than Sorry
  • Globe-trotting

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
     
    ADVERTISEMENT

    Route your faxes to your email inbox. Private, secure fax numbers available from CallWave. Choose your fax number.

    The Importance Of Interface Text (part 2) - Better Safe Than Sorry
    (Page 7 of 8 )

    Confirmation messages are displayed after modifications have been madeto the system by the user. The aim of these messages is to inform the userof the impact of the action and elicit a "yes" or "no" response for furtherprocessing.

    A common irritant here is messages asking you to confirm what you've justdone - without a reason for asking it. For example, if your intranetapplication allows the administrator to delete a folder off the fileserver, a confirmation message asking the question: "Are you sure you wantto delete the Accounts folder?" will only make the user feel that you doubthis or her intelligence. A better option would be: "Deleting the Accountsfolder will also delete all the files within it. Do you wish to continue?"

    In some cases, it is more appropriate to show a message after an action hasbeen performed. This is especially true if the user's action triggers offan internal event within the application. For example, suppose youradministrative application stores users in separate "data files" based onwhether they are confirmed employees or not; these appear to the user astwo separate categories, "Probationers" and "Employees". On the basis ofcertain criteria, the system turns a probationer into an employee and movesthe corresponding data to the "Employee" data file. Let's assume that onesuch criterion is the achievement of a Grade A for performance. When theadministrator enters this grade into the application and submits it, apost-submission message could be: "Wella Cruz has been updated to Employeestatus. In future, please access the Employee menu for her data."

    As a parting shot, ensure that your confirmation questions elicit a directanswer. The following is the best example of what it should *not* be: "Youhave changed the mail server settings. Would you like to discard changes?"

    In this case, the user would need to select "No" to save the changesmade...completely non-intuitive and quite illogical.

    More Practices Articles
    More By Deepa L, (c) Melonfire


     

       

    PRACTICES ARTICLES

    - The System in So Many Words
    - Basic Data Types and Calculations
    - What`s the Address? Pointers
    - Design with ArgoUML
    - Pragmatic Guidelines: Diagrams That Work
    - Five-Step UML: OOAD for Short Attention Span...
    - Five-Step UML: OOAD for Short Attention Span...
    - Introducing UML: Object-Oriented Analysis an...
    - Class and Object Diagrams
    - Class Relationships
    - Classes
    - Basic Ideas
    - Choosing the Right Team
    - Trees
    - Basic Array Searching in C++

     
    Accelerating Trading Partner Performance
     
    Competing on Analytics
     
    Cost Effective Scaling with Virtualization and Coyote Point Systems
     
    Five Checkpoints to Implementing IP Telephony
     
    Hosted Email Security: Staying Ahead of New Threats
     




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 6 hosted by Hostway