home

Requirements Based Testing

A cross-over to the testing discipline which discusses how testing is driven by use cases and other requirements work products.

Using a Requirements Composition Table to Assess Test Coverage

Article Sponsored By
Lets innovate! Try Jama Contour.

by Yuri Chernak
Testers in the field com­monly deal with incomplete and even missing software requirements. On such projects, they do not have sufficient vis­ibility into the application’s test cover­age. 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 com­pleteness and identify test coverage gaps. Once gaps are identified, testers can bet­ter 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.

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.

    Sponsored Announcements & Special Offers

Are Your Processes Making You See RED?
Learn how to save Time, Cost and Heartburn!
Register for our OnDemand Webinars ($150 per webinar):
* Essentials of Process Mapping
* Eliminating Non-Value Added Activities

These pre-recorded e-Learning modules are based on time-tested seminars that are sponsored by prestigious universities from coast to coast. For more information, call us at 800-510-2117. Orion Development Group is the premier strategic process management training and consulting firm in America. For more information

view counter

Iterative Requirement Management – Just Got Easier
Write effective functional specs, use cases or user stories. Elicit, manage and elaborate software requirements. Communicate iterative change. Discover how AppLife DNA can enable iterative requirements elicitation and allow your team to reap the benefits of a living requirements document. You will see the difference. Take a 30-day FREE TRIAL

view counter
© 2007 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group