OK, a lot of keys, but it's still easier to change software than a suspension bridge.
是的，有很多键，但改变软件仍然要比建一座吊桥容易。
In the wireless communication environments, the radio software download can dynamically change software inside the devices, whereas itself is a quite complicated procedure.
在无线网络环境中，无线电软件下载能够动态地更新设备软件，然而它本身是一个非常复杂的过程。
Our software should also reflect this change.
我们的软件也应该反映这种变化。
Then the way we write software will change, yet again.
届时我们编写软件的方式将会改变，再一次。
Fourth, customers have to change the way they think about software.
第四，客户必须改变他们考虑软件的方式。
Certainly, many of our software projects do change rapidly and move quickly, but not all of them.
当然，我们的软件项目变化是很快，但并不是所有的都是这种情况。
Lately I've gotten interested in an area that I think has the potential to create the next fundamental change in software development: collaboration and creativity support.
最近我对一个领域产生了兴趣，我认为该领域有潜力创造软件开发中的下一个根本的改变：协作和创造力支持。
How would change in software development capability impact business results?
软件开发能力的改变如何影响商业结果？
Even worse, some companies allow their business process to change to accommodate the software.
更糟糕的是，一些公司还允许改变他们的业务流程来适应软件。
A new piece of software may change this.
一款新软件也许会改变这种状况。
A small change can provoke software to break in a surprising manner and at the worst of the moments.
即使一个细微的变化，都会导致软件在最糟糕的时刻以令人莫名惊诧的方式而停止运转。
This introduces the one constant in software analysis and design: change.
这引入了软件分析和设计中的一个常量：变更。
However, because business environments can change quickly, software requirements ought to follow.
然而，由于业务环境可能快速变化，软件需求也应当如此。
Had I tried to fundamentally change how everyone writes software, I'm sure I would have failed.
我曾经试着根本性地改变人们编写软件的方式，但我确信我失败了。
Software is going to change so many fields.
软件会改变如此多的领域。
We lowered our cost of change by always building less software.
我们总是构建更少功能的软件，以此减小变化的代价。
This includes defect and change tracking along with software asset management.
这包括在软件资产管理中的缺陷和变更跟踪。
DNA is the software of the cell, and our studies have shown that when we change the software we change the species.
DNA相当于细胞的软件。我们的研究证明了当软件(也就是DNA)被改变的时候，生物种类也会相应改变。
Testers must revise these documents as developers change the software being tested.
当开发人员改变在测软件时，测试人员就必须修改这些文档。
It is about creating the kind of organizational change necessary to produce great software.
它是关于为了生产优秀软件所需创建的某种组织性变革。
For example, if you know that a software change request from marketing will make a piece of software used in sales obsolete, then you need to explain that in those simple terms.
例如，如果您知道某个来自市场部门的软件变更请求会使销售部门使用的某部分软件过时，您需要以简单的术语解释这种情况。
Also, search for detours around writing more software. Can you change the copy on the screen so that it suggests an alternate route to customers that doesn't require a change in the software model?
同时，寻求避免多写软件的招数。你可以向客户建议其它的替代路线，能否通过改变屏幕上的拷贝，而不需要改变软件模型？
In contrast, customization requires the development of additional code (in a programming language) to extend and change a software component in order to support a specific a "custom" behavior.
相反，自定义要求开发额外的代码(使用编程语言)来扩展和更改软件组件，以支持特定的“自定义”行为。
Don't try to describe what the software change will specifically do, just leave it at something like, "Changing this software will result in an increased expense for sales."
不要尝试描述该软件变更会明确地做什么，只需使用类似如下的说明：“更改此软件将导致销售开支上升。”
But if you get it wrong, you've only added complexity that makes it more difficult to change your software. You're obviously not getting the payback.
但如果你的预期是错的，那么你所引入的复杂性将使软件变得更加难以改动，因而该灵活性是毫无意义的。
Why then not also make the software that powers the change management for your software subject to change management?
那为什么不用增强变更管理的软件也处于变更管理之下呢？
A precooked meal is hard to change, and so are traditional software applications.
预煮的饭菜是很难更改的，而传统的软件应用也是如此。
Add functionality to support all the steps of the software change lifecycle.
添加功能以支持软件变更周期的所有步骤。
Avoiding change is both difficult and undesirable in software.
在软件中避免更改很困难且没有必要。
应用推荐