ISO 15745-1:2003 産業オートメーションシステムと統合—オープンシステムアプリケーション統合フレームワーク—パート1：一般的なリファレンスの説明 | ページ 6

3.1

action

something which happens

[SOURCE: ISO/IEC 10746-2]

Note 1 to entry: Every action of interest for modelling purposes is associated with at least one object (see ISO/IEC 10746-2).

3.2

actor

coherent set of roles that users of use cases play when interacting with these use cases [UML]

Note 1 to entry: An actor has one role for each use case with which it communicates.

3.3

aggregation

special form of association that specifies a whole-part relationship between the aggregate (whole) and a component part [UML]

3.4

AIP developer

person (or persons) who uses the application integration framework to develop integration models and/or profiles

3.5

association

semantic relationship between two or more classifiers that specifies connections among their instances [UML]

3.6

base specification

reference document containing information that is referenced by a profile

3.7

class

description of a set of objects that share the same attributes, operations, methods, relationships, and semantics [UML]

3.8

classifier

mechanism that describes behavioural and structural features [UML]

Note 1 to entry: Classifiers include interfaces, classes, data types, and components.

3.9

communication network profile

representation of the integration aspects of a communication network supported by a networked device

3.10

compliance

relation between two specifications, A and B, that holds when specification A makes requirements which are all fulfilled by specification B (when B complies with A)

[SOURCE: ISO/IEC 10746-1]

3.11

device

entity that performs control, actuating and/or sensing functions and interfaces to other such entities within an automation system

Note 1 to entry: Devices alone do not perform material processing, material transport or material storage functions. (See 3.15).

3.12

device profile

representation of the integration aspects of a device

3.13

element

atomic constituent of a model [UML]

3.14

entity

any concrete or abstract thing of interest

[SOURCE: ISO/IEC 10746-2]

3.15

equipment

entity that is stand alone, or interfaces to an automation system, and that performs material processing, material transport, or material storage functions

Note 1 to entry: Equipment can contain devices. (See 3.11).

Note 2 to entry: Equipment cannot have a direct connection to the communication network – only devices can be directly connected to the communication network.

3.16

equipment profile

representation of the integration aspects of an item of equipment

3.17

generalization

taxonomic relationship between a more general element and a more specific element [UML]

Note 1 to entry: 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.

3.18

human profile

representation of the integration aspects of a person

3.19

information

any kind of knowledge, that is exchangeable amongst users, about things, facts, concepts and so on, in a universe of discourse

[SOURCE: ISO/IEC 10746-2]

3.20

instance

entity that has unique identity, a set of operations that can be applied to it, and state that stores the effects of the operations [UML]

3.21

interface

named set of operations that characterize the behaviour of an element [UML]

3.22

material

matter used in manufacturing the product

3.23

material profile

representation of the integration properties of the material

3.24

message

specification of the conveyance of information from one instance to another, with the expectation that activity will ensue [UML]

3.25

name

term which, in a given naming context, refers to an entity

[SOURCE: ISO/IEC 10746-2]

3.26

object

entity with a well-defined boundary and identity that encapsulates state and behaviour [UML]

Note 1 to entry: State is represented by attributes and relationships, behaviour is represented by operations, methods, and state machines. An object is an instance of a class.

3.27

operation

service that can be requested from an object to effect behaviour [UML]

3.28

profile

set of one or more base specifications and/or sub-profiles, and, where applicable, the identification of chosen classes, conforming subsets, options and parameters of those base specifications, or sub-profiles necessary to accomplish a particular function, activity, or relationship

Note 1 to entry: Adapted from ISO/IEC TR 10000-1

3.29

relationship

semantic connection among model elements [UML]

3.30

resource

device, communication network, equipment, human or material used in a process

3.31

state

condition or situation during the life of an object during which it satisfies some condition, performs some activity, or waits for some event [UML]

3.32

system

something of interest as a whole or as comprised of parts

[SOURCE: ISO/IEC 10746-2]

Note 1 to entry: Therefore a system may be referred to as an entity. A component of a system may itself be a system, in which case it may be called a subsystem. (See ISO/IEC 10746-2).

3.33

<X> template

specification of the common features of a collection of <X>s in sufficient detail that an <X> can be instantiated using it

[SOURCE: ISO/IEC 10746-2]

Note 1 to entry: <X> can be anything that has a type

3.34

type (of an <X>)

predicate characterizing a collection of <X>s

[SOURCE: ISO/IEC 10746-2]

3.35

use case

<class> specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system [UML]

3.36

view

projection of a model, which is seen from a given perspective or vantage point and omits entities that are not relevant to this perspective [UML]