以下是在敏捷系统测试活动中面临的一些最重要的挑战。
Following are some of the most important challenges faced in the course of agile system test activities.
敏捷系统是市场和客户的需求快速变化的产物。
The diverse requirements of market or customer lead to the birth of the agile system.
敏捷系统需要动态地进化，不断进化的系统意味着系统的规模、复杂程度持续增长。
In an agile system, dynamic evolution should be satisfied which means that the scale and complexity of system keep increasing.
一般来说，在敏捷的开发周期中对系统测试缺陷的开发关注较多。
In general, there was more development focus on system test defects during the agile development cycle.
这种处理RUP的方法支持尽早且频繁地向生产交付系统的敏捷原则。
This approach to RUP supports the agile principle of delivering systems to production early and often.
操作系统虚拟化对于敏捷开发尤其有好处，因为它可以在不影响现有操作的情况下按需提供资源。
Where as operating system virtualization provides special benefits for agile development as it can provide on demand resource with out effecting existing operations.
为了便于理解并实现这样复杂的系统，在这个行业中，我们已经设计了新的技术，例如敏捷的开发过程。
To help understand and implement such complex systems, we in this industry have designed new techniques, such as agile development processes.
SPL的主要目标是通过利用所有开发生命周期阶段中的可重用资产，从而实现敏捷和高速的成员系统开发。
The main goal of SPL is the agile and speedy development of member systems by taking advantage of reusable assets from all phases of the development life cycle.
本文介绍了团队所采用的将一组系统测试子集作为敏捷开发环境的一部分，并与代码开发活动并行的方法。
This article describes the approach taken by one team for including a subset of system test as part of our agile development environment and in parallel with code development activities.
在敏捷的环境中，与开发密切合作的核心系统测试团队向开发组织提供了重大的潜在好处。
A core system test team working closely with development in an agile environment offers significant potential benefits to the development organization.
例如，世界最大的系统集成商最近在敏捷开发商投入了经多的精力。
For example, the world's largest system integrators have recently put more focus on agile development.
敏捷的开发周期的迭代特性令系统测试团队以较小的且更容易消费的规模在较长的时间内理解产品。
The iterative nature of the agile development cycle allowed the system test team to understand the product over a longer timeframe in smaller, more readily consumable pieces.
以下是与敏捷的系统测试工作相关的具体好处。
Among the specific benefits associated with agile system test efforts were the following.
它常常被忘记是因为大部分敏捷团队假定每个项目都会有一个源代码控制系统，并且每个项目都会正确的使用它。
It's forgotten because most Agile teams assume that every project has a source control system and that every project USES it correctly.
在敏捷性不是管理层的最优先考虑事项的组织中，这种虚线类型的报告系统非常典型。
This dotted-line type of reporting system is typical in organizations where agility isn't at the top of the list for management.
在敏捷的环境中，系统测试更容易检验修补，由于缺陷周转时间较快，并且由于准确的测试环境仍旧适当。
System test more easily verified fixes in an agile environment, due to defect turnaround time being faster and since the exact test environment was still in place.
我在参与的很多敏捷团队里应用了团队管理系统思想，并取得了成功。
I've successfully applied the team Management Systems concepts to many Agile teams that I've been a part of.
开发团队为了响应一个易变的环境必须越来越敏捷，在这种环境中，在一个满足涉众需求的系统能够被部署之前，需求可能经常发生变化。
Development teams must be increasingly agile in order to respond to a volatile environment, in which requirements might change even before a system that satisfies stakeholder needs can be deployed.
因此，即使敏捷的版本周期包含一系列相关的短迭代，仍旧能够执行系统测试的子集。
Therefore, even though this agile release cycle consisted of a series of relatively short iterations, a subset of system testing was still able to be performed.
在敏捷的开发周期中加入系统测试子集的另一个优点是它促进较深入的系统测试应用程序开发和测试技能。
Another advantage of including a system test subset during the agile development cycle is that it fostered deeper system test application development and test skills.
敏捷的开发周期允许系统测试团队扮演实际的客户，从应用程序设计到系统测试应用程序的编码和单元测试。
The agile development cycle allowed the system test team to act like a real customer, from the application design right through coding and unit testing of the system test application.
维护成熟系统的条件通常对于敏捷方法来说也是成熟的。
The conditions for maintaining mature systems are often ripe for an Agile approach.
对于管理者们而言，既然你们选定持续的目标，并且致力于用敏捷或者精益来实现它，那么小心地逐步地把敏捷引入管理系统中也是可以的。
Managers, it's ok to dip your toe into agile for the management systems, as long as you take a coherent piece and commit to agile or lean for that piece.
最后，我们由我们的研究中得知，已经有许多公司采取品质导向的将敏捷式的系统开发方法，因此可以平顺地整合开发品质与使用者经验这两种工作。
Finally, we know from our research that many companies have made things work swimmingly — once they adapted the Agile methodology to suit quality-focused system development.
除此之外，敏捷配置管理方法还能够帮助新项目重复使用现有系统与项目的构建流程加快构建与运行的脚步。
Additionally, an Agile CM approach can help new projects get up and running faster by reusing build processes from existing systems and projects.
和敏捷软件开发一样，敏捷运维显然与那些“牛仔”管理员的方式不同，他们只会狂乱地管理系统而没有任何计划和文档。
Like agile software development, agile operations emphatically does not equate to cowboy administrators running amok on the systems, without plan or documentation.
当TasktopSync缓存构建完成后，测试系统中的变更会传递到敏捷工具中，反之亦然。
Once Tasktop sync builds up the cache, the changes in the test system are propagated to the agile tool and back.
面向遵循敏捷方法或开发低复杂度系统的团队。
Mixed modeling for less complex systems or teams following an agile approach.
对于大系统的可扩展的敏捷配置管理
受支持的设备数不胜数，您用于运行和安装ubuntu的方法很敏捷，这使得系统的使用毫无难度、甚至非常简单。
The myriad supported devices and the flexible way you can run and install Ubuntu make the system painless, and even unobtrusive, to use.
应用推荐