semi合集-English.pdf - 第3134页

SEMI E125-0305 © SEMI 2003, 2005 42 R1-3.4 Retrieve Equipment Parameter Descriptions — This use case provides a way for an application to request a description o f all of the data it ems provided by the e quipment, and t…

100%1 / 7923
SEMI E125-0305 © SEMI 2003, 2005 41
R1-3.3 Retrieve Exception Descriptions — This use case provides a way for an application to request a description
of all of the exceptions generated by the equipment, and to determine which components of the equipment generate
which exceptions. This supports automated usage, so that applications that are looking for standardized or well-
known equipment specific exceptions can discover their existence on a specific tool. It also supports any manual
usage in which a human user would like to understand available equipment-specific exceptions. Figure R1-4 shows
one example of how this use case can be realized using messages from the interface defined in this specification (see
Section 9).
: EquipmentD iagnost icsClient
Equipm ent
GetExceptions()
GetT ypes ()
GetUnits()
GetEquipment NodeDes cript ions()
GetEquipment Struc ture()
Get all except ion def init ions
in use by the e quipment
Get all ty pe def initions in use by
the equipment, look for types
us ed by ex ception parameters.
Get all unit definitions , determine
unit s used by exc eptio n parameter
type definit ions
Get all equipm ent nodes, det ermine t he
nodes prov iding the ex ceptions of
interest
Get th e equipm ent structure to und erstand
the rol e of each equipment node in t he overall
equipm ent struct ure
Figure R1-4
Use Case Realization for “Retrieve Exception Descriptions”
SEMI E125-0305 © SEMI 2003, 2005 42
R1-3.4 Retrieve Equipment Parameter Descriptions — This use case provides a way for an application to request a
description of all of the data items provided by the equipment, and to determine which components of the equipment
provide that data. This supports automated usage, so that applications that are looking for standardized or well-
known equipment-specific data items can discover their existence on a specific tool. It also supports any manual
usage in which a human user would like to browse and understand equipment-specific data that has not been
standardized. Figure R1-5 shows one example of how this use case can be realized using messages from the
interface defined in this specification (see Section 9).
: Proc essC ontrolC lient
Equipment
GetEquipmentNodeDescriptions()
GetTypes()
GetUnits()
GetEquipmentStructure()
Get all equipment nodes, look for
parameters def ined for each node
Get all type definitions in use by
this equipment, look for types
used by parameters
Get all unit definitions, determine
used by parameter ty pe definitions
Get the equipment structure to
underst and the role of eac h equipment
node in the overall equipment st ruct ure
Figure R1-5
Use Case Realization for “Retrieve Equipment Parameter Descriptions”
SEMI E125-0305 © SEMI 2003, 2005 43
R1-3.5 Retrieve Equipment Configuration — This use case is directly supported by this specification, and provides
a way for an application to request a description of the physical and logical equipment configuration. Figure R1-6
shows one example of how this use case can be realized using messages from the interface defined in this
specification (see Section 9).
: EquipmentD iagnosticsC lient
Equipment
GetEquipment NodeDes criptions()
GetEquipment Struc ture()
Get all equipment nod es, det ermine
nodes that refer to softw are modules
of interest
Get the equipment st ructure to
understand t he role of each node
in the o verall equ ipme nt
Figure R1-6
Use Case Realization for “Retrieve Equipment Configuration”