|
Functional Audit |
Physical Audit |
|
Objective: To provide an independent evaluation of software products, verifying that its configuration items’ actual functionality and performance is consistent with the requirement specifications.
|
Objective: To provide an independent evaluation of a software product configuration item to confirm that components in the built version map to their specifications.
|
|
Audit Requirements:
1. Software Requirements Specification (SRS), System Specification (SS) 2. Waiver or Deviation List Prepared 3. Verification Test Procedures Prepared. 4. Verification Test Procedures Reviewed and Approved. 5. Verification Test Data and Results Reviewed and Approved 6. Test Results submitted. 7. Test Readiness Review completed 8. Test Readiness Review minutes and open action items from past reviews available 9. Copy of baseline and database change requests with their associated status accounting records along with all design provided |
Audit Requirements:
1. Approved final draft of the configuration item (CI) product specification. 2. A list delineating both approved and outstanding changes against the configuration item. 3. Acceptance test procedures and associated test data. 4. Findings / Status of quality assurance programs. 5. Manuscript copy of all software CI manuals. 6. Computer Software Version Description Document. 7. Current set of listings and updated design descriptions or other means of design portrayal for each software CI. 8. FCA (Functional Configuration Audit) minutes for each configuration item. |
December 16, 2008...3:48 pm
Functional Audit vs Physical Audit
Jump to Comments
