Hi, > IMHO, that definition is meaningless to end users and of very little > practical use when building commercial software. Instead, it can be used as > an opportunity for developers and QA teams to dodge responsibility for using > their brains during design and testing.
it's not a definition that's intended for end users, who tend to say "it doesn't work". It's a useful definition for developers because it tells us what to fix: - operator error: rtfm - documentation does not match the code: fix the documentation - code does not match the spec: fix the code - spec does not match the requirements: fix the spec - new or changed requirements: fix the requirements -- Cheers, Bob
