[Reprinted] interface design test specifications

Some Interface Standard 1: follow consistent standards, establish standards and follow
Whether it is the use of controls, prompt information wording, color, window layout style, follow the unified standard, to achieve true consistency.
Benefits:

1: enables users to build accurate mental models. After a user is familiar with an interface, switching to another interface can easily deduce various functions, the statement does not need to be understood.

2: Reduce training and support costs, and support staff will not be able to provide guidance on a case-by-case basis.

3: Give the user a unified feeling, do not feel confused, have a good mood, and increase support

Practice:

Experienced persons in the project team should establish the UI specifications:

· The artist provides the color scheme and the overall color table.

· The interface control program personnel and user experience personnel propose a control library for reasonable and unified use. Refer to the standard interface usage specifications:

Controls comply with industry standards. For Windows platforms, see Microsoft user experience (in msdn, Chinese has been translated and published, and the project team must have one)

You can modify the style and tone of a widget within the allowed range.

Refer to the advanced operations of other software to extract functions useful to this project for use. It is absolutely not intended for blind access.

Design special operation controls as needed. The principle is to simplify operations and achieve certain functional purposes.

· The interface implementer and the artist discuss the feasibility of the control. (If this step is not implemented, it will lead to dissatisfaction with the work of the other party and inconsistency ). Repeat the above work.

· Establish a rational document UI standard to describe the above specifications,

· The interface designer is forced to understand and act as a development criterion,

· SQA personnel monitor the compliance of developers and warn developers in a timely manner.

II. (color) the color is used properly and follows the comparison principle:
1: Unified tone. Select the appropriate color for the software type and the user's work environment:

For example: security software, according to industrial standards, you can select yellow, green to reflect environmental protection, blue to show fashion, purple to show romantic and so on, light color can make people comfortable, dark background makes people feel tired

2: If you do not have a series of interfaces of your own, you can use the standard interface to avoid this aspect, so as to be consistent with the operating system and read the standard color table of the system.

3: blind and weak users, even if a special color is used to represent the key or special things, should they also use a special indicator ,? Quot ;!,? Duplicate numbers and icons

4: The color scheme also needs to be tested. Because of the display and video card problems, the color performance varies with each machine. Therefore, the color scheme should be tested strictly.

5: Follow the comparison principle: Use dark text on a light background, use light text on a dark background, blue text is easy to recognize on a white background, and red background is not easy to distinguish, the reason is that there is no contrast between red and blue, while the contrast between blue and white is very large. Unless in special cases, do not use strong contrast, people produce a sense of hate color. 6: use different colors as few colors as possible for the entire Interface

ITOP color table

For specific standards, refer to the academic standards of Fine Arts statistics. The construction of the color table serves as a standard reference for the artist in the design and packaging design of the pattern, and plays a rule-based role for the design controls and form color of the program interface designer.

III. (Resource) Resources
A colorful human-computer interaction interface is indispensable for exquisite mouse cursors, icons, graphic images, and basemap.

1: you also need to follow the unified rules, including the above-mentioned establishment of the color table, the creation steps of the icon should also be as standard as possible, refer to the iTOP outlookbar icon design standard

2: Standard icon style design, unified layout, unified color tone, contrast, color level, and image Style

3: The basemap should be integrated with the basemap, with light color, low contrast, and as few colors as possible.

4: icons and images should clearly express the meaning, follow common standards, or easily think of objects on the user's machine. By default, fantastic patterns are definitely not allowed.

5: The mouse and cursor style are unified. Try to use system standards to prevent repeated situations. For example, the shape of a hand in some software may be four minutes different.

Example: how to create an XP iconHttp://www.microsoft.com/china/msdn/library/dnwxp/html/winxpicons.asp

Attachment: iTOP outlook howto.doc describes how to create an outlookxp icon in the iTOP project.

4: (font) font
The unified font is used. The font standard is determined by the operating system type.

The Chinese language adopts the standard font, "", and the English language adopts the standard Microsoft sans serif without considering special fonts (such as the Yellow Book and the Yellow Book, which can be replaced by images in special cases ), make sure that each user is properly displayed.

The font size is based on the system's Standard font, for example, the MSS font is 8 lbs, And the (9 lbs) is 5 lbs (10.5 lbs ).

All controls should use uniform-size font attributes as much as possible, except for special prompts, enhanced display, and other exceptions.

ITOP adopts BCB, and all controls use parent font by default, which is not allowed to be modified. This facilitates unified adjustment.

· Handling of changes to the font attributes of the system.

In Windows, there is a desktop setting and a large font attribute. Many interface designers are often annoyed with this. If the design follows Microsoft's standards, the relative size is used as the control size settings, when switching between large and small fonts, there is no special problem.

However, because it is often convenient to use lattice as a window design unit, the layout is messy after the large font is changed.

In this case, the corresponding processing should be done:

1: The write program automatically adjusts the size. The dot matrix value is multiplied by a corresponding proportion.

2: All use dot matrix as the unit. Ignore the system font adjustment, which can reduce the trouble caused by large font adjustment. This method is often used in BCB/Delphi, but the result is inconsistent with the system.

V. Text
The text expression of prompt information and help documents follows the following guidelines:

1: colloquial, polite, and versatile. Please do not use or use less professional terms to prevent typos.

2: the use of the comma (;) in the end of a sentence. If there are too many messages, you should segment them,

3: Corresponding representation of warnings, messages, and errors

4: Use a unified language description. For example, if a button for disabling a function can be described as exit, return, or close, it should be uniformly specified.

5: different users use the appropriate word tone, such as special software, can appear in many professional belongs to the user for children: this can be a friendly tone, elderly users should be mature and stable. Follow the standards.

6: (style) control style. Do not use error controls. The control functions must be specific.
There are controls of the same style designed. If you cannot design a set of controls, you can use standard controls.

· Do not use the control incorrectly, for example:

Use the button style for tTable, and display the copyright information on the main menu bar,

· Controls of the same type are operated in the same way. For example, you can double-click a control to execute some actions, but double-click does not reflect any

· A control only provides a single function and does not need to be reused.

Many people prefer to use different functions of a control in different situations for the convenience of writing programs. This increases the difficulty of users' first understanding and can be understood only after they are familiar with it. For example

Change the red option. The parameters on the left represent different settings. It may be used only by skilled users to save the control or programming workload. In this case, the solution is as follows:

1: group, use dual control.

2: Use the table page to give users obvious visual changes

7: (align) controls layout, windows are not crowded, and controls are combined by functions
1: The screen cannot be crowded

Crowded screens are hard to understand and therefore difficult to use. The overall screen coverage of the test results (Mayhew, 1992) should not exceed 40%, and the group clock coverage should not exceed 62%.

People can neither be too crowded nor loose.

The entire project uses a unified control spacing. by adjusting the size of the form to be consistent, even if the size of the form remains unchanged, leave some areas blank and do not destroy the row spacing between controls.

2: Region Arrangement

One row of controls, which are aligned vertically and the control spacing is basically the same

The spacing between rows is the same, and the boder distance of the form should be greater than that between rows (the spacing and edge are left blank ).

When the screen has multiple editing areas, You need to organize these areas with visual effects and efficiency.

3: Proper Data Alignment

Description text. The Chinese version should use the Chinese full-width colon. When vertically alignment, right-click it by colon ,. The width of the vertical control is as close as possible. And left alignment.

For example, the characters such as the amount should be aligned according to the decimal point or right aligned

4: Effective Combination

Logically associated controls should be combined to indicate their associativity. Otherwise, any project that does not want to be light should be in a style and be grouped between project sets at intervals, or use the box to divide the respective regions.

For example, on the following page, select a search method to determine whether the number range indicates the caller's number range or the called number range, which has nothing to do with the billing method,

You should change it to: search mode and accounting method change location. To avoid misunderstanding.

5. widget position and layout during Window Scaling:

Solution:

1: fixed window size. size cannot be changed,
2: Change the widget position and size in the onsize window.

In BCB/Delphi VCL, most controls have layout attributes:

Some controls have the alignment attribute and can be used for Layout Adjustment: tcustompanel, tmemo, etc. The attribute is left-to-right, top-to-bottom, and full-client, which is used to automatically adjust the layout.

Most controls have the anchors attribute. If the value is true, such as akleft and aktop, the distance between them and the edge is changed. This can further design the typographical work.

8: (Tab order) tab order
Usage habits, reading order, from left to right, from top to bottom

The tab key activation order of the control in the form, taborder,. BCB/Delphi, right-click the form design, select taborder settings, and press Ctrl + D in the res editing area of the Form in VC.

9: (shortcutkey & accelerator & popmenu) shortcut keys, acceleration keys, and pop-up menus
· Shortcut keys:

1: Enter Ctrl + XXX into the help list in the global shortcut menu.

2: The shortcut key is used to write help, special instructions, and emphasized when using the training.

· Acceleration key:

1: Use a non-destructive default button. Press ENTER or ESC to correctly use a form with a default acceleration key. For example, press enter to activate the button action set to default in the current window, ESC indicates closing the window.

When calling the default button action or closing action, you should not perform destructive operations to avoid harm caused by incorrect operations. For example, you cannot use the buttons for data deletion and other functions as the default button. When you want to submit a large amount of data, you should block ESC, or exit the prompt to tell the user whether to save and submit.

2: The receiving action control must have an acceleration key and a unified acceleration key description (&)

To work with the keyboard, the operable controls should all have the acceleration key. The definition criterion of the acceleration key is the first letter of an English word. If the same form is repeated, the second letter is used, and so on, the acceleration mode is Alt +, which is identified in a unified way on the interface, such as XXX (A) or Wps. xxx can be used to identify the underline cancel directly under a letter,

For controls such as edit that cannot display shortcuts like button, the shortcut keys are displayed in the label described in edit.

· Pop-up menu

The secondary menu must have corresponding buttons or menu options on the visual interface.

The Help menu can be displayed to the user only after you click the mouse key or other actions. It cannot be clearly displayed to the user, so the corresponding options should be available in other ways, such as corresponding controls on the interface or shortcut menu buttons.

10: (Action) User Interaction
1: Disable instead of not visible

To prevent users from using a function, you must use the disable attribute to hide the control.

2: the pop-up position of the window should be obvious.

Click a control. In the pop-up window or menu, you should be prompted clearly. The minimum requirement is to overwrite the position you just clicked, so that you can easily jump to the new interface.

3: a prompt is required for executing the action.

While giving users a visual experience, they should pay attention to the user's interaction experience when writing programs. The UI is used as a tool for human-machine interaction and the user performs any action, the user should be given a visual, auditory, and tactile tip. In addition, this prompt should be clear, but it should not be too long. You can use the following methods:

When a user clicks a button and other actions for a job:

1: The Interaction dialog box is displayed, asking the user to click OK.

2: Prompt for changing the control parameters in the UI: (the prompt does not need to be confirmed by the user, there is a certain delay, or the prompt is automatically cleared after the user presses the key .)

For example, you can change the title bar string, display "information: submitted successfully", or set a special status bar, tlable, and so on for prompts.

3: Auditory tip:

When the sound card is confirmed to allow the user to hear the sound, a special sound prompt is sent. It is generally used as an aid for important prompts. The voice should not be too long. The emergency prompt should be short and frequent. The success prompt should be soothing and easy. Wait ......

11: (HELP) online help:
When to help and when not to help

1: system default, industrial standard control operations do not need to be described one by one, only need to describe special controls 2: special operations, special functional interfaces, add controls on the interface and directly connect to the corresponding help file.

3: The special settings are detailed. You should use concise and clear statements on the interface, or use tiptool, which will be assisted by step 2.

Help document:

Structured, divided by functional modules

It is necessary to describe how functions can be implemented in software.

The help document helps users better use the software. The wording should be appropriate, simple, and easy to understand. Each sentence should have a purpose to help users solve problems.

Help files are not advertisements, and commercial software does not allow advertisements. The purpose of company information description is to help users find after-sales support without any solution. The website connection, mailbox address, and phone number cannot be invalid.

12. Release rules
Describe the unified things one by one and describe them in a typical way. Put them in the help and user manual, and add a vocabulary.

Appendix:
When will the artist participate:

As the main person in interface beautification, the artist not only has the talent of artistic design and packaging design, but also should be interspersed with the whole project to provide system reference opinions to the interface program designer.

1: In the early stage of software design, the artist needs to participate in understanding, analyze the shortcomings of similar software interfaces, propose the main tone, typical interface style, and design the entire art package.

2: In the interface prototype design process, modify and discuss the final expression style with the developer, and establish the UI standard.

3: Standard Style resource files (such as icon, cur, and BMP) are provided during program development, and the design process of uniform style resources is summarized to form a standard document *.

4: assist in the production of help files, website styles, and participation in the production of product-based images, animations, product packaging, posters, etc.

Interface Design Test Specification

========================================================== ========================================================== ======================================
Interface Design Test Specification

Interface Test
By flowingice

I have summarized some interface design and testing specifications in my work and shared them with you. Interface Design and Test rules
The interface is the most direct layer for software-to-user interaction. The quality of the interface determines the first impression of the software. In addition, the well-designed interface can guide the user to complete the corresponding operations and play a wizard role. At the same time, the interface, such as the face of the same person, has the direct advantage of attracting users. A well-designed interface can give users a relaxed and pleasant feeling and a feeling of success. On the contrary, the failure of the interface design gives users a sense of frustration, the practical and powerful functions may be lost in the fear and abandonment of users. At present, the design of the interface has attracted much attention from software designers. It was not until the recent rise of Web Page production that it was favored by experts. In addition, well-designed interfaces are rejected because they require artistic talents.
Currently, there are three popular interface styles: multi-form, single-form, and resource manager styles. The following rules should be emphasized regardless of the style.

1: ease of use:
The button name should be easy to understand, accurate words, and no words can be left blank. It should be easy to distinguish from other buttons on the same interface, so it is best to understand the text. The ideal situation is that the user can know the functions of the interface and perform relevant operations without checking the help.

Easy-to-use Details:
1): the buttons that complete the same or similar functions are framed by frame. Common buttons must support shortcuts.
2): place the elements that complete the same function or task in a centralized position to reduce the distance between the mouse movement.
3): divide the local block by function, enclose it in a frame, and provide a function description or title.
4): the interface must support the keyboard automatic Browse button function, that is, the automatic switch function by pressing the tab key.
5): the control that should be input and important information on the interface should be in front of the tab order, and the position should also be placed in a prominent position on the window.
6): the number of controls on the same interface should not exceed 10. If there are more than 10 controls, you can use pagination interface display.
7): The paging interface must support shortcut switching between pages. Commonly Used combination Shortcut Keys: Ctrl + Tab
8): the default button must support the enter and select operations, that is, automatically execute the corresponding operation of the default button after pressing enter.
9): After the writable control detects illegal input, it should provide instructions and automatically obtain the focus.
10): the order of the tab key and the control arrangement must be consistent. Currently, the top-down mode is popular, and the lines are arranged from left to right at the same time.
11): check boxes and option boxes are arranged based on the high probability of selection.
12): check boxes and option boxes must have default options, and Tab selection is supported.
13): Multiple option boxes are used at the same time without the drop-down list box.
14): the drop-down box is used when the page space is relatively small, instead of the Option box.
15): use the option box when the number of options is small. Instead, use the drop-down list box.
16): Professional Software should use related terminology, while the universal interface should advocate the use of universal word eye.
2: Normative:
Generally, the interface design is based on the specifications of the Windows interface, that is, the standard format of "menu bar, toolbar, tool compartment, status bar, scroll bar, right-click shortcut menu" can be said: the higher the degree of standardization of the interface, the better the usability. Small Software generally does not provide a tool compartment.

Regulatory rules:
1): Common menus must have command shortcuts.
2): menus with the same or similar functions are separated by a horizontal line and placed in the same position.
3): The icon in front of the menu can intuitively represent the operation to be completed.
4): Generally, the menu depth must be limited to three layers at most.
5): You can customize the toolbar according to your requirements.
6): place the toolbar with the same or similar functions together.
7) prompt information should be provided for each button in the toolbar.
8): the maximum length of a toolbar cannot exceed the screen width.
9): the toolbar icons can intuitively represent the operations to be completed.
10): Set the default placement position in the commonly used toolbar.
11) when there are too many toolbar tools, you can consider using the tool compartment.
12): the tool compartment must be changeable and customized by the user based on the requirements.
13): the default total width of the tool compartment should not exceed 1/5 of the screen width.
14): the status bar must display the information that the user actually needs. Commonly used:
The current operation, system status, user location, user information, prompt information, error information, etc. If an operation takes a long time, the progress bar and process prompt should also be displayed.
15): the length of the scroll bar must be changed in time based on the length or width of the display information to help you understand the position and percentage of the display information.
16): the height of the status bar should be five good words, and the width of the scroll bar is slightly narrower than that of the status bar.
17): the menu and toolbar must have a clear line; the menu must be highlighted so that there is still a stereoscopic effect when the toolbar is removed.
18): The menu and status bar usually use the font No. 5. The toolbar is generally wider than the menu, but not too wide. Otherwise, it looks very uncoordinated.
19): the shortcut menu adopts the same principle as the menu.

3: help facilities:
The system should provide detailed and reliable help documents, so that users can seek a solution if they are confused.

Help facility details:
1): The Performance description and description in the help document should be consistent with the system performance. (Our system help documentation is a description of the system's ancestor period, confusing ).
2): When packaging a new system, modify the changes in the help document.
3): promptly call the system help function during operations. F1 is commonly used.
4): when calling help on the interface, you should be able to locate the help location corresponding to this operation in time. That is to say, the Help needs to be targeted in real time.
5): it is best to provide popular online help formats or HTML Help formats.
6): You can use keywords to search for the expected help in the Help Index. Of course, you should also provide the help keywords.
7): If you do not provide any written help documentation, it is best to print the help function.
8): Our technical support methods should be provided in the help. Once the user is difficult to solve the problem by themselves, they can easily seek new help methods.

4: Rationality:
The intersection of the diagonal lines of the screen is where the user looks directly. The top 1/4 is a location that is easy to attract the user's attention. Pay attention to the two locations when placing the form.

Detailed rules on Rationality:
1): the center of the parent form or main form should be near the diagonal focus.
2): The position of the subform should be in the upper left corner or center of the main form.
3): when multiple subforms are displayed, they should be shifted to the lower right to show the title of the form.
4): Important Command buttons and frequently used buttons should be placed on the interface for attention.
5): buttons that are easy to exit or close due to incorrect use should not be placed in easy points. The start or end of the horizontal column and the end of the vertical column are easy points.
6): buttons irrelevant to ongoing operations should be blocked (highlighted in gray in windows and cannot be used ).
7): You must provide confirmation information for operations that may result in data recovery failure and give the user the opportunity to give up their selection.
8): Illegal input or * instructions should be provided.
9): a prompt should be prompted for errors that occur during the running process, so that users can understand the error source and avoid waiting for an indefinite period of time.
10): the prompt, warning, or error description should be clear, clear, and appropriate.
5: appearance and coordination:
The interface size should be suitable for aesthetic points of view. It feels coordinated and comfortable, and can attract the user's attention within the effective scope.

Detailed rules on appearance and coordination:
1): the length and width ratio is close to the Golden Point. Do not adjust the length and width ratio, or the width exceeds the length.
2): The layout should be reasonable, should not be too dense, should not be too empty, and reasonable use of space.
3): The button size is similar. Do not use too long names to avoid occupying too many interface positions.
4): the button size should be consistent with the page size and space.
5): avoid placing large buttons on open interfaces.
6): After the control is placed, the interface should not be very vacant.
7): the font size should be consistent with the size ratio of the interface. The commonly used font contains a beautiful font ranging from 9 to 12, and rarely contains a font larger than 12.
8): the foreground and background colors should be properly matched, and the contrast should not be too large. It is best to use less dark colors, such as red and green colors. For common colors, use Windows interface tones.
9): If you use other colors, the main color should be soft, with affinity and magnetic force, and resolutely put an end to the color of the thorn.
10): Major colors commonly used in large systems include "# e1e1e1", "# efefef", and "# c0c0c0.
11): the UI style should be consistent, and the word size, color, and font should be the same unless it is art processing or has special requirements.
12): If the form can be minimized or maximized, the controls on the form also need to be scaled with the form. Do not zoom in the form only and ignore the zoom of the control.
13): interfaces with buttons generally do not support scaling, that is, only the function is disabled in the upper right corner.
14): when the parent form supports scaling, there is no need to scale the child form.
15): it is better to provide users with custom interface styles. You can select colors and fonts by yourself.

6: menu position:
Menus are the most important elements on the interface. Menu positions are organized by function.

Menu settings test rules:
1): Menus are usually arranged in the "commonly-used-Main-secondary-tool-help" location, in line with the popular Windows style.
2): common options include "file", "edit", and "View". These options are available in almost every system. Of course, you must choose between different systems.
3): the drop-down menu should be grouped according to the meaning of the menu options, arranged according to certain rules, separated by a horizontal line.
4): when the use of a group of menus requires a sequence or has a wizard function, they should be arranged in sequence.
5): menu items without sequence requirements are arranged according to the frequency and importance of use. Commonly Used menu items are placed at the beginning rather than the back. Important menu items are placed at the beginning and secondary menu items are placed at the back.
6): if there are many menu options, extend the menu length and reduce the depth.
7): Generally, the menu depth must be limited to three layers at most.
8): Quick commands must be provided for commonly used menus. For the combination principles, see 8.
9): the menu irrelevant to the operation should be blocked. If the dynamic loading mode is used, that is, only the required menu is displayed.
10): the icon in front of the menu should not be too big, and keep it best with the word height.
11): the width of the main menu should be close, and the number of words should not exceed four. The words in each menu can be the same and the best.
12): The number of main menus should not be too large. It is best to arrange the menus in a single row.
. 7: uniqueness:
If you follow the industrial interface standards blindly, you will lose your personality. In the case that the framework complies with the above specifications, it is particularly important to design an interface with its own unique style. Especially in the circulation of commercial software, there is a good advertisement utility for the migration pipeline.

1): the installation interface should contain organization introduction or product introduction with its own icons.
2): the main interface, preferably a company icon on most interfaces.
3): the logon interface must contain the logo of this product and the company icon.
4): the "about" in the Help menu should contain copyright and product information.
5): The company's series of products should maintain a consistent interface style, such as the background color, Font, menu arrangement, icons, installation process, button terms, and so on.

8: Combination of shortcuts
Using shortcut keys in menus and buttons makes it easier for users who prefer to use the keyboard. Most of the shortcut keys used in western windows and their applications are consistent.
Menu:
1): transaction-oriented combinations include:
CTRL-D Delete; Ctrl-F find; Ctrl-H replace; Ctrl-I insert; Ctrl-N new record; Ctrl-s save Ctrl-o open.
2): List:
CTRL-R, Ctrl-G, and Ctrl-tab to navigate to the same page control in the next page or in reverse order ;.
3): Edit:
CTRL-a select all; Ctrl-C copy; Ctrl-V paste; Ctrl-x cut; Ctrl-Z undo *; Ctrl-y recover.
4) file:
CTRL-P print; Ctrl-W close.
5): System Menu
Alt-A file; Alt-e edit; Alt-T tool; Alt-W window; Alt-H help.
6): MS Windows reserved key:
CTRL-ESC task list; Ctrl-F4 close window; Alt-F4 end application; Alt-tab next application; enter default button/OK *; ESC cancel button/cancel; shift-F1 context-related help.
Button:
It can be adjusted according to system requirements. The following are only common combinations.
Alt-y OK (yes); Alt-C canceled; Alt-N No; Alt-D deleted; Alt-Q exited; Alt-A added; Alt-e edited; alt-B browsing; Alt-r reading; Alt-W writing.
These shortcut keys can also be used as the standard for developing Chinese application software, but can also start with a letter in Chinese pinyin.
9. security considerations:
You can control the error probability in the following ways on the interface to greatly reduce the damage caused by user-caused errors. Developers should take into account all possible problems as much as possible to minimize the possibility of errors. If the application exits from the system due to a protective error, the user may lose confidence in the software. This means that the user has to interrupt his or her thinking and log on again with time and effort, and all the operations that have been done will be lost because no disk is saved.

Security rules:
1): the most important thing is to eliminate errors that may cause the application to stop abnormally.
2): avoid unintentional data input by users as much as possible.
3): use related controls to restrict the types of user input values.
4): when there are only two possibilities for a user to make a choice, you can use a single region.
5): when there may be more options, you can use the check box. Each option is valid and you cannot enter any invalid options.
6): when there are many options, you can use the list box and drop-down list box.
7): In an application system, developers should avoid unauthorized or meaningless operations by users.
8): restrict or block input characters or actions that may cause fatal errors or system errors.
9): actions that may have serious consequences must be remedied. The user can return to the correct status through remedial measures.
10): determines the input of some special symbols and the characters that conflict with the symbols used by the system, and prevents users from entering this character.
11): it is best to support reversible handling of right and wrong operations, such as canceling series operations.
12): users should be prevented from performing operations only after they enter valid characters.
13) the cancellation function should be provided for * tasks that may have a long wait time.
14): special characters are often; '"> <, comment':" ["{,/|}] + =)-(_ * & ^ % $ #@! ~,..? /There are spaces.
15): conflicts with reserved characters used by the system must be restricted.
16): when reading the information entered by the user, select whether to remove the leading and trailing spaces as needed.
17): Some Fields read into the database do not support spaces in the middle, but you must enter spaces in the middle. In this case, you must process the fields in the program.

10: Multi-Window applications and system resources:
Well-designed software should not only have complete functions, but also occupy the minimum resources as much as possible.
1): In a multi-window system, some interfaces must be kept at the top level, so that you do not need to switch or even minimize other windows to display them when opening multiple windows.

2): After loading on the main interface, the memory is automatically detached to allow the occupied Windows system resources.
3): Close all forms. After the system exits, it will release all the system resources it occupies, unless it is a system that needs to run in the background.
4): Try to avoid exclusive use of the system.