《《《《《《《《内容已删除》》》》》》》》》

大家在查：高架桥桥面 swamm manoeuver 美国CDC wanb STRIPPOKER entire army 季时节 party school Ferragamos

UML1

UML1

UML1

UML1

1

Unfortunately , the UML 1 version of activity modeling had a number of serious limitations on the types of flows that could be represented .

不幸的是，在 UML1 中，行为建模在流的类型方面有大量严格的限制，这些限制被提出了异议。

2

Note that this was not the case in UML 1, where, for example, the activities formalism was based entirely on the state machine formalism.

注意：这在 UML1 中是不行的，在 UML1 中，活动的形式完全是基于状态机的形式。

3

Let us consider for the moment the typical method for model management in the UML 1. x -- packages .

让我们暂时考虑 UML1.x 中的模型管理 ——包 ——的典型方法。

4

To a degree , these concepts could already be found in the UML 1 definition of collaborations , except that they were not applied recursively .

从某种程度上来说，这些概念在 UML1 中对于协作的定义里可以找到，只可惜它们不能用于递归。

6

Like back in the days of UML 1. x, there is no exchange format for the graphical models .

就像回到了 UML1.x 时代，图形模型没有交换格式。

7

In UML 1, the basic units of compliance were defined by the packages of the metamodel , with literally hundreds of possible combinations .

在 UML1 中，规范性的基本单元是由元模型的包定义的，包含了差不多成百个可能的组合。

8

The definition of semantics of the UML 1 modeling concepts was problematic in a number of ways .

UML1 模型概念语义的定义在许多方法都存在问题。

9

However , the UML 1. 4 notation set did not scale well in larger systems.

然而，UML1.4 符号集在较大的系统中不能很好地调节。

10

Interactions in UML 1 were represented either as sequenced message annotations on collaboration diagrams , or as separate sequence diagrams .

在 UML1 中，交互性是由协作图中序列消息的注释或单独的序列图来表现的。

11

In the area of component based design , UML 1 had a confusing abundance of concepts .

基于组件的设计领域中，UML1 有很多使人混淆的概念。

12

Also , the UML 1. x notation set was at times difficult to apply to larger applications.

同时，UML1.x 符号集合有时难以适用于较大的应用程序。

13

The semantics of extension by profiles have been improved with the UML 1. 0 major revision .

的语义扩展的配置文件已得到改善的 UML1.0 的重大修改。

14

In UML 1. x, a guard could only be assigned to a single message .

在 UML1.x 中，一个约束只可能被分配到一个单一消息。

15

There is also no exchange format for the content of the models (so no XMI like for UML 1. x).

它连模型的内容交换格式（因此没有 UML1.x 中类似的 XMI ）都没有。

16

The above UML 1. 4 notation is still supported in UML 2.

上述的 UML1.4 符号在 UML2 中仍然被支持。

17

Compared with UML 1. x, this UML 2 modeling ambiguity is new .

与 UML1.x 相比较，这个 UML2 模型歧义是新的。

19

However , different UML modeling tools talk different versions of UML: e. g. , UML 1 . 3 , 1. 4, and so on.

但是，不同的 UML 建模工具使用不同的 UML 版本，例如 UML1.3 、1.4 等等。

20

For example , modeling logical flow in UML 1. x was complicated and at times impossible.

举例来说，UML1.x 的模型逻辑流程太复杂，有时不可能完成。

热词推荐

大家在看