Game Development Reference
In-Depth Information
chapter 6
Measurement Metrics
for Tool Quality
There is an old saying with software that three years from now, no one will
remember if you shipped an awesome software release a few months late.
What customers will still remember three years from now is if you shipped
a software release that wasn't ready a few months too soon. It takes multiple
product releases to change people's quality perception about one bad release.
Scott Guthrie
The risk of failure for software development is increasing at a rapid rate because
of the need for higher quality software that is also more cost effective and deliv-
ered in a timely manner. With the growing focus on quality, there is a definite need
to improve the quality of software to meet the needs of the industry. One common
problem when trying to determine how to improve quality is establishing a mean-
ingful way to measure quality so that you can quantify your results. If a developer
told you that a piece of software was top-notch quality, just what does that mean?
If a developer told you that a piece of software has only failed twice in over three
years of usage, there would be more value behind that statement. The only differ-
ence between the two statements is that the second one presents a quantifiable
measurement detailing the number of times the software failed in a three-year
period. Both statements could be referring to the same piece of software, yet the
second statement is the only one that is an acceptable and accurate description of
software quality.
Search Nedrilad ::

Custom Search