Practices
  Home arrow Practices arrow Page 7 - The Importance Of Interface Text (part 2)
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
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? 
Google.com  
PRACTICES

The Importance Of Interface Text (part 2)
By: Deepa L, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 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:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log 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


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

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

    A common irritant here is messages asking you to confirm what you've just done - without a reason for asking it. For example, if your intranet application allows the administrator to delete a folder off the file server, a confirmation message asking the question: "Are you sure you want to delete the Accounts folder?" will only make the user feel that you doubt his or her intelligence. A better option would be: "Deleting the Accounts folder 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 has been performed. This is especially true if the user's action triggers off an internal event within the application. For example, suppose your administrative application stores users in separate "data files" based on whether they are confirmed employees or not; these appear to the user as two separate categories, "Probationers" and "Employees". On the basis of certain criteria, the system turns a probationer into an employee and moves the corresponding data to the "Employee" data file. Let's assume that one such criterion is the achievement of a Grade A for performance. When the administrator enters this grade into the application and submits it, a post-submission message could be: "Wella Cruz has been updated to Employee status. In future, please access the Employee menu for her data."

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

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

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

       

    PRACTICES ARTICLES

    - More Techniques for Finding Things
    - Finding Things
    - Finishing the System`s Outlines
    - 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





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 1 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek