Information Technology Reference
In-Depth Information
Once the system xyz n.m meets the acceptance criteria at the end of the
acceptance period, the customer will formally declare his acceptance of the
system.
Should the acceptance criteria not be met by 100 %, acceptance can be declared
conditionally. The constraints have to be documented.
After acceptance the project will amend known errors in sequence of their
priorities right after going productive. During acceptance procedures error
amendments (patches) should have been introduced already.
The acceptance configuration was provided including servers with the following
utilities:
-
.
...
The acceptance configuration for system xyz was provided by
.in
location,
...
<
in the premises of the customer ABC.
Dates: start of acceptance tests:
postal address
>
mm.dd.yyyy
<
>
End of acceptance tests:
mm.dd.yyyy
>
The acceptance test results are shown under list item 5 (Acceptance Results
Rel_n.m) in detail.
Errors recorded by the customer ABC are described in an error protocol with
their respective priorities. This protocol will be handed over as soon as possible at
the end of the acceptance test period to the supplier DEF. It may contain a
declaration of acceptance refusal, a possible justification for the refusal and the
final error protocol.
Errors are prioritised in the following way:
<
Production prohibiting: die function produces wrong results, breaks down,
follows a logic, which is unusable etc. (Prio 1)
Production prohibiting, but can be used on a temporary basis by employing a
workaround (the duration of the workaround until the error to be fixed has to be
agreed upon) (Prio 2)
All other errors (Prio 3).
At the end of the various acceptance phases the list of identified errors is the
basis for a final evaluation. During this process errors, which had already been
amended during this acceptance phase, are marked as corrected since they had been
quality assured by the supplier.
Acceptance of the system xyz is granted, if at the end of the acceptance test
period at
mm.dd.yyyy
no errors remain, which are bound to impede the proper
<
>
functioning of the system.
Errors of priority 2 and 3 remaining after acceptance tests will be fixed during
productive operation according to an agreed upon schedule as fast as possible.
