Programming Books C Java PHP Python Learn more Browse Programming Books
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Change-Based Test Management: Improving the Software Validation Process Paperback – January 1, 2002


Amazon Price New from Used from
Paperback, January 1, 2002
"Please retry"
$48.95 $14.35
NO_CONTENT_IN_FEATURE

Shop the New Digital Design Bookstore
Check out the Digital Design Bookstore, a new hub for photographers, art directors, illustrators, web developers, and other creative individuals to find highly rated and highly relevant career resources. Shop books on web development and graphic design, or check out blog posts by authors and thought-leaders in the design industry. Shop now

Product Details

  • Series: Engineer to Engineer series
  • Paperback: 186 pages
  • Publisher: Intel Press (January 2002)
  • Language: English
  • ISBN-10: 0971786127
  • ISBN-13: 978-0971786127
  • Product Dimensions: 9.1 x 7.5 x 0.5 inches
  • Shipping Weight: 14.1 ounces
  • Average Customer Review: 4.5 out of 5 stars  See all reviews (2 customer reviews)
  • Amazon Best Sellers Rank: #4,782,039 in Books (See Top 100 in Books)

Editorial Reviews

Review

"An essential book for any developer involved with software testing. Extremely practical." -- Virginia Aldrich, Senior Software Engineer, Express Imaging

About the Author

Jon Sistowicz is a member of Intel's chipset software validation team where he helped develop and introduce CBTM. Jon created the first delta report generator, which established CBTM as a cornerstone of Intel's driver validation efforts. As part of Intel's chipset team, Jon implemented VHDL coverage practices and helped write a key feature specification for Intel's next generation graphics chipset. Prior to Intel, Jon worked for Unisys Corporation where he wrote Java applications enabling legacy hardware for the Internet. Jon holds a Bachelor's Degree in Computer Engineering from Pennsylvania State University.

Ray Arell manages the Validation Architecture department within Intel's Desktop Platforms Group. Ray has over 18 years of development, validation, and management experience, and has been with Intel for 10 years. During this time, he has worked on a variety of teams focused on CPU, chipsets, and graphics system-level testing including the i386™, i486™, and Pentium® processors, and supporting chipsets. Ray’s programming projects have included a variety of test applications, including the concept and development of key validation capabilities like the Visual Test Creator graphics tool.

Customer Reviews

4.5 out of 5 stars
5 star
1
4 star
1
3 star
0
2 star
0
1 star
0
See both customer reviews
Share your thoughts with other customers

Most Helpful Customer Reviews

3 of 3 people found the following review helpful By Mike Tarrani HALL OF FAMETOP 50 REVIEWER on June 29, 2004
You need not change your existing testing process to accommodate the central ideas from this book - the method of managing testing can be bolted onto most standard approaches.
The keys to change-based testing are:
- prioritization and delta testing
- validation
- layered testing (from regression at the least complex level, to structural performance, to certification and standards testing at the most complex level and when appropriate)
Delta testing - focusing on changes in the code or product base - is the essence of this approach and from where the title was derived.
Validation, which follows verification, is another key component. Note that verification is assuring that all requirements are included, and validation is assuring that they correctly function. This means that testing begins early in the life cycle, at the requirements and design stages where it is significantly less costly to remove a defect than in the test phase. This also expands the scope of most testing organizations, and makes it more akin to SQA than testing. The differences are not so subtle. Although not directly stated in the book, as the additional elements of change-based testing are bolted on, defect removal efficiency (a key metric indicating test effectiveness) can be replaced by defect density metrics which identify where in the life cycle a defect was introduced. This leads to process improvement opportunities that will strengthen the entire development process.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
5 of 6 people found the following review helpful By Robert on August 29, 2003
This book gave insightful and pratical ways to better test software projects. As our software becomes more and more complex, we need ways to ensure we're meeting our customers expectation and not creating "blue screens of death." The concepts given are easy to read and process. I especially liked the little "Ray's Insights" tidbits. It's a good read - one to start some process improvements with.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Customer Images