Abstract
Everyone agrees that quality software is a good thing. But no one agrees on what quality software is or how one goes about constructing quality software. Past efforts have typically focused on the computer side of software development, using traditional TQM or QIP. Instead I argue that software quality should be measured from the end-user perspective and by its measurable impact on the end-user. While many of the attributes of quality software (e.g., correctness, flexibility, portability) are common to computer professionals and end-users, their weighting schemes are quite different. In this talk, I argue for the end-user perspective and the end-user's definition or quality being balanced against the software engineer's quality definition. This presentation will point out differences from traditional approaches and suggest ways to implement such a quality program.