Many organizations also have discovered that capture/playback tools require a significant investment in building and maintaining test scripts. They also discover that the scripts cannot keep up with rapidly changing specifications.
This presentation will address how a Requirements-Based Testing (RBT) process provides major productivity gains. The RBT process stabilizes the completeness of the specifications early in the development process. RBT is made up of two components that support Verification and Validation. RBT uses a verification technique called Ambiguity Reviews to drive out ambiguities from requirements. It also uses a test case design technique called Cause-Effect Graphing that derives an optimized set of test cases that covers 100% of the problem description. The results are fewer tests with greater functional coverage, shortened time to delivery, reduced costs of development, and significantly improved quality.
This is an open event, however space is limited so register now
Register now to discover:
- The 12 point Requirements-Based Testing (RBT) process
- How the RBT process stabilizes the completeness of the specifications early in the development process
- The two components of RBT, Verification and Validation including a verification technique called Ambiguity Reviews to drive out ambiguities from requirements
- Tools to translate Cause-Effect Graphs into logical test cases and evaluate previously existing test libraries to cover the problem description
- Discussion with Expert Panel:
- Gary Mogyorodi, President of CSTB
- Sammy Kolluru, Executive CSTB Board Member
- TFS Expert
Hosted by SELA Canada and Microsoft Canada
Where:
Microsoft Office
1950 Meadowvale Blvd., Mississauga,
ON, L5N 8L9
Thursday, Mar 29, 2012,
from 6:00PM to 8:30PM
1950 Meadowvale Blvd., Mississauga,
ON, L5N 8L9
Thursday, Mar 29, 2012,
from 6:00PM to 8:30PM