描述未密封类的设计准则。
在类的设计中包括调试策略经常是有用的。
It is often useful to incorporate a debugging strategy into the design of our classes.
只有3个其他类使用这个类，这说明不值得花费大量时间改进这个类的设计。
Only three other classes use this class, which suggests it's not worth investing lots of time improving the class's design.
这个原理声称一个类的设计者和这个类的使用者，共同分享关于类的实现的假设。
This principle asserts that the designer of a class and the user of that class share assumptions about the class implementation.
应用实例表明，控件的属性类的设计必须考虑其应用的透明性和修改的封装性。
The example shows that the design of control property class must be considered its application transparence and modification seal.
契约式设计让类的设计者专注于实现了类的功能性的逻辑，而不用担心实参的有效性。
Design by Contract lets the class designer concentrate on the logic that implements the class functionality without worrying about the validity of arguments.
然后在介绍了分层网络数据包的类型及结构的基础上，给出数据包分析处理类的设计。
Then, It introduces the types and structures of packets and presents the design of packet analysis class.
基本小部件类的设计利用了Dojo提供的继承特性，以下是基本小部件实现的一些功能。
The base widget class has been designed to take advantage of the inheritance feature provided by Dojo. Following are some of the functions the the base widget implements.
该方法用COOZ描述类的设计规格说明，实现了从形式化需求描述到形式化设计的平滑过渡。
We use COOZ to describe design specification of classes. Therefore, the formal requirement specification can transfer to formal design smoothly.
要清理Struts代码库中多个类的设计，一种方法就是意识到这种惯用模式的存在并巩固这一行为。
One way to clean up the design of multiple classes in the Struts code base is to realize that this idiomatic pattern exists and consolidate that behavior.
这还不利于域类的设计，因为这个实用类现在必须位于对象层次结构的顶层，不允许您使用继承来整合常见行为。
It also hurts the design of your domain classes because this utility class must now sit at the top of your object hierarchy, not allowing you to use inheritance to consolidate common behavior.
公共空间是民生类的设计，我需要花更多的时间去思考设计以外的一些诸如社会学，人类学，甚至历史等问题。
The public space design is the design for people's life, so I need to spend more time to think about something besides the design, such as sociology, anthropology, and even history.
在流程执行模块中，本文主要研究了工作流实例的运行原理和引擎执行的设计、关键类的设计、并发聚合路由算法设计。
In the process execution model, the workflow instances execution principles and engine execution design, the design of the key classes and the parallel assembly routing algorithm are researched.
在此之中笔者产生了关于海报作品审美以及如何设计谋划的疑问，诸如“图像时代下，视觉类的设计是如何被审美的?。
Some doubts on how to judge those posters come out like:how did those visual works be judged in this image era?
似乎游戏中有剧情解释一类的设计，但是据我所知还真没人关心过这个剧本——看剧情，意味着晋级下一关的时间要被耽误了。
There is some kind of plot that explains all this, but nobody I know has ever bothered to pay attention to it, because that would delay the arrival of the next level.
如图1所示，每个问题都提示架构师：这是一类特定的设计问题，需要作出架构决策。
As Figure 1 shows, an issue informs the architect that a particular design problem exists and requires an architectural decision.
但在高级别上，他们关于“定义设计类”的工作流会基本上保持不变。
But at a high level their workflow related to "define design classes" will largely remain the same.
目前使用的类有几个设计缺陷。
每个类为不同的场合进行设计和优化。
Each of these classes has been designed and optimized for use in different situations.
从用例到设计类的转化。
推动基于架构的设计(uml——类图)。
Driving design based on Architecture (UML — Class diagrams).
这不是直接的映射，我们正在做出一个关于如何指定子系统和类中表现功能的设计决策。
This is not a direct mapping; we are making design decisions about how the functionality represented in the subsystems and classes will be allocated.
原型的一些方面(类的说明、设计模式或者编码习惯)也许可以被重用，但是我们在重用这一点上给团队非常小的压力。
Some aspects of the prototype (class specifications, design patterns, or coding idioms) might be able to be reused, but we placed very little pressure on the team to consider reuse at this point.
现在我们可以理解这条非常重要的表述了：你发现和使用的设计类依赖于你采用的设计方法。
Now we can appreciate this very important statement: the design classes you discover and use will depend on the design approach you take.
其中一部分是因为类能做的超出了您真正需要的，与只为一种用途设计的类相比，它们会产生更多的开销。
Partly because the classes usually do more than you actually need, they impose more overhead than a class designed for one purpose only.
一旦我们确定了我们的类的职责，我们就可以设计一个分析类图，来描述类间关系的整体结构。
And once we identify our class responsibilities, we should construct an analysis class diagram to capture the structure of the relationships among our classes.
从用例和分析类到设计和设计类的转化是不可避免的模糊的。
The transition from use cases and analysis classes to design and design classes was unavoidably blurry.
用例实现会议应该生成主要的输出工件，软件开发过程常常提出由交互和设计类图组成的设计模型。
Use-case realization sessions should produce a main output artifact; software development processes often suggest a design model composed of interaction and design class diagrams.
它为在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.
它为在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.
应用推荐