Among the specific benefits associated with agile system test efforts were the following.
以下是与敏捷的系统测试工作相关的具体好处。
The diverse requirements of market or customer lead to the birth of the agile system.
敏捷系统是市场和客户的需求快速变化的产物。
Following are some of the most important challenges faced in the course of agile system test activities.
以下是在敏捷系统测试活动中面临的一些最重要的挑战。
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.
一般来说，在敏捷的开发周期中对系统测试缺陷的开发关注较多。
Agile iterations, which are usually one to six week time boxes where a working subset of the system is built, is rarely adopted.
敏捷迭代提出的使用一到六个周的时间盒来构建一个可运行的部分系统的要求，很少得到采纳。
Where as operating system virtualization provides special benefits for agile development as it can provide on demand resource with out effecting existing operations.
操作系统虚拟化对于敏捷开发尤其有好处，因为它可以在不影响现有操作的情况下按需提供资源。
It's forgotten because most Agile teams assume that every project has a source control system and that every project USES it correctly.
它常常被忘记是因为大部分敏捷团队假定每个项目都会有一个源代码控制系统，并且每个项目都会正确的使用它。
It looks more like Kanban in factories than Agile Kanban does and it can be a pull system by making a rule to allow only the downstream process to move the CARDS 8.
它比敏捷看板看起来更像工厂中的看板，而且通过制定规则只允许下游工序移动卡片8，可以使其成为拉动式系统。
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.
敏捷的开发周期允许系统测试团队扮演实际的客户，从应用程序设计到系统测试应用程序的编码和单元测试。
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.
本文介绍了团队所采用的将一组系统测试子集作为敏捷开发环境的一部分，并与代码开发活动并行的方法。
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.
开发团队为了响应一个易变的环境必须越来越敏捷，在这种环境中，在一个满足涉众需求的系统能够被部署之前，需求可能经常发生变化。
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.
敏捷的开发周期的迭代特性令系统测试团队以较小的且更容易消费的规模在较长的时间内理解产品。
Our agile coaches were able to redirect our thinking to focus on what is important now rather than trying to design the entire system and predict a rigid project plan.
我们的敏捷教练指出我们应考虑把注意力集中在当前重要的事上，而不是试着设计整个系统并制订一个严格的项目计划。
To reiterate, just because a project or organization has a source control system does not mean that that system will support an Agile CM approach.
重申一下，仅仅因为项目或组织具有源代码控制系统不意味着系统支持敏捷配置管理方法。
We began our SOA project, designed to re-engineer our servicing system, using agile in late 2005.
在2005年下半年，我们开始了SOA项目，用敏捷方法设计并重构我们的服务系统。
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.
在敏捷的环境中，系统测试更容易检验修补，由于缺陷周转时间较快，并且由于准确的测试环境仍旧适当。
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.
最后，我们由我们的研究中得知，已经有许多公司采取品质导向的将敏捷式的系统开发方法，因此可以平顺地整合开发品质与使用者经验这两种工作。
In this article, I'll look at some of the impediments to adopting agile operations and some ways you might be able to work the system.
本文中，我会和你一起讨论采用敏捷运维的障碍，以及你可以使其发挥作用的一些方式。
This type of centralized build system is widely adopted by agile software teams to make sure that the source code in the repository is always tested and in a releasable state.
这种类型的集中生成系统被灵敏软件团队广泛采用，以便确保总是测试库中的源代码且该代码处于可释放状态。
To avoid this situation, agile projects typically "stage" and re-use pre-built binaries, and only rebuild the whole system when necessary (for example, nightly or weekly).
为了避免这种情况，敏捷项目“执行”并再利用预构建好的二进制码，并且只有再必要时重新构建整个系统(例如，每夜或每周)。
But the reality is the Eclipse project is an Agile project, and that's hundreds of developers worldwide working on a complex system.
但是实际情况是，Eclipse项目就是一个敏捷的项目，全世界有数百位开发人员工作于一个复杂的系统。
In a recent discussion on the Agile usability group, members discuss various ways for evaluating system usability.
最近，在AgileUsability邮件组中，成员讨论了各种方法来评价系统的可用性。
Once Tasktop sync builds up the cache, the changes in the test system are propagated to the agile tool and back.
当TasktopSync缓存构建完成后，测试系统中的变更会传递到敏捷工具中，反之亦然。
Agile heavily relies on executable artifacts - i.e. the tests written (both unit and system).
敏捷非常依赖于可执行的的工件，例如：编写好的测试(不管是单元测试还是系统测试)。
A core system test team working closely with development in an agile environment offers significant potential benefits to the development organization.
在敏捷的环境中，与开发密切合作的核心系统测试团队向开发组织提供了重大的潜在好处。
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.
因此，即使敏捷的版本周期包含一系列相关的短迭代，仍旧能够执行系统测试的子集。
This paper starts with summarizing the characteristic of assembly CAPP for Agile Manufacturing, and analyzes in detail the demands of function, performance, information of the system.
本文从总结敏捷制造环境下装配CAPP的特点入手，对系统的功能需求、性能需求和信息需求进行了详细分析。
应用推荐