Glossary of Terms beginning Alphabet-F
A test is considered as fail if its actual result does not match its expected result.
Failure means actual deviation of the component or system from its expected delivery, service or result.
Failure Mode refers to 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.
Failure Mode and Effect Analysis (FMEA):
Failure Mode and Effect Analysis is a systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence.
Failure Rate is the ratio of the number of failures of a given category to a given unit of measure, e.g. failures per unit of time, failures per number of transactions, failures per number of computer runs.
Fault Tolerance refers to 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.
Fault Tree Analysis:
Fault Tree Analysis is a method used to analyze the causes of faults or defects.
Feasible Path is a path for which a set of input values and preconditions exists which causes it to be executed.
Feature is an attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints).
Feature Freeze or Code Freeze:
Feature Freeze represents a point in time in the software development process after which the rules for making changes to the source code or related resources become more strict. A freeze helps move the project forward towards a release or the end of an iteration. The stricter rules may include only allowing changes, which fix bugs, or allowing changes only after thorough review by other members of the development team. It is a particular kind of freeze of features, when all work on adding new features is suspended, shifting the effort towards fixing bugs and improving the user experience.
Firewall leakage Testing:
Firewall leakage Testing is a type of testing in which someone will enter as one level of user and try to access the other level unauthorized pages in order to check whether the firewall is working properly or not.
Flexibility is a quality attribute pointing towards an effort required to modify an operational program.
Pictorial representation of data flow and computer logic. It is easier to understand and assess the structure and logic of an application system by developing a flow chart rather than attempting to understand narrative descriptions or verbal explanations.
Force Field Analysis:
Force Field Analysis refers to a group technique used to identify both driving and restraining forces, which influence a current situation.
Formal Analysis refers to technique which uses rigorous mathematical techniques to analyze the algorithms of a solution for numerical properties, efficiency and correctness.
Frozen Test Basis:
Frozen Test Basis refers to a test basis document that can only be amended by a formal change control process.
Function coverage is a metric, which reports whether we invoked each function or procedure. It is useful during preliminary testing to assure at least some coverage in all areas of the software. Broad, shallow testing finds gross deficiencies in a test suite quickly.
Function Point Analysis:
A function point is a unit of measurement to express the amount of business functionality an information system provides to a user. Function points are an ISO recognized software metric to size an information system based on the functionality that is perceived by the user of the information system, independent of the technology used to implement the information system. The method of measuring the size of an information system and expressing it in a number of function points is called function point analysis (FPA). FPA can be used to find the testing effort required in the information system; The formula is Number of Test Cases = (Function Points)
Functional Decomposition is a technique used during planning, analysis and design; creates a functional hierarchy for the software.
Functional Integration is an integration approach which combines the components or systems for the purpose of getting a basic functionality working early.
Functional Requirement refers to a requirement that specifies a function that a component or system must perform.
Functional Specification is a document that describes in detail the characteristics of the product with regard to its intended features.
Functional Test Design Technique:
Functional Test Design Technique is a set of documented procedure to derive and select test cases based on an analysis of the specification of the functionality of a component or system without reference to its internal structure.
Functional Testing refers to testing which ensures all functional requirements are met without any consideration to the final program. structure. It verifies that the application supplies what the users need. It emulates user actions to ensure that execution paths operate correctly and the appropriate responses are returned for the given requests. It is a black-box testing aimed to validate functional requirements of an application. The testers usually do this.
Functionality is the capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions.
Functionality Testing is the process of testing to determine the functionality of a software product.
Explanation to All Alphabets in the Glossary of Terms