Non-Functional
Requirement:
Non-Functional Requirement is a requirement
that describes how the component or system will do what it is supposed to do.
Non-Functional
Testing:
Non-Functional Testing is a testing conducted
to evaluate the compliance of a component or system with non-functional
requirements.
Operational
Acceptance Testing:
Operational testing in the acceptance test
phase, typically performed in a (simulated) operational environment by
operations and/or systems administration staff focusing on operational aspects,
e.g., recover-ability, resource-behavior and technical compliance.
Operational
Environment:
Operational Environment is the combination
of hardware and software products installed at users' or customers' sites where
the component or system under test will be used. The software may include
operating systems, database management systems, and other applications.
Output:
Output is the data transmitted by a
component or system to an external destination.
Pass:
A test is deemed to pass if its actual
result matches its expected result.
Path:
Path is a sequence of events of a component
or system from an entry point to an exit point.
Peer
Review:
Peer Review is review form where review of
work products performed by others qualified to do the same work.
Performance
Efficiency:
Performance Efficiency is the extend to
which a component or system uses time, resources and capacity when
accomplishing its designated functions.
Performance
Indicator:
Performance Indicator is a high-level
metric of effectiveness and/or efficiency used to guide and control progressive
development, e.g., lead-time slip for software development.
Performance
Testing:
Performance Testing is the testing which
determines the performance of a software product.
Performance
Testing Tool:
Performance Testing Tool is a test tool
that generates load for a designated test item and that measures and records
its performance during test execution.
Perspective-Based
Reading
Perspective-Based Reading
Planning
Poker:
Planning Poker is an estimation technique
where, mostly used to estimate effort or relative size of user stories in Agile
software development. It is a variation of the Wideband Delphi method using a
deck of cards with values representing the units in which the team estimates.
Portability:
Portability is the ease with which the
software product can be transferred from one hardware or software environment
to another.
Portability
Testing:
Portability Testing is the testing to
determine the portability of a software product.
Post-condition:
Post-Condition is the expected state of a
test item and its environment at the end of test case execution.
Pre-condition:
Pre-Condition is the required state of a
test item and its environment prior to test case execution.
Priority:
Priority is the level of (business)
importance assigned to an item, e.g., defect.
Probe
Effect:
Probe Effect is the effect on the component
or system by the measurement instrument when the component or system is being
measured, e.g., by a performance testing tool or monitor. For example:
performance may be slightly worse when performance testing tools are being
used.
Problem:
Problem is an unknown underlying cause of
one or more incidents.
Process:
Process is a set of interrelated
activities, which transform inputs into outputs.
Process
Improvement:
Process Improvement is a program of
activities designed to improve the performance and maturity of the
organization's processes, and the result of such a program.
Product
Risk:
Product Risk is a risk impacting the
quality of a product.
Project:
Project is a unique set of coordinated and
controlled activities with start and finish dates undertaken to achieve an
objective conforming to specific requirements, including the constraints of
time, cost and resources.
Project
Risk:
References:
ISTQB
Wikipedia
