Chapter 12: Fit Criterion ( Duy Anh Tran )
- A fit criterion is neither a test nor the design for a test, but rather a benchmark that the delivered product has to be tested against.
- It is used as input to building a test case through which the tester ensures that each of the product's requirements complies with its fit criterion.
- Quantifying or measuring the requirement gives you a better opportunity to interact with your stakeholders:
- By agreeing on a measurement, you confirm that you have understood the requirement correctly, and that both you and your stakeholders have an identical understanding of it.
- As a by-product, you will also find quantifying it ensures that the requirement is both wanted and necessary.
- Including a fit criterion in a requirement encourages testers to participate in the requirements process. In other words, the testers are excellent consultants for the fit criteria.
- The fit criterion, not the description, is the real requirement. The description you write is the stakeholder’s way of stating the intention of the requirement.
- If your stakeholders are like most of us, they speak using everyday language, which is, unfortunately, often ambiguous and often not precise enough. You need to clarify the requirement with a fit criterion that is stated in unambiguous, precise terms and probably uses numbers or a measurement to convey its meaning.
- Fit criteria are also a vehicle for reaching a consensus among multiple stakeholders. Your attempts to clarify and measure will almost always result in hidden meanings becoming visible, hidden requirements bubbling to the surface, and, most importantly, the stakeholders agreeing on what is needed.
- Fit criteria are usually derived after the requirement description is written:
- You derive a fit criterion by examining the requirement's description and rationale, and determining which quantification best expresses the user’s intention for the requirement.
- You may sometimes find that this close examination results in changes to the requirement, but these changes are for the better and should be considered quite normal; their occurrence simply means the requirement was not properly understood in the first instance.
- With patience and persistence, and with the wise use of measurements, you can ensure that each of your requirements is unambiguous, testable, and real.
Comments
Post a Comment