Practices
  Home arrow Practices arrow Page 3 - 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) - The Screening Process
    ( Page 3 of 8 )

    Having got the menu titles out of the way, we now come to the screen, or window, titles.

    Ideally, the screen title should reflect the menu option clicked for ease of understanding and reference.

    There may be times when the functions available within the user interface require more than one screen. For example, for an "Edit Item" function, the first screen may allow the user to search for an existing item, while the second screen displays the settings and allows modification.

    In such cases, the first question to be asked is whether this is the norm with all such options. If it is, then you may assign nomenclature for these screen types - for example, "Search For Item" and "Edit Item Details" would be appropriate titles. If, however, this is a one-off occurrence, and you cannot fit this screen into any of your existing types, you would be better off *not* setting nomenclature for the screens. Setting separate titles in such cases merely adds one more level of complexity, and requires more help material for those users who get confused.

    Another case is of screens that pop up in new windows for additional data entry. Title these screens to indicate exactly the task they perform, or the data they need. Trying to depict a link with the parent screen is not required, because the context is already set by the display of the sub-screen at that particular point.

     
     
    >>> 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