MVC is all about proper separation of concerns.
MVC最重要的就是合理的分离关注点。
Separation of Concerns and Configuration files.
关注点分离和配置文件。
A key characteristic of an ESB is separation of concerns.
ESB的关键特性是分离关注点。
Keep separation of concerns by separating the interfaces from each other.
通过相互分离接口保持关注点的分离。
Finally, delegating logic often leads to a cleaner separation of concerns.
最后，委派逻辑通常会得到更干净的关注点分离。
It also allows for an improved separation of concerns in the finished system.
它还允许在最终完成的系统中实现更好的关注分离。
Separation of concerns refers to extracting the code into various layers
关注点分离指把代码提取到不同的层
Separation of concerns simplifies integration architecture implementation.
关注点分离简化了集成体系结构的实现。
This tutorial will demonstrate two implementations of this separation of concerns.
这篇教程将展示关注点分离的两个实现。
One of the goals of leveraging an Enterprise Service Bus (ESB) is separation of concerns.
利用企业服务总线(Enterprise Service Bus,ESB)的目标之一是关注事项分离。
This yields a true separation of concerns, enabling the repurposing of software components.
这就产生了关系的分离，使软件组件可以被重用。
By nature, the MVC pattern is highly testable and encourages good separation of concerns.
MVC模式天生就是可测试的，而且鼓励对关注点的分离。
Respecting separation of concerns, even if initial size of the two concerns is rather unequal.
注重关注点分离，即使两个关注点的初始大小差别很大。
But that is the whole point of separation of concerns that we have discussed throughout these columns.
但它是分离关注点的关键，我们在这些专栏中讨论过这个问题。
It is designed to create a separation of concerns between application protocols and security protocols.
它用于创建应用程序协议和安全协议之间的分离关系。
Through separation of concerns, integration requirements are decomposed into more granular services.
通过关注点分离，可以将集成需求分解为更细粒度的服务。
So, Scala traits preserve separation of concerns while giving us the ability to compose behavior on demand.
所以，Scalatraits在保留分离关键点的同时给了我们按需整合行为的能力。
In a Web service implementation, the services can delegate to the controller for proper separation of concerns.
在Web服务实现中，服务可以委托给控制器，以对有关方面进行恰当的分离。
You can leverage this separation of concerns to test their behavior separately from the crosscutting specification.
可以利用这种关注点的分离分别测试横切规范及它们的行为。
And with this natural separation of concerns, the back-end work will either be outsourced, or it will be automated.
并且通过这种关系的自然分离，后面的工作将要么是外包的，要么可以自动化。
As a result, the concept of separation of concerns is the foundation to the definition of the integration services.
因此，关注点分离的概念是定义集成服务的基础。
This implies that you need to maintain separation of concerns and to group like calls within a deployment unit.
这意味着需要保持关注点分离，并且需要在部署单元内像调用一样分组。
This separation of concerns means you can change one component with zero to minimal impact on other components.
采用关注点分隔原则意味着，对一个组件的修改对其他组件的影响非常小，甚至没有影响。
This functionality enables you to implement one of the key characteristics of an SOA-based ESB: separation of concerns.
这一功能性使您能够实现基于soa的esb的主要特性之一：分离业务。
This approach is a variation of the separation of concerns principle embodied in the Model-View-Controller architecture.
这种方法是分离关注点原则的一个变种，附在模型-视图-控制器架构中。
It enhances our ability to express the separation of concerns necessary for a well-designed, maintainable software system.
它提高了我们对于一个设计良好的、可维护的软件系统所需的、关注点分离的表达能力。
Separation of concerns is fundamental to well-structured code, because it encapsulates responsibilities and dependencies.
关注点分离是实现具有良好结构的代码的基础，它封装了责任和依赖关系。
Each layer performs a clearly defined role that allows for easy separation of concerns, and work, among our team members.
每个层执行一个定义清楚的角色，使得小组成员之间可以很容易地分工。
But decoupling, separation of concerns, reuse, and agile solutions are fundamental to SOA, and getting them isn't always easy.
但是去耦合性、关注的分割、复用和敏捷的解决方案是SOA的基础，并使得它们并不总是那么容易。
The three primary goals of MDA are portability, interoperability, and reusability through architectural separation of concerns.
MDA的三个首要目标就是通过关注点的架构分离的可移植性、互操作性和可重用性。
应用推荐