GB/T 11457-2006Information technology Software engineering terminology (English PDF)

2.6 Abend

Abbreviation for abnormal end. A process is terminated before it is completed. See also. abort (2.8) and exception (2.575).

2.7 Abnormal end

A process is terminated before it is completed. See also. abort (2.8) and exception (2.575).

2.8 Abort

A process is forced to terminate before it is completed. See also. abend (2.6) and exception (2.575).

2.9 Absolute address

An address that is permanently assigned to a device or storage location and that identifies the device or location without the need for translation or calculation.

See also. absolute assembler (2.10), absolute code (2.11), absolute instruction (2.12) and absolute loader (2.13).

Contrast with. relative address (2.1331), relocatable address (2.1342) and symbolic address (2.1636).

2.10 Absolute assembler

An assembler that produces absolute code. Contrast with. relocating assembler (2.1346).

2.11 Absolute code

A code in which all addresses are absolute addresses. Contrast with. relocating code (2.1343).

2.12 Absolute instruction

A computer instruction in which all addresses are absolute addresses.

See also. direct instruction (2.483), effective instruction (2.532), immediate instruction (2.722) and indirect instruction (2.745).

2.13 Absolute loader

A loader that reads absolute machine code into main memory, beginning at the initial address assigned to the code by the assembler or compiler, and performs no address adjustments on the code. Contrast with. relocating loader (2.1347).

2.14 Absolute machine code

A machine language code that must be loaded into a fixed storage location and cannot be relocated each time it is used.

2.92 Assessment instrument

A tool or set of tools that is used throughout an assessment to assist the assessor in evaluating the performance or capability of processes and in handling assessment data and recording the assessment results.

2.93 Assessment output

All of the tangible results from an assessment (See. assessment record (2.96)).

2.94 Assessment participant

An individual who has responsibilities within the scope of the assessment.

2.95 Assessment purpose

A statement, provided as part of the assessment input, which defines the reason for performing the assessment.

2.96 Assessment record

An orderly, documented collection of that information which is pertinent to the assessment and adds to the understanding and verification of the process profiles generated by the assessment.

2.97 Assessment scope

A definition of the boundaries of the assessment, provided as part of the assessment input, encompassing the organizational limits of the assessment, the processes to be included, and the context within which the processes operate (See. process context (2.1194)).

2.98 Assessment sponsor

The individual, internal or external to the organization being assessed, who requires the assessment to be performed, and provides financial or other resources to carry it out.

2.99 Assignment statement

A computer program statement that is used to express a series of operations, or to assign an operand to a specified variable, or a symbol, or both a variable and a symbol; for example, Y = X + 5. See also. clear (2.213), initialize (2.756) and reset (2.1372). Contrast with. control statement (2.343) and declaration (2.416).

2.100 Association

To specify semantic association between multiple categories connected between instances.

2.101 Association class

A model element that combines the dual nature of association and class. An association class can be thought of as having class nature or as a class with associative nature.

2.102 Association end

For an association, the end point that connects it to classifier.

2.103 Atomic type

A data type, each of whose members consists of a single, non-decomposable data item. Contrast with. composite type (2.268).

2.104 Attribute

A characteristic of an item; for example, the item's color, size, or type. See also. quality attribute (2.1295).

2.105 Audit

2.106 Authoring language

A high-level programming language used to develop courseware for computer-assisted instruction. See. authoring system (2.107).

2.107 Authoring system

A programming system that incorporates an authoring language.

2.108 Automated design tool

A software tool that assists in the synthesis, analysis, simulation, or documentation of software design. Examples of automated design tool are. simulator, analysis tool, design representation processor, and file generator.

2.109 Automated test case generator

See also. automated test generator (2.111).

2.110 Automated test data generator

See also. automated test generator (2.111).

2.111 Automated test generator

A software tool which uses computer programs and guidelines as input to generate test input data that meets the requirements of these guidelines, and sometimes determines the expected results.

2.112 Automated verification system

2.114 Auxiliary class

A derivation of a class that is to achieve a two-level logic or control flow as a typical way so as to support another, more central or more basic class. The use of auxiliary class with focus class is representative and is particularly useful during the design process for specifying secondary business logic or control flow for each component. See also. focus class (2.639).

2.115 Availability

2.116 Availability model

A model used to predict, estimate, and determine availability.

2.117 Back-to-back testing

Testing in which two or more variants of a program are executed with the same inputs, the outputs are compared, and errors are analyzed in case of discrepancies. See also. mutation testing (2.1001).

2.118 Background

In job scheduling, the computing environment in which low-priority processes or those not requiring user interaction are executed. See also. background processing (2.119). Contrast with. foreground (2.641).

2.119 Background processing

The execution of a low-priority process while higher priority processes are not using computer resources, or the execution of processes that do not require user interaction. Contrast with. foreground processing (2.642).

2.120 Backup

a) A system, component, file, procedure, or person available to replace or help restore a primary item in the event of a failure or externally caused disaster;

b) To create or designate a system, component, file, procedure, or person as in a);

c) To prepare for recovery of data files or software, restart processing, and use of backup computer equipment in the event of a system failure or disaster.

2.121 Backup programmer

The assistant leader of a chief programmer team; responsibilities include contributing significant portions of the software being developed by the team, aiding the chief programmer in reviewing the work of other team members, substituting for the chief programmer when necessary, and having an overall technical understanding of the software being developed. See also. chief programmer (2.205).

2.122 Backward execution

See. reversible execution (2.1391).

2.123 Backward recovery

a) The reconstruct ion of a file to a given state by reversing all changes made to the file since i t was in that state;

b) A type of recovery in which a system, program, database, or other system resource is restored to a previous state in which it can perform required functions. Contrast with. forward recovery (2.650).

2.124 Base address

An address used as a reference point to which a relative address is added to determine the address of the storage location to be accessed.

See also. indexed address (2.740), relative address (2.1331) and self-relative address (2.1429).

2.125 Baseline

a) A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures;

b) A document or a set of such documents formally designated and fixed at a specific time during the life cycle of a configuration item. Baselines, plus approved changes from those baselines, constitute the current configuration identification.

See also. allocated baseline (2.57), developmental configuration (2.470), functional baseline (2.659) and product baseline (2.1213).

c) Any agreement or result designated and fixed at a given time, from which changes require justification and approval. For configuration management, there are three baselines. Functional baseline. initially passed feature configuration; Allocated baseline. initially passed allocation configuration; Product baseline. initially passed or conditionally passed product configuration.

2.126 Baseline configuration management

Establishment of a baseline for formal review and consent and as a basis for subsequent development work. Some software work products, such as software design and code, have established baselines at predetermined points and impose strict change control procedures on them. See also. base management (2.127).

2.127 Baseline management

In configuration management, the application of technical and administrative direction to designate the documents and changes to those documents that formally identify and establish baselines at specific times during the life cycle of a configuration item.

2.128 Batch

Pertaining to a system or mode of operation in which inputs are collected and processed all at one time, rather than being processed as they arrive, and a job, once started, proceeds to completion without additional input or user interaction.

Contrast with. conversational (2.348), interactive (2.792), on-line (2.1045) and real time (2.1313).

2.129 Bathtub curve

A graph of the number of failures in a system or component as a function of time. The name is derived from the usual shape of the graph. a period of decreasing failures (the early-failure period), followed by a relatively steady period (the constant failure period), followed by a period of increasing failures (the wear-out-failure period).

2.130 Begin-end block

A sequence of design or program statements enclosed by begin and end delimiters. It is characterized by a single inlet and a single outlet.

2.131 Behavior

An observable effect on an operation or event (including the result of the operation or event).

2.132 Behavioral feature

A dynamic feature of a model element; for example, an operation or method.

2.133 Behavioral model aspect

A model appearance that focuses on the behavior of each instance in the system (including method, collaboration, and state).

2.134 Benchmark

a) A standard against which measurements or comparisons can be made.

b) A procedure, problem, or test that can be used to compare systems or components to each other or to a standard as in a).

c) A recovery file.

2.135 Bidder

An individual, partnership, company or association that has submitted a proposal and been accepted as a candidate of one or more product design, development and/or manufacturing contract.

2.136 Big-bang testing

A type of integration testing in which software elements, hardware elements, or both are combined all at once into an overall system, rather than in stages.

2.137 Binary association

An association between two classes. A special case of N-ary associations.

2.138 Binary digit [bit]

2.139 Bind

To assign a value to an identifier. For example, to assign a value to a parameter or to assign an absolute address to a symbolic address in a computer program. See also. dynamic binding (2.515) and static binding (2.1579).

2.140 Binding

To assign a value or a specified object (referent) to an identifier. For example, to assign a value to a parameter or assign an absolute address, virtual address, or device identifier to a symbolic address or label in a computer program. See also. dynamic binding (2.515) and static binding (2.1579). […]