Perspective-based reviewing assigns different reviewers to examine the requirements from the viewpoint of different stakeholders (such as end users, developers, and testers), often having them build work products like test cases or use cases from that specific perspective. This technique is specifically designed to diversify the angles from which a document is examined, which increases the likelihood that different reviewers will uncover different types of defects rather than converging on the same ones — directly addressing the problem of uneven review coverage caused by reviewers all sharing the same implicit viewpoint. Checklist-based reviewing standardizes what reviewers look for (which can actually cause convergence rather than diversity), and scenario-based reviewing structures the review around specific usage scenarios rather than stakeholder viewpoints.
Community Discussion