semi合集-English.pdf - 第2984页

SEMI E120-0705 © SEMI 2003, 2005 20 RELATED INFORMATION 1 FURTHER BACKGROUND AND JUSTIFICATION NOTICE: This Related Information is not an official pa rt of SEMI E120. This Related Information is not intended to modify or…

100%1 / 7923
SEMI E120-0705 © SEMI 2003, 2005 19
11 Related Documents
11.1 Unified Modeling Language (UML) Specification, Version 1.4, OMG Specification 01-09-67, available from
http://www.omg.org/technology/documents/modeling_spec_catalog.htm.
3
3 This specification uses object-modeling terminology consistent with this OMG standard for UML.
SEMI E120-0705 © SEMI 2003, 2005 20
RELATED INFORMATION 1
FURTHER BACKGROUND AND JUSTIFICATION
NOTICE: This Related Information is not an official part of SEMI E120. This Related Information is not intended
to modify or supersede the official standard. Determination of the suitability of the material is solely the
responsibility of the user.
R1-1 UML Terminology
R1-1.1 In order to help with understanding terminology used in conjunction with object technology, this section
shares excerpts from the glossary of the OMG standard for UML—the predominant modeling notation.
Unified Modeling Language (UML) Specification, Version 1.4, OMG Specification 01-09-67, available from
http://www.omg.org/technology/documents/modeling_spec_catalog.htm
R1-1.2 These definitions are taken from B.2 Glossary of Terms of the above document.
R1-1.2.1 abstract class — a class that cannot be directly instantiated. Contrast: concrete class.
R1-1.2.2 aggregate [class] — a class that represents the “whole” in an aggregation (whole-part) relationship. See:
aggregation.
R1-1.2.3 aggregation — a special form of association that specifies a whole-part relationship between the aggregate
(whole) and a component part. See: composition.
R1-1.2.4 association — the semantic relationship between two or more classifiers that specifies connections among
their instances.
R1-1.2.5 attribute — a feature within a classifier that describes a range of values that instances of the classifier may
hold.
R1-1.2.6 cardinality — the number of elements in a set. Contrast: multiplicity.
R1-1.2.7 child — in a generalization relationship, the specialization of another element, the parent. See: subclass,
subtype. Contrast: parent.
R1-1.2.8 class — a description of a set of objects that share the same attributes, operations, methods, relationships,
and semantics. A class may use a set of interfaces to specify collections of operations it provides to its environment.
See: interface.
R1-1.2.9 classifier — a mechanism that describes behavioral and structural features. Classifiers include interfaces,
classes, datatypes, and components.
R1-1.2.10 classification — the assignment of an object to a classifier. See dynamic classification, multiple
classification and static classification.
R1-1.2.11 class diagram
— a diagram that shows a collection of declarative (static) model elements, such as
classes, types, and their contents and relationships.
R1-1.2.12 composition — a form of aggregation which requires that a part instance be included in at most one
composite at a time, and that the composite object is responsible for the creation and destruction of the parts.
Composition may be recursive. Synonym: composite aggregation.
R1-1.2.13 concrete class — a class that can be directly instantiated. Contrast: abstract class.
R1-1.2.14 constraint — a semantic condition or restriction. Certain constraints are predefined in the UML, others
may be user defined.
R1-1.2.14.1 Constraints are one of three extensibility mechanisms in UML. See: tagged value, stereotype.
R1-1.2.15 diagram — a graphical presentation of a collection of model elements, most often rendered as a
connected graph of arcs (relationships) and vertices (other model elements). UML supports the following diagrams:
class diagram, object diagram, use case diagram, sequence diagram, collaboration diagram, state diagram, activity
diagram, component diagram, and deployment diagram.
SEMI E120-0705 © SEMI 2003, 2005 21
R1-1.2.16 element — an atomic constituent of a model.
R1-1.2.17 feature — a property, like operation or attribute, which is encapsulated within a classifier, such as an
interface, a class, or a datatype.
R1-1.2.18 generalization — a taxonomic relationship between a more general element and a more specific element.
The more specific element is fully consistent with the more general element and contains additional information.
An instance of the more specific element may be used where the more general element is allowed. See:
inheritance.
R1-1.2.19 inheritance — the mechanism by which more specific elements incorporate structure and behavior of
more general elements related by behavior. See: generalization.
R1-1.2.20 instance — an entity that has unique identity, a set of operations that can be applied to it, and state that
stores the effects of the operations. See: object.
R1-1.2.21 interface — a named set of operations that characterize the behavior of an element.
R1-1.2.22 interface inheritance — the inheritance of the interface of a more general element. Does not include
inheritance of the implementation. Contrast: implementation inheritance.
R1-1.2.23 method — the implementation of an operation. It specifies the algorithm or procedure associated with an
operation.
R1-1.2.24 model [MOF] — an abstraction of a physical system with a certain purpose. See: physical system.
Usage note: In the context of the MOF specification, which describes a meta-metamodel, for brevity the
metametamodel is frequently to as simply the model.
R1-1.2.25 multiplicity — a specification of the range of allowable cardinalities that a set may assume. Multiplicity
specifications may be given for roles within associations, parts within composites, repetitions, and other purposes.
Essentially a multiplicity is a (possibly infinite) subset of the non-negative integers. Contrast: cardinality.
R1-1.2.26 object — an entity with a well-defined boundary and identity that encapsulates state and behavior. State
is represented by attributes and relationships, behavior is represented by operations, methods, and state machines.
An object is an instance of a class. See: class, instance.
R1-1.2.27 object diagram — a diagram that encompasses objects and their relationships at a point in time. An
object diagram may be considered a special case of a class diagram or a collaboration diagram. See: class diagram,
collaboration diagram.
R1-1.2.28 operation — a service that can be requested from an object to effect behavior. An operation has a
signature, which may restrict the actual parameters that are possible.
R1-1.2.29 parent — in a generalization relationship, the generalization of another element, the child. See:
subclass, subtype. Contrast: child.
R1-1.2.30 qualifier — an association attribute or tuple of attributes whose values partition the set of objects related
to an object across an association.
R1-1.2.31 relationship — a semantic connection among model elements. Examples of relationships include
associations and generalizations.
R1-1.2.32 role — the named specific behavior of an entity participating in a particular context. A role may be static
(e.g., an association end) or dynamic (e.g., a collaboration role).
R1-1.2.33 signature — the name and parameters of a behavioral feature. A signature may include an optional
returned parameter.
R1-1.2.34 subclass — in a generalization relationship, the specialization of another class; the superclass. See:
generalization. Contrast: superclass.
R1-1.2.35 subtype — in a generalization relationship, the specialization of another type; the supertype. See:
generalization. Contrast: supertype.