Prev | Current Page 343 | Next

Peter Farrell-Vinay

"Manage Software Testing"


??? The status of each problem is tracked and reported.
??? Records of the problems are maintained in a database and are available during the project to client.
??? Inputs to the corrective action process consist of problem/change reports and other anomaly
reports.
??? Each problem is classified by category, severity, and priority.
??? Trends in the problems reported are analyzed.
??? Corrective actions are evaluated to:
??“ Verify that problems have been resolved, adverse trends have been reversed, and changes
implemented in the processes and items.
??“ Help determine whether additional problems have been introduced.
8.21.8.2 Reviews
Describe the technical and managerial reviews to be conducted with respect to the system development,
either directly or by reference to a standard.
8.21.8.3 Testing
Include a statement of the testing strategy to be adopted. Refer to the method of test planning and
documentation. Define the level of testing rigor in the Testing section.
8.21.8.4 Quality Control Records
Specify quality control records selected to match the development method.
8.21.8.5 Other Quality Controls
All the elements of the plan apply to all deliverables: hardware, software, documentation, or training.
Test Documents 169
8.21.9 Client-Supplied Material
If there be deliverables or items furnished by the client or other third party used on the project, the
quality plan must stipulate their care and control.


Pages:
331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355