Verify that acceptance procedures and acceptance criteria for each product are defined, reviewed, and approved prior to tests AT-2 and that test results are documented. Acceptance procedures must also address the process by which any software product that does not pass acceptance testing will be corrected. Verify that a sufficient number and type of case scenarios are AT-3 used to ensure comprehensive but manageable testing and that tests are run in a realistic, real-time environment. Verify that test scripts are complete, with step-by-step AT-4 procedures, required pre-existing events or triggers, and expected results. Verify that test results are verified, that the correct code configuration has been used, and that the test runs are AT-5 appropriately documented, including formal logging of errors found in testing. Validate that the acceptance test plan satisfies the following criteria: Traceable to the software requirements and design; External consistency with the software requirements and design; Internal consistency between unit requirements; Test coverage AT-6 of requirements in each component; Feasibility of software integration and testing; and Feasibility of operation and maintenance (e.g., capability to be operated and maintained in accordance with user Verify that the acceptance test organization has an appropriate AT-7 level of independence from the subcontractor. Validate that appropriate acceptance testing based on the AT-8 defined acceptance criteria is performed satisfactorily before acceptance of software products. Verify that the process by any software product that does AT-9 not pass acceptance testing should be corrected has been defined and documented. a. Validate that the results of the Acceptance Testing of each software configuration item indicates that the item correctly implements the software design for the item as documented in the software design documentation for that item. b. Document the results as required by the test plan. AT-10 c. Validate that the results of the Acceptance Testing of each software configuration item satisfies the test acceptance criteria as specified in the Acceptance Test Plan. d. Document discrepancies between actual and expected test results. Implementation I-1 Review and evaluate implementation planning. Verify that all software products required to install and operate I-2 each software component being implemented by the project are present in the software component’s installation package. Validate that all site-dependent parameters or conditions to I-3 verify supplied values are correct.
AT-2 Verify that acceptance procedures and acceptance criteria for each product are defined, reviewed, and approved prior to tests and that test results are documented. Acceptance procedures must also address the process by which any software product that does not pass acceptance testing will be corrected. AT-3 Verify that a sufficient number and type of case scenarios are used to ensure comprehensive but manageable testing and that tests are run in a realistic, real-time environment. AT-4 Verify that test scripts are complete, with step-by-step procedures, required pre-existing events or triggers, and expected results. AT-5 Verify that test results are verified, that the correct code configuration has been used, and that the test runs are appropriately documented, including formal logging of errors found in testing. AT-6 Validate that the acceptance test plan satisfies the following criteria: Traceable to the software requirements and design; External consistency with the software requirements and design; Internal consistency between unit requirements; Test coverage of requirements in each component; Feasibility of software integration and testing; and Feasibility of operation and maintenance (e.g., capability to be operated and maintained in accordance with user AT-7 Verify that the acceptance test organization has an appropriate level of independence from the subcontractor. AT-8 Validate that appropriate acceptance testing based on the defined acceptance criteria is performed satisfactorily before acceptance of software products. AT-9 Verify that the process by any software product that does not pass acceptance testing should be corrected has been defined and documented. AT-10 a. Validate that the results of the Acceptance Testing of each software configuration item indicates that the item correctly implements the software design for the item as documented in the software design documentation for that item. b. Document the results as required by the test plan. c. Validate that the results of the Acceptance Testing of each software configuration item satisfies the test acceptance criteria as specified in the Acceptance Test Plan. d. Document discrepancies between actual and expected test results. Implementation I-1 Review and evaluate implementation planning. I-2 Verify that all software products required to install and operate each software component being implemented by the project are present in the software component’s installation package. I-3 Validate that all site-dependent parameters or conditions to verify supplied values are correct.