Requirements-Based Testing (RBT) is used to test any application running on any platform written in any language. RBT derives the necessary and sufficient set of test cases to cover 100% of the requirements. RBT is comprised of two techniques: Ambiguity Reviews and Cause-Effect Graphing.
An Ambiguity Review is used in the requirements phase of software development to identify ambiguities in requirements. The intent of an Ambiguity Review is to identify anything that is ambiguous, unclear and imprecise in the functional requirements. The elimination of these ambiguities improves the quality of the requirements, helps identify missing requirements, and improves the quality of the development and test effort. Half of the problem testing software is working with untestable requirements.
Cause-Effect Graphing is an advanced test case design technique that is performed once requirements have been reviewed for ambiguity, followed by a review for content. Requirements are reviewed for content by domain experts to insure that the requirements are correct and complete. The Cause-Effect Graphing technique derives the minimum number of test cases to cover 100% of the functional requirements, to improve the quality of test coverage, and to avoid the risk of releasing untested code into production.
A two-day RBT Proof of Concept can show you the entire RBT process using one of your organization’s requirement specifications. Please call to schedule a meeting.
Quality Management Planning provides a plan for assessing the quality of all assets developed by your project team using your software development life cycle – from the requirements documents to the delivered software.
A Quality Assessment provides an evaluation of an organization's quality processes and makes recommendations on:
- Integration of testing with the rest of your software development life cycle
- Test case design approaches, standards and procedures
- Test management and defect tracking
- Test organization and staffing
- Quality management