UML 1.1 图形表示法指南

需积分: 10 25 浏览量更新于2024-07-30 收藏 728KB PDF 举报

"UML1.1 符号指南" 这篇文档详细阐述了统一建模语言（UML）的视觉表示符号。UML是一种用于软件工程的建模语言，旨在提供一个标准化的方式来描述、构建和文档化系统的行为和结构。这份文档是与UML语义文档一起使用的，它包含了UML构造的简短语义概述，但完整的细节需要参考语义文档。 UML Notation Guide 版本1.1于1997年9月发布，由多个知名软件公司如Rational Software、Microsoft、Hewlett-Packard等共同参与编写。这份文档旨在为开发者和设计者提供一个一致的视觉表示规则，使得UML模型能够被广泛理解和应用。在UML中，有多种图形元素用于表示不同的概念，如类、对象、接口、用例、关系、活动和状态机等。以下是一些主要的UML符号和它们的含义： 1. **类(Class)**：通常用一个带有三个部分的矩形表示，顶部是类名，中间是属性，底部是操作。 2. **对象(Object)**：与类相似，但更强调实例，通常只显示名称。 3. **接口(Interface)**：用带有圆角的矩形表示，表明一个实体可以提供的服务。 4. **用例(Use Case)**：通常用椭圆形表示，描述系统与用户或其他系统之间的交互。 5. **关系(Relationship)**：包括关联(Association)、依赖(Dependency)、聚合(Aggregation)和组合(Composition)，通过线条和箭头来表示。 6. **泛化(Generalization)**：表现为一条带空心三角箭头的线，表示子类继承父类的特性。 7. **实现(Implementation)**：用虚线带空心三角箭头表示，常用于接口的实现。 8. **操作(Operation)**：在类或接口内部列出的方法，带有返回类型和参数列表。 9. **状态机(State Machine)**：用一系列状态和转换表示对象行为。 10. **活动图(Activity Diagram)**：用流程图形式展示系统的操作序列和决策流程。 11. **协作图(Collaboration Diagram)**：强调对象间的合作关系，显示消息传递顺序。 12. **序列图(Sequence Diagram)**：类似于协作图，但更专注于时间顺序和交互细节。此外，UML还支持注释(Annotation)、约束(Constraint)和标记值(Marker Value)等附加信息的表示，以增强模型的完整性和精确性。为了确保正确理解和使用UML符号，读者需要理解每个图形元素背后的语义，并参照UML语义文档以获取深入细节。UML的目的是提高软件开发的效率和质量，通过清晰的可视化工具帮助团队成员更好地沟通和协调。因此，掌握UML符号对于任何软件开发项目都至关重要。

Diagram Elements

10 UML v1.1, Notation Guide

item

‘.’

selector

the

selector

is the name of an attribute in the item or the name of a role of

the target end of a link attached to the item. The result is the value of the

attribute or the related object(s). The result is a value or a set of values

depending on the multiplicities of the item and the association.

item

‘.’

selector

‘[‘

qualifier-value

‘]’

the

selector

designates a qualified association that qualifies the

item.

The

qualifier-value

is a value for the qualifier attribute. The result is the related

object selected by the qualifier. Note that this syntax is applicable to array

indexing as a form of qualification.

set

‘

−>

’ ‘select’ ‘(‘

boolean-expression

‘)’

the

boolean-expression

is written in terms of objects within the set. The

result is the subset of objects in the set for which the boolean expression is

true.

2.9.7 Example

flight.pilot.training_hours > flight.plane.minimum_hours

company.employees

−>

select (title = “Manager” and self.reports

−

>size > 10)

2.10 N

OTE

A note is a graphical symbol containing textual information (possibly including embedded images).

It is a notation for rendering various kinds of textual information from the metamodel, such as con-

straints, comments, method bodies, and tagged values.

2.10.1 Semantics

A note is a notational item. It show textual information within some semantic element.

2.10.2 Notation

A note is shown as a rectangle with a “bent corner” in the upper right corner. It contains arbitrary

text. It appears on a particular diagrams and may be attached to zero or more modeling elements by

dashed lines.

2.10.3 Presentation options

A note may have a stereotype.

Diagram Elements

UML v 1.1, Notation Guide 11

A note with the stereotype “constraint” or a more specific form of constraint (such as the code body

for a method) designates a constraint that is part of the model and not just part of a diagram view.

Such a note is the view of a model element (the constraint). Other kinds of notes are purely notation;

they have no underlying model element.

2.10.4 Example

See also Section 4.1.3 for a note symbol containing a constraint.

Figure 2. Note

2.10.5 Mapping

A note may represent the textual information in several possible metamodel constructs; it must be

created in context that is known to a tool, and the tool must maintain the mapping. The string in the

note maps to the body of the corresponding modeling element. A note may represent: a constraint;

a tagged value; the body of a method; or other string values within modeling elements. It may also

represent a comment attached directly to a diagram element.

2.11 T

YPE

-I

NSTANCE

ORRESPONDENCE

A major purpose of modeling is to prepare generic descriptions that describe many specific partic-

ular items. This is often known as the

type-instance dichotomy.

Many or most of the modeling con-

cepts in UML have this dual character, usually modeled by two paired modeling elements, one of

which represents the generic descriptor and the other of which the individual items that it describes.

Examples of such pairs in UML include: Class-Object, Association-Link, Parameter-Value, Oper-

ation-Call, and so on.

Although diagrams for type-like elements and instance-like elements are not exactly the same, they

share many similarities. Therefore it is convenient to choose notation for each type-instance pair of

elements such that the correspondence is immediately visually apparent. There are a limited number

of ways to do this, each with advantages and disadvantages. In UML the type-instance distinction

is shown by employing the same geometrical symbol for each pair of elements and by underlining

the name string (including type name, if present) of an instance element. This visual distinction is

generally easily apparent without being overpowering even when an entire diagram contains

instance elements.

This model was built

by Alan Wright after

meeting with the

mission planning team.

Model Management

UML v 1.1, Notation Guide 13

3. MODEL MANAGEMENT

3.1 P

ACKAGES

AND

ODEL

RGANIZATION

3.1.1 Semantics

package

is a grouping of model elements. Packages themselves may be nested within other pack-

ages. A package may contain both subordinate packages and ordinary model elements. Some pack-

ages may be Subsystems or Models. The entire system description can be thought of as a single

high-level subsystem package with everything else in it. All kinds of UML model elements and dia-

grams can be organized into packages.

Note that packages

own

model elements and model fragments and are the basis for configuration

control, storage, and access control. Each element can be directly owned by a single package, so the

package hierarchy is a strict tree. However, packages can reference other packages, so the usage net-

work is a graph.

There are several predefined stereotypes of Model and Subsystem. See the metamodel document

for details. In particular, the stereotype «system» of Subsystem denotes the entire set of models for

the complete system being modeled; it is the root of the package hierarchy and the only model ele-

ment that is not owned by some other model element.

3.1.2 Notation

A package is shown as a large rectangle with a small rectangle (a “tab”) attached on one corner (usu-

ally the left side of the upper side of the large rectangle). It is a manila folder shape.

If contents of the package are not shown, then the name of the package is placed within the large

rectangle.

If contents of the package are shown, then the name of the package may be placed within the tab.

A keyword string may be placed above the package name. The keywords

subsystem

and

model

indi-

cate that the package is a metamodel Subsystem or Model. The predefined stereotypes

system,

facade, framework,

and

top package

are also notated with keywords. User-defined stereotypes of

one of these predefined kinds of package are also notated with keywords, but they must not conflict

with the predefined keywords.

A list of properties as may be placed in braces after or below the package name. Example:

{abstract}. See Section 4.2.2 for details of property syntax.

The contents of the package may be shown within the large rectangle.

The visibility of a package element outside the package may be indicated by preceding the name of

the element by a visibility symbol (‘+’ for public, ‘-’ for private, ‘#’ for protected). If the element

剩余147页未读，继续阅读

vagawind

粉丝: 0
资源: 1

UML 1.1 图形表示法指南

Python库 | dice_notation-1.2.0-py2.py3-none-any.whl

PyPI 官网下载 | engineering_notation-0.2.2-py3-none-any.whl

python编程实现：采用arcpy和坐标转换注记工具(ConvertCoordinateNotation)将coordinate_notation.xlsx转换为*.shp文件, 输出的坐标格式为: DD_2，输出的坐标系统为: GCS_WGS_1984。

采用arcpy和坐标转换注记工具(ConvertCoordinateNotation)将coordinate_notation.xlsx转换为*.shp文件, 输出的坐标格式为: DD_2，输出的坐标系统为: GCS_WGS_1984。

tcl脚本将“xxxx-xxxx-xxxx”格式的MAC地址转换为“xx.xx.xx.xx.xx.xx”格式

科学计数法与小数形式转换Python

python科学计数法与小数形式转换

stm32f4蜂鸣器两只老虎

如何用python获取科学计数法中的乘数

用程序实现波兰符号法

最新资源