统一建模语言

复杂的软件设计和业务流程可以通过可视化模型表达出来,,en,例如统一建模语言,,en,本系列文章描述了我用来创建UML设计的工具和方法。,,en,够好了,,en,了解,,en,UML标准很复杂,,en,有几层规格,,en,有很多图,,en,连接器,,en,元素,,en,等等,,en,难怪这种语言的标准制定机构被称为,,en,OMG标准,,en,我仅使用用例就能满足所有建模需求,,en,活动,,en,状态图和序列图,,en,在这四个基本组之后，收益递减,,en,其余的UML图过于专业,,en,使用Visio绘制网络或使用Wiki描述部署，我可以达到相同的结果,,en,我的UML图是,,en,供开发人员理解,,en, such as the Unified Modeling Language. This series of posts describes the tools and methods I use to create my UML designs that are "good enough" to understand.

The UML standard is complicated, with several layers of specifications. There are many diagrams, connectors, elements, etc. Is it any wonder that the standards-setting body for this language is called OMG?

I am able to satisfy all of my modeling needs using just Use Case, Activity, State and Sequence diagrams. There are diminishing returns after this basic set of four; the remaining UML diagrams are too specialized. I can achieve the same results using Visio to draw a network or Wiki to describe deployment.

My UML diagrams are "good enough" for a developer to understand. 它们不遵循完整的规范，并且存在建模语法错误,,en,这些语法错误是可以的,,en,因为没有人使用我的UML设计注意到它们,,en. These syntax errors are OK, as no one using my UML designs has ever noticed them.