semi合集-English.pdf - 第920页

SEMI E118-1104 E © SEMI 2002, 2004 14 RELATED INFORMATION 1 SCENARIOS NOTE: This related information is not an official part o f SEMI E118 and was derived from work of the originating task force. This related information…

100%1 / 7923
SEMI E118-1104
E
© SEMI 2002, 2004 13
NOTICE: SEMI makes no warranties or representations as to the suitability of the standards set forth herein for any
particular application. The determination of the suitability of the standard is solely the responsibility of the user.
Users are cautioned to refer to manufacturer's instructions, product labels, product data sheets, and other relevant
literature, respecting any materials or equipment mentioned herein. These standards are subject to change without
notice.
By publication of this standard, Semiconductor Equipment and Materials International (SEMI) takes no position
respecting the validity of any patent rights or copyrights asserted in connection with any items mentioned in this
standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and
the risk of infringement of such rights are entirely their own responsibility.
SEMI E118-1104
E
© SEMI 2002, 2004 14
RELATED INFORMATION 1
SCENARIOS
NOTE: This related information is not an official part of SEMI E118 and was derived from work of the originating
task force. This related information was approved for publication by full letter ballot procedures on July 19, 2002.
R1-1 Examples
R1-1.1 This section provides examples of typical scenarios for a WIDR with two read heads.
Table R1-1 Reset Scenario
Controller WIDR Head1 Head2
Msg. Msg. Action State Action State Action State
Reset→
Perform
Reset
OPERATING or
MAINTENANCE
OPERATING OPERATING
←Reset Reply
OPERATING or
MAINTENANCE
OPERATING OPERATING
Table R1-2 Get Status Scenario
Controller WIDR Head1 Head2
Msg. Msg. Action State Action State Action State
Get Status 0→
Determine
Status
OPERATING or
MAINTENANCE
Any Any
←Status Reply
Same Any Any
Table R1-3 Scenario for Interleaved Read WID from Both Head
Controller WIDR Head1 Head2
Msg. Msg. Action State Action State Action State
Read WID 01→
OPERATING
Start
Read
BUSY IDLE
Read WID 02→
OPERATING BUSY
Start
Read
BUSY
←Read WID
Reply 01
OPERATING IDLE BUSY
←Read WID
Reply 02
OPERATING IDLE IDLE
SEMI E118-1104
E
© SEMI 2002, 2004 15
RELATED INFORMATION 2
OBJECT MODEL
NOTE: This related information is not an official part of SEMI E118 and was derived from work of the originating
task force. This related information was approved for publication by full letter ballot procedures on July 19, 2002
R2-1 Object Model Notes
R2-1.1 Object models provide a graphic representation of entities. The models in this section use the Object
Modeling Technique (OMT) described in Object-Oriented Modeling and Design. Object types are represented by
rectangles with one, two, or three sections. The name of the object type is in the first, or only section. Attributes,
information about the object, are shown in the second section. Operations or services are shown in a third section.
Lines between objects represent relationships.
R2-1.2 Three models are shown for purposes of illustration. The general multi-head case is shown first with only
the required attributes and services. Next, the full model for the multi-head case is shown with all attributes and
services defined in this standard. Finally, the full model for the integrated single-head case is shown.
R2-1.3 Note that the Upstream Controller sends all service requests to the WIDR controller, including services
shown for the individual heads. Services shown on these models for WIDR are those with a Head ID service
parameter value of zero while services shown for the Head are those with a Head ID service parameter value
between one and thirty-one.
R2-2 Fundamental Requirements Example Object Models
R2-2.1 The object model in Figure R2-1 shows objects for the general (multi-head) WIDR satisfying fundamental
requirements only. It shows the WIDR subsystem as made up of one or more heads. It also illustrates the required
attributes and services provided by the WIDR and its relationships with its upstream controller and with its heads.
1+
WIDR
- Confi
g
uration
- AlarmStatus
- SoftwareRevLevel
- O
p
erationalStatus
Chan
g
eState
Get Attributes
Get Status
H
ead
- HeadAlarmStatus
- HeadID
- HeadStatus
Get Attributes
Get Status
ReadWID
U
p
stream
Controller
requests services
from
is made up of
Figure R2-1
Object Model for Fundamental Requirements