Transcription of Improving Quality Through Software Inspections
{{id}} {{{paragraph}}}
Copyright 1995 by Karl E. Wiegers. All Rights Quality Through Software Inspections1 Karl E. WiegersProcess the earth cooled. Then the dinosaurs came, but they didn t make it. Next, humans beganprogramming computers using coding forms and punched cards. With just a few compilation cyclesper day, there was plenty of time to study the listings and look for those elusive , in modern times, we all write programs at the keyboard and compile them as frequentlyas we like. Complete listings are rarely printed out for entire Software applications, let aloneexamined line by line by a group of people on a bug hunt. Ironically, this very process, officiallytermed Software inspection , is one of the most effective methods we have for identifying errors ina program. So much for time I actually sit down and read Through an entire listing of a program, I find ways itcan be improved: redundant logic, unused variables, incorrect boolean tests, comments that don tmatch the code, and a hundred other errors that make me glad I took the time to look.
Copyright © 1995 by Karl E. Wiegers. All Rights Reserved. Improving Quality Through Software Inspections 1 Karl E. Wiegers Process Impact www.processimpact.com
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}
National Standards Quality Indicators, National Standards & Quality Indicators, Improving Quality in Business Process Outsourcing, Improving Quality in Business Process Outsourcing through Technology, Improving Reassessment and Documentation of, Quality, Improving Virginia’s Early Childhood Development, Improving Virginia’s Early Childhood Development Programs, Improving Unit Cohesion, Introduction of Fridge, Improving, Improving API 1104 for the Twenty-second Edition