Abstract

Scenario Based Testing (SBT) is a paradigm shift in the system test arena. It broadens the purpose of system level acceptance testing. Requirements Based Testing (RBT), as an exclusive acceptance vehicle, is flawed because it verifies only the static features of a system. In contrast, SBT focuses on verifying the system dynamics. SBT, however, does not obviate requirements or the need to verify them. System characterizations need to be expressed in requirements, because we need to build the constituent components. But, requirements cannot express system behaviors very well. Even allowing for perfect requirements, leaving out verification of the system behavior results in an incomplete test program, at best. The combination of RBT and SBT thus provides a more robust acceptance vehicle assuring the customer that the system will satisfy his needs.

-- JasonKealey - 12 Oct 2005

Discussion

  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title A Methodology for the Planning of a Scenario Based Test Program
Authors E. Radzius
Type Other
Conference/Journal Title
Volume/Number
Editors
Publisher
Month August
Year 2001
Pages 7
Keywords scenario based testing, requirements based testing
Topic revision: r2 - 12 Oct 2005, JasonKealey
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback