On large software products, each stage of development that a defect survives will increase the cost of fixing the defect by ten to fifty times. The longer a defect remains, the harder it is to fix. Most bugs are not detected or fixed until long after their introduction. The most common approach is to delay major testing until the final QA phase of software development, where defects are often discovered for the first time.
This sounds simple, but it is a rare practice. The basic tenet of ZDSD is this: Maintain your product in what you believe to be a defect-free state throughout the development process.
Defects in the development of a computer game would include unpolished artwork, an unacceptably low frame rate on the target system, levels that aren't fun enough, or any number of unfinished features. This broad definition includes bugs as well as unwanted deviations from the desired final outcome. "Defects" are aspects of the evolving software that would not be suitable for the final product as-is. Not to be taken as meaning "bug-free," Zero-Defect Software Development (ZDSD) is a practice of developing software that is maintained in the highest quality state throughout the entire development process. To deal with these issues, I gradually adopted a system of Quality Assurance (QA) practices that allowed me to significantly increase product quality while simultaneously reducing development time. Because of the short lifespan of most computer games and their dependence on transient technology, my opportunities to improve a released product based on customer feedback are minimal. When I release a new game, I must make sure it is of very high quality because my users won't think to look for an upgrade. I can sell sequels or expansion packs, but I generally cannot sell upgrades as with other software. As an independent game developer, I will work from six months to a couple years to develop and release a new computer game.
0 kommentar(er)
