|
Problem 1
High volume of error checking and program unit interface defects.
Cause 1
Lack of error checking and program unit interface definition in the
design process. Programs are not always desk checked prior to release to
system test.
Problem 2
Confusion exists on the use of tables versus
hard coding.
Cause 2
The procedure is explained in the development standards. Adherence to
standards needs to be checked and enforced. Programs are not always desk
checked prior to release to system test.
Problem 3
Some of the functional specifications are being misinterpreted.
Cause 3
The functional specifications that are being misinterpreted were
written at a level that is too general. In future, functional
specifications need to be reviewed to ensure enough specificity exists
to prevent multiple interpretations. A Standard Review Procedures
checklist exists, but this item is not included.
Problem 4
There is some confusion on the definition of a defect versus a change
request.
Cause 4
Staff who are documenting the errors lack knowledge on the definition
of a change request.
Problem 5
Inconsistency in the Functional Specification between the narrative
description and the screen layout.
Cause 5
Oversight on the part of the reviewers of the Functional
Specification. The document was reviewed and approved without
identification of these two inconsistencies. A Standard Review
Procedures Checklist exists, but this item is not included. |
