semi合集-English.pdf - 第6941页
SEMI S8-0705 © SEMI 1995, 2005 38 R6-1.2.7 The quality of feedback or exp lanations should mini mize the need to consult u ser manuals and other external info rmation, th us avoiding frequent media swit ches. R6-1.2.8 If…
SEMI S8-0705 © SEMI 1995, 2005 37
RELATED INFORMATION 6
USER COMPUTER INTERFACE
NOTICE: This related information is not an official part of SEMI S8 and is not intended to modify or supersede the
official guidelines. It was derived from the work of the originating task force. Publication was authorized by full
ballot procedures. Determination of the suitability of the material is solely the user’s responsibility.
R6-1 Operator Interaction
NOTE R6-1: Refer to ISO 9241 for detailed guidance.
R6-1.1 The dialogue should be suitable for the task.
NOTE R6-2: A dialogue is suitable for a task when it supports the user in the effective and efficient completion of the task.
R6-1.1.1 The dialogue should present the user only with information related to the completion of the task.
R6-1.1.2 The information displayed should be in a directly usable form to avoid the need to transpose, compute,
interpolate, or translate.
R6-1.1.3 Help information should be task dependent.
R6-1.1.4 Any actions that can appropriately be allocated to the interface software for automatic execution should be
carried out by the software without user involvement.
R6-1.1.5 When designing the dialogue, consideration should be given to the complexity of the task with respect to
the users’ skills and abilities.
R6-1.1.6 The format of input and output should be appropriate to the given task and user requirements.
R6-1.1.7 The dialogue should support the user when performing recurrent tasks.
R6-1.1.8 If default input capabilities exist for a given task (e.g., standard default values) it should not be necessary
for the user to input such values. It should also be possible to replace default values with other values or other
appropriate default values.
R6-1.1.9 During performance of a task in which data is changed, the original data should remain accessible if the
task requires it.
R6-1.1.10 The dialogue should avoid forcing unnecessary task steps.
R6-1.2 The dialog should be self-descriptive.
NOTE R6-3: A dialogue is self-descriptive when each dialogue step is immediately comprehensible through feedback from the
system or is explained to the user on request.
R6-1.2.1 After any user action, the dialogue should provide feedback, where appropriate. If severe consequences
result from the user action, the system should provide explanation and request confirmation before carrying out the
action.
R6-1.2.2 Feedback or explanations should be presented in consistent terminology, which is derived from the task
environment, rather than from the dialogue system technology (e.g., when the user wants to input an order to load a
cassette, LOAD should be the command rather than a code followed by pressing the ENTER key).
R6-1.2.3 Feedback or explanations should assist the user in gaining a general understanding of the dialogue system
as a possible supplement to user training.
R6-1.2.4 Feedback or explanations should be based on the level of knowledge which the typical user may be
expected to have.
R6-1.2.5 Feedback or explanations varying in types and length, based on user needs and characteristics, should be
available for the user.
R6-1.2.6 To enhance their value for the user, feedback or explanations should strictly relate to the situation for
which they are needed.
SEMI S8-0705 © SEMI 1995, 2005 38
R6-1.2.7 The quality of feedback or explanations should minimize the need to consult user manuals and other
external information, thus avoiding frequent media switches.
R6-1.2.8 If defaults exist for a given task they should be made available to the user.
R6-1.2.9 The user should be informed about changes in the dialog system status that are relevant to the task.
R6-1.2.10 When input is requested, the dialogue system should give information to the user about the expected
input.
R6-1.2.11 The requirement to learn special program codes, long sequences, and special instructions should be
avoided.
R6-1.3 The dialogue should be controllable.
NOTE R6-4: A dialogue is controllable when the user is able to initiate and control the direction and pace of the interaction until
the point at which the goal has been met
R6-1.3.1 The speed of interaction should not be dictated by the operation of the system. It should always be under
the control of the user according to the user's needs and characteristics.
R6-1.3.2 The dialogues should give the user control over how to continue with the dialogue. Exceptions may be
made for critical alarms, fault situations, as well as process and safety reasons. User interrupt or abort options to
terminate interactions should be provided.
R6-1.3.3 If the dialogue has been interrupted, the user should have the ability to determine the point of restart when
the dialogue is resumed, if the task permits.
R6-1.3.4 If interactions are reversible and the task permits, it should be possible to undo at least the last dialogue
step.
R6-1.3.5 Different user needs and characteristics require different levels and methods of interaction.
R6-1.3.6 The way that input/output data are represented (format and type) should be under the control of the user.
R6-1.3.7 Where alternative input/output devices exist, the user should have the option of which one to use.
R6-1.4 The dialogue should conform with user expectations.
NOTE R6-5: A dialogue conforms with user expectations when it is consistent and corresponds to the user characteristics, such
as task knowledge, education, experience, and to commonly accepted conventions.
R6-1.4.1 Dialogue behavior and appearance within a dialogue system should be consistent.
R6-1.4.2 State change actions should be implemented consistently.
R6-1.4.3 Dialogues used for similar tasks should be similar so that the user can develop common task solving
procedures.
R6-1.4.4 Immediate feedback on user input should be given where appropriate to user expectations. It should be
based on the level of knowledge of the user.
R6-1.4.5 The cursor should be located where the input is wanted.
R6-1.4.6 If a response time is likely to deviate considerably from the expected response time,
the user should be
informed of this.
R6-1.5 The dialogue should be error tolerant.
NOTE R6-6: A dialogue is error tolerant if, despite evident errors in input,
the intended result may be achieved with either no or
minimal corrective action by the user.
R6-1.5.1 The application should assist the user in detecting and avoiding errors in input. The dialogue system
should prevent any user input from causing undefined dialogue system states or dialogue system failures.
R6-1.5.2 Errors should be explained to help the user to correct them.
R6-1.5.3 Depending on the task, it may be desirable to apply special effort in presentation techniques to improve
the recognition of error situations and their subsequent recovery.
SEMI S8-0705 © SEMI 1995, 2005 39
R6-1.5.4 In cases where the dialogue system is able to correct errors automatically, it should advise the user of the
execution of the corrections and provide the opportunity to override the corrections.
R6-1.5.5 User needs and characteristics may require that error situations are deferred, leaving the decision to the
user when to handle them.
R6-1.5.6 Additional explanations should be provided during error correction on request.
R6-1.5.7 Validation/verification of data should take place before attempting to process the input.
R6-1.5.8 Additional controls should be provided for commands with serious consequences.
R6-1.5.9 Error correction should be possible without switching dialogue system states, where the task permits.
R6-1.6 The dialogue should be capable of individualization.
NOTE R6-7: A dialogue is capable of individualization when the interface software can be modified to suit the task needs,
individual preferences, and skills of the user.
NOTE R6-8: Although, in many cases, providing users with customization capabilities is very desirable, it is not an acceptable
substitute for ergonomically designed dialogues. In addition, customization capabilities should be provided only within certain
limits such that modifications cannot cause users any potential discomfort (e.g., unacceptable noise levels with user configured
auditory feedback).
R6-1.6.1 Mechanisms should be provided to allow the dialogue system to be adapted to the user's language and
culture, individual knowledge and experience of task domain, perceptual, sensory-motor, and cognitive abilities.
R6-1.6.2 The amount of explanation (e.g., details in error messages, help information) should be modifiable
according to the level of knowledge of the user.
R6-1.6.3 The user should be allowed to incorporate their own vocabulary to establish individual naming for objects
and actions if it suits the contexts and tasks. It should also be possible for the user to add individualized commands.
R6-1.6.4 The user should be able to set up operational time parameters to match their individual needs.
R6-1.6.5 Users should be able to choose between different dialogue techniques for different tasks.
R6-1.6.6 Log in should be a separate procedure that is completed before a user may select an operational step.
Passwords should be used to protect (limit access to) parts of the operating system which may be beyond the user’s
skill level to control safely.
R6-1.7 The dialogue should be suitable for learning.
NOTE R6-9: A dialogue is suitable for learning when it supports and guides the user in learning to use the system.
R6-1.7.1 Rules and underlying concepts which are useful should be made available to the users, thus allowing the
users to build up their own grouping strategies and rules for memorizing activities.
R6-1.7.2 Relevant learning strategies, (e.g., comprehension oriented, learning by doing, learning by example)
should be provided.
R6-1.7.3 Relearning facilities should be supported.
R6-1.7.4 A number of different means to help the user to become familiar with the dialogue elements should be
provided.
R6-2 Video Display Terminals
NOTE R6-10: Refer to ISO 9241 and EN 894-2 for detailed guidelines.
R6-2.1 Display characteristics should be selected to suit the specific conditions of use. For example, the expected
viewing distance, ambient levels of illumination, and lighting color (e.g., yellow illumination) in the work area
should be considered.
R6-2.2 Displays should be perpendicular to the user’s normal line of sight. The angle of the screen should be
adjustable or positioned to minimize glare.
R6-2.3 Surfaces immediately adjacent to the display should have a matte finish to control glare.