Information Technology Reference
In-Depth Information
Requests formulated during the acceptance test period will be handled by
request/change management of the project xyz and documented in the daily review
protocols.
3. Participants
see Template Table
3.2
.
4. Acceptance Objects
All modules of the delivery are detailed in the document “Acceptance Specification
xyz Version n.m”.
5. Results
Number and Priority of Errors by Test Case:
Component
Test Case
Prio 1
Prio 2
Prio 3
Remarks
Divers
Tracker Entries
Error Total
List of Errors Known Beforehand:
Short description
Priority
Status
Object
Evaluation and Acceptance Status
A
without fault
¼
B
accepted under the condition “amendment asap” (fixing of errors is man-
aged transparently via a tracker and will be quality assured by the supplier)
¼
C
not accepted
¼
Acceptance object
Acceptance status
Software System xyz n.m
6. Acceptance by the Ordering Party
The acceptance of the acceptance objects outlined above is granted after thorough
review of the documents provided and the test results obtained.
The results and evaluations of this acceptance test are recorded in list item
5 “Results” (with some possible constraints) and logged in the tracker.
Date Acceptance Manager
