Software interface test and design

xiaoxiao2021-03-06  64

In today's software, there is almost no interface, and the interface design and testing has slowed slowly in my country. At present, interface design causing software designers' attention to not enough, until the rise of the recent pages, it is favored by everyone. The designed interface is rejected due to the need for artistic talent. Domestic software companies do not pay much attention to this. The interface is the most direct level of software and user interaction, and the quality of the interface determines the user's first impression of the software. The design excellent interface can guide the user to complete the corresponding operation, play a guide. At the same time, the interface is like a person's face, has a direct advantage of attracting users. The design reasonable interface can bring easy feelings and success. On the contrary, due to the failure of interface design, it is possible to make the user's fear and abandonment in the user's fear. At present, there are three ways of popular interface: multi-form, single-window, and resource manager style, regardless of the style, the following principles should pay attention or reference. 1. Easy Principles The name of the button should be easy to understand, accurately use the word, shield no two-can-face words, to easily distinguish between other buttons on the same interface, and the best of the energy. Ideally, the user can know the functionality of the interface without consulting the help and performs the correct operation. Easy to use the rules: 1) Complete the same or similar functions, use the Frame box, the common button to support shortcuts. 2) Complete the elements of the same function or task in a centralized position, reduce the distance of mouse movement. 3) Press the function to divide the domain block, with the frame box, and have a function description or title. 4) The interface must support the keyboard automatic browsing button function, which is the automatic switching function of the Tab key. 5) The information on the interface should first be entered and the control of important information should be proceed in the Tab sequence, and the position should also be placed on the window. 6) The number of controls on the same interface is preferably not more than 10, and more than 10 can consider using the paging interface display. 7) Page Interface To support shortcut switching between pages, common combination shortcut ctrl tab8) The default button to support Enter operation, which is automatically executed after pressing ENTER. 9) The input control can be input after the illegal input should be input and the instructions should be given and the focus can be automatically obtained. 10) The order of the Tab key is arranged in the sequence of controls. At present, the popular overall is from top to bottom, while the line is from left to right. 11) The check boxes and options boxes are arranged later in the highlights of the selection. 12) The check box and option box must have the default option and support TAB selection. 13) Options The same time Multi-use option box without the drop-down list box. 14) The interface space is used to use the drop-down box without the option box. 15) Use the option box when the option is small, and the drop-down list box is used. 16) Professional Strong Software To use the relevant professional terms, the versatile interface will advocate the use of versatility. 17) For the case of high input reproducibility, the interface should fully support keyboard operations, ie, the keyboard is operated without using the mouse. 2. The principle of normative principles The usual interface design is designed according to the specification of the Windows interface, which contains the standard format of "menu bar, toolbar, toolbar, status bar, scroll bar, right-click", which can be said: Interface is standardized The higher the degree, the better it is, the better it is. Small software generally does not provide a toolbaux. Normative Rules: 1) The common menu must have a shortcut to a command. 2) The menu that completes the same or similar functions is open to the same position with the horizontal line. 3) The icon can be intuitive representative before the menu. 4) Menu depth general requires up to three levels. 5) Toolbar requirements can be customized according to user requirements. 6) The toolbar of the same or similar function is placed together. 7) Every button in the toolbar must be prompted in time.

8) The length of a toolbar cannot exceed the screen width. 9) The toolbar can be intuitive representative to complete the operation. 10) The system-wide toolbar settings the default placement position. 11) Toolbars can consider using toolbars. 12) The toolboy must have an increased reduction, and the user is customized according to the requirements. 13) The default total width of the toolboy should not exceed the screen width 1 / 5.14) Status balance to display the user's practical information, commonly used: current operation, system status, user location, user information, prompt information, Error message, using unit information and software developer information, etc. If a certain operation takes longer, progress bar and process tips should be displayed. 15) The length of the scroll bar should be transformed according to the length or width of the display information, so that the user understands the position and percentage of display information. 16) The height of the state strip is suitable for placing five good words, and the width of the scroll bar is slightly narrow than the status bar. 17) The menu and toolbar must have a clear boundary; the menu requires convex display so that there is a three-dimensional sense when the tool strip is removed. 18) The 5 fonts are usually used in menus and status bars. The toolbar is generally wider than the menu, but not too many, otherwise it seems uncoordinated. 19) Right-click the shortcut menu with the same criteria as the menu. 3. Helping the facility principle system should provide detailed and reliable help documentation, you can seek a solution when you use it when you use it. Help Facilities Clean: 1) Help the performance introduction in the documentation and instructions are consistent with the system performance. 2) When packaging a new system, a modified place to do corresponding modifications in helping documents, and do a version unity. 3) Provide the function of timely calling the system. Commonly used F1.4) When calling help on the interface, it should be able to position a help location relative to this operation when calling help. That is to say, help have immediate targeted. 5) It is best to provide currently popular online help format or HTML help format. 6) Users can use keywords to search for the help index, of course, should also provide help the subject. 7) If there is no written help document, it is best to print the function. 8) In Help, we should provide our technical support, once the user is difficult to solve the new help method. 4. The position of the reasonable principle screen diagonal intersection is where the user's direct view is, and in the top quarter, it is easy to attract the user's attention. When placing the form, pay attention to the use of these two locations. Rationality rules: 1) The center position of the parent form or the main form should be near the diagonal focus. 2) The position of the subform should be in the upper left corner or in the main form. 3) When multiple child forms pop-up, it should be shifted below the right below to display the title of the form. 4) Important command buttons are placed on the interface with the more frequent buttons. 5) Error use easy to cause the interface to exit or close the button should not be placed in the easy point position. The opening or final with the vertical roll is the easy position. 6) The button that is not related to the ongoing operation should be shielded. 7) Actions that may cause data cannot be recovered must provide confirmation information to give users a chance to give up the choice. 8) Illegal input or operation should have sufficient prompts. 9) If there is a problem in the operation, there must be a prompt to let the user understand the error, avoiding the formation of indefinitely. 10) Tips, warnings, or erroneous descriptions should be clear, clear, appropriate and should avoid the appearance of English tips. 5. The principles of beautiful and coordination should be sized for aesthetic perspective, and feel coordinated and comfortable, can attract users' attention within a valid range. Beautiful and coordinated rules: 1) long width approach the gold medal ratio, avoid the long-width ratio disorder, or the width exceeds the length. 2) The layout should be reasonable, should not be too intensive, and it is not too empty and reasonable.

3) The button is basically similar, avoiding too long names, levy from excessive interface position. 4) The size of the button should be coordinated with the size and space of the interface. 5) Avoid placing a large button on the open interface. 6) The rear interface of the placed control should not have a lot of vacancies. 7) The size of the font should be coordinated with the size ratio of the interface, and the Song's 9-12 in the font used is more beautiful, and the fonts of more than 12 are rarely used. 8) Prospects and background color matching reasonable coordination, the contrast is not too big, it is best to use dark, such as Dahong, Green, etc. Common color considers using Windows interface hue. 9) If you use other colors, the main color is soft, with affinity and magnetic force, and resolutely put the colors of your interest. 10) The main color commonly used in large systems has "# E1e1e1", "# Efefef", "# c0c0c0", etc. 11) The interface style should be consistent, the size, color, and font must be the same, unless there is a place where art processing or special requirements are required. 12) If the form supports minimizes and maximizes or enlarges, the controls on the form should be scaled as the form; avoid only the form of the form and ignore the zoom of the control. 13) For interfaces containing buttons, it is generally not supported, ie there is only a shutdown function in the upper right corner. 14) When the parent form supports zooming, the subsidiary is not necessary to zoom. 15) If you can provide a custom interface style, you can choose color, font, and so on by the user yourself. 6. Menu location The principles menu is the most important element on the interface, and the menu location is organized according to function. Menu Settings Rules: 1) Menu usually use "common-primary-secondary-tool-help" position, in line with popular Windows style. 2) Commonly used "File", "Edit", "View", etc., almost every system has these options, of course, according to different systems. 3) The drop-down menu is to group according to the meaning of the menu option, and cut according to certain rules, separated by horizontal line. 4) When using a set of menus, it should be arranged in the previous order when the use of a set of menus is required or awarded. 5) The menu item without the order requires the use of frequency and importance, which is commonly placed, is not commonly placed; it is important to start, the secondary is placed behind. 6) If there are many menu options, the length of the length of the long menu should be used to reduce the principles of depth. 7) Menu depth general requires up to three levels. 8) Seeing a shortcut command mode for a common menu, see 8.9 of the combination principle 8.9) If the menu that is not related to the operation is handled, if you use a dynamic loading method - that is, only the menu is displayed - the most Great. 10) The icon before the menu is not too big, and the word high is always the best. 11) The width of the main menu is close, the number of words should not be more than four, and the number of words in each menu can be the same. 12) The number of main menu should not be too much, preferably a single row arrangement. 7. Unique principle If you follow the industry's interface criteria, you will lose your personality. In the case where the framework meets the above specifications, it is especially important to design your own unique style. Especially in the circulation of commercial software, there is a good way of migration. Uniqueness rules: 1) There should be unit introductions or product introductions on the installation interface, and have its own icon or logo. 2) Main interface, it is best to have a company icon or logo on most interfaces. 3) The login interface must have the logo of this product, and include the company icon or logo. 4) Help menu "About" should be copyrighted and product information.

5) The company's series of products should maintain a constant interface style, such as background color, font, menu arrangement, icon, installation process, buttons, etc. should be substantially consistent. 6) Should make a unique icon for the product and distinguish from the company icon or logo. Most of the use of shortcut keys in the software is consistent. Menu: 1) The combination of transactions is: Ctrl-D deletion; Ctrl-f looks; Ctrl -h replacement; Ctrl-i insertion; Ctrl-n new record; Ctrl-S Save Ctrl-o open. 2) List: Ctrl-r, Ctrl-G positioning; Ctrl-Tab Next Page window or inward browsing the same page control; 3) Edit: Ctrl-a allocation; Ctrl-C copy; Ctrl-V paste; Ctrl-x shear; Ctrl-z revoked operation; CTRL-Y recovery operation. 4) File operation: CTRL-P printing; Ctrl-W is closed. 5) System menu: ALT-A file; ALT-E editing; ALT-T tool; ALT-W window; Alt-h Help. 6) MS Windows Reserved Key: CTRL-ESC Task List; CTRL-F4 Close window; ALT-F4 ends; Alt-Tab Next Application; Enter Default Button / Confirmation Action; ESC Cancel Button / Cancellation; SHIFT-F1 Context related help. In the button: can be adjusted according to the needs of the system, the following is just a commonly used combination. ALT-Y determined (yes); alt-c cancel; Alt-N No; ALT-D deletion; ALT-Q exit; Alt-a added; Alt-E editing; Alt-r; alt- W Write. These shortcuts can also be used as a standard for developing Chinese applications, but can also use Chinese pinyin beginners. 9. The principle of torment is considering the error rate in the interface, which greatly reduces the damage caused by the system because the user is incorrect. Developers should try to take into account various possible problems, so that the error can be minimized. If you use a protective error, you exit the system, this error is easier to make users lose confidence in the software. Because this means that the user wants to interrupt the idea and re-logs in, and the operation has been lost because there is no storage disk. Ratio Rules: 1) The most important thing is to eliminate errors that may make the application abnormally. 2) Attention should be taken to avoid unintentional data of invalidity as much as possible. 3) Use related controls to limit the type of user input value. 4) When the possibility of the user makes it, only two boxes can be employed. 5) When you select more, you can use a check box, each option is effective, and the user is not possible to enter any invalid selection. 6) When the option is specifically available, you can use the list box, drop-down list box. 7) In an application system, the developer should avoid the user to make an unauthorized or meaningless operation. 8) To add or block the input character or action that may cause fatal errors or system error. 9) There must be remedies on the operation of the possible serious consequences. Users can return to the original correct state by remedial users.

转载请注明原文地址:https://www.9cbs.com/read-119549.html

New Post(0)