***************
Sun 16th Oct 2011
Time spent: 3 hours
Deadline 5 months
***************
Continuing with Literature Review:
http://doit.maryland.gov/SDLC/Documents/User_Acceptance.pdf
Definition of User Acceptance
User acceptance is the confirmation, through testing, that the delivered system meets all
requirements, functions according to design parameters, and satisfies all business, technical, and
management stakeholders.
Effective user acceptance criteria:
• Are based on functional and non-functional requirements
• Are specific, unambiguous, measurable, attainable, and realistic
• Contain specific pass or fail criteria
• Address all aspects of the system in detail
• Indicate if a requirement is critical or non-critical (i.e., not required for acceptance)
• Identify unacceptable errors
The execution of user acceptance testing is most successful when:
• Predefined and approved user acceptance criteria exist
• Users of the system perform the tests
• The test environment simulates real-world usage conditions
• Tests are conducted on a completed system that has passed unit testing, integration testing,
and system testing
• Tests are conducted utilizing test cases that cover all scenarios. Test cases describe the
functionality (scenario) being tested, input, expected result, actual result, pass/fail status and
rectification strategy for the problems discovered, test run date and time, name of the
person/role who ran the test
• All data has been migrated/converted (if applicable) prior to user acceptance testing
• Test case execution is automated with test scripts (when possible)
No comments:
Post a Comment