ISO/IEC 23004-1:2007 情報技術—マルチメディアミドルウェア—パート1：アーキテクチャ | ページ 6

4.1.1

API specification

M3W API specification, which defines a collection of software interfaces providing access to coherent streaming-related functionality

4.1.2

interface suite

collection of mutually related interfaces providing access to coherent functionality

4.1.3

logical component

coherent unit of functionality that interacts with its environment through explicit interfaces only

4.1.4

role

abstract class, i.e. a class without implementation defining behavior only

4.1.5

role instance

object playing a role, i.e. an object displaying the behavior defined by the role

4.1.6

attribute

instance variable associated with a role

Note 1 to entry: Attributes are used to associate state information with roles.

4.1.7

signature

definition of the syntactic structure of a specification item such as a type, interface or function in IDL

Note 1 to entry: For C functions, signature is equivalent to prototype.

4.1.8

specification item

entity defined in a specification

Note 1 to entry: Data type, role, attribute, interface and function are examples of specification items.

4.1.9

IDL

Interface Definition Language

4.1.10

qualifier

predefined keyword representing a property or constraint imposed on a specification item

4.1.11

constraint

restriction that applies to a specification item

4.1.12

execution constraint

constraint on multi-threaded behavior

4.1.13

model type

data type used for specification (modeling) purposes only

Note 1 to entry: Set, map and entity are examples of model types.

4.1.14

model constant

constant used for specification (modeling) purposes only

4.1.15

enum element type

enumerated type whose values can be used to construct sets (bit vectors) of at most 32 values by logical or-ing

4.1.16

enum set type

32-bit integer data type representing sets of enumerated values

4.1.17

set type

data type whose values are mathematical sets of values of a specific type

Note 1 to entry: Unlike enum sets, these sets may be infinite.

4.1.18

map type

data type whose values are tables mapping values of one type (the domain type) to values of another type (the range type)

Note 1 to entry: Maps are a kind of generalized array. Unlike arrays, the domain and range types may be arbitrary, and possibly infinite types.

4.1.19

entity type

class of objects that may have attributes associated with them

4.1.20

interface-role model

extended Unified Modeling Language class diagram showing the roles and interfaces associated with a logical component, and their mutual relations

4.1.21

logical component instance

incarnation of a logical component: a configuration of objects displaying the behavior defined by the logical component

4.1.22

provides interface

interface that is provided by a role or role instance

4.1.23

requires interface

interface that is used by a role or role instance

4.1.24

specialization

behavioral inheritance

definition, by a role, of behavior which implies the behavior defined by another role

Note 1 to entry: A role S specializes a role R if the behavior defined by S implies the behavior defined by R, i.e. if S has more specific behavior than R.

4.1.25

diversity

set of all parameters that can be set at instantiation time of a logical component and that will not change during the lifetime of the logical component

4.1.26

mandatory interface

provides interface of a role that should be implemented by each instance of the role

4.1.27

optional interface

provides interface of a role that need not be implemented by each instance of the role

4.1.28

configurable item

parameter that can be set at instantiation time of a logical component, usually represented by a role attribute

4.1.29

diversity attribute

role attribute that represents a configurable item

4.1.30

instantiation

process of creating an instance (an incarnation) of a role or logical component

4.1.31

initial state

state of a role instance or logical component instance immediately after its instantiation

4.1.32

observable behavior

behavior that can be observed at the external software and streaming interfaces of a logical component

4.1.33

function behavior

behavior of the functions in the provides interfaces of a role

4.1.34

streaming behavior

input-output behavior of the streams associated with a role

4.1.35

active behavior

autonomous behavior that is visible at the provides and requires interfaces of a role

4.1.36

instantiation behavior

behavior of a role at instantiation time of a logical component

4.1.37

independent attribute

attribute whose value may be defined or changed independently of other attributes and entities

4.1.38

dependent attribute

attribute whose value is a function of the values of other attributes or entities

4.1.39

invariant

assertion about a role or logical component that is always true from an external observer’s point of view

Note 1 to entry: In reality, the assertion may temporarily be violated.

4.1.40

callback interface

interface provided by a client of a logical component whose functions are called by the logical component

Note 1 to entry: A notification interface is an example of this, but there may be other call-back interfaces as well, e.g. associated with plug-ins.

4.1.41

callback-compliance

general constraint that the functions in a callback interface should not interfere with the behavior of the caller in an undesirable way, such as by blocking the caller or by delaying it too long

4.1.42

event notification

act of reporting the occurrence of events to ‘interested’ objects

4.1.43

event subscription

act of recording the types of event that should be notified to objects

4.1.44

cookie

special integer value that is used to identify an event subscription

Note 1 to entry: Clients pass cookies to a logical component when subscribing to events. Logical components pass cookies back to clients when notifying the occurrence of the events.

4.1.45

event-action table

table associating events that can occur to actions that will be performed in reaction to the events

Note 1 to entry: This is used to specify event-driven behavior.

4.1.46

non-standard event notification

event notification that is accompanied by other actions (such as state changes of the notifying logical component)

4.1.47

client role

role modeling the users of a logical component

4.1.48

actor role

role (usually a client role) whose active behavior consists of calling functions in interfaces without any a priori constraints on when these calls will occur

4.1.49

control interface

interface provided by a logical component that allows the logical component’s functionality to be controlled by a client

4.1.50

notification interface

interface provided by a client of a logical component that is used by the logical component to report the occurrence of events to the client

4.1.51

specialized interface

interface of a role R that is inherited from another role and is further constrained by R

4.1.52

precondition

assertion that should be true immediately before a function is called

4.1.53

action clause

part of an extended precondition and postcondition specification defining the abstract action performed by a function

Note 1 to entry: The abstract action usually defines which variables are modified and/or which out-calls are made by the function.

4.1.54

out-call

out-going function call of an object on an interface of another object

4.1.55

postcondition

assertion that will be true immediately after a function has been called

4.1.56

asynchronous function

function with a delayed effect

Note 1 to entry: The effect of the function will occur some time after returning from the function call.