Application Acceptance Criteria

Hi,

Can anyone provide me with or point me to some good examples of developing acceptance criteria for the delivery of an application?

Many thanks
DonossAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Suhas .QA ManagerCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jeroen RosinkSoftware testing consultantCommented:
Hello Donoss,
Creating acceptance criteria can be done in several ways and on several levels.
Normally I define a Master test plan which describes the proces over all test phases. In that place I write the general criteria how many issues there are allowed to be open. Something like:

Severity      FT      SIT      UAT
Critical      0      0      0
Major      2      0      0
Minor      5      Tbd      Tbd

(FT= Functional Test, SIT= System Integration Test, UAT= Usser Acceptance Test)

For every testphase I also write a detailed test plan.
In that plan I write down for example this criteria:

Acceptance criteria for the SIT are:
1.      All test scenarios have to be executed
2.      The number of outstanding critical issue should be zero;
3.      The number of outstanding major issues should be zero
4.      Project management should discuss the number of outstanding issues with other severity than critical or major.

I can use these kind of criteria as I made it visible how I cover my requirements with test cases and am able to show the results of all test cases. This gives information that all requirements are tested and the chance it smaller that issues are behind those tested situation. To get more trust of the quality you have to use more formal testing techniques.

You might take a look at the checklist for acceptance criteria:
http://quality-assurance-software-testing.blogspot.com/2005/11/checklist-for-acceptance-test.html

I hope this helps you out
regards,
Jeroen
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Quality Assurance

From novice to tech pro — start learning today.