Information Technology Reference
In-Depth Information
An error is classified as acceptance prohibiting, when the productive use of the
software is impeded seriously because the function in question is not carried out at
all or in such an erroneous way that its intended function cannot be achieved even
by a work around.
During the acceptance test phase these errors have to be fixed within a controlled
patch delivery schedule under the responsibility of the configuration management.
Priority 2: the error leads to production break down but there exists a work around.
Priority 3: the errors neither leads to production stand still nor to production
impediment.
Errors of category 2 and 3 are classified as not to be acceptance prohibiting.
These errors limit the operational usage of the software only in a limited way. Such
errors are documented for later corrections in a follow up list in the tracking tool.
In the end the list of identified errors is subject to a final evaluation. Those errors
having been amended during the acceptance test phase already are marked as
corrected in as much as they have been quality assured by the internal quality
management of the project. Evaluation criteria:
A
without fault
¼
B
¼
acceptance under the condition that errors will be amended (the amendment of errors is
tracked by the error tracker and managed by the internal quality management)
C
not accepted
¼
After or during the passing of all test process steps all test results are
documented. If there should be no acceptance prohibiting error at the end of the
test series a protocol confirming acceptance will be provided by the steering group.
5.4.10.2 Access Rights
The access concept has to be tested on the basis of a test scenario including
acceptance criteria with respect to two aspects:
Conformity with the IT standards of the ordering party,
Possibility to implement special user profiles with regard to specific xyz
functionalities.
5.4.10.3
Interface Functions Under Simulated Conditions
Test cases and thus test process steps demand interface data and functions with
regard to:
Explicit test case functions (work instructions)
Input from interfaces for further processing
Output to external systems via interfaces.
