How perspective-based reading can improve requirements inspections
How perspective-based reading can improve requirements inspections
复制标题
基于视角的阅读如何改进需求检查
作者：
F. Shull;I. Rus;V. Basili
由于缺陷构成软件开发的不可避免的方面，因此发现和及时删除它们至关重要。被忽略的缺陷（例如软件系统需求，设计或代码中的故障）传播到随后的开发阶段，在该阶段中检测和纠正它们变得更加困难。充其量，开发人员最终会遇到缺陷，但要付出时间表延迟和其他产品开发成本。在最坏的情况下，缺陷将仍然存在，客户将收到有缺陷的产品。作者解释了他们基于视角的阅读（PBR）技术，该技术提供了一组程序，以帮助开发人员解决软件需求检查问题。 PBR审稿人代表文档中的特定利益相关者，以验证需求规格的质量。作者展示了PBR如何导致单个审阅者和与不熟悉应用程序域工作的审核团队的缺陷检测率提高。
Because defects constitute an unavoidable aspect of software development, discovering and removing them early is crucial. Overlooked defects (like faults in the software system requirements, design, or code) propagate to subsequent development phases where detecting and correcting them becomes more difficult. At best, developers will eventually catch the defects, but at the expense of schedule delays and additional product-development costs. At worst, the defects will remain, and customers will receive a faulty product. The authors explain their perspective based reading (PBR) technique that provides a set of procedures to help developers solve software requirements inspection problems. PBR reviewers stand in for specific stakeholders in the document to verify the quality of requirements specifications. The authors show how PBR leads to improved defect detection rates for both individual reviewers and review teams working with unfamiliar application domains.