ISO/IEC/IEEE 29119-4:2015 ソフトウェアおよびシステムエンジニアリング—ソフトウェアテスト—パート4：テスト手法 | ページ 6

4.1

Backus-Naur Form

formal meta-language used for defining the syntax of a language in a textual format

4.2

base choice

see base value

4.3

base value

input parameter value used in ‘base choice testing’ that is normally selected based on being a representative or typical value for the parameter. Also called base choice

4.4

c-use

see computation data use

4.5

computation data use

use of the value of a variable in any type of statement

4.6

condition

Boolean expression containing no Boolean operators

4.7

control flow

sequence in which operations are performed during the execution of a test item

4.8

control flow sub-path

sequence of executable statements within a test item

4.9

data definition

statement where a variable is assigned a value. Also called variable definition

4.10

data definition c-use pair

data definition and subsequent computation data use, where the data use uses the value defined in the data definition

4.11

data definition p-use pair

data definition and subsequent predicate data use, where the data use uses the value defined in the data definition

4.12

data definition-use pair

data definition and subsequent data use, where the data use uses the value defined in the data definition

4.13

data use

executable statement where the value of a variable is accessed

4.14

decision outcome

result of a decision (which therefore determines the control flow alternative taken)

4.15

decision rule

combination of conditions (also known as causes) and actions (also known as effects) that produce a specific outcome in decision table testing and cause-effect graphing

4.16

definition-use pair

data definition and subsequent predicate or computational data use, where the data use uses the value defined in the data definition

4.17

definition-use path

control flow sub-path from a variable definition to a predicate-use (p-use) or computational-use (c-use) of that variable

4.18

entry point

point in a test item at which execution of the test item can begin

Note 1 to entry: An entry point is an executable statement within a test item that may be selected by an external process as the starting point for one or more paths through the test item. It is most commonly the first executable statement within the test item.

4.19

executable statement

statement which, when compiled, is translated into object code, which will be executed procedurally when the test item is running and may perform an action on program data

4.20

exit point

last executable statement within a test item

Note 1 to entry: An exit point is a terminal point of a path through a test item, being an executable statement within the test item which either terminates the test item, or returns control to an external process. This is most commonly the last executable statement within the test item.

4.21

p-use

see predicate data use

4.22

P-V pair

combination of a test item parameter with a value assigned to that parameter, used as a test condition and coverage item in combinatorial test design techniques

4.23

path

sequence of executable statements of a test item

4.24

predicate

logical expression which evaluates to TRUE or FALSE, normally to direct the execution path in code

4.25

predicate data use

data use associated with the decision outcome of the predicate portion of a decision statement

4.26

sub-path

path that is part of a larger path

4.27

test model

representation of a test item that is used during the test case design process

4.28

variable definition

see data definition