semi合集-English.pdf - 第6940页

SEMI S8-0705 © SEMI 1995, 2005 37 RELATED INFORMATION 6 USER COMPUTER INTERFACE NOTICE : This related i nformati on is not an official part of SEMI S8 and is not intended to m odify or supersede the official guideli nes.…

100%1 / 7923
SEMI S8-0705 © SEMI 1995, 2005 36
R5-3.5 The display should be positioned so the user has a clear line of sight. Displays should not be located where
they are obstructed (by controls, equipment, body parts, etc.) or subject to glare. Display viewing should not require
awkward body postures.
R5-3.6 The legibility of a display is determined primarily by its visual angle and luminance contrast with the
background.
R5-3.7 There should be sufficient contrast between the object, letters, or numbers on a display to separate them
from the background, minimum ratio 3:1, preferred is 7:1 (ISO 9241). Too much contrast may result in glare.
R5-3.8 The ability of displayed information to communicate with the user clearly and precisely depends on the
amount of information displayed. Display design should emphasize simplicity and usability to:
R5-3.8.1 Reduce error and decrease response time.
R5-3.8.2 Provide only the amount of information necessary and only at a level of precision required.
R5-3.8.3 Display content in a directly usable form with no transformation required.
R5-4 Auditory Displays
R5-4.1 Auditory coding or signals may be used to alert a user to critical conditions or operations. Auditory coding
should be supplementary to visual coding. Auditory displays can be used effectively when:
R5-4.1.1 Vision is overburdened or degraded,
R5-4.1.2 The message requires immediate action,
R5-4.1.3 The job requires the operator or maintainer to move around frequently,
R5-4.1.4 The message is simple and short,
R5-4.1.5 The message signals an event in time, or
R5-4.1.6 The message does not need to be referred to later.
R5-5 Control - Display Relationships
R5-5.1 The relationship between associated controls and displays (their organization and layout) is critical to
optimizing system performance and minimizing operator error.
R5-5.2 Controls and displays should be organized into functional groups and positioned according to criticality,
sequence of operation, and frequency of use.
R5-5.3 Control-display compatibility refers to the extent to which the relationship between a control operation and
its effect is predictable by the user. Predictability is determined by individual and population cultural stereotypes
(user expectations, previous experience, an idea of the way equipment works, etc.). Lack of compatibility degrades
speed, accuracy of performance, and increases probability of error. Types of compatibility include sequential
arrangement, spatial organization, and direction of movement. Technology transfer and utilization by a multi-
cultural or multi-ethnic work force, as well as across global user populations should consider the impact of cultural
and behavioral stereotypes.
R5-5.4 Display layout, control location, and operation should be similar throughout a particular type and/or model
of equipment or system. Consistency is particularly important for color, shape, and size of controls, scale markings
on displays, and labeling.
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.