从用例到设计类的转化过程是缓慢的，需要进行多次的迭代。
The migration from use cases to design classes was slow, requiring a number of iterations.
如果没有坚实的面向对象设计基础，我们很快就会迷失在对象、关系和类的世界里。
Without a solid background on object oriented design, we can quickly get lost in a world of objects, relations and classes.
但在高级别上，他们关于“定义设计类”的工作流会基本上保持不变。
But at a high level their workflow related to "define design classes" will largely remain the same.
当设计的内聚力较低时，它就不能良好地组织类和方法。
When a design has low cohesion, it has classes and methods that are not grouped well.
作为抽象的主要方法，类的使用在面向对象框架设计中是很关键的。
The use of the class as the primary means of abstraction is key to object-oriented framework design.
欧洲造船厂擅长设计电缆铺设船和其他服务类船只。
Europe’s shipmakers are adept at designing cable-laying ships and other service vessels.
如果方法和类都具有高度的内聚力，则可以轻松地分解整个组而不影响设计。
If methods and classes are highly cohesive, you are able to easily split off entire groups without affecting the design.
设计细粒度的类层次和粗粒度的数据表。
Design fine-grained class hierarchy and coarse-grained database tables.
在设计类中软件架构文档(SAD)内容的实现。
Realization of the Software Architecture Document (SAD) content through the design classes.
架构师对系统层类进行改进以设计业务层接口。
The architect refines the system-level classes to design the business-layer interface.
UML类图设计为一种可直接阅读的形式。
UML class diagrams are designed to be straightforward to read.
当您考虑使用设计模式时，您就需要了解类之间如何进行交互。
When you think in design patterns, you're forcing yourself to be aware of how classes interact with each other.
上述设计没有区分这两类通知，但是或许我们应该区分。
The designs above don't make a distinction between these two types of notifications, but perhaps we should.
目前使用的类有几个设计缺陷。
每个类为不同的场合进行设计和优化。
Each of these classes has been designed and optimized for use in different situations.
开发者可以使用类图，来设计并为系统的代码(或即将成为代码的)类写文档。
Developers can use class diagrams to design and document the system's coded (or soon-to-be-coded) classes.
现在，控制器类是设计实现系统商业逻辑填充的一个或多个类的位置保持器。
For now, a controller class is a placeholder for one or more classes that would be fleshed out during design to implement the business logic of your system.
从用例到设计类的转化。
推动基于架构的设计(uml——类图)。
Driving design based on Architecture (UML — Class diagrams).
现在我们可以理解这条非常重要的表述了：你发现和使用的设计类依赖于你采用的设计方法。
Now we can appreciate this very important statement: the design classes you discover and use will depend on the design approach you take.
这个原理声称一个类的设计者和这个类的使用者，共同分享关于类的实现的假设。
This principle asserts that the designer of a class and the user of that class share assumptions about the class implementation.
设计网页的时候经常会遇到这样的情况：一个类可能除了自己的样式外，还需要其他类的所有样式。
There are often cases when designing a page when one class should have all the styles of another class, as well as its own specific styles.
给规类为概念设计分类活动是系统分析与系统设计的常见活动。
The activities categorized as conceptual design are the usual activities of System Analysis and System design.
一旦我们确定了我们的类的职责，我们就可以设计一个分析类图，来描述类间关系的整体结构。
And once we identify our class responsibilities, we should construct an analysis class diagram to capture the structure of the relationships among our classes.
详细的ESB设计和配置又引起另一类问题。
The detailed ESB design and configuration trigger another set of issues.
它为在php中进行高级的面向对象编程敞开了大门，并允许实现更加简单的设计模式，以及更好的设计类和API。
It opened the door for advanced objected-oriented programming in PHP, and allowed you to implement many design patterns much easier, along with better design classes and APIs.
我所说的不是早期设计文档，甚至也不是更为详细的设计文档；我说的是记录类上的各个方法和属性。
I am not talking about the early design documents, or even the more detailed design documents; I am talking about documenting individual methods and properties on classes.
从用例和分析类到设计和设计类的转化是不可避免的模糊的。
The transition from use cases and analysis classes to design and design classes was unavoidably blurry.
这与我们软件设计中的分类有点相似，它在其它类中调用方法。
This is somewhat analogous to classes in our software designs that call methods in other classes.
这个新特性使类设计人员可以保证对类的内在特性的控制，同时告诉类的使用者哪些类可以而哪些类不可以触及。
This addition allows class designers to retain control over the internals of their classes while expressing to the client of the class what he should or should not touch.
应用推荐