One key aspect of the quality of a requirement is that it is ‘testable’. In addition to being used as a communication channel between the business and the development communities, requirements must also provide testers with a clear definition of what is required from them in terms of the creation of test plans and expected results. To facilitate this, it is vital that, in addition to the description of the requirements themselves, the business analyst also defines detailed acceptance criteria for each requirement. Also known as ‘fit criteria’ or ‘test completion criteria’, these acceptance criteria are absolutely vital in ensuring that the correct solution is delivered. In fact, a requirement that does not contain a clear definition of its acceptance criteria will probably need to be clarified further during testing, resulting in unnecessary reworking and extra costs.