uml

In discussion about my answer to this question , there was some disagreement over how to model this code: public class MainClass { private Something something; public void Action() { OtherClass other = something.GetOtherClass(); } } The key points being: the Something class is an attribute in MainClass , suggesting an association the Something class is referenced within MainClass , suggesting a dependency A dependency is supposed to be a specialised association However, since a dependency is can be appropriate in cases where the supplier class is not an attribute, does using a dependency "hide

I'm wondering if there are any clear reasons to choose UmlGraph over APIViz for javadoc UML diagram generation in a Maven2 build. Are there any integration or features that one has over the other, they seem pretty similar? Pascal Thivent There is an interesting thread here about UMLGraph vs apiviz (which are mentioned in this question on SO too) and my understanding is the following: UMLGraph is older but is really nice (dixit Fowler which has more weight than me). apiviz is a rewrite of UMLGraph but it's not really clear why the rewrote it. The "big" advantage of apiviz is that the build won

在画类图的时候，理清类和类之间的关系是重点。类的关系有泛化(Generalization)、实现（Realization）、依赖(Dependency)和关联(Association)。其中关联又分为一般关联关系和聚合关系(Aggregation)，合成关系(Composition)。下面我们结合实例理解这些关系。 基本概念 类图（Class Diagram）: 类图是面向对象系统建模中最常用和最重要的图，是定义其它图的基础。类图主要是用来显示系统中的类、接口以及它们之间的静态结构和关系的一种静态模型。 类图的3个基本组件：类名、属性、方法。 泛化(generalization)：表示is-a的关系，是对象之间耦合度最大的一种关系，子类继承父类的所有细节。直接使用语言中的继承表达。在类图中使用带三角箭头的实线表示，箭头从子类指向父类。 实现（Realization）:在类图中就是接口和实现的关系。这个没什么好讲的。在类图中使用带三角箭头的虚线表示，箭头从实现类指向接口。 依赖(Dependency)：对象之间最弱的一种关联方式，是临时性的关联。代码中一般指由局部变量、函数参数、返回值建立的对于其他对象的调用关系。一个类调用被依赖类中的某些方法而得以完成这个类的一些职责。在类图使用带箭头的虚线表示，箭头从使用类指向被依赖的类。 关联(Association) : 对象之间一种引用关系

I have a question regarding UML. I have a class which simply contains an inner class with the private access modifier - cannot be accessed from anywhere else... Normally in order to present an inner class relation I can use a (+) relation like here ( InnerOddIterator ): (taken from http://www.uml-diagrams.org/nested-classifier.html ) I have not found anywhere any information about how can clearly emphasize that this class is private. Do you know if such a method exist at all? If yes I'll be grateful you give me some link here or something? Just to keep things clear, a sample code: public class

前言 关于UML类图的这篇文章，我觉得把它放在设计模式专栏的篇首最为合适，因为在学习设计模式的时候，经常会遇到有关UML类图，没有去专门学过的童鞋肯定会感觉很复杂。学到后面，发现不掌握UML类图，对设计模式或者某一个框架没有整体的把控。所以学好UML类图，你将会更加有自信！ 如果你对类之间的依赖、聚合、关联、组合等关系还很抵制的话，那么这篇文章就很有必要看了，随着对设计模式的慢慢深入了解，或许你也会发现，UML类图就显得格外重要了，是的，UML类图主要是用来描述类之间的轮廓图，而类之间的常见关系就是泛化（Generalization）、实现（Realization）、依赖（Dependence）、关联（Association）、聚合（Aggregation）、组合（Composition）等。类之间关系的强弱：依赖 < 关联 < 聚合 < 组合 < 泛化（继承） @[toc] 1、啥是UML类图？ 首先来看一个专业一点的定义【来自维基百科】 UML即 统一建模语言 （Unified Modeling Language）,它是一种开放的方法，用于说明、可视化、构建和编写一个正在开发的、面向对象的、软件密集系统的制品的开放方法。UML展现了一系列最佳工程实践，这些最佳实践在对大规模，复杂系统进行建模方面，特别是在软件架构层次已经被验证有效。 不得不说，越专业的描述越让人看得越发懵逼..

Can UML state machine diagram be used to show the screen navigation? Sure you can create a UML model of the UI as a state machine, for example: Screens are states State transitions i.e. screen changes occur on specific inputs or other triggers Did you actually have some more specific question? You can use state machines but it is also possible to use sequence diagrams for that. If you don't need to stick to the pure UML, there are plenty of approaches devoted to the specification of web systems that include the concept of web navigation models (with elements as pages, links,...). These