Переклад Glossary all terms 3.1 / Glossary all terms 3.1: F :: Паляниця!

Glossary all terms 3.1 / Glossary all terms 3.1: F

Власник перекладу встановив такі правила доступу, що ви не можете переглядати чужі варіанти перекладів тут.
Оригінал англійською Переклад українською

factory acceptance testing

#1

fail

#2

failover testing
See Also: recoverability testing
Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained (e.g., function availability or response times).

#3

failure

#4

failure mode
Ref: IEEE 610
The physical or functional manifestation of a failure. For example, a system in failure mode may be
characterized by slow operation, incorrect outputs, or complete termination of execution.

#5

Failure Mode and Effect Analysis (FMEA)
See Also: Failure Mode, Effect and Criticality Analysis
Synonyms: Software Failure Mode and Effect Analysis
A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting
to prevent their occurrence.

#6

Failure Mode, Effects, and Criticality Analysis (FMECA)
See Also: Failure Mode and Effect Analysis
Synonyms: software failure mode
An extension of FMEA, as in addition to the basic FMEA, it includes a criticality analysis, which is used to chart
the probability of failure modes against the severity of their consequences. The result highlights

#7

failure modes
with relatively high probability and severity of consequences, allowing remedial effort to be directed where it will
produce the greatest value.

#8

failure rate

#9

false-negative result
Synonyms: false-pass result
A test result which fails to identify the presence of a defect that is actually present in the test object.

#10

false-positive result
Synonyms: false-fail result
A test result in which a defect is reported although no such defect actually exists in the test object.

#11

fault attack

#12

fault injection
See Also: fault tolerance
The process of intentionally adding defects to a system for the purpose of finding out whether the system can
detect, and possibly recover from, a defect. Fault injection is intended to mimic failures that might occur in the
field.

#13

fault seeding
Ref: After IEEE 610
Synonyms: bebugging , error seeding
The process of intentionally adding defects to those already in the component or system for the purpose of
monitoring the rate of detection and removal, and estimating the number of remaining defects. Fault seeding is
typically part of development (pre-release) testing and can be performed at any test level (component,
integration, or system).

#14

fault seeding tool
Synonyms: error seeding tool
A tool for seeding (i.e., intentionally inserting) faults in a component or system.

#15

fault tolerance
Ref: ISO 9126 See Also: reliability, robustness
The capability of the software product to maintain a specified level of performance in cases of software faults
(defects) or of infringement of its specified interface.

#16

Fault Tree Analysis (FTA)
Synonyms: Software Fault Tree Analysis
A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose.

#17

feasible path
A path for which a set of input values and preconditions exists which causes it to be executed.

#18

feature

#19

feature-driven development
See Also: Agile software development
An iterative and incremental software development process driven from a client-valued functionality (feature)
perspective. Feature-driven development is mostly used in Agile software development.

#20

finite state machine
Ref: IEEE 610
A computational model consisting of a finite number of states and transitions between those states, possibly with accompanying actions.

#21

firewall
A component or set of components that controls incoming and outgoing network traffic based on predetermined security rules.

#22

formal review

#23

frozen test basis
See Also: baseline
A test basis document that can only be amended by a formal change control process.

#24

Function Point Analysis (FPA)
Method aiming to measure the size of the functionality of an information system. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity, the estimation of the needed resources, and project control.

#25

functional integration
See Also: integration testing
An integration approach that combines the components or systems for the purpose of getting a basic functionality working early.

#26

functional requirement

#27

functional test design technique
See Also: black-box test design technique
Procedure to derive and/or select test cases based on an analysis of the specification of the functionality of a
component or system without reference to its internal structure.

#28

functional testing

#29

functionality

#30

functionality testing
The process of testing to determine the functionality of a software product.

#31

fuzz testing
Synonyms: fuzzing
A software testing technique used to discover security vulnerabilities by inputting massive amounts of random data, called fuzz, to the component or system.

#32

Хвилинку...