它还允许在最终完成的系统中实现更好的关注分离。
It also allows for an improved separation of concerns in the finished system.
体系结构本身充当将应用程序划分为反映关注分离的结构的主要机制。
The architecture itself serves as the primary vehicle for dividing the application into structures that reflect a separation of concerns.
然而，根据面向服务的准则构建的系统(如松散耦合和关注分离)总是会产生中间媒介。
However, systems that are built following principles of service orientation, such as loose coupling and separation of concern, will often introduce intermediaries.
因此，只要关注分离所需的抽象存在，我认为可以不使用任何特定的图书馆。
Therefore, as long as the separation of concern and required abstraction is present, I think it would be OK not to use any specific library.
此逻辑经常与表示信息交织在一起，即体系结构内没有清楚的关注分离，从而进一步限制了灵活性。
This logic was often interspersed with presentational information, meaning that there was no clear separation of concerns within the architecture, further restricting flexibility.
首先，我们建立了一个具有彻底的且可维护的、包含了恰当关注分离体系结构的应用程序。
First, we are building an application with a sound and maintainable architecture that involves proper separation of concerns.
ApacheCocoon：下载此框架并了解这个围绕关注分离概念构建的Web开发框架的更多信息。
Apache Cocoon: Download and get more information on this Web development framework built around the concepts of separation of concerns.
通常，在您计划如何为被测试应用的特性和行为进行分离和组织测试代码时，您将会使用关注分离这个基本原理。
Typically, you will use the separation of concerns principle when you plan how you will divide and structure your test code for application-under-test features and behaviors.
为了将传统方法开发的系统转换成面向方面的系统，实现关注分离，提出了一种从遗产系统中发现横切关注点的方法。
A novel method to discover crosscutting concerns from source-code for transformation from legacy system to Aspect-oriented system was proposed.
就实现具体的解决方案而论，将此功能放在单独的网关组件中可以支持进一步的关注事项分离。
Putting out this functionality into a separate gateway component supports further separation of concern when it comes to implementing a concrete solution.
通过SOA实现的关注事项分离甚至允许试验项目以能够积累专业经验和验证业务价值但不中断主要操作的方式引入SOA。
The separation of concerns possible with SOA lets even a pilot project introduce SOA in a way that allows building expertise and verifies the business value, but doesn't disrupt major operations.
通过抽象重要概念和分离关注的事项，软件体系结构可以降低复杂性。
Software architecture reduces complexity by abstracting key concepts, and separating concerns.
工程关注项的分离和集成。
但它是分离关注点的关键，我们在这些专栏中讨论过这个问题。
But that is the whole point of separation of concerns that we have discussed throughout these columns.
这篇教程将展示关注点分离的两个实现。
This tutorial will demonstrate two implementations of this separation of concerns.
通过相互分离接口保持关注点的分离。
Keep separation of concerns by separating the interfaces from each other.
服务规范仅定义外部特征，以维持服务使用者与服务提供者之间的关注事项分离。
The service specification defines only external characteristics to maintain separation of concerns between the service consumer and service provider.
可以利用这种关注点的分离分别测试横切规范及它们的行为。
You can leverage this separation of concerns to test their behavior separately from the crosscutting specification.
这意味着需要保持关注点分离，并且需要在部署单元内像调用一样分组。
This implies that you need to maintain separation of concerns and to group like calls within a deployment unit.
图1显示了开发工作站和最终生产环境之间的代码流，我们以此来说明关注点分离的概念。
Figure 1 illustrates the separation of concerns concept by showing the flow of code between the development workstation to final production.
最后，委派逻辑通常会得到更干净的关注点分离。
Finally, delegating logic often leads to a cleaner separation of concerns.
将应用程序划分为层，这是一种在体系结构中关注点分离的基本技术。
Dividing the application into tiers (or layers) is an essential technique for separating concerns within the architecture.
它提高了我们对于一个设计良好的、可维护的软件系统所需的、关注点分离的表达能力。
It enhances our ability to express the separation of concerns necessary for a well-designed, maintainable software system.
MVC最重要的就是合理的分离关注点。
我们所指的关注点分离阶段是指使用不同的环境控制组成部署发布版本的代码流和其他文件。
By the phrase separation of concerns we mean the use of different environments to control the flow of code and other files that make up a deployment release.
实际上，除了规模大小有区别外，面向对象语言中对象之间的关注点分离与模块化的概念基本一致。
In fact, the kind of separation of concerns between objects in an OO language is much the same concept as for modules, except on a larger scale.
MVC模式天生就是可测试的，而且鼓励对关注点的分离。
By nature, the MVC pattern is highly testable and encourages good separation of concerns.
业务集成得益于强制关注点分离集成数据和应用程序以满足业务要求。
Business integration benefits from an enforcement of separation of concerns to integrate data and applications as appropriate for business needs.
通过关注点分离，可以将集成需求分解为更细粒度的服务。
Through separation of concerns, integration requirements are decomposed into more granular services.
体系结构可以分离关注事项，并单独地对它们进行处理，同时确保它们不会相互冲突。
Architecture separates concerns and addresses them separately, while at the same time making sure they are not conflicting.
应用推荐