转换的FBX导入到您的玛雅包含你的模型场景文件。
Import your converted FBX file into your Maya scene containing your model.
它没有准确如实地描述场景或模型。
注意：你也可以清除此选项以减少合并，但是为了此次测试的目的，你要使用模型文件执行一个合并场景，因此激活此选项。
Note: you can clear this option to reduce merging, but for the purpose of this test, you will run a merge scenario with model files, so enable this option.
注意使用模型片段在该场景的工作流程中是可选择的。
Note that using model fragments is optional in the workflow of this scenario.
然而，销售的企业需要创建多个站点，在这些业务模型中存在一些公共场景。
However, there are some common scenarios within these business models in which the selling enterprise needs to create multiple sites.
执行一个像这样的地域上分布的模型是集中构建和发布管理过程的完美场景。
Executing in a geographically distributed model like this is the perfect scenario for centralizing build and release management processes.
我使用供应链管理、设备工程管理和许可物理研究论文场景作为加入并订阅模型的示例。
I give Supply Chain Management, Plant Engineering Management, and Licensing Physics Research Papers scenarios as examples of the join-to-subscribe models.
这种方法使业务分析师可以分离流程中重复的路径，为分析业务场景中的流程模型提供了方便。
This technique enables a business analyst to separate repeated paths in a process, and it facilitates the analysis of the process model in a business scenario.
本文的第 1部分介绍了两个场景，主要解决如何在流程模型中设计分支和迭代行为这一问题。
Part 1 of this article deals with two scenarios that address the modeling of branching and iterative behavior in business processes.
这个数据模型代表一个典型的场景，其中XML 数据部分被 “分割”成关系结构。
This data model represents a common scenario in which portions of XML data are often "shredded" into a relational structure.
这些情况下，往往需要为每个具体错误使用特定模式来定义信息，这样可以有效地扩展领域语义模型以描述失败场景。
These situations often call for special schemas defining information for every specific error, thus effectively extending domain semantic model to describe failure scenarios.
在本系列中，可以学习如何用模型驱动开发方法来开发业务场景。
In this series, you'll learn how to use the Model Driven Development approach to develop a business scenario.
我们将根据第一条法则来组织场景：在模型被强壮的设计之后，强壮的所有权是否就被实践了呢？
We'll organize the scenarios according to the first principles: Are the models strongly designed, and is strong ownership practiced?
在“业务流程管理”场景内建立的模型中，可以对服务进行标识。
The services can be identified from the business process models that are modeled in the Business Process Management scenario.
反之，人类则可以考虑物体的相对大小，物理特性以及一些基本常识，通过观察相片而在脑海中构造场景的模型。
Humans, by contrast, are able to construct a mental model of a scene from a photograph by taking into account the relative sizes of recognised objects, the laws of physics and some basic common sense.
应用程序需要一个健壮的安全模型来处理类似场景。
Applications require a robust security model to handle likely scenarios.
对于这个场景，可以直接从逻辑模型中导出基本数据类型，作为XML开发的起点。
For this scenario, it can be useful to export the base data types directly from the logical model as a starting point for XML development.
取决于您是否希望更新业务项或逻辑数据模型，中间会合式场景有两种用例。
There are two use cases in the meet-in-the-middle scenario, depending on whether you want to update your business items or logical data models.
由于此场景中的模型并不复杂，并且未涉及冗长的建模方法，因此本文仅讨论如何从重新开始创建模型。
Because the model for this scenario is not complicated and does not involve a long modeling approach, this article just covers how to create the model from scratch.
动态api场景并不要求为数据模型中的对象生成类型接口、工厂类或实现类。
A dynamic APIs scenario does not require the generation of a typed interface, factory class, or implementation class for the objects in your data model.
与此同时，芝加哥商品交易所开发了一种基于场景的模型，设计它的目的时计算系统风险和异常风险。
CME, meanwhile, has developed a scenario-based model designed to take into account systemic and idiosyncratic risk factors.
在往返场景中，业务模型已经完成，技术模型也已完成，并投入了生产运行。
In a round-trip scenario, the business model has been completed, the technical model is also completed, and placed into production.
从编程模型的角度来看，这个场景与场景3(使用信用验证进行标识断言)相同。
From the programming model point of view, this scenario is the same as scenario 3 (Identity assertion with trust validation).
在Spring的精神中，我们有一个能够跨越不同运行时场景的编程模型。
In the spirit of Spring, we have one programming model that can span different runtime scenarios.
场景6：在分层流程模型中重用活动
Scenario 6: Reuse of activities in hierarchical process models
行业解决方案的架构和其中的PaaS使用根据企业或者特定于解决方案的应用程序场景、业务模型和企业架构不同而不同。
The architecture of industry solutions and the use of PaaS in it varies according to the enterprise or solution-specific application scenario, business model, and enterprise architecture.
点到点消息传送模型的场景示例。
这些增强实现了单一页面中多schema模型和多个请求及响应的场景。
These enhancements resulted in a scenario of multiple schema models and multiple requests and responses for a single page.
扩展的站点业务模型及场景。
点对点消息模型的应用场景。
Application scenario for the point-to-point messaging model.
应用推荐