The Unified Modeling Language (UML) has quickly become the de-facto standard for building Object-Oriented software. This tutorial provides a technical overview of the 13 UML diagrams supported by Enterprise Architect. UML 2 semantics are explained in detail in the new UML 2.0 tutorial.
统一建模语言(UML)已经迅速变成建立面向对象软件的事实标准。本教程提供了Enterprise Architect支持的13种UML图的技术概览。UML 2 详细的语义解释请看新的UML 2.0 教程。
Firstly... What is UML?
首先... 什么是UML?
The OMG specification states:
"The Unified Modeling Language (UML) is a graphical language for visualizing,specifying, constructing, and documenting the artifacts of a software-intensive system.The UML offers a standard way to write a system's blueprints, including conceptualthings such as business processes and system functions as well as concrete things suchas programming language statements, database schemas, and reusable softwarecomponents."
OMG组织规范声明 :
"统一建模语言(UML)是一种图形化的语言，用于软件密集系统要素的可视化、制定规范、构建对象和编写文档。UML提供了一种标准的方式来描述系统的设计图，既包括概念方面，例如业务过程和系统功能，也包括具体事务，如编程语言语句，数据库图示和可重用的软件组件。
The important point to note here is that UML is a 'language' for specifying and not a method or procedure. The UML is used to define a software system; to detail the artifacts in the system, to document and construct - it is the language that the blueprint is written in. The UML may be used in a variety of ways to support a software development methodology (such as the Rational Unified Process) - but in itself it does not specify that methodology or process.
这里着重指出的是UML是一种说明性的“语言”，而不是一种方法或程序。UML通常用来定义软件系统与细化、编写、构造系统中的要素，是“写”设计图的语言。UML可以用不同的方式来支持软件开发方法(例如：统一软件开发过程) ——但是它本身并不指定某种方法或过程。
UML defines the notation and semantics for the following domains:
- The User Interaction or Use Case Model - describes the boundary and interaction between the system and users. Corresponds in some respects to a requirements model.
- The Interaction or Communication Model - describes how objects in the system will interact with each other to get work done.
- The State or Dynamic Model - State charts describe the states or conditions that classes assume over time. Activity graphs describe the workflows the system will implement.
- The Logical or Class Model - describes the classes and objects that will make up the system.
- The Physical Component Model - describes the software (and sometimes hardware components) that make up the system.
- The Physical Deployment Model - describes the physical architecture and the deployment of components on that hardware architecture.
UML 定义了下列领域的标注和语义:
- 用户交互或用例模型 - 描述系统和用户之间的界定和交互。在某些方面对应于一个需求模型。
- 交互或通信模型 - 描述系统中的对象彼此之间如何进行交互以完成工作。
- 状态或动态模型 - 状态图表描述随着时间变化，类所呈现的状态和条件。活动图则描述系统即将执行的工作流程。
- 逻辑或类模型 - 描述构成系统的类和对象。
- 物理组件模型 - 描述构成系统的软件(有时也包含硬件)。
- 物理部署模型 - 描述物理架构与物理架构中组件的部署。
The UML also defines extension mechanisms for extending the UML to meet specialized needs (for example Business Process Modeling extensions).
UML 也定义了一些扩展机制，以扩展UML符合特别需要(例如：业务过程建模的扩展)。