F

A B C D E F G

Failure: Non performance or deviation of the software from its expected delivery or service.

Fault: A manifestation of an error in software. Also known as a Bug.

Feasible Path: A path for which there exists a set of input values and execution conditions which causes it to be executed.

Feature Testing: A method of testing which concentrates on testing one feature at a time.

Firing a Rule: A rule fires when the "if" part (premise) is proven to be true. If the rule incorporates an "else" component, the rule also fires when the "if" part is proven to be false.

Fit For Purpose Testing: Validation carried out to demonstrate that the delivered system can be used to carry out the tasks for which it was designed and acquired.

Forward Chaining: Applying a set of previously determined facts to the rules in a Knowledge Base to see if any of them will fire.

Full Release: All components of the release unit that are built, tested, distributed and implemented together. See also Delta Release.

Functional Specification: The document that describes in detail the characteristics of the product with regard to its intended capability.

Functional Decomposition: A technique used during planning, analysis and design; creates a functional hierarchy for the software. Functional Decomposition broadly relates to the process of resolving a functional relationship into its constituent parts in such a way that the original function can be reconstructed (i.e., recomposed) from those parts by function composition. In general, this process of gaining insight into the identity of the constituent components (which may reflect individual physical processes of interest, for example), or for the purpose of obtaining a compressed representation of the global function, a task which is feasible only when the constituent processed possess a certail level of modularity (i.e. independence or non-interaction).

Functional Requirements: Defie the internal workings of the software: that is, the calculations, technical details, data manipulation and processing and other specific functionality that show how the use cases are to be satisfied. They are supported by non-functional requirements, which impose constraints on the design or implementation (such as performance requirements, security, quality standards, or design constraints).

Functional Specification: A document that describes in detail the characteristics of the product with regards to its intended features.

Functional Testing: See also Black Box Testing.

• Testing the features and operational behavior of a product to ensure they correspond to its specifications.
• Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.