一旦开发者完成了编码变更，通过了代码评审，单元测试变更的记录就将结束。
Once the developer has completed the coding changes, passed code review and unit tested the changes the record is closed.
第一个步骤是以新资讯(新增的记录、变更的记录或删除的记录)来更新资料模型。
The first step is to update the data model with new information - new records, changed records, or deleted records.
然而，索引要么增加要么减少了添加，变更，以及删除数据库记录的操作执行。
However, indexes can either increase or decrease the performance of operations to add, change, and delete database records.
对于每一个包含从现在到将来多种必要状态的需求，需求分析师打开一个变更需求记录就代表着一个评审活动。
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.
当您只想对可疑处理(比如超过10%的工资变更)生成审计记录时，这个特性可能有用。
This can be useful when you want to generate auditing records only for suspicious processing like salary changes of more than 10%, for example.
举例来说，当你应用其中一个标准模板来管理你的变更管理过程时，所有的团队成员缺省可以查询数据库中的所有记录。
For example, when you apply one of the standard templates to administer your change management processes, all team members can by default query all records in the database.
例如，如果生产环境中所有的变更都完全自动化，那么版本控制系统会保留每个人的修改记录。
For example, if all changes to production are fully automated, then the version control system keeps a record of every individual's modifications.
这包括管理报告，比如小组成员中变更记录的分配，故障确定的平均时间，等等。
This includes management reports such as change record distribution across team members, average bug fix time, etc.
工作项可以与和变更管理不相关的记录联系起来，并且可以用于分配和追踪工作。
Work items can be linked to records that are not change management-related and can be used to assign and track work.
清单3中的代码返回了在过去一个月中变更过的所有的里程记录。
The code in Listing 3 returns all mileage records that changed in the past month.
在最后的检入时创建的新文件，还有已经被修改的任何已有文件，将会被关联到此活动，并且会被记录在活动的变更集中。
The new files created since the last check-in, as well as any existing files that have been modified, will be associated with this activity, and will be recorded in the activity's change set.
ClearQuest变更请求记录类型到Jazz工作项的映射必须得到建模和实施。
A mapping of the ClearQuest change request record type to Jazz work items must be modeled and implemented.
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.
同样，变更请求记录的拥有权在多个团队不同的团队成员之间传递时，您可以选择Connector。
Also, choose the Connector when ownership of the change request record is passed among team members across multiple platforms.
增加、缺陷及其他由ClearQuest管理的变更请求记录存储在名为“用户数据库”的关系数据库中。
Enhancements, defects, and other change request records managed by ClearQuest are stored in a relational database called the "user database."
例如，RationalTeam Concert服务器记录了数据集市中对存储库所做变更的信息，例如每一天创建了多少的新工作项。
For example, the Rational Team Concert server records information in the data mart about the changes to the repository, such as how many new work items are created each day.
在ClearQuest先前版本中，必须通过为每个被管理(缺陷、变更请求，等等。)的条目创建记录类型的方式来管理工作。
In previous versions of ClearQuest work was managed by creating a record type for each item to be managed (Defect, Change Request, etc.).
对于那些不拥有到服务器的非常可靠且快捷的连接的远程用户来说，可以使用Web接口来添加、更新及查询变更请求记录。
For remote users who don't have an extremely reliable and fast connection to the servers, a Web interface is available to allow users to add, update, and query change request records.
例如，您没有记录到基线之中的业务进程可能在一个，或者多个，或者全部的目标结构中发生变更。
For example, a business process that you failed to document in your baseline may have changed in one, more, or all of your target architectures.
通过使用这个工作流，您可以变更和可视化代码，以记录它，并更好的理解它的结构和行为。
By using this workflow, you can change and visualize code to document it and better understand the architecture and behavior.
即使在最糟糕的情况下，当一个变更记录以模糊的状态或者高层次开始时，它至少要被跟踪和存档。
Even in the worst case, when a change record starts off as vague or high-level, it is at least being tracked and documented.
这一版本的变更在变更记录里进行了概要描述。
The changes in this release are outlined in the change notes.
这个变更管理工具读取了变更组合列表，并在记录的变更组合中执行了合并过程。
The change management tool reads the change set list and performs an automated merge on the recorded change set.
但是，如果当前的状态得到完善的记录，那么重新记录程序变更的部分事情（需求，架构和测试）就不是必要的。
However, if the current state is well-documented, it is not necessary to re-document the portions of things (requirements, architecture, and tests) that are not changed by the program.
比起更广泛且更一般的记录类型，它们还表现出对变更管理系统的维护者更少的约束。
They also present fewer constraints to the maintainers of the change management system than broader and more generic record types.
关注的还有出于统计和管理的目的，为所有变更维持历史记录的必要性。
Also implied is the need to maintain history for all changes for audit and management purposes.
请求要么记录在变更控制系统中，要么对于更不正式的项目来说，特别是在极限程序设计项目中，记录在卡片上或活动挂图上。
Requests are recorded either in change control systems, or even for more informal projects, particularly within eXtreme Programming projects, on CARDS or flip charts.
这个变更控制管理器创建了一个变更请求记录类型，它包含了与变更需求相关的活动，而不是创建一个新的需求属性。
Instead of creating a new requirement attribute, the change-control manager creates a change request record type containing activities related to the need to change a requirement.
在每个版本描述下面通常都包含一个变更记录，您可以通过它查看发行版周期中的变化。
Below each edition description is often a change log which allows you to see the changes within a release cycle.
然而，一个被手工生成的文档也应当存在，作为一个记录公司变更流程的变更管理方案。
One manually generated document that should exist, however, is a change management plan that documents the flow of changes through the organization.
应用推荐