这些思想会给希望进一步优化其变更管理过程，从而更好地服务于所有涉众的所有软件开发组织带来潜在的利益。
These ideas will be of potential interest to any software development organization that wishes to further optimize its change management processes to better serve all stakeholders.
最终将应用程序部署到产品环境中，作为客户的标准变更管理过程的一部分。
Finally, the application is deployed to the production environment as part of the customer's standard change management processes.
术语变更管理（CM）涉及到一个组织或项目用来计划、执行和跟踪一个软件系统变更的过程和工具。
The term change management (CM) refers to the processes and tools an organization or project uses to plan, execute, and track changes to a software system.
如果这个过程简单而且没有干涉或者减缓它们进展的时候，开发人员通常是理解变更管理的系统的利益的。
Developers generally understand the benefits of a change management system if the process is simple and does not interfere with or slow their progress.
这些特性提高了模型元素、代码引用，以及管理变更过程之间的稳定性。
These features improve the consistency between the model element, the code references, and the process to manage changes.
举例来说，当你应用其中一个标准模板来管理你的变更管理过程时，所有的团队成员缺省可以查询数据库中的所有记录。
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.
在传统的软件开发中，跟踪变更的方法是使用某种类型的变更管理系统、过程或工具。
The traditional approach to keeping track of changes in software development is to use some type of change management system, process, or tool.
同时开发人员想利用更少的过程，约束以及控制，而采用更简单更倾向于变更和配置管理的解决方案。
At the same time developers want to use easier and leaner change and configuration management solutions with less overbearing process, restriction, and control.
既然我们已经讨论过如何成功地组织一个项目，现在让我们来讨论一些更为具体和重要的开发过程：需求和管理变更。
Now that we've talked about organizing the project for success, let's talk about a couple of specific, crucial development processes: requirements and change management.
并且，随着较作为低级别的抽象，例如存储库和工作空间，变得普通和广泛被接受，较高等级功能可以放在顶端，以简化变更管理过程。
And, as lower-level abstractions such as repository and workspace become common and widely accepted, higher-order functions can be layered on top to simplify the change management process.
本文中所说的通用工作流的概念可以视为是具有广泛，跨行业适应性的一般的变更管理模板及过程。
The concept of a common workflow as illustrated in this article can be viewed as a generic change management template and process with broad, cross-industry applicability.
不管是对于应用程序还是对于产品代码本身，变更管理的过程都相当成熟。
The process of managing changes to an application or to the product code itself is quite mature.
变更管理影响软件开发的全部过程，但是被跟踪的与测试工作最相关的变更是缺陷。
Change management affects all parts of software development, but the tracked changes most relevant to the testing effort are defects.
UCM 授予您管理您的项目的变更过程的最终能力。
UCM gives you the ultimate ability to govern the change process for your projects.
这样的一个规范变更管理过程通常在多个团队与角色之间进行。
Such a formal change management process often flows through multiple teams and roles.
范围蔓延是一个术语，用以定义在未经范围变更管理过程而进行的针对项目的一系列小型的范围变更。
Scope creep is a term used to define a series of small scope changes that are made to the project without scope-change management procedures being used.
这个变更管理工具读取了变更组合列表，并在记录的变更组合中执行了合并过程。
The change management tool reads the change set list and performs an automated merge on the recorded change set.
其中有非常复杂的变更管理过程，但是却没有涉及到真正的变更系统。
There's a very elaborate Change Management process, but it doesn't involve actually changing systems.
一个全面的解决方案将会包括对于过程指导、需求管理、软件资产管理、缺陷和变更跟踪、测试管理以及共同报告的综合支持。
A comprehensive solution will include integrated support for process guidance, requirements management, software asset management, defect and change tracking, test management, and common reporting.
如果使用变更管理系统，则构成存储过程的所有对象(例如源代码、DBRM、JAR文件)都在这个环境中得到管理。
If a change management system is used, all objects that comprise a stored procedure (for example, source code, DBRMs, JAR files) are managed in this environment.
这种自动化过程指导使软件开发的最佳实践具体化，这些最佳实践包括迭代化方法、变更管理、可视化建模和持续质量保证过程。
This automated process guidance embodies software development best practices, including an iterative approach, change management, visual modeling, and continuous QA procedures.
优化需求和变更管理过程。
Optimizing the requirements and change management processes.
更重要的是，Subversion只是这个模式的一半，因为有效软件开发过程的另一个关键组件是变更管理。
More important, Subversion is only half of the story, because the other key component of an effective software development process is change management.
很多基于脚本的变更管理过程，在ClearCase上构建，在定义什么是UCM上扮演了一个关键角色--并且将会在确定它将会成为什么上继续进行下去！
Many of these script-based change management processes, built on top of ClearCase, played a key role in defining what UCM is -- and will continue to do so in determining what it will become!
无论是不是一个正式的过程团队，ProjectManagementOffice或者QualityAssurance部门，都经常有各种将同变更管理系统发生交互的用户。
Whether it is a formal process team, the Project management Office, or the Quality Assurance department, there is often a variety of users who will interact with the change management system.
首先，Allen讨论了变更脚本——一种管理除视图、存储过程、函数以外的数据库对象的机制。
First, Allen discusses the mechanism he USES to manage changes to schema objects other than views, stored procedures, and functions - change scripts.
最近的行业法规，例如SarbanesOxley、BaselII，和CFR21Part11会向s CM过程施加繁重的管理成本，特别是关于变更控制的方面。
Recent industry regulations such as Sarbanes Oxley, Basel II, and CFR 21 part 11 can place onerous overheads on SCM processes, particularly with respect to change control.
所有这些变更需要通过合适的过程和工具来管理，这样我们就可以有效地管理变更而不影响我们的创造性。
All this change needs to be managed by having the processes and tools in place so we can effectively manage change without hindering creativity.
在此阶段过程中，活动应该是高度可处理的，主要关注于变更管理，以便不引入新的风险。
During this phase, the activities should be highly transactional, with a major focus on change management so that new risks are not introduced.
与变更请求联合的工作流程应该加强这个过程，通过这个工程您地组织就可以跟踪并管理变更。
The workflow associated with a change request should enforce the process by which your organization intends to track and manage change.
应用推荐