是否有测试需求评审记录和测试计划？
7Does the factory have assessment/review records of product test need and product test plan?
最后阐述了需求评审与需求确认管理。
Finally, requirement evaluation and confirmation is described.
EMS公司已开始设计初样单元，并准备在2008年底进行系统定型需求评审。
EMS has begun design of early prototype units and is preparing for the formal system requirements review later this year.
然而，由于它是在假设会被抛弃的情况下建立的，它会迂回于需求评审，设计评审，代码评审和单元测试之间。
However, because it was created under the presumption that it would be thrown away, it bypassed requirements reviews, design reviews, code reviews, and unit testing.
在大多数情况下，在需求评审中找到一个需求问题，要比等到程序设计好、编码好，构建好以及测试好之后再找到，成本要低得多。
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.
在我们讨论与评审和细化需求相关的活动之前，让我们提出一个问题，您“为什么”需要这样做。
Before we discuss the activities associated with the review and refinement of requirements, let's address "why" you need to do this.
在已经评审并可能已细化所有需求之后，下一个活动就是讨论门户的功能。
After all requirements have been reviewed and possibly refined, the next activity is to discuss portal features.
当它是空白时，说明此需求当前没有必需被评审。
When it is blank, then no review is currently necessary for that requirement.
个体可以通过为配对编程或者执行之后的评审来满足这个需求。
The individual can satisfy this requirement by pair programming or after-the-fact review.
评审需求时您要记住这一点。
在直接转入评审需求之前，协调人必须执行一些标准的会议规则。
Before jumping directly into the requirements review, there are some standard meeting rules that the facilitator must administer.
对于每一个包含从现在到将来多种必要状态的需求，需求分析师打开一个变更需求记录就代表着一个评审活动。
For each requirement that contains multiple necessary states from now and into the future, a requirements analyst opens a change request record representing a review activity.
项目团队会重复地评审和更新评价过程，以交付项目的需求基线。
The project team will also review and update the assessment iteratively to deliver the requirements baseline for the project.
很多需求都可能与类似于这样的评审行为相关联。
Many requirements might be associated with each such review activity.
当然，这里的好处是不用有人必须记得要在需求管理工具中运行查询，来看什么需求应该接受一个版本控制的评审。
Of course, the advantage here is that no one has to remember to run queries in the requirements management tool to see what requirements should receive a versioning review.
为了版本控制的目的，这种评审活动只应该发生在需求分析师要对需求文本进行评审的时候，或者之后。
The review activity should occur on or after a specific date on which the text of the requirements is to be reviewed by a requirements analyst for versioning purposes.
然而，当提交需求的参与者在研讨会期间评审每一项需求时，需求的目的可能会引发大量的讨论。
However, when each requirement is reviewed during the workshop by the stakeholder who submitted it, then the intent of the requirement can inspire a lot of discussion.
使用这些信息，您就可以评审需求，以找到哪一个需求最容易实现自动化的。
Using this information, you can review the requirements to find which requirements are the most automatable.
在研讨会的第一个上午，参与者评审预先收集到的需求；这个会议是一个“评审和细化”活动。
During the first morning of the workshop, the participants review the requirements that were collected beforehand; this session is a "review and refinement" activity.
例如，可能您的团队会评审一个价值流图，以理解实施一个外部客户源的新需求需要多长的时间。
For example, it may be the case that your team is reviewing a Value Stream Map to understand how long it takes to implement a new requirement that comes from an external customer source.
从团队为什么需要细化和评审需求的讨论中，可以看出我们已经无意中定义了评审和细化。
You can see from this discussion of why the team needs to refine and review requirements that we have inadvertently defined what we mean by review and refine.
然后团队成员可以评审和注释需求及其相关的工件，但是仍然有规范的评审和确认过程。
Team members can then review and comment on the requirement and the associated artifacts, but there is also a formal process of review and validation.
在此阶段，可以通过业务和IT团队的联合评审，做出有关配置/扩展的SBS模型是否满足业务需求的建议和决策。
At this stage, the joint review of the business and IT team could be conducted to make recommendations and decision on whether the configured/extended SBS models could serve the business neeeds.
评审需求并作出相关的推荐。
Review requirements with testability in mind and make recommendations or changes accordingly.
在LCA评审中，我们必须评审DW的业务案例，以确定是否有意义，根据我们对架构和需求的进一步了解来构建系统。
At the LCA review we must review the business case for the DW to determine if it still makes sense to build it based on our improved understanding of the architecture and requirements.
VersioningReviewRecord表示一个变更请求记录，其包含了对每个被追踪需求的评审日期。
The Versioning Review Record represents a change request record that contains the date of review for the requirement(s) to which it is traced.
在创建工件和需求之后，Victor会邀请其他的团队成员评审评价文件并添加评论。
After creating the artifacts and requirements, Victor invites other team members to review the assessment documentation and add comments.
当需求做好在RequisitePro 中管理的准备之后（假设评审和批准过程发生了），您就可以将状态属性更改为“批准”。
When the requirement is ready to manage in RequisitePro (assuming a review and approval process has taken place), you can change the status attribute to "Approved."
Revisions帮助你追踪“谁改变了什么，什么时候，以及为什么”，提供了需求变更的评审踪迹。
Revisions helps you track who changes what, when and why, to provide an audit trail of requirement changes.
总而言之，评审过程只需仔细检查每一项需求，以解决需求中的任何问题。
To summarize, the review portion is simply going through each requirement to resolve any issues with it.
应用推荐