Improving Requirements through Testing

[article]
Member Submitted
Summary:

There is no way to significantly improve software quality or productivity without first addressing the quality of the requirements. This article will teach you how to: perform ambiguity reviews of each process, design test cases for each individual process, and how to sequence requirements writing to allow for early full thread test definitions.

There is no way to significantly improve software quality or productivity without first addressing the quality of the requirements. This article will teach you how to: perform ambiguity reviews of each process, design test cases for each individual process, and how to sequence requirements writing to allow for early full thread test definitions.

About the author

Richard Bender's picture Richard Bender

Richard Bender has more than forty years of experience in software with a primary focus on testing and quality assurance. He has consulted internationally to large and small corporations, government agencies, and the military. Richard’s work has included a wide variety of application classes and technology bases from embedded systems to super computer-based systems—and everything in between—consulting to both vendors and IT departments alike. He has been active in establishing industry standards for software quality and is a frequent speaker at conferences, universities, and corporate events. For his breakthroughs on code-based testing, Richard was one of the first programmers ever awarded IBM’s Outstanding Invention Award. 

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Apr 29
Apr 29
May 04
Jun 01