Ergonomic requirements for office work with visual display terminals (VDTs)-Part 10:Dialogue prinip
Some standard content:
ICS 13. 180
National Standard of the People's Republic of China
GB/T 18978. 102004/IS0 9241-10:1996 Ergonomic requirements for office work with visual display terminals(VDTs)-Part 10:Dialogue principles(1S0 9241-10:1996,IDT)
Published on 2004-05-10
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Administration of Standardization of the People's Republic of China
Implementation on 2004-12-01
CB/T18978.10—2004/IS0 9241-10:1996 GB/T18978 "Ergonomic requirements for office use with visual display terminals (VDTs)" covers the ergonomic requirements for hardware and software involved in the use of visual display terminals, and is intended to be divided into the following 17 parts: - Part 1: Overview;
Part 2: Work requirements guide;
Part 3: Visual display requirements;
Part 4: Keyboard requirements:
--- Part 5: Workbench layout and posture requirements; : Part 6: Work environment guidelines:
--- Part 7: Display requirements with reflection;
Part 9: Display color requirements;
Part 9: Non-keyboard input device requirements: ... --- Part 10 Dialogue original purchase,
- Part 11: Usability guide:
Part 12: Information display
Part 13 ·User Guide·
…Part [·Single dialogue
Part 15: Command dialogue:
Part 16: Direct operation dialogue:
-Part 17: Filling in the form dialogue:
This part is Part 10 of GB/T 18978
This part is equivalent to 1S0922110:1996: Ergonomic requirements for office work using visual limit display terminals: Part 0: Dialogue principles (English version)
This part is translated according to 1S09241-10:1996. When introducing the dialogue principles in Part 3.2 to 3.8, the typical applications and examples of various dialogue principles have been edited according to Chinese conventions, that is, they are compiled in Chinese tables and table titles are added: This part is proposed by the China National Institute of Standardization and is developed by the National Technical Committee for Ergonomics Standardization! This part was drafted by China Academy of Standardization and Chemical Engineering, Lenovo Group Co., Ltd., Institute of Software, Chinese Academy of Sciences, Fourth Research Institute of Air Force, Dalian Maritime University, Institute of Psychology, Chinese Academy of Sciences. The main contributors to this part are Chen Guangqiao, Yang Li, Xu Zhong, Guo Xiaochao, Liu Zhijie, Chen Baihong, and Fu Xiaolan. TYYKAONKAa
CB/T 18978.10--2004/ISO 9241-10:1996
This part of GB/T18978 is mainly aimed at the ergonomic design of software for visual display terminals (VDIs). It describes the general principles of ergonomics independent of any specific dialogue technology. When applying these principles, it is advisable to be consistent with GB/T18978. These principles can be applied when defining, developing or evaluating dialogue systems, but they can only be used as a general guide. The application method of each dialogue principle depends on the characteristics of the target users of the system, the tasks, the environment and the specific dialogue technology used. Guidelines for identifying user tasks and related aspects of the use environment are given in GB/T 18978.11; specific guidelines for the use of menus, command language, direct operation and form filling techniques will be specified in GB/T 18978 Parts 11 to 17. The ultimate beneficiaries of GB/T 18978 are the end users of VIT. It was these user needs that provided the developers of ISO 9241-10:1996 Ergonomic requirements for office use with visual display terminals (VDTs) Part 10: Dialogue principles This part of ISO 9241-10:1996 describes the general principles of ergonomics, i.e. ergonomic principles are given without regard to the context of use, application, environment or technology.
The ergonomic principles presented in this part of ISO 1001 apply to the specification, design and evaluation of dialogs for visual display terminals (VDTs). 2 Terms and definitions
Terminology and definitions apply to this part of ISO 1001. 2.1
Dialogue
Interaction between a user and a system to achieve a specific purpose. 2.2
User
The individual who interacts with the system.
3 Dialogue principles
3.1 General
The following seven principles are important for the design and evaluation of VDT dialogs: Appropriateness for the task:
Descriptiveness;
Controllability;
Conformity with user expectations
Tolerance;
Appropriateness for personalization:
Appropriateness for learning.
3.2 to 3.8 introduce these dialogue principles and provide brief descriptions and typical applications and examples. These examples illustrate only some possible applications. These applications and examples have been selected for clarity and are not intended to be exhaustive. 3.1.1 User Characteristics
When applying dialogue principles, it is advisable to consider user characteristics, such as - attention span;
, the limits of short-term memory;
, learning behavior;
, work level and experience with the system;
, the user's subjective understanding of the underlying structure and purpose of the system with which he interacts. 3.1.2 Task Characteristics
The system dialogue characteristics make it possible to achieve the current task performance. If the task performance requirements are met, the effectiveness and efficiency of the performance can be improved.
TYYKAONKACa
GB/T 18978. 10--2004/1S0 9241-10: 19963. 1. 3 Relationship between principles
Dialogue principles are interrelated and it is necessary to weigh the pros and cons of each principle against the other principles. The applicability and relative importance of each principle will vary depending on the specific scope of the application, the user group and the chosen interactive technology. This means considering the following aspects: the organization's mouth;
The needs of the target (ultimate) user group;
The tasks supported;
The available technology and resources.
When applying these principles, it is necessary to establish priorities based on the specific circumstances of each case. 3.2 Appropriateness for the taskbZxz.net
A dialogue is appropriate for a task if it supports users to complete the task effectively and efficiently. Typical applications and examples of the principle of "suitability for the task" are shown in Table 1.
Table 1 Typical applications and examples of the principle of appropriateness for tasks
Dialogs should provide information relevant to the task being completed. The information should be determined by the task.
Appropriately assigned to the interface software Any actions that are automatically performed should be performed by the software without user involvement.
When designing the dialogs, the complexity of the task should be considered relative to the user's abilities and capabilities.
The input and output formats should be appropriate to the given task and the user's requirements. The activities should support the user in performing recurring tasks. If default capabilities exist for a given task (e.g., standard default examples), formatting information (e.g., colors), and information about the current date, time, etc., are presented only when it is helpful to complete the task. When the user requests help, the dialog system provides information related to the current task (e.g., if the program is in editing mode, a list of editing commands is provided). When a specific dialog box is displayed and the user requests help, the interface software provides information related to the dialog box. The cursor is automatically placed in the initial input area related to the task. The system automatically executes the program. In a public access system, if there is a set of optional input methods, a menu is used to provide possible options. Make screen input structured,In order to bring together all data obtained from a single source and to sequence and format these data items in the same way as in the data source, regardless of whether the underlying system uses the data in that sequence or format.
The precision of the input should be equal to the precision required by the task. The dialog system allows sequences of actions to be saved and allows the user to reuse these actions (for example, the use of macros).
If the task requires the current date, it does not need to be entered by the user, but it can be entered by the user. It should also provide the possibility for other users to modify the data. Appropriate default values should replace these missing values. When performing tasks that require data changes, the original data should remain accessible if the task requires it.
The dialog should avoid imposing unnecessary task steps. 3.3 Self-descriptiveness
The content of the input text can be restored to the state before the field was edited by pressing the main Sc key.
It takes only one step for the user to save the document and exit
When each step of the dialogue can be immediately understood through system feedback or explained when the application requests it, the dialogue is self-descriptive. Typical applications and examples of the principle of "self-descriptiveness" are shown in Table 2.
GB/T 18978.10—2004/ISO 9241-10:1996 Table 2 Typical applications and examples of the principle of "self-descriptiveness"
After the user performs any operation, the dialogue should provide feedback where appropriate.
The feedback of complex operation status is helpful for users to understand the operation. If the operation may lead to serious consequences, the system should provide explanations and ask for confirmation before executing the operation.
Feedback or explanation should be provided in consistent terms derived from the task environment rather than the technology of the dialogue system.
As a possible supplement to user training, feedback or explanation is helpful to gain human understanding of the dialogue system. Feedback or explanation is based on the expected level of knowledge of typical users. The needs and characteristics of the user, the feedback or explanation changes in the type and length it can provide to the user,
To increase the value of the feedback or explanation to the user, the feedback or explanation should be relevant to the situation in which the feedback or explanation is needed. To increase the value of the feedback or explanation, the feedback or explanation should minimize references to manuals and other external information to avoid frequent media switching,
If default values exist for a given task, the user can use them: The user should be informed of changes in the dialog system state related to the task. When requesting input, the dialog system should provide relevant information for the user. The message should be clearly expressed in an understandable, objective and constructive style and consistent structure for the intended input. The message should not contain value judgments such as "the content of this message is meaningless". 3.4 Controllability. If the dialog can be rolled back, the application should indicate this by clearly giving information that some operations can be rolled back. If the deletion is irreversible, the system should require that the deletion operation be confirmed: Technical terms used in the activity are declared as terms actually used in the specific application field. In addition, the user The term explanation is obtained by entering the relevant words: thus, after entering the term "proportional change", the user will get an explanation of the task and a reference to the relevant program and user manual for additional information. During file saving, a message "Data is being saved to the document, please wait" is displayed. Technical users receive information about the system's technical aspects, while public users receive definitions of the data recording task. By pressing the "HELP" key once, the user can get a short explanation, and by pressing "HELP" twice, the user can get a detailed explanation of the command. The user can choose between general term explanations and exemplary explanations. The system provides help information that is sensitive to the current activity. In the context of the active dialog, the current session is displayed, and the software interface lists the available options for editing. In order to understand the current dialog state, the user's execution options can be displayed, such as:
When to expect input
The command currently being processed;
An overview of future changes, including possible user response options;
The history of the transaction process.
The dialog system asks for input by presenting the segment name and data type (for example: date, number, mark) and input format (for example: y, im, dd) information. The message indicates: "Please use the following format: YY/Mm-i)t
When the user can actively control the behavior and speed of the interaction until the desired behavior is achieved, the dialogue is controllable. Typical applications and examples of the "controllability" principle are shown in Table 3.
YYKAONYKAca-
GB/T 18978.10—2004/SO 9241-10:1996 Table 3 Typical applications and examples of the "controllability principle" should be
The interaction speed should not be determined by the operation of the system, but should be kept under the control of the user according to the needs and characteristics of the user. The user should be given control over how to continue the dialogue. If the task allows, if the dialogue has been interrupted, the user can determine the restart position when restarting the dialogue. If the interaction is reversible and the service allows, at least the last step of the dialogue can be erased.
Different user needs and preferences require different interaction levels and methods. The way (format and type) of expressing input and output data should be under the control of the user.
If controlling the amount of data displayed is useful for a specific task, the user should be able to exercise this control.
When input and output devices are available, the user should have the right to choose which device to use. 3.5 Conformity with user expectations
The dialog system does not clear the replaced text field until the user signals that the data entry is complete (e.g. by pressing the FNTER key). To ensure that it is accessible to the user, the dialog system sets the cursor to the next input field, but offers the user the possibility to select a different field. The user can decide after an interruption (e.g. based on intermediate results), whether the session should be continued from the point of interruption, whether certain interactive activities should be withdrawn or whether the entire session should be cancelled, under certain conditions that may dictate the restart of the loop. The dialog system provides the possibility to read and delete objects, menus for new users and shortcut key help for experienced users. The level of detail is consistent with the different expertise of the users. The system provides the possibility to switch between text and icon presentation for the file list, and a form to be filled is displayed in separate pages, allowing the user to select the displayed page according to the work situation. The user can stop the output if it receives unwanted output. It is possible to choose between mouse and keyboard input devices. The dialog system provides the possibility to choose between several printers. The dialog meets the expectations of the user when it is consistent and corresponds to the user's characteristics (e.g. task knowledge, level of education and experience) and common conventions. Typical applications and examples of the principle of "conformity with user expectations" are shown in Table 4. Table 4 Typical applications and examples of the principle of "conformity with user expectations" should be shown in Table 4.
In a dialog system, the behavior of the dialog should be consistent. The behavior to achieve state changes should be consistent. The application software uses familiar queries in task execution. Similar tasks should use similar dialogs so that users can establish common task solutions.
Instant feedback on user input should appear where the user expects. It should be based on the user's knowledge level.
System status messages always appear in the same line. The same key is always used to terminate the activity.
The F1 key is always used to obtain data.
The technical terms used in the dialog are those actually used in the context of the user's task.
In a system with many different applications, in order to activate an application, the user always needs to double-click the corresponding icon to open it. The user moves all movable windows by dragging a pre-defined area near the top of the window: 1.
In the command dialog, the standard structure of all commands (including common grammatical rules) should remain unchanged and use a consistent set of names as much as possible. After the relevant input device moves, the dialog system immediately follows: move the cursor.
The cursor is located at the desired input position. Table 4 (continued)
GB/T 18978.102004/IS0 9241-10:1996
For the system to automatically move the cursor to the next expected input position,
If the response time is likely to deviate significantly from the expected response time, the user should be informed of this.
3.6 Fault Tolerance
The user receives a message such as "Please wait; your data is being processed" or a graphical indicator symbol indicating waiting is provided, such as an hourglass. Before starting the dialogue, the user can get an overall picture of the current state of the dialogue system. Inform the dialogue system of downtime, availability and other related characteristics.
Despite obvious errors in the input, the expected results can still be achieved with no or very few corrective actions by the user. The dialogue is fault-tolerant. Typical applications and examples of the "fault-tolerant" principle are shown in Table 5. Table 5 Typical applications and examples of the principle of "tolerance" Application
Application software helps users detect and avoid input errors. Display
If operations are required to be performed in sequence, the designed interface software can prevent any questions that lead to an uncertain dialog system state or the next step in any operation sequence from being determined quickly. User input of the dialog system failure.
Errors should be explained to help users correct them. Depending on the task, it is necessary to make special efforts in presentation technology to improve the recognition of error conditions and subsequent correction methods. If the dialog system can automatically correct errors, it is expected that users will be informed of these hot The error handling can be delayed according to the needs and characteristics of the user, and the decision of when to handle it can be left to the user.
During the error correction process as required by the user, it is best to provide the user with an additional instruction:
Before attempting to process the input, confirmation or verification should be performed. For commands with serious consequences, additional control should be provided. If the service allows, the error can be corrected without switching the dialog system state.
3.7 Appropriate personalization
For example; in the form filling dialog, there can be clear and sticky labels at the fields to be filled in
If the instrument allows Enter a number and the interface software checks whether the input is mathematical.
The dialog system displays an error message with information about the error, the type of error and possible corrections that the dialog system can determine: the dialog system finds an error that is clearly related to a specific data segment, marks the field and automatically places the cursor at the beginning of the field.
Display acceptable input
In the typesetting checker, provide error messages for misspelled words: Correction options are provided as requested.
In the support processing dialog system with spelling help function installed, when a letter is written, no correction will be suggested before the user requests it. In the given error message dialog box, a button is included to provide the user with further information. The deleted items are displayed in advance and the actual deletion is performed only after confirmation. When the form is input, the user can make corrections on the wrong symbols if the user is not allowed to switch to edit mode. When the interface software can be improved to suit the task needs, individual preferences and user skills, it has the ability to be personalized. Typical applications and examples of the principle of "adaptation" are shown in Table 6. Note: Although it is possible to consider providing users with customized capabilities in many cases, this cannot replace the ergonomic design of the dialog. In addition, the customization capability should only be provided within a certain limit so that the changes do not cause any potential discomfort to the user (for example, user-configured audio feedback may cause unacceptable noise levels!). 9241-10:1996 Table 6 Typical applications and examples of “appropriate personalization” principles
The dialog should be tailored to the user’s language and culture.
Increase font size for visually impaired users. Adjust colors for users with color perception impairments. Individual knowledge and experience of the task domain, as well as the user’s perception and feeling. Design for users with different motor and cognitive abilities with different cultural backgrounds.
The system should allow users to choose from alternative presentation methods based on individual preferences and the complexity of the information to be processed.
The amount of information (e.g., details of error messages and help messages) should be tailored to the user’s individual knowledge level. . If appropriate to the context and task, the user is allowed to integrate his or her own queries into the dialog system to create personalized object and action naming. The user can also add personalized commands
The user should be able to adjust the run-time parameters to match his or her personal needs.
The user should be able to choose different dialog technologies for different dialog tasks. 3.8 Suitable for learning
The keyboard layout.
The mouse can be suitable for left-handed or right-handed use, and the user can change the presentation and/or format of the output according to individual preferences.
The user can change the detail of the output as appropriate (e.g., more detailed corrections when learning, medium detail for error feedback, status The user can record sequences and even chains of sample functions to simplify the sequential execution of repeated commands. A dialog system allows the user to control the speed of scrolling information output. A dialog system allows the user to enter a command or select a menu item and initiate a dialog function. A dialog is suitable for learning when it supports and guides the user in learning how to use the system. Typical applications and examples of the principle of "suitability for learning" are shown in Table 7. It is recommended to provide users with rule bases that help them learn. To this end, it is recommended to allow users to gradually refine the concepts in order to remember the activities. The user should establish his or her own grouping strategy and rules.
It is advisable to provide relevant learning strategies (e.g., understanding guidance, learning by doing, learning by demonstration)
It is advisable to provide relearning tools!
It is advisable to provide different means to help users familiarize themselves with the dialog system: demonstration
The user can obtain information about the model on which the program is based. In certain cases, shortcut key combinations are used to clearly indicate the menu commands
The user can always switch between cognitive help information and example learning solutions (e.g., the user can ask for an overview of the overall structure of the database system, and then ask for instructions on certain functions, or "how these functions will be performed if... "). Learning this approach by practice is supported by encouraging users to experiment with alternative approaches, by demonstrating the correctness of the alternatives (e.g., allowing errors to occur without potentially serious consequences). Online interactive guides support learning this approach by practice. Pay attention to the frequency of command use: For commands that are used frequently, provide users with shortcuts and default values. For commands that are not frequently used, give them more self-explanatory information and more instructions, use unified positioning for time-type messages, and use similar screens for similar services. References GB/T 18978.10--2004/IS0 9241-10, 1996L1/AFNOR Z 67 ll0, Fanuaryt 1988, Infurialion Processiug, Frgomomics and Man-Computt?Ihalogue-Parl 1: Cone-pts
L2] DIN Gt 234-8, VDl3 work *tatinns---Part 8: P:inciples of crgonomic diaioguc: designF3l srnold, AG and rar, RA Action farilitation: a theorctical concept and its use in user interface desigi. In: Work with Coiputers: Organizational, Maragement, Streas and Heelth Aspects.Smith, MJ and Salvendy, G, tds. Elsevier, Arnsterdlarn.se-perce:ved quslity of interactive systcma. IEEETrams. Softw. Eng., SEz, 1978L6. harcker, W. B. Dcsigning the Lixer Interface: Straregies for Effective Huinan-CuinpulerIateraction.Adison-Wesley.Is8?[8] sperandio,I.. J. Software ergonamics of interface design. Behav. Inf. I'erhuol.. 6, 1u7,pp .271278
YrKAKAca
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.