举例来说，UML 1. x的模型逻辑流程太复杂，有时不可能完成。
For example, modeling logical flow in UML 1.x was complicated and at times impossible.
Rails迁移支持把模型逻辑用于数据迁移，而sql脚本做不到这一点。
Rails migrations let you use model logic with your data migration where SQL scripts don't.
这样的设计使得维护几乎不可能实现，因为无论视图何时改变，您都必须改变模型逻辑，反之亦然。
Such a design makes maintenance all but impossible, because whenever the view changes, you must change the model logic, and vice versa.
但在我们的示例中，因为servlet实际上创建了下行视图，所以我们需要另外的组件来包装控制器和模型逻辑。
But in our case, because the servlet actually creates the downstream view, we need additional components to wrap our controller and model logic.
我更喜欢使用控制器，因为我可以使用它来触发模型逻辑，然后进行某种验证处理，接着将用户路由到一个相应的错误处理或结果页。
I prefer to use a controller, because I can use it to fire the model logic, then do some validation processing, and then route the user to an error-handling or result page as appropriate.
在Monitor V6.1.2中添加了Monitor模型调试工具，以了解监视器模型的操作，并确定和解决模型逻辑问题。
The monitor model debugger was added in monitor V6.1.2 as way to understand the operation of a monitor model and to identify and resolve model logic problems.
如果您还没有找到陷阱，请注意其中的查询看起来有点象从数据库读取数据的模型逻辑，而out. println语句中的信息看起来象是HTML。
If you haven't spotted the trap, notice that the query looks suspiciously like model logic reading from a database, and the information in the out.println statements looks like HTML.
我们正在混合模型和视图逻辑。
我们也取得了相对容易的分布各个层的能力；所有“模型”逻辑可以被轻易的作为一个单元转移到单独的层。
We also get the ability to distribute the layers relatively easily; all "model" logic can easily be moved as a unit to a separate tier.
将模型和逻辑封装为可重用的组件。
逻辑模型表达了信息的业务视图。
The logical model expresses the business view of information.
当业务部门创建并批准模型时，逻辑模型创建阶段就开始了。
When the business departments create and approve the model, the phase to create logical models starts.
ARTS数据模型的逻辑视图中避免使用缩写词。
The logical view of the ARTS Data Model avoids abbreviations.
描述数据元素在信息模型的逻辑上下文中的位置。
Place data elements within the logical context of the information model.
您不能删除逻辑模型中的实体。
然而，IT可以更改逻辑模型的结构。
流：模型文件的逻辑组。
正常情况下，程序部署团队开始创建逻辑模型，然后将逻辑模型和物理模型集合起来。
Normally, an application development team starts by creating logical models and then iterating through logical and physical models together.
逻辑模型设计包含两个步骤：先设计DWH逻辑模型(CDW)，然后设计DM逻辑模型。
The design of logical models consists of two steps: designing the DWH logical model (CDW) followed by designing the DM logical model.
用于组织模型的逻辑内容的通用技术。
General techniques for organizing logical content of models.
uml模型文件：逻辑单元和片断。
将两个逻辑模型组合为一个逻辑模型。
使用一个单独的成碎片的模型/逻辑单元。
阶段II：从逻辑模型中得出物理业务逻辑设计模型。
Phase II: Derive physical business process design model from logical model.
使用建议的方法，我们可以利用多种格式的现有资产：uml模型、逻辑或物理数据模型(ddl格式)、XSD模式和代码模块。
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.
完成以下步骤，将物理模型转换成逻辑模型。
Transform the physical data model into a logical model by completing the following steps.
也许这是因为他们一旦排外地使用了片断划分，单个的模型/逻辑单元就将被证明为并不方便作为发布该模型的基础。
Perhaps this is because, had they used Fragment partitioning exclusively, the single model/LU would have proven to be inconvenient as the basis for publishing the model.
每一个应用系统的核心是描述这个系统的基础模型 --领域模型、类模型、逻辑模型、实体模型等等。
The heart of every application is the base model that describes it -- a domain model, class model, logical model, entity model, or the like.
逻辑数据模型：逻辑数据模型代表企业实体、实体属性(数据)，以及它们之间的关系。
Logical data model: Logical data model represents the enterprise entities, their attributes (data) and the relationship among them.
在此模型中，我们将可视化(图形)模型映射到业务逻辑(域模型)中。
In this model, we map our visual (graph) model to our business logic (domain model).
应用推荐