ISO 13209-2:2012 道路車両—オープンテストシーケンス交換フォーマット（OTX）—パート2：コアデータモデルの仕様と要件 | ページ 6

3.1.1

attribute

<UML> a property of a UML class

3.1.2

attribute

<XSD/XML> named property of an XSD complex type or an XML element

3.1.3

after market

part of the automotive industry concerned with manufacturing, remanufacturing, distribution, retailing, and installation of all vehicle parts, chemicals, tools, equipment and accessories for light and heavy vehicles, after the sale of the automobile by the original equipment manufacturer (OEM) to the consumer

3.1.4

after sales

after sales department

department of an automotive OEM that is concerned with the distribution, retailing, servicing, repair and installation of vehicles of that OEM

3.1.5

constant

identifier of a non-writable memory location

3.1.6

context

environmental circumstances which influence test sequence execution

Note 1 to entry: OTX test sequences can be configured to behave differently according to different context situations. Contextual information depends on factors such as the particular vehicle that is currently attached to the test application (e.g. the current vehicle's model type, the engine type, etc.), on the test application settings (e.g. a setting controlling whether the test sequence shall run in debug mode) or on other factors such as whether the test sequence is running in a manufacturing or a service workshop environment, etc.

3.1.7

engineering

engineering department

department of an automotive OEM which is concerned with the design, development, integration and testing of vehicles of that OEM

3.1.8

expression

syntactical construct which describes a specific computation with a set of arguments and a single return value

3.1.9

identification routine

method or software by which a diagnostic application identifies contextual information

3.1.10

manufacturing

manufacturing department

department of an automotive OEM which is concerned with the production and end-of-line testing of vehicles of that OEM

3.1.11

original equipment manufacturer

OEM

automotive company that engineers, manufactures, sells and services vehicles

3.1.12

OTX Core

most generic and stand-alone part of the overall OTX data model which describes the basic structure underlying every OTX document and comprises detailed data model definitions of all required control structures (loops, branches, …) by which test sequence logic is described, but also definitions of the outer, enveloping document structure in which test sequence logic is embedded

3.1.13

OTX Extension

OTX Standard Interface Definition

otxIFD

set of OTX data type-, action-, term- and signature-definitions that are tailored for a specific area of application and that are defined aside of the OTX Core

Note 1 to entry: OTX Extensions model the data types, actions, terms and signatures needed for communication through diverse interfaces. By using these interfaces, calls can be performed to external systems whose internal behaviour does not have to be known to the (client) OTX test sequence/runtime. The system-side interface (server-side) can be proprietary because the adapter design pattern is applied.

3.1.14

procedure signature

description of the interface of an OTX procedure

3.1.15

reference

value which refers to data in memory

3.1.16

session

instance of test sequence execution

3.1.17

term

value described by and computed from an expression

3.1.18

test sequence

test procedure defining a full test

Note 1 to entry: A test sequence is a procedure also, but not all procedures are test sequences. In an OTX document, the procedure representing a test sequence shall be named"main". By using procedures, a test sequence may be split into several procedure modules. An adequately assembled set of frequently needed procedures may serve as a library which provides procedures that can be called from any other (client) procedure or test sequence.

3.1.19

test procedure

procedure

stand-alone, parameterisable flow of OTX actions that can be called from other OTX procedures

3.1.20

validity

Boolean context variable, global Boolean constant or a named Boolean expression used for activating/deactivating parts of the OTX test sequences according to the current context situation

Note 1 to entry: Parts of OTX test sequences which are marked with a validity name shall be executed only if the associated Boolean expression is true according to the current context situation.

3.1.21

variable

identifier of a writable memory location

Note 1 to entry: The term"variable" is used as a collective term for document scope variables, local variables, non-con­stant parameters and also items in non-constant lists or maps or other compound data structures. In OTX, these can be addressed by giving the identifier of the variable or parameter, optionally accompanied by a path into compound data structures which allows the inner parts of variables or parameters to be addressed.