Global Sources
EE Times-India
EE Times-India > EDA/IP

Find defects in software with RBT

Posted: 21 May 2009     Print Version  Bookmark and Share

Keywords:software builds  RBT  requirements-based testing 

The primary job of QA and testing professionals is to find defects in software builds. Fortunately, however, most of us have moved beyond exposing and tracking bugs to the more critical role of ensuring that the software our companies deliver meets customer expectations before it is released. To do this, many organisations have recently embraced requirements-based testing (RBT).

Teams can be more effective using RBT because it enables them to target the root causes of quality issues by being tightly coupled with application requirements and integrated through various activities throughout the software lifecycle.

The challenge is to ensure these processes with existing QA and testing best practices. To that end, these suggestions to improve your RBT practices are offered.
Suggestion 1: Test early and frequently, so testing becomes a parallel activity to the development process, a constant pursuit that spans all roles and makes all stakeholders aware of quality objectives.
Suggestion 2: Test with your head, not your gut, to inject repeatability and method in to the test planning process, in order to make test coverage more predictable.
Suggestion 3: Test with measurement and improvement in mind to quantify the status of deliverables and activities, so management can oversee quality initiatives across the IT application portfolio.

View the PDF document for more information.

Comment on "Find defects in software with RBT"
*  You can enter [0] more charecters.
*Verify code:


Visit Asia Webinars to learn about the latest in technology and get practical design tips.


Go to top             Connect on Facebook      Follow us on Twitter      Follow us on Orkut

Back to Top