Game Development Reference
In-Depth Information
In both cases, some basic strategies to address low PCE areas are:
Improve knowledge of the subject matter and provide relevant training.
Have successful team members provide mentoring to less-successful members.
Document methods used by successful individuals and deploy them through-
out the team.
Increase compliance with existing methods and standards.
Add standards which, by design, help prevent faults.
Add checking tools that run during the creation process, such as color-coded
and syntax-aware editors.
Add checking tools that run after the creation process, such as stronger compilers
and memory leak checkers.
Quality Plans
Each game project should establish its own plan for how quality will be monitored
and tracked during the project. This is typically documented in the Software Quality
Assurance Plan (SQAP). The SQAP contains no information about testing the game.
That is covered in the game's Software Test Plan. An SQAP is strictly concerned with
the independent monitoring and correction of product and process quality issues. It
should address the following topics, most of which are covered in more detail here:
QA personnel
Standards to be used in the product
Reviews and audits that will be conducted
QA records and reports that will be generated
QA problem reporting and corrective actions
QA tools, techniques, and methods
QA metrics
Supplier control
QA records collection, maintenance, and retention
QA training required
QA risks
The topic's CD provides a link to an SQAP template document from Teraquest
( that follows this outline.
Search WWH ::

Custom Search