将自适用性的理念引入软件工程领域，以期缓解业务变更频繁带来的设计矛盾。
The article introduces the idea of self-applicability into software design to account for the problem.
规划要求一个更复杂的管理组织，这是因为它们包括基本的业务变更和重要结果影响的支出。
Programs require a more complex governing structure because they involve fundamental business change and expenditures with significant bottom-line impact.
例如，我曾工作过的一个团队，有一个关于在计划产品开发跌代期间如何处理业务变更的问题。
For example, one team I worked with had an issue of how to handle operational change requests that came in during their planned product development iterations.
无业务价值的的变更只是消耗资源，几乎没有回报。
Changes with no business value simply eat up resources with little reward.
变更业务需求将迫使你的服务演变，这应该驱使你在你的SOA架构和设计实践中包含服务生命周期管理(SLM)。
Changed business requirements will compel your services to evolve, which should cause you to include service Lifecycle Management (SLM) capabilities in your SOA architecture and design practices.
同样，有业务价值的变更也可能因为对现有的需求、设计、编码和测试影响过大而得不偿失。
Similarly, changes that do have business value but would also have great impact on existing requirements, designs, code, and tests may not be worth the effort.
灵活地处理未来的变更，支持更有竞争性的业务。
Agility to handle future change and support a more competitive business.
开发组织可以在业务环境中更迅速的响应变更。
The development organization can react more quickly to changes in the business context.
将应用程序定义为服务的集合，可帮助进行重用和减少与添加新业务服务相关的变更影响。
Defining your application as a collection of business services AIDS reuse and reduces the impact of the change associated with adding new business services.
可以采用各种各样的方法来自动化变更过程，并为业务用户提供对这些变更最大限度的控制。
There are various ways to automate the change process and give utmost control of these changes to business users.
它必须允许应用程序逐渐提高其模块化程度，并能简化管理和支持业务中的变更所需的底层IT基础设施。
IT must allow applications to become increasingly modular, and simplify the underlying IT infrastructure required to manage and support changes in the business.
公司需要关注于组织变更对业务能力的影响，以保持在市场中的竞争力。
Businesses need to focus on the impact of organizational changes on business capabilities in order to stay competitive in the market.
如果公司决定改变业务方向，随之而来的系统变更需求将令人痛不欲生。
If the business needs to change direction there's often a very painful change request system put in place.
可适应性——增加对业务用户提出的小型变更的实现来支持短期需求，同时仍然控制在强有力的IT管理范围内。
Adaptability - Increased enablement of small changes by Business users to support short term needs, whilst still controlled within strong it governance.
对于有效的测试管理来说，必须有对于最新系统变更和业务需求的无缝接口。
For test management to be effective, there must be seamless access to the latest changing system and business requirements.
您的主要目标是创建提高生产力的复合应用程序，但是我们都知道，应用程序不是静态的，并且必须总是随业务需求的变更而变化。
Creating a composite application that increases productivity is your primary goal, but we all know that applications are not static and must always adapt to the changing needs of business.
通过集中开发基础，公司可以快速响应变更的业务需要和范围以及源项目，同时降低开发的总体成本。
By centralizing the development infrastructure, organizations can rapidly respond to changing business needs and scale and source projects, while lowering the total cost of development.
数据结构必须在严格的变更控制下，以便于可以适当地管理各种业务和系统牵连的变更。
Data structures must be under strict change control, so that the various business and system implications of any change can be properly managed.
对于许多企业来说，他们不确定如何进行那些变更，那些变更对业务有什么影响，更重要的是，从哪里开始过程。
For many it's the uncertainty of how to make those changes, what impact those changes will have on their business, and most importantly, where to begin the process.
对于已经拥有变更管理产品的组织来说，几乎业务的每个方面都可能拥有软件变更管理过程。
For organisations that already have a change management product, nearly every aspect of a business is likely to have involvement with the software change management process.
使用简单的声明性sql语句，您可以维护数据库变更的历史，跟踪有效的业务日期，以及分析变更历史。
With simple declarative SQL statements, you can maintain a history of database changes, track effective business dates, and analyze the history of changes.
实现工作的重点是接口变更和业务逻辑变更，从而最大化地对未变更逻辑进行重用。
The implementation effort focuses on the interface changes and business logic changes, maximizing the reuse of unchanged business logic.
您的公司能够实现新的计划来支持业务策略中的变更的程度称为业务敏捷性。
The degree to which your company can implement new initiatives to support changes in business strategy is known as business agility.
精益治理可以由灵活的架构来实现，因为它们使开发团队对业务的变更的需求进行有效地反应。
Lean governance is enabled by flexible architectures because they enable development teams to react effectively to the changing needs of the business.
这些变更是由各种因素驱动的，比如业务扩张、合并、竞争压力、成本缩减、策略变更等等。
Changes are driven by various factors like expansion of business, mergers, competitive pressure, cost-cutting, policy changes, and more.
变更计划还应该提供控制对业务过程的破坏程度的控制，并且评价变更的积极影响。
Change initiatives should also have measures to control the degree of disruption to business processes and assess the change's positive impact.
如果报告表明，业务需求中的变更很重要，需要合并IT技术并演进IT治理及业务目标的话，生命周期就会进行迭代。
The lifecycle makes an iterative round if the reports show the changes in business requirements are significant to keep up with the merging it technology and evolving it governance and business goals.
最坏的情况是，在变更实施到业务环境之前，这个变更已经不符合当前的业务需求了。
In the worst cases by the time the change was rolled out the business environment had changed and the change no longer met the current business need.
它们只在业务需求变更时才发生变更。
迭代开发强调了在业务需求变更、尽早测试，以及在原型化阶段更深层次的让客户参与进来方面进行持续的结合。
Iterative development emphasizes continuous alignment with changing business requirements, early testing, and deep client involvement in prototyping and beyond.
应用推荐