RUP Modeler allows you to create structural plug-ins for RUP that change RUP's underlying meta-model.
RUP Modeler允许你为RUP创造结构的插件，它们改变RUP的底层结构。
This part offers a RUP model process based on UML by analyzing and designing the order management system.
这部分通过对订单处理子系统进行分析和设计，从而提出了一个基于UML的RUP建模过程。
The RUP model template is one of several that are accessible through the wizard you see when you start up Rose, or you can find it in the Frameworks directory within the Rose program folder.
RUP的模型模板是可以在启动Rose时看到的，我们可以通过向导来访问的几个模板之一，或者你也可以在Rose应用程序的Frameworks目录中找到他们。
From the RUP perspective, a model is a logical concept, as opposed to a physical one, and we will adopt that viewpoint here.
从RUP的角度来看，模型就是一个与物理概念相对的逻辑概念，此处我们将采用这种观点。
Although the solution to this problem depends on what we mean by "domain concept," we show how rebuilding the UML model of the software through RUP-based disciplines can help solve this problem.
虽然此问题的解决方案依赖于我们所说的“领域概念”，但是我们将展示通过基于RUP的规程重新构建软件的UML模型能够如何帮助解决该问题。
It is worth mentioning the central role played by the use-case model in this work as in any RUP-based software development project.
值得提到的是在此工作中的用例模型所扮演的重要角色与在任何基于RUP的软件开发项目中一样。
Therefore, for RUP purposes, a model could be a drawing on a napkin or a whiteboard, something in a modeling tool, or even a mental image.
因此，对于rup来说，一个模型就像是餐巾纸或者白板上面的图画，它是建模工具中的某样东西，甚至是一个想象中的图画。
Significant changes to the RUP se architecture framework have already made it an even more useful mechanism for describing development artifacts captured in the architecture model.
RUPSE体系结构框架发生的重要变化已经使其成为更加有用的在体系结构模型中获取开发工件的机制。
It is unfortunate that RUP phases feel like they were extrapolated from a building development lifecycle model of the construction industry.
不幸的是RUP阶段感觉好像是从建筑行业的构建开发生命周期模型中推出来的。
Table 1 shows RUP-SE's typical system modeling viewpoints, as well as sample development artifacts produced for specific model levels.
表1显示了RUP - SE的典型系统建模视点，还有特定模型级别所产生的开发工件范例。
The RUP documentation shows the evolution from business use-case model to business object model and system use-case model; we found this to be quite accurate and helpful.
RUP的文档显示了从业务用例模型到业务对象模型和系统用例模型的演进；我们发现这是非常正确和有帮助的。
The design model, as defined by RUP SOMA, is the core output work product from service realization.
由RUPSOMA定义的设计模型，是服务实现的核心输出工作产品。
The team model in MSF, known as "team role," is based on sets of activities, while the roles described in RUP are based on responsibilities.
MSF中的团队模型，通称“团队角色”，是基于多组活动的，而RUP中所描述的角色是基于职责的。
RUP describes a model as an abstract representation or simulation of a system that provides a complete description of the system from a particular perspective.
RUP将模型定义为系统的抽象表示或模拟，可从特定的角度提供对系统的完整描述。
In RUP, for example, a use-case model ACTS as a measure of complexity and risk and is, typically, used as an input to project and iteration planning.
比如，在RUP中，使用用例模型可以作为复杂度和风险的度量，随后作为项目和迭代计划的输入。
In RUP a domain model (see Figure 5) is defined as the place to capture the most important types of objects in the context of the domain.
在RUP中一个域模型(见图5)被定义为：在域的语境中捕获最重要类型的对象。
Table 1 illustrates the RUP se architecture framework, representing viewpoints as columns and model levels as rows (see sidebar "Definitions for the RUP se Plug-In").
表1说明了RUPSE体系结构框架，按列表示观点且按行表示模型级别(参见工具条“RUP SE插件的定义”)。
To become a real value to AOA-equipped process engineers, the existing search functionality must be expanded to fully support the RUP meta-model.
要成为一个真正有价值的AOA过程工程师，现已存在的搜索功能就必须被扩展为完全支持RUP的元模型。
Table 1b adds columns to support a more specific review model than that in the standard RUP template.
表1b比标准RUP模版增加了支持更多的评审模型。
In a previous section, we defined a model as a logical construct, according to RUP. We followed that with a definition of modeling file.
在上一小节中，我们根据RUP将模型定义为一个逻辑结构。
In this classic pattern, the model is the process (RUP), the view is that of Ginger, and the controller is quality activities (including test).
在这个经典模式中，模型是过程(RUP)，视图是Ginger的，并且控制器是质量活动(包括测试)。
AS a starting point for our new model file (ASDI.mdl), we used the Rose template that follows the structure defined by the RUP (see Figure 1).
我们从一个开始点来创建我们的新模型文件(ASDI .mdl)，我们使用符合RUP中定义的结构的Rose模板(见图1)。
The IBM Rational Unified Process (RUP) defines a model as "a complete specification of a problem or solution domain from a particular perspective."
IBMRationalUnifiedProcess（RUP）将模型定义为：“一个问题或者解决方案域从某个特定角度来看待的一个完整的规范。”
Use Rose's RUP template, providing a model framework that adhered to RUP guidelines.
使用Rose的RUP模板，提供一个附带 RUP指南的模型框架。
Table 4: Hierarchical representation of the RUP meta-model.
表4：rup元模型的分等级表示。
Rational's tools (SoDA, REI scripts, and so on) more effectively interact with a model if it's structured according to RUP guidelines.
如果模型的结构是根据RUP的指导创建的，Rational的工具(SoDA,rei脚本等)将更加有效的与模型进行交互。
These qualifier names will become clearer later in the article when I discuss the RUP meta-model.
这些限定词名称将在本文后面关于rup元模型的讨论时变得更加明确。
A sample hierarchical representation of the RUP meta-model is shown in Table 4 below.
rup元模型的一个分级表示法的例子如下面的表4所示。
A process engineering task requires good understanding of RUP taxonomy (meta-model) and availability of a consistent extension mechanism.
一个过程工程任务需要对RUP分类法(元模型)具备很好的理解，以及具备相互兼容的扩展机制。
A process engineering task requires good understanding of RUP taxonomy (meta-model) and availability of a consistent extension mechanism.
一个过程工程任务需要对RUP分类法(元模型)具备很好的理解，以及具备相互兼容的扩展机制。
应用推荐