In fact, the concept of reuse has been well understood and leveraged right from the day of object orientation (OO).
事实上，重用的概念从面向对象（OO）诞生的那天起就已经被人们很好的理解并应用。
I also mention in my book that when we use the OO paradigm, it is not easy to represent graphically at all times where our application is.
在书中我还提到，当我们使用OO范式的时候，要在任何时间图形化地表示出我们的应用程序在哪里并不容易。
It is the solo portion"East St. Louis Toodle-Oo".
它是“东圣路易斯再见”的独奏部分。
As far as I'm concerned, this is the best of all possible worlds — I like the oo goodness of being able to ignore cleanup, but I don't like the discipline of writing oo code straight through.
就我所知，这是所有当中最好的——我喜欢面向对象的好处，因为它可以忽略清除。但是我并不喜欢要从头到尾写面向对象的代码的规定。
Modularity - one of the key characteristics of good oo design - helps with this maintenance.
模块化—优秀OO设计的主要特性之一—可以帮助完成这样的维护。
This is partly why the issue of "impedance mismatch" appears so important to a lot of OO people.
这就是为何“阻抗失谐”问题对于许多OO人员来说显得如此重要的部分原因。
In OO systems, though, even objects that you think of as passive have responsibilities and operations defined on them.
而在OO系统里，即使被认为是被动的对象也有定义于其上的职责和操作。
However, OO still is a valuable approach for design of the underlying class and component structure within a defined service.
然而，对于设计已定义的服务中的底层类和组件结构，OO仍然是一种有价值的方法。
And there is no obvious problem in power, since you can always do class-based OO by convention, if you want.
从功能上来说这没有什么明显的问题，只要你想，你总可以根据规约实现基于类的OO。
As we'll see in upcoming columns, the process of OO design is really a form of semantic analysis.
正如我们要在即将出现的专栏中所见，OO过程实际上是一种语意分析形式。
OO development focuses on incremental development of applications, implementing one business scenario or use case at a time.
OO开发集中于应用程序的渐进式开发，每次实现一个业务场景或用况。
Typically, however, using good oo habits pays off in the long run, as future changes are greatly solidified.
但是，通常，使用优秀的OO习惯从长远来看十分划算，因为将极大地巩固未来更改。
A crosscutting concern, when implemented in a traditional OO approach, cuts across many classes and methods.
一个横切关注点，在用传统OO方法实现时，会分解成很多类和方法。
For example, when we re-implement design patterns using AOP, are they any better than the standard OO patterns?
例如，当我们使用AOP重新实现设计模式时，它们要比标准的面向对象模式好一些吗？
It builds upon the OO paradigm by addressing situations where the OO approach does not adequately provide the most desirable solution.
它通过处理许多面向对象方法不能充分提供最合适方案的情形，构建了面向对象的范例。
OO is a well-established paradigm familiar to the majority of developers.
OO是被大多数开发者所熟悉的行之有效的范式。
Most of the traditional OO systems and programs consist of business objects manipulating hierarchies of domain data objects.
大部分传统OO系统和程序都包括对领域数据对象的层次结构进行操作的业务对象。
For example, applying general software architecture principles and OO techniques is a valid start in any SOA effort.
例如，在任何SOA工作中，应用通用的软件体系结构原则和OO技术都是一个有效的开端。
While services appear to be (on the outside) very large-grained distributed objects, they can, in fact, be implemented in any of a number of ways, in both OO and non-OO languages.
虽然服务看起来(从表面上)是非常大粒度的分布式对象，然而，它们实际上可以用面向对象或非面向对象语言通过几种方式中的任何一种来实现。
Recorded scripts are often long and written in proprietary languages lacking object-oriented (OO) language features.
记录的脚本通常很长，且用专用语言编写，缺乏面向对象(OO)的语言特性。
This does not exclude the OO viewpoint adopted by RUP, but rather implements another layer of abstraction above it.
这并没有排除RUP采用的OO观点，而是在其上实现了另一个抽象层。
To successfully apply OO analysis to SOA projects, you must examine more than one system at a time.
要将OO分析成功地应用于SOA项目，您就必须一次分析多个系统。
I think class based OO have to be learned, and that most people will find prototype based OO more intuitive once they unlearn the class based OO mantra.
我觉得基于类的OO是需要学习的，而大多数人都会发现基于原型的OO更加直观，前提是他们并没有被人灌输基于类的OO的所谓优点。
I actually think that prototype based OO is more natural, and easier to understand than class based OO.
实际上我认为基于原型的OO要比基于类的OO更自然，也更容易理解。
See Resources for more on this way of looking at OO systems.
有关以这种方式考虑OO系统的更多信息，请参阅 参考资料。
Unlike the OO paradigm, this model does not represent a functional system.
与OO范式不同，这个模型并不表示功能系统。
When I was first learning about OO concepts, I was doubtful that interfaces were really helpful.
在我最初了解OO概念时，我十分怀疑接口是否真正有帮助。
OO analysis is a very powerful and proven approach, and as such, SOAD should make use of OO analysis techniques as much as possible.
OO分析是一种非常强大且广为赞誉的方法，同样，SOAD应该尽可能多地利用OO分析技术。
The subjects were asked to make four repeated sounds –“oo”, “ah”, “eh”, and “ee”.
研究要求试验参与者重复发出“哦”、“啊”、“嗯”和“咦”四种声音。
Another interesting subject in OO is object persistence.
OO中另一个有趣的主题就是对象持久性。
应用推荐