User interface design style
2.3 Wizard Usage Principles For certain parts of the application, the user must enter the operation information in order to enter the specified order, and the user should use the necessary reference to use the wizard, which is relaxed when using the user. However, the wizard must be used in a fixed processing process, and the processing flow should be more than 3 processing steps.
2.4 System Response Time System Response Time includes two aspects: time length and time variability. The user response time should be appropriate, the system response time is too long, the user will feel uneasy and frustrated, and the response time is sometimes short to make the user speed up the rhythm, resulting in errors. The variability of the system response time refers to the deviation of the average response time. Even if the response time is relatively long, the low response time variability also helps the user build a stable rhythm. Therefore, in the system response time, the following principle: Response time length interface design 0-10 second mouse display to become a hover 10 to 18 seconds by micro-help display processing progress 18 seconds or more display processing window, or display progress bar a long time process Complete warning information should be given when completed
The variability interface of the response time does not feel that the user does not consider that the user is slightly felt by micro-help provides a variability. It is easy to show a large and time to show the volatility prompt.
2.5 Users help facilities are commonly used by two: integrated and additional. The integrated help facility is designed in the software. It is related to the context, and the user can directly select the subject related to the operational operation. By integrating help facilities can shorten the time of users get help, increase the friendliness of the interface. Additional help facilities are added after the system is built. It is usually a relatively weak inquiry ability. This system provides these two ways to help facilities, design, and implementations: 1) When system interaction, provide some help features, ie help for the main operation 2) Users can pass the help menu, F1 keys, and help buttons ( If any, if you have, the access help 3) provides a selection of three ways as needed when you are help: another form, micro-help and point out for a document 4) How do users return to normal interactive ways: Return to And Function Key 5) Construction of Help Information: Held Help 6) Micro> Provide: Provided by the status bar, or the prompt text on the control
2.6 Error Information and Warning Error Information and Warning Formation When there is a problem, the bad news given when the problem is displayed. This system should follow the following principles for error information and warnings: 1) Information is described in terms that the user can understand; 2) How to provide Constructive advice from errors; 3) Information should point out errors may result in those undue consequences so that users check these situations or help users to correct them; 4) Information should be accompanied by visual tips, such as special Image, color or information flashes. 5) Information cannot with the judgment color, that is, if you can't accuse the user
2.7 Command Interaction Since the system is a Windows user, the system does not provide command interaction.
2.8 General Interaction Principle This system generally interacts the following principles: 1) Consistency: Menu selection, data display, and other functions should use the consistent format. 2) Provide meaningful feedback 3) Execute a large destructive action Requirements 4) Allow Most Operation 5 on data entry 5) Reduce the number of information necessary to remember between the action 6) in dialogue, move, and think Increase efficiency 7) Allows users to be non-malicious errors, the system should protect the damage of the dead crop 8) Press the function to the action, and press this screen layout, the designer should increase the order of the command and action organization 9 ) Provide context-related help mechanism 2.9 Information Display Principle This system information display follows the principles: 1) Only information related to the current user context environment; 2) Do not use data to surround the user, use easy users to quickly absorb information Fashion information; 3) Use consistent markers, standard abbreviations, and predictable colors, display information should be very clear, users do not have to refer to other information sources; 4) Generate meaningful error information, see 2.6; 5) Indengements and text to assist in understanding; 6) Use window separation controls to divide different types of information; 7) Efficiently use the display space of the display.
2.10 Data Enter Principle This system data input follows the following principles: 1) minimize the number of user input actions; 2) Maintenance information display and data input consistency; 3) Interaction should be flexible, the flexibility input to the keyboard and mouse input Support; 4) In the context of current action, the unsuitable command does not work; 5) Let the user control the interactive flow, the user can skip unnecessary actions, change the order of the required action (if allowable) and Recovery from the error state without exiting the system; 6) Provide help for all input actions, see 2.5; 7) Eliminate redundant input. Possibly provide a default value, never let the user provider can automatically obtain or calculate information.
3 User Interface Design Changes and Adjustments 3.1 Change Description Change this user interface design The consent of all developers should be made, all developers should modify and design the user interface according to the correct principles.
3.2 Additional Instructions When the user interface is added to all developers, all developers should modify and design the user interface as followed.
4 Others.
The above code from: the source code database (SourceDataBase) Copy Time: 2002-04-20 23:16:07 Current Version: 1.0.583 Author: Shawls profile: Http://Shawls.Yeah.Net E-Mail: ShawFile @ 163.NET QQ: 9181729
