<6. User Acceptance Test>
6. User Acceptance Test (UAT)
Before starting user acceptance test ( UAT), verify that all function tests have
been completed and all specification changes have been addressed.
Equipment to be used in UAT may not always be identical to the actual
system.
In such cases, it is important to obtain prior consent of the user by explaining
the differences between the equipment to be used in UAT and the actual
system – what they are, how they will be simulated, and what problems may
arise from such simulation.
This chapter describes a list of items that should be checked and a list of
items that should be explained to the user before UAT.
6.1 Pre-UAT Checklist
Before starting UAT, perform the following pre-test checks.
6.1.1 UAT Prerequisites
Before starting UAT, ensure that the following preconditions are met.
• Function test is completed.
Verify that operation of all items described in the function specification or
requirement specification from the user have been validated.
• All specification changes have been addressed.
Verify that all specification changes, if any, arising during control application
creation have been addressed.
For any specification change that cannot be addressed in time for the user
acceptance test, confirm when it will be addressed.
• FCN-500, FCN-RTU setup is properly done.
Verify that hardware setup of the FCN-500 or FCN-RTU has been properly done
as described in Chapter 2, @Basic Design and Function Design“ and Chapter 3,
“Hardware Setup.“
• There are no unused device labels.
Using the procedure described in “● Detecting Unused Global Variables Using
Cross References” of Section 9.1.8, “Cross References” of Chapter 9,
“Advanced Engineering,” verify that there are no unused device label variables.