RM Articles
RM Articles provides original articles from industry thought leaders, analysts and software providers on a wider variety of requirements management and requirements reuse topics
 Suscribe to the RSS Feed
|
 |
|
|
Written by Robin F. Goldsmith, JD
|
|
Robin F. Goldsmith, JD
17 Feb 2009 | SearchSoftwareQuality.com
For something that is essential, fairly fundamental and seemingly straightforward, requirements-based software testing sure does generate a lot of discussion. Rather than representing opposite extremes of the same continuum, pro and con camps come at the topic from disparate perspectives. Advocates of requirements-based testing tend to be analytical, whereas opponents tend to couch their objections in more emotional terms. Each approach has its own strengths and issues. We'll start by ...
|
|
|
Written by Richard
|
|
Many people think you don't "do" requirements on an agile project. Hogwash. Indeed, agile projects use requirements-but just enough requirements at just the right time.
In this article by author Ellen Gottesdiener, Principal Consultant at EGB Consulting, Inc., she argues that requirements do matter, and that Agile projects shouldn't abandon requirements management. Taking a light weight approach to requirements management on large agile projects saves time and money and accelerates the team's ability to deliver the right product, sooner.
Read the article
|
|
Written by Doug Akers
|
 Author: Doug Akers
The main benefit of today’s Agile development methodologies such as Scrum or XP is the promise of delivering more in a shorter period of time and the value derived from having the flexibility to adjust your course mid-way through a development effort. But does this type of approach allow for requirements management? Is RM necessary given the shorter development windows – sprints, milestones, stories, whatever you call them?
Well -- does the need to deliver what the requirement originally requested go away? Does the desire to control change to the requirement go away? Of course not, and neither does the need for requirements management under these newer methodologies. The nature of RM will change, certainly, but the fundamental principles will not.
|
|
Written by Bob Aiello
|
 Author: Bob Aiello
There has never been a more exciting and rewarding time to
be in the industry of systems application development. There also has never
been a time when the risks were greater and the margin for error more critical
- you must get it right or your failure will make headlines the next day. From process
workflow, application requirements, source code management, through setting up
a seamless deployment strategy - MKS leaves a lot of its competitors stunned by
its full set of features and versatile comprehensive solution. If you are a
development manager and you want to get your projects under control than you
should take a serious look at MKS Integrity 2007. Read on if you want to learn
more about this process and workflow platform that can set the stage for your
large scale development effort to be a success in terms of meeting your
deliverables on time and within budget.
|
|
Author: Moty Aharonovitz
Publisher: CIO Magazine
Our primary job, as 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 company is delivering meets
customer expectations before it is released. To do this, many organizations
have recently embraced requirements-based testing (RBT)…
|
|
Author: Gary E. Mogyorodi
Publisher: The Journal of
Software Testing Professionals December 2002 Issue, International Institute for
Software Testing
An overview of the Requirements-Based Testing (RBT) process. RBT is a rigorous
process for improving the quality of requirements and for deriving the minimum
number of test cases to cover 100% of those requirements. RBT is comprised of
two techniques: Ambiguity Reviews and Cause-Effect Graphing. This article
addresses the first RBT technique - the Ambiguity Review.
|
Author: David W. Johnson
Publisher: Dev Bistro (www.devbistro.com)
Function (Integration) test is usually the first test phase that a test
organization is responsible for during any given release. Requirements based
Function Test is one approach to Function (Integration) test - it is a powerful
and effective testing approach, which will significantly reduce the number of
undetected defects (faults) being released into production. The premise is that
a well-formulated set of functional requirements give the Test Designers
|
Author: James Bach
Publisher: IEEE Computer Society
A look at the risks with testing against
requirements, how to state requirements in testable terms, and the need for
traceability between test cases and requirements.
|
|
Written by Adam Kolawa
|
|
Author: Rick Craig
Publisher: Stickyminds.com
Many of the testers reading this article use white box testing
techniques based upon the structure of the code. Others conduct primarily black
box testing based upon some external specification such as the requirements.
And of course, some of them do both. In this short article I will focus on the
value of requirements based testing.
|
|
|
|
|
<< Start < Prev 1 2 Next > End >>
|
|
Page 1 of 2 |
