SCA将业务逻辑中有关访问技术、实现和协议的大量细节移动到中间件层中。
SCA moves many of the details of access technology, implementation, and protocols to the middleware layer - away from the business logic.
然而，只是简单的将二者分离开无法实现有效的功能，还需要加入一个间接层以连接并协调表现层与业务逻辑层。
However, keeping the two isolated does not serve any useful purpose. It also suggests adding a layer of indirection to join and mediate between presentation and business logic layers.
SCA包含大量有关访问技术、实现和协议的细节，并将它们从业务逻辑转移到中间件层。
SCA takes many of the details of access technology, implementation, and protocols, and moves them into the middleware layer away from the business logic.
控制器层负责实现服务的业务逻辑，具体通过调用其他服务、其他控制器或实体管理层实现。
The controller layer is responsible for implementing the business logic of the service, achieved by invoking other services, other controllers, or an entity management layer.
封装——存储过程是实现最低的业务逻辑层的好方法。
Encapsulation — Stored procedures are a good means to implement the lowest layer of business logic.
CICS和IMS应用程序的一个最佳实践是将3270UI支持从业务逻辑拆分出来，然后使用消息接口实现这两个层间的耦合。
A best practice for CICS and IMS applications is to split the 3270 UI support from the business logic, then couple these two layers using the message interface.
此外，由于将来可以使用新的REST和mvc框架，实现它们变得更加容易，无需重写业务逻辑层。
In addition, as new REST and MVC frameworks become available in the future, it is easier to implement them without rewriting the business logic layer.
逻辑视图中的三个软件层(表示层、业务层和数据层)是以代码形式被物理实现，并部署到这些节点上。
The three software layers in the logical view (presentation, business, and data) are physically implemented as code and deployed onto these nodes.
目标是适当地分离与应用程序每一层相关的问题 ——也就是，业务逻辑仍旧在实现层，UI 在用户界面层，等等。
The goal was to have a proper separation of concerns for each layer of the application -- i.e., the business logic remains in the implementation layer, the UI in the user interface layer, etc.
ExposedBusinessservices层通常只实现最少的业务逻辑。
The Exposed business Services tier typically implements minimal business logic.
只要command实现的输入输出保持不变，业务逻辑中的更改不必去影响Web服务实现层。
As long as the inputs and outputs of the command implementations remain constant, changes in business logic do not need to impact the Web services implementation layer.
从业务逻辑层中解耦browserRequestHandler和Resource Request Handler有助于促进代码重用，并能实现灵活和可扩展的架构。
Decoupling the Browser Request Handler and Resource Request Handler from the business logic layer helps facilitate code reuse, and leads to a flexible and extensible architecture.
数据接口层(DataAccess Layer)利用WPF实现UI组件对业务逻辑和数据组件的绑定。
The data Access Layer utilizes WPF data binding to tie UI components to business logic or data components.
本文以自己实现的IOC容器进行系统分层，更好地把业务逻辑抽取出来单独成为一层。
This thesis tiers system with own implementation IOC container and it extracts business logic into one separate layer.
EJB是实现J2EE架构业务逻辑层商务功能的可重用组件。
The logic transaction tier of J2EE is implemented by the reusable component of EJB.
本文叙述根据数据库架构信息和定制的代码模板自动生成业务逻辑层代码的实现方法。
According to the database schema information and customized code template, code is built for business logic layer.
依据实际业务中对数据的操作要求，并对数据和操作进行封装和抽象，产生业务逻辑层的类及其类层次结构。实现对业务逻辑层的设计。
It gives the classes and hierarchical structure of them and the implementation of the design of logic layer, according to data and operation of practical business and encapsulation and abstract.
模型层：主要负责业务的处理逻辑实现与数据库的交互等，是该系统的主要计算单元。
Model layer: responsible for handling business logic interacts with the database, are the system 's main computing unit.
业务层，包含了实现服务业务逻辑的组件。
The business layer, which incorporates components that implement the business logic of the service.
业务逻辑层实现了核心业务逻辑，持久化层负责对数据库的具体操作。
Business sublayer implements business logic and persistent sublayer is responsible of operating with data source.
业务逻辑层实现了核心业务逻辑，持久化层负责对数据库的具体操作。
Business sublayer implements business logic and persistent sublayer is responsible of operating with data source.
应用推荐