Requirements Based Testing
Using a Requirements Composition Table to Assess Test Coverage
by Yuri Chernak
Testers in the field commonly deal with incomplete and even missing software requirements. On such projects, they do not have sufficient visibility into the application’s test coverage. This article provides a solution that I have found to be effective for this problem on many critical projects. The solution, a technique called requirements composition table (RCT), allows testers to assess the regression test suite completeness and identify test coverage gaps. Once gaps are identified, testers can better decide how to evolve the regression test suite to improve the application’s test coverage.
This article is a re-print from the March, 2008 edition of Better Software magazine.
The Requirements Networking Group at Three Years: A Retrospective
by Rob Beckmann
This month marks the three year anniversary of the Requirements Networking Group. During that time the site has grown from zero members to well over 12,000 members from all over the world. The site has become the prime destination for those who wish to hone their requirements analysis skills. This success has only occurred because of the great content contributed by the RQNG members.
Rob Beckmann, the editor of RQNG, looks back over that period and highlights the articles posted on RQNG along major themes that may give the reader a different perspective on some of the site content.
- 4 comments
- 685 reads
Steps for Business Analyst To Gather Security Requirements from Misuse Cases by Manish Kumar
In this post, I will talk about misuse cases and steps to identify security requirements. Ivar Jacobson while working on large telecommunication systems introduced use cases. According to him use cases describe system's desired behavior in the form of a story ('Scenario')from the point view of a user or interfacing system('Actor') and supported by subsidiary scenarios in the form of alternatives and exceptions[Jacabson 1992]. On the other hand misuse cases are the inverse of use cases. The concept was coined in 1990s by Guttorm Sindre of the Norwegian University of Science and Technology, and Andreas L. Opdahl of the University of Bergen, Norway.
- manish9.k's blog
- Login or register to post comments
- Read more
- 263 reads
