The assignment turned out to be a little different than what they originally asked for, and now I am writing a process document for how we achieve user sign-off or acceptance... So I decided to split User Acceptance out from User Acceptance testing because that is not the only way the users approve the product. They will review results of a Functional or Integration test for example.... Anyway, how do you feel about this. Does "User Acceptance" exist as a concept of its own, or can it only be linked to UAT?
Here is what I wrote as a definition...
User Acceptance (sign-off) is an approval granted by the users of a product that states the product is acceptable to be installed and used at (my company name here). The product is deemed to be acceptable if the evaluation process confirms that the product meets or exceeds the Acceptance Criteria established for the project. The results of the process determines whether the users will accept the system, therefore, it requires involvement of those who will prepare the input, operate the system, and use the output. User Acceptance promotes user and management "buy in" prior to deployment, and increases confidence that the systems and processes being deployed meet expectations and result in no negative surprises.
User Acceptance as you define in your post is really User or Customer Sign-off and I would call it that so that it does not generate confusions with User Acceptance testing which is often truncated to User Acceptance or UAT.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison