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.
文本提出了一种面向组件的业务流程建模方法，解决了业务流程模型中的模型规模、重用、模块化和灵活性问题。
Whichever approach you choose, these models and mappings give you the components needed to implement the update methods.
无论选择哪种方法，这些模型和映射都能提供实现更新方法所需的组件。
There is a not a lot of science behind these models other then taking an iterative approach; there is no beginning and no end.
这些模型的背后不是采用了许多科学技术，而是采用了迭代的方法；没有开始和结束。
In the same way that we now have decoupled business processes, we also end up with corresponding "decoupled" monitor models and, as a by-product, a much more modular approach to monitoring.
我们现在除了拥有已解耦的业务流程，最终还得到了相应的“已解耦”监控模型，并且作为一种副产品，我们还实现一种更加模块化的监控方法。
This approach allows software developers to contribute to a project through the types of models that best match the kinds of information and decisions they make.
这种方法允许开发人员通过使用与他们的信息和决定最匹配的模型类型对项目作出贡献。
The third and final installment of this series will refer to these models to reconcile the commonalities and differences of the two frameworks and compile them into a common implementation approach.
该系列的第三个安装与最后一个安装，将会引用这些模型，以协调两种框架的相同处与不同处，并将它们汇编到一个公共的实施方法之中。
With additional work, however, the bottom-up approach can support hierarchical data models and, therefore, should not be automatically dismissed.
然而，通过额外的工作可以使自底向上的开发方法支持层次数据模型，因而不会被自动淘汰掉。
This approach forces you to make a synchronization between the logical and physical data models, but this article covers that later.
这种方法迫使您在逻辑与物理数据模型之间进行同步，本文后面会讲到。
In order to create a more realistic approach to BPM for widespread adoption, we need to start by making a better distinction between analysis process models and executable process models.
为了创建一个更实际的能被普遍采用的BPM方法，我们需要从理清分析过程模型和可执行过程模型的区别开始。
Adopt the right approach in identification of services by using both domain decomposition business process models and bottom-up models.
通过同时使用领域分解业务流程模型和自底向上的模型，从而在服务标识过程中采用正确的方法。
A traditional approach to business process modeling frequently results in large models that are difficult to change and maintain.
传统的业务流程建模方法通常会产生难以更改和维护的大型模型。
The Industry Models start with a purely business-driven approach — analyzing business-to-be processes and deriving analysis-level service definitions.
行业模型以纯业务驱动的方法开始——分析将要成为过程的业务，并导出分析级服务的定义。
The term architecture blueprint is defined as a prescriptive approach for developing adaptable architectures rapidly by leveraging proven reusable assets, methodologies, patterns, and models.
体系结构蓝图是一种通过利用现有的可重用资产、方法、模式和模型开发具有适应性的体系结构的描述性方法。
Models and model driven software development are at the heart of the MDA approach.
模型和模型驱动的软件开发是MDA方法的核心。
Better business and it alignment - structural equivalence between business process models and implementation is more likely with this approach.
更好的业务与IT的一致性——通过这种方法更易实现业务流程模型与实现之间的结构均衡。
This approach can be used even when the HLDM is a meta-model and implementation models are concrete, or vice-versa.
甚至当HLDM作为元模型并且实现模型是具体的时候该方法也可以使用，反之亦然。
We would also like to thank the project teams who decided to follow the SBS approach and utilize the SBS Models, that eventually created a wonderful win-win for us and the project teams.
我们也非常感谢决定使用SBS方法并利用 SBS模型的项目团队，最终取得了我们和项目团队的双赢结果。
Today, a majority of software developers still take a code-only approach (left end of the modeling spectrum, Figure 1) and do not use separately defined models at all.
今天，多数的软件开发人员仍然在使用单独-代码的方法(在建模光谱的左端，图1)并且根本没有分离的定义模型。
This approach is geared toward WSDL object models and lets you manipulate the WSDL directly.
这种方法倾向于WSDL模型，它允许您直接操作 WSDL 。
The OASIS CAM template approach is based on a simple approach to XML content handling and validation that allows businesses to create common interchange models for their exchanges in XML.
OASISCAM模板方法是基于XML内容处理和验证的简单方法，它允许企业创建xml格式的通用交换模型。
This article Outlines a recommended approach for governing and managing a set of evolving, under-development enterprise models.
本文概述了管理开发企业模型的推荐方法。
The current 4.0 version of MSF defines itself as an approach for projects that defines a set of principles, models, disciplines, concepts, guides, and practices already proven by Microsoft.
目前的MSF 4.0版将其本身定义为一种定义了一组已经由 Microsoft证明了的规则、模型、规程、概念、指导和实践的开发项目的方法。
Santamaria plans to test his approach in models of other autoimmune diseases, such as multiple sclerosis and rheumatoid arthritis.
Santamaria计划在其他自身免疫疾病模型上测试他的方法，如多发性硬化和类风湿性关节炎。
Tools that implement this approach, such as IBM Rational Rose, can offer multiple transformation services supporting RTE between models and different implementation languages.
实现这个方法的工具，比如ibmRationalRose能够支持在模型与不同实现语言之间双向提供多种转换服务。
External industry reference models and standards (such as ACCORD, IxRetail) could also be a key input to our approach.
外部行业参考模型和标准(如accord、IxRetail)也可以成为我们的方法的关键增补。
Rational Application Developer simplifies the process of creating Web services in a top-down approach based on requirements specifications and UML models.
RationalApplication Developer根据需求规范和uml模型，采用自顶向下的方法简化Web服务的创建流程。
With the proposed approach, we can leverage existing assets of many formats: UML models, logical or physical data models (in DDL), XSD schemas, and code modules.
使用建议的方法，我们可以利用多种格式的现有资产：uml模型、逻辑或物理数据模型(ddl格式)、XSD模式和代码模块。
This COA approach requires looking at the details of the business process and UI models to pick the most likely candidates for each approach. For example.
这种COA方法需要考虑业务流程和UI模型的细节，以便为每种方法挑选最可能的候选者。
Using the combination of UML models, transformations, and code modeling to practice a Mixed modeling approach to Architecture management.
使用uml模型、转换，及代码建模的组合来实现对架构管理的Mixed Modeling(混合建模)方法。
Using the combination of UML models, transformations, and code modeling to practice a Mixed modeling approach to Architecture management.
使用uml模型、转换，及代码建模的组合来实现对架构管理的Mixed Modeling(混合建模)方法。
应用推荐