UML基本架构建模--通用机制的术语和概念(一)



Terms and Concepts

术语和概念

A
note is a graphical symbol for rendering constraints or comments attached to an element or a collection of elements.
Graphically, a note is rendered as a rectangle with a dog-eared corner, together with a textual or graphical comment.

备注是一个将约束或说明附加到一个元件或一个元件集的图形符号.图形表现上,一个备注被表现为一个在右上角带有狗耳朵的矩形方框,连带有一段文字或是图形加以说明.

A
stereotype is an extension of the vocabulary of the UML, allowing you to create new kinds of building blocks similar
to existing ones but specific to your problem. Graphically, a stereotype is rendered as a name enclosed by guillemets ( French quotation marks of the form
?? ), placed above the name of another element.

模式化是UML词汇表的扩展,允许你创建与已有的构建块相类似,但专门针对你个人问题的新类型的构建块.图形表现上,一个模式化被表现为在双引号之内的名称(法国的引用形式是《》),放置在另一个元件的名称之上.

Optionally the stereotyped element may be rendered by using a new icon associated with that stereotype.

任意地模式化元件可以通过使用关联到那个模式化的新图标表现.

A
tagged value is a property of a stereotype, allowing you to create new information in an element bearing that stereotype.
Graphically, a tagged value is rendered as a string of the form name=value within a note attached
to the object.

标签值是模式的一个属性,允许你在一个承担那个模式的元件上建立新信息.图形表现上,一个标签值被表现为形如名称=值的一串字符串,附加在对象的一个备注里.

A
constraint
is a textual specification of the semantics of a UML element, allowing you to add new rules or to modify existing ones. Graphically, a constraint is rendered as a string enclosed by brackets
and placed near the associated element or connected to that element or elements by dependency relationships. As an alternative, you can render a constraint in a note.

约束是一段文本,用以描述UML元件的语义,允许你加新的规则或是修改现有的元件.图形表现上,约束被表现为用一对括弧括起的一串字符串,并被放置在关联元件的附近或是那个元件或元件组的依赖关系附近.作为替代方案,你可以在一个备注里表现一个约束.

时间: 2025-01-02 18:36:14

UML基本架构建模--通用机制的术语和概念(一)的相关文章

UML基本架构建模--通用机制的术语和概念(四)

 Constraints 约束 Everything in the UML has its own semantics. Generalization (usually, if you know what's good for you) implies the LisKov substitution principle, and multiple associations connected to one class denote distinct relationships. With c

UML基本架构建模--通用机制的术语和概念(三

 Stereotypes 模式化 The UML provides a language for structural things, behavioral things, grouping things, and notational things. These four basic kinds of things address the overwhelming majority of the systems you'll need to model. However, sometime

UML基本架构建模--通用机制的术语和概念(二)

 Notes 备注 A note that renders a comment has no semantic impact, meaning that its contents do not alter the meaning of the model to which it is attached. This is why notes are used to specify things like requirements, observations, reviews, and expl

UML基本架构建模--获取类

 Getting Started 开始 Modeling a system involves identifying the things that are important to your particular view. These things form the vocabulary of the system you are modeling. For example, if you are building a house, things like walls, doors, w

UML基本架构建模--类的辅助信息

 Organizing Attributes and Operations 组织属性和操作 When drawing a class, you don't have to show every attribute and every operation at once. In fact, in most cases, you can't (there are too many of them to put in one figure) and you probably should not

UML基本架构建模--通用机制概述

 Common Mechanisms 通用机制 The UML is made simpler by the presence of four common mechanisms that apply throughout the language: specifications, adornments, common divisions, and extensibility mechanisms. This chapter explains the use of two of these

UML基本架构建模--获得通用机制

 Sometimes you just have to color outside the lines. For example, at a job site, an architect might scribble a few notes on the building's blueprints to communicate a subtle detail to the construction workers. In a recording studio, a composer migh

UML基本架构建模--通用机制的通用建模技术(一)

 Modeling Comments 注释建模 The most common purpose for which you'll use notes is to write down free-form observations, reviews, or explanations. By putting these comments directly in your models, your models can become a common repository for all the

UML基本架构建模--通用机制的通用建模技术(二)

 Modeling New Properties 新特性建模 The basic properties of the UML's building blocks-----attributes and operations for classes, the contents of packages, and so on----are generic enough to address most of the things you'll want to model. However, if yo