scispace - formally typeset
Book ChapterDOI

Walkthroughs, Code Reviews, and Inspections

John F. Dooley
- pp 209-220
TLDR
Here’s a shocker: your main quality objective in software development is to get a working program to your user that meets all their requirements and has no defects.
Abstract
Here’s a shocker: your main quality objective in software development is to get a working program to your user that meets all their requirements and has no defects. That’s right: your code should be perfect. It meets all the user’s requirements and it has no errors in it when you deliver it. Impossible, you cry? Can’t be done? Well, software quality assurance is all about trying to get as close to perfection as you can - albeit within time and budget. (You knew there was a catch, didn’t you?)

read more

Citations
More filters
Journal ArticleDOI

Building and Testing a Fuzzy Linguistic Assessment Framework for Defect Prediction in ASD Environment Using Process-Based Software Metrics

TL;DR: A methodological framework based on fuzzy linguistic modelling has been proposed to predict the defect density using various process metrics derived from literature studies to measure the attributes stated in the agile manifesto.
References
More filters
Book

Agile Software Development, Principles, Patterns, and Practices

TL;DR: This comprehensive, pragmatic tutorial on Agile Development and eXtreme programming, written by one of the founding father of Agile development, teaches software developers and project managers how to get projects done on time, and on budget using the power ofAgile Development.
Journal ArticleDOI

Design and code inspections to reduce errors in program development

Michael Fagan
- 01 Sep 1976 - 
TL;DR: It is shown that by using inspection results, a mechanism for initial error reduction followed by ever-improving error rates can be achieved.
Journal ArticleDOI

Advances in software inspections

TL;DR: Studies and experiences are presented which enhance the use of the inspection process and improve its contribution to development of defect-free software on time and at lower cost.
Book

The humble programmer

TL;DR: As a result of a long sequence of coincidences I entered the programming profession officially on the first spring morning of 1952, and as far as I have been able to trace, I was the first Dutchman to do so in my country.
Journal ArticleDOI

The humble programmer

TL;DR: Dijkstra's "Humble Programmer" as discussed by the authors is one of the great classics in the field, providing an educational experience for the junior programmer, and truly delightful reading for the veteran.