BENCHMARK-USER TESTING SCRIPT 1
Benchmark-User Testing Script
Name
Grand Canyon University: HCI-670
Date
, BENCHMARK-USER TESTING SCRIPT 2
Benchmark-User Testing Script
According to a study of 8000 software projects reported by the Standish Group, “the top
three reasons software projects were late, over budget, or failed to deliver desired functionality
all had to do with requirements management practices: lack of user input, incomplete
requirements, and changing requirements,” (Davis & Venkatesh, 2004). Davis and Venkatesh
(2004) classify software defects as “either defects in implementing specified user requirements
due to design or coding errors, or defects in the correctness of requirements due to discrepancies
between specified user requirements and true user requirements.”
User acceptance testing (UAT) is the last phase of the software testing process and is
performed to minimize software defects prior to the software being launched. There are three
things that UAT does for the software development team. First, UAT measures how compliant
the system is with the business requirements. Next, UAT exposes functionality/business logic
problems that unit testing and system testing missed. Finally, UAT provides a means of
determining how “finished” the system is (USER ACCEPTANCE TESTING (UAT) PROCESS,
2008).
When Oncology North and Oncology South merged, the EHR from both facilities also
needed to change in order to accommodate the new workflow that would be implemented at both
facilities. Due to the changes in the EHR being made, UAT is needed to develop confidence of
users at both facilities that the product is fit for the workflow purpose (Pandit & Tahiliani, 2015).
Members of the User Testing Team
Having the appropriate members on a UAT team will lead to a better end-product with
fewer system errors. The members of the UAT team should include members of the quality
Benchmark-User Testing Script
Name
Grand Canyon University: HCI-670
Date
, BENCHMARK-USER TESTING SCRIPT 2
Benchmark-User Testing Script
According to a study of 8000 software projects reported by the Standish Group, “the top
three reasons software projects were late, over budget, or failed to deliver desired functionality
all had to do with requirements management practices: lack of user input, incomplete
requirements, and changing requirements,” (Davis & Venkatesh, 2004). Davis and Venkatesh
(2004) classify software defects as “either defects in implementing specified user requirements
due to design or coding errors, or defects in the correctness of requirements due to discrepancies
between specified user requirements and true user requirements.”
User acceptance testing (UAT) is the last phase of the software testing process and is
performed to minimize software defects prior to the software being launched. There are three
things that UAT does for the software development team. First, UAT measures how compliant
the system is with the business requirements. Next, UAT exposes functionality/business logic
problems that unit testing and system testing missed. Finally, UAT provides a means of
determining how “finished” the system is (USER ACCEPTANCE TESTING (UAT) PROCESS,
2008).
When Oncology North and Oncology South merged, the EHR from both facilities also
needed to change in order to accommodate the new workflow that would be implemented at both
facilities. Due to the changes in the EHR being made, UAT is needed to develop confidence of
users at both facilities that the product is fit for the workflow purpose (Pandit & Tahiliani, 2015).
Members of the User Testing Team
Having the appropriate members on a UAT team will lead to a better end-product with
fewer system errors. The members of the UAT team should include members of the quality
