In this case, the conceptual model still guides the definition of business types within the component and of those passed through the interfaces of the components.
在这种情况下，概念模型仍然指导组件中的业务类型和通过组件的接口传递的业务类型的定义。
The business delegate component invokes the service and wraps any return value as a model object.
业务委派组件调用该服务，并将任何返回值打包为模型对象。
The component values will have been converted, validated, and applied to the model objects, so you can now use them to execute the application's business logic.
组件值已经经过了类型转换和有效性验证，并被应用到模型对象中了，因此您现在可以使用它们来执行应用程序的业务逻辑了。
Sometimes referred to as "the SOA layered architecture", this model introduces layers and concepts such as business process, service, or service component, as well as the relationships between them.
有时也将其称为“SOA分层体系结构”，其中介绍了各个层次和概念(如业务流程、服务或服务组件)及其相互间的关系。
Selection of a component model requires an understanding of the dimensions of the business problem in the context of SOA best practices and current IT technologies.
选择组件模型需要在SOA最佳实践和当前的IT技术上下文中了解业务问题的各个方面。
The core idea behind SCA is to establish a common component model for the definition of business services.
SCA背后的核心思想是为业务服务的定义建立公共组件模型。
For example, WebSphere process Server also supports the SCA programming model and introduces a large set of component types, like business processes and human tasks.
例如，WebSphereProcessServer还支持SCA编程模型，并引入了许多组件类型，如业务流程和人工任务。
Represented as a pure object model, a sample model for a business component PartyManagement can look like this.
业务组件PartyManagement的示例模型表示为纯对象模型，如下所示。
Service components, which adopt the Service component Architecture (SCA) programming model, use business objects for exchanging data among them.
服务组件采用的是服务组件架构(Service Component Architecture,SCA)编程模型，它使用业务对象在服务组件之间交换数据。
At the same time, Seam expands the EJB3 component model to POJOs and brings the stateful context from the web tier to the business components.
同时，Seam拓展了EJB3到POJO的组件模式，从we b层到业务层都有了状态上下文。
We partitioned the design model by business component first and then by layer (often not the same thing), rather than by layer first.
我们首先通过业务组件对设计模型进行了划分，然后再对他们进行层次的划分(这两个任务通常是不同的)，而不是一开始就对模型进行层次划分。
This article addresses the issues of model size, re-use, modularity and flexibility in business process models by proposing a component-oriented approach to business process modeling.
文本提出了一种面向组件的业务流程建模方法，解决了业务流程模型中的模型规模、重用、模块化和灵活性问题。
In the fourth chapter, enterprise business modeling based on model component and design and realization of corresponding enterprise information system are discussed.
第四章论述了基于模型构件的企业业务建模与信息系统的设计和实现。
A business component contains a hierarchical XUML model.
一个业务组件包含一个层次化的XUML模型。
To capture business components with high reusability, a reusable component design method based on domain business model was proposed.
为获取具有较高重用度的业务构件，提出了一个基于领域业务模型的可重用构件设计方法。
To capture business components with high reusability, a reusable component design method based on domain business model was proposed.
为获取具有较高重用度的业务构件，提出了一个基于领域业务模型的可重用构件设计方法。
应用推荐