Software Testing Glossary - Software Testing as a Service - page 198

Simulator: A device, computer program, or system used during testing, which
behaves or operates like a given system when provided with a set of controlled
inputs. [After IEEE 610] See also emulator .
Site acceptance testing: Acceptance testing by users/customers at their site, to deter-
mine whether or not a component or system satisfies the user/customer needs and
fits within the business processes, normally including hardware as well as software.
Smoke test: A subset of all defined/planned test cases that cover the main func-
tionality of a component or system, to ascertain that the most crucial functions of
a program work, but not bothering with finer details. A daily build and smoke test
is among industry best practices. See also intake test .
Software: Computer programs, procedures, and possibly associated documenta-
tion and data pertaining to the operation of a computer system. [IEEE 610]
Software feature: See feature .
Software quality: The totality of functionality and features of a software product
that bear on its ability to satisfy stated or implied needs. [ISO 9126]
Software quality characteristic: See quality attribute .
Software Requirement Specification (SRS): For developing any software appli-
cation for a client, customer requirements are captured and are stored in a document
which is commonly known as the SRS document. SRS is primarily divided into
2 parts: functional requirements and non-functional requirements. Functional
requirements pertain to requirements which enable the users of the built software
to complete their transactions, view reports, and perform other routine tasks. Non-
functional requirements are related to performance of the application under dif-
ferent loads on the server on which the application is installed, security, usability,
and compatibility. Non-functional requirements are important because they allow
the users of the application to complete their tasks using the application without the
hindrance of issues related to security, compatibility, and performance.
Software test incident: See incident .
Software test incident report: See incident report .
Software Usability Measurement Inventory (SUMI): A questionnaire-based
usability test technique to evaluate the usability (e.g., user satisfaction) of a compo-
nent or system.
Source statement: See statement .
Specification: A document that specifies, ideally in a complete, precise, and veri-
fiable manner, the requirements, design, behavior, or other characteristics of a
component or system, and, often, the procedures for determining whether these
provisions have been satisfied. [IEEE 610]
Specification-based testing: See black box testing .
Specification-based test design technique: See black box test design technique .
Specified input: An input for which the specification predicts a result.
Stability: The capability of the software product to avoid unexpected effects from
modifications in the software. [ISO 9126] See also maintainability .
Standard software: See off-the-shelf software .