Quick Review on basic usability test

The feedback detailed below represents a brief heuristic review of the system. The purpose of this type of review is to provide immediate feedback of whole system with different framework. Compliance Checklist (a mark in the checkbox indicates applicability)
This dialogs interface design: language and phrases familiar to user organizes screen information in a natural and logical order facilitates users decision making and task processing provides an easy exit for the user prevents user error provides error messages that indicate the error and recovery processes provides visual cues (signs) for easy task processing allows swift (quick) and easy processing for experienced users while supporting novice (beginner) users organizes rarely used dialog information to promote visibility of all important dialog elements provides visual help cues that are easily accessed and consistent (help button) is quick and easy to use provides user feedback and system status when needed is designed to be visually pleasing to the user allows for rapid, accurate and complete task processing is consistent with other dialogs designed for this system meets physical handicap requirements ( not sure we want this or not?) user cant switch from one framework to another framework in exiting application (framework open option ) How critical is this requirement? ___ Low ___ Low ___ Low ___ Low ___ Low ___ Low ___ Low ___ Low ___ Low ___ Low ___ Low ___ Low ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ Medium ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High ___ High

___ Low ___ Medium ___ Low ___ Medium

___ Low ___ Medium ___ Low ___ Low ___ Medium ___ Medium

Summary comments & enhancement suggestions: Is easy to learn, Is efficient to use, Provides quick recovery from errors, Is easy to remember, Is enjoyable to use, Is visually pleasing As customers depend more and more on software to get their jobs done, usability can be the critical factor that ensures that your applications will be used.
Low: cosmetic or minor, cause minimal difficulty Moderate: causes some problems to doing work or causes the user to stumble, but recovery is possible. High: effectively prevent the user from doing work, the user will fail or have extreme difficulty.

Usability Report (Recommendations for make system more user friendly)

Recognition rather than recall >> Make 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. Good tooltip and descriptive notes are also crucial for recognition. 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. Errors will happen, despite all your efforts to prevent them. Every error message should offer a solution (or a link to a solution) on the error page. Interaction >> Interaction should be predictable, visible and reversible. When the user clicks a button, something on the screen should change so the user knows the system has registered the action. When possible, offer a preview of the results of an action. Any delay intrudes on users' tasks and erodes confidence in the system. Users feel more comfortable with interfaces in which their actions do not cause irreversible consequences. Users should feel confident exploring and know they can try an action, view the result, and undo the action if the result is unacceptable. Instruction >> Design that promotes multiple, open channels of communication between the company and the consumer establishes trust and credibility. So go ahead and tell people what to do. Dont make them think, guess or wonder. Some users like more instruction than others; thats why knowing your users is essential when it comes to assisting their process on a system. Help them find information quickly and easily. Use tooltip, title tags, to give instructions. Let them know how long something will take to load and where their system is in the loading process. Control >> Personalization is the ultimate in control, Allowing a user to personalize the apps for their interests and preferences can make the interface feel comfortable and familiar to each one, which leads to higher productivity and user satisfaction. Allowing users to decide how the screen is laid out, which elements are hidden and which are visible, can save them time and hassle when accessing frequently used functions. (with some drag down functionality which Photoshop software have like user decided where we want to fixed the toolbox etc.) Provide clearly marked exits >> Users often choose systems functions by mistake and will need a clearly marked "emergency unit" to leave the unwanted state without having to go through an extended dialogue. Flexibility and efficiency of use & Provide shortcuts >> Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system caters to both inexperienced and experienced users. Allow users to tailor frequent action Some of the best accelerators are provided by the system like help

Please note this testing is done on very basic level. Some part of my recommendation may be already done in new release build or else may tester raised these recommendation earlier not make out. This is not up to my knowledge. May I have also missed some component it also happen.

Usability Report (Recommendations for make system more user friendly)

Simple and natural dialogue, 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. Irrelevant icons on a screen is a distraction and a slow-down. Make rarely needed icons accessible via a screen. The best way to help make sure you are not providing too much (or too little) information at once is to use progressive levels of detail. Put the more general icons higher up in your hierarchy and let users drill down deeper if they want the details.
#
1.1
1.2 1.3 1.4 1.5

Review Checklist
Is only (and all) information essential to decision making displayed on the screen? Have large objects, bold lines, and simple areas been used to distinguish icons? Does each icon stand out from its background? Are meaningful groups of items separated by white space? Are all icons in a set visually and conceptually distinct?

Yes No
O O O O O O O O O O

Comments
NO yes Yes somewhere yes yes

Visibility of system status >> The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. Probably the two most important things that users need to know at your site are "Where am I?" and "Where can I go next to finished my job?
# 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 Review Checklist Is there a consistent icon design scheme and stylistic treatment across the system? Is a single, selected icon clearly visible when surrounded by unselected icons? Do screen instructions, prompts, and error messages appear in the same place(s) on each screen? If pop-up windows are used to display error messages, does it show code in error message? After the user completes an action (or group of actions), does the feedback indicate that the next group of actions can be started? Is there visual feedback when objects are selected or moved? Is the current status of an icon clearly indicated? Is there feedback when function keys are pressed? Are response times appropriate to the task? Simple, frequent tasks: less than 1 second Common tasks: 2-4 seconds Complex tasks: 8-12 seconds Are responses times appropriate to the users cognitive processing? Is the icon-naming terminology consistent with the user's task domain? Does the system provide visibility: that is, by looking, can the user tell the state of the system and the alternatives for action? Do GUI icons make obvious which item has been selected? Do GUI icon make obvious whether deselect icon is possible? Yes No O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O Comments It is there but need to improve more Yes but it should be little more prompt Not sure Not good tradition. No feedback No feedback to user what action should performed Yes but it should be little more perceptible Cltr, shift etc NO Yes it is Creating primary line Adding collar, nudge, abutment Some time it takes long time. For Generating coping yes yes Is not there but not sure whether it is possible or not. It is there It is there

Usability Report (Recommendations for make system more user friendly)

Speak the user's language >> Match between system and 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.
#
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9

Review Checklist
Are icons concrete and familiar? If there is a natural sequence to screen, has it been used? Do related and interdependent task appear on the same screen? If shape is used as a visual cue, does it match cultural conventions? Do the selected colors correspond to common expectations about color codes? Are tool tips parallel grammatically? Does the command language employ user jargon and avoid computer jargon? Are command names specific rather than general? Does the system automatically enter leading or trailing spaces to align decimal points?

Yes No
O O O O O O O O O O O O O O O O O O

Comments
Is there but it have two flow which confused 1st time. Is there yes Is there yes Yes used domain related language Yes Yes While Mentioning width

User control and freedom >> Users should be free to select and sequence tasks (when appropriate), rather than having the system do this for them. 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. Users should make their own decisions (with clear information) regarding the costs of exiting current work. The system should support undo and redo.
# 4.1 4.2 4.3 4.4 4.5 4.6 4.7 Review Checklist If setting up application first time is easy to remember or hard? When a user's task is complete, does the system wait for a signal from the user before processing? Is there an "undo" function at the level of a single action? Can users cancel out of operations in progress? If the system has multiple levels, is there a mechanism that allows users to go back to previous level? Can users easily reverse their actions? If the system allows users to reverse their actions, is there a retracing mechanism to allow for multiple undos? Yes No O O O O O O O O O O O O O O Comments Yes very easy Yes system give options of save, cancel ,exist yes NO, user need to close the window No direct option to move to the last level but doing restart. User can move to the first level Yes some of actions my doing undo redo, delete. 10 times user can undo & redo

Privacy>> The system should help the user to protect personal or private information- belonging to the user or the his/her clients.
# 5.1 5.2 5.3 Review Checklist Are protected areas completely inaccessible? Can protected or confidential areas be accessed with certain passwords? Is this feature effective and successful? Yes No O O O O O O Comments Not there but not sure also whether there is any provision for this or not.

Usability Report (Recommendations for make system more user friendly)

Consistency and standards >> Users should not have to wonder whether different icons , buttons , or actions mean the same thing. Follow platform conventions. Within your application, use icon & buttons consistently. Inconsistent icons ,buttons can confuse users who think they ended up in the wrong spot because the destination screen had different icon & button. To prevent confusion and anxiety, a application should be graphically and interactively consistent from screen to screen, section to section. Screens should share the same basic layout grids, graphic themes, editorial conventions, and hierarchies of organization. Users shouldnt have to remember what the elements mean from one screen to another, which means using the same buttons or interactive icons, the same terminology, the same organization of actions throughout the application to help to reduce memory load. Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
# 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 Review Checklist Do in whole application standards been followed consistently in all screens within a system? Are icons labeled? If "exit" button is present in all screen, Are screen titles either centered or left-justified? Are attention-getting techniques used with care? Size: up to four sizes Font family : up to three Color: up to four (additional colors for occasional use only) Sound: soft tones for regular positive feedback, harsh for rare critical conditions Are there no more than four to seven colors, and are they far apart along the visible spectrum? Is the most important information placed at the beginning of the prompt? Are user actions named consistently across all prompts in the system? Are system objects named consistently across all prompts in the system? Does the structure of icon choice names match their corresponding icon titles? Are keys used the same way, and do they mean the same thing, in all parts of the system? Yes No O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O Comments Yes is there yes Yes, widow exit Yes centered yes yes yes yes no yes no no yes Yes some where need to improve no

Good error messages >> Help Users Recognize, Diagnose, and Recover From Errors >> They should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution. Even better than good error messages is a careful design that prevents a problem from occurring in the first place.
# 7.1 7.2 7.3 7.4 7.5 7.6 7.7 Review Checklist Is sound used to signal an error? Are error messages worded so that the system, not the user, takes the blame? Are error messages grammatically correct? Do error messages avoid the use of exclamation points? Do error messages inform the user of the error's severity? Do error messages suggest the cause of the problem? Do error messages provide appropriate semantic information? Yes No O O O O O O O O O O O O O O Comments no yes yes no no no no

Usability Report (Recommendations for make system more user friendly)

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. But as soon as you try any complicated tasks, you will need some help for those tasks.
# 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 8.13 8.14 8.15 8.1 8.2 8.3 Review Checklist Do the instructions follow the sequence of user actions? Is the help function visible; for example, a key labeled HELP or a special menu? Is the help system interface (navigation, presentation, and conversation) consistent with the navigation, presentation, and conversation interfaces of the application it supports? Navigation: Is information easy to find? Presentation: Is the visual layout well designed? Conversation: Is the information accurate, complete, and understandable? Is the information relevant? Goal-oriented (What can I do with this application?) Descriptive (What is this thing for?) Procedural (How do I do this task?) Interpretive (Why did that happen?) Navigational (Where am I?) Can users easily switch between help and their work? Is it easy to access and return from the help system? Can users resume work where they left off after accessing help? Do the instructions follow the sequence of user actions? Is the help function visible; for example, a key labeled HELP or a special menu? Is the help system interface (navigation, presentation, and conversation) consistent with the navigation, presentation, and conversation interfaces of the application it supports? Yes No O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O Comments

Yes but file not opened Not seen Help doc for all framework

Pleasurable and Respectful Interaction with the User >> The users interactions with the system should enhance the quality of her or his work-life. The user should be treated with respect. The design should be aesthetically pleasing- with artistic as well as functional value.
# 9.1 9.2 9.3 9.4 9.5 Review Checklist Is each individual icon a harmonious member of a family of icons? Has excessive detail in icon design been avoided? Has color been used with discretion? Has color been used specifically to draw attention, communicate organization, indicate status changes, and establish relationships? Are the most frequently used function keys in the most accessible positions? Yes No O O O O O O O O O O Comments Yes some what Yes Yes Yes but user dont know what & when it should used.