You can use Business Objects, extensions of Service Data Objects (SDO), to provide an abstraction layer for data access.
可以使用业务对象（服务数据对象 (SDO)的扩展）为数据访问提供抽象层。
Model is also pretty easy to understand: business processes and objects exist in this layer.
模型也是很容易理解的：业务逻辑和对象都处于这个层。
The SOA approach is to separate the layers with consumers interacting with the business objects through the service layer rather than directly.
SOA方法分离各个层，消费者通过服务层与业务对象进行交互，而不是直接进行交互。
Create a business object layer, called intermediate objects, which serves as a placeholder for data used in event evaluation.
创建业务对象层，即所谓的中间对象，它们将用作事件评估中使用的数据的占位符。
The business layer should operate on business objects — not on a particular data representation tied to the view.
业务层应该对业务对象进行操作，而不是对与视图相关的特定数据表示进行操作。
If you introduce a layer of Web Services between the persistent objects and the business objects operating on them, then you lose that ability.
如果您在持久性对象和操作它们的业务对象之间引入了一层Web服务，那么您就丧失了这种能力。
The example in this article consists of the Data Abstract Layer (DAL), Data Transfer Objects (DTOs), the Business Logic Layer (BLL), the Presentation Layer, and supporting helper classes.
本文中的示例包含数据抽象层（DAL）、数据传输对象（DTO）、业务逻辑层（BLL）、表示层和用于支持的helper类。
It does not contain business rules or knowledge, but only coordinates tasks and delegates work to collaborations of domain objects in the next layer down.
它不包含业务逻辑或者业务相关的知识，而只是协调任务以及把任务委托给下一层中的一组对象。
These business objects form a layer between the presentation layer and the data tier, resulting in a three-tier application architecture.
这些商务物件会在展示层和资料层之间构成一个层级，形成三层式应用程序架构。
However, a common application design practice is to separate the presentation layer from business logic and encapsulate the business logic in business objects.
然而，常见的应用程序设计是将展示层与商务逻辑分开，并且将商务逻辑封装在商务物件中。
However, a common application design practice is to separate the presentation layer from business logic and encapsulate the business logic in business objects.
然而，常见的应用程序设计是将展示层与商务逻辑分开，并且将商务逻辑封装在商务物件中。
应用推荐