RR：需求评审

“Requirements Review”常缩写为RR，这一形式广泛应用于机构领域和军事相关语境中，旨在提高书写与交流的效率。其标准中文译名为“需求评审”，特指对项目或任务需求进行系统性评估与确认的关键环节。

Requirements review can also be done using prototypes and domain models.
需求审核也可以使用原型和领域模型来完成。
Before jumping directly into the requirements review, there are some standard meeting rules that the facilitator must administer.
在直接转入评审需求之前，协调人必须执行一些标准的会议规则。
If you're writing e-mails or coding during a requirements review meeting or teleconference walk-through, your attention is misplaced.
如果在需求审阅会议或电话会议走查过程中撰写电子邮件或编码，您的注意力就放错了地方。
In most cases, finding a requirement problem in a requirements review is far cheaper than waiting until the application is designed, coded, built, and in testing to find the problem.
在大多数情况下，在需求评审(RR)中找到一个需求问题，要比等到程序设计好、编码好，构建好以及测试好之后再找到，成本要低得多。
This means that during the requirements review activities, for example, the developer's primary task is " requirements review. "
这意味着在需求审阅活动过程中，举例来说，开发人员的主要任务是“需求审阅。”

本站英语缩略词为个人收集整理，可供非商业用途的复制、使用及分享，但严禁任何形式的采集或批量盗用

若RR词条信息存在错误、不当之处或涉及侵权，请及时联系我们处理：675289112@qq.com。