模型视图——用于编辑实体的视图
图1显示了此体系结构的逻辑模型视图。
表示此区域的模型视图集合的主题是依赖关系管理。
The theme for the collection of model views that represents this area is dependency management.
该逻辑模型视图对SOA解决方案的功能基础进行了分解。
The logical model view decomposes the functional underpinnings of an SOA solution.
哪一个单个模型视图将被处理？以及每个视图将开发出哪些工件？
Which individual model views will be addressed and what artifacts will be developed for each view?
第一篇文章提供完整的组件模型视图，介绍产品可跟踪性的基本知识。
The first article introduces general product traceability by providing a complete component model view.
图1显示了SOAFoundation参考体系结构逻辑模型视图。
Figure 1 shows the SOA Foundation Reference Architecture logical model view.
视角定义为模型视图的集合，使用一组关系图、文档和其他相关构件进行表示。
A viewpoint is defined as a collection of model views that are represented by a collection of diagrams, documents, and other related artifacts.
了解了逻辑组件及其集成的概况之后，现在看看更详细的组件模型视图，见图3。
After understanding the logical components and their integration on a high level, now move from the high-level overview into a more detailed component model view, as shown in Figure 3.
与规则组建模图相结合，这两种模型视图可提供业务规则组中的规则的全面视图。
Combined with the rule group-modeling diagram, these two model views can provide a full picture of the rules embodied in a business rule set.
图1不包括任何持久性或者系统类，但是如果包括了，您将创建一个我们的模型视图，它没有显示这些类。
Figure 1 does not include any persistence or system classes, but if it did, you would want to create a view of our model that did not show them.
其他一些新特性还有：支持。NET 4.0、模型先行或数据库先行的开发模式、模型视图、项目验证等等。
Other new features are: support for.net 4.0, model-first or database-first development mode, model view, project validation.
MVC架构（或设计模式）是图形用户界面（GUI）的设计样式，由三部分构成：模型、视图和控制器。
The MVC architecture (or design pattern) is a graphical user interface (GUI) design style that consists of three parts: model, view, and controller.
生成器块会指定应用程序的首选项，并根据您的模型、视图等调用适当的生成器。
The generators block specifies your preferences for the application and invokes the proper generator for your models, views, and so on.
我们的应用开发工具支持“IBM电子商务框架”，它支持模型-视图-控制器（MVC）概念。
Our application development tools support the IBM Framework for e-business, which advocates the model view controller (MVC) concept.
DPTK设计为使用模型-视图-控制器模式。
模型-视图-控制器(MVC)是一种常用的设计模式，用于构建许多不同类型的应用程序。
Model View Controller (MVC) is a popular design pattern for building many different types of applications.
应用程序目录，包括模型、视图和控制器的子目录。
Application directories with subdirectories for model, view, and controller.
为了说明这些限制，要创建带有模型、视图和控制器的Location。
To illustrate these limitations, you'll create a Location with model, view, and controller.
Rails帮助器是帮助简化模型、视图、控制器代码的函数。
Rails helpers are functions that help to simplify model, view, or controller code.
最重要的是，XForms分隔表单的数据模型、视图和控制器。
Most importantly, XForms splits a form's data model, view, and controller.
您已经看到了Monkeybars如何划分模型、视图和控制器。
You've seen how Monkeybars splits things up into model, view, and controller.
所有的数据和动作(请求服务器)都属于模型的一部分，和典型的模型-视图-控制器(MVC)架构一样。
All the data and the actions (requests to the server) are part of the model, as is common in typical model View Control (MVC) architectures.
这种假定就意味着您根本不需要担心模型-视图分离，对吗？
This assumption means that you don't need to worry about model-view separation at all, right?
您很可能也知道这种分离的根源要追溯到最早的设计模式之一：模型-视图-控制器。
You probably also know that the roots of this separation go back to one of the earliest design patterns: Model-View-Controller.
随着时间推移，很多框架代替了控制器的角色，而模型-视图分离也变得微不足道。
Over time, many frameworks took the role of the controller, and model-view separation became trivial.
例如，在模型-视图-控制器(MVC)设计模式中，控制器调用方法。
For example, in the Model-View-Controller (MVC) design pattern, the controller invokes methods.
该命令将创建模型-视图-控制器(mvc)的视图和控制器部分。
This command creates the proverbial view and controller part of Model-View-Controller (MVC).
这就是模型-视图-控制器和呈现-内容被认为是好东西的主要原因。
This is much of the reason that model-view-controller and presentation-content partitions are supposed to be good things.
它实现了模型-视图模型-视图-控制器这个看起来在WPF中很流行的模式。
It implements the Model - ViewModel - View - Controller pattern that seems to be popular in WPF.
应用推荐