We use Altova UModel (all our diagrams are in UML). I prefer it to Visio, but Visio is a reasonable alternative. You are talking about a couple of different types of diagrams, Activity Diagrams and Sequence Diagrams. Also useful are Data Flow Diagrams. Given a correct set of these documents, getting a new developer up to speed can be much easier. Of course, from time to time you will have to get them up to speed on UML first (although reading UML is much easier than writing proper UML).
From their page (emphasis added) ...
Visually design application models and generate Java, C#, or VB.NET code and project documentation. Or, reverse engineer existing programs into UML 2 diagrams then fine tune your designs and complete the round trip by regenerating code.
Personally I use Enterprise Architect for this type of modeling. It can automatically build certain relationships by analyzing both your static source code information as well as runtime behavior. However, I personally don't use it that way... I model the system first, then build the system based on that model (often with a good deal of code generation from the model.
发布评论
评论（2）
我们使用 Altova UModel（我们所有的图表均采用 UML 格式）。 与 Visio 相比，我更喜欢它，但 Visio 是一个合理的选择。 您正在谈论几种不同类型的图表，活动图和< a href="http://www.altova.com/umodel/sequence-diagrams.html" rel="nofollow noreferrer">序列图。 同样有用的还有数据流程图。 有了一组正确的这些文档，让新开发人员快速上手就会容易得多。 当然，有时您必须首先让他们加快 UML 的速度（尽管阅读 UML 比编写正确的 UML 容易得多）。
从他们的页面（添加了重点）...
We use Altova UModel (all our diagrams are in UML). I prefer it to Visio, but Visio is a reasonable alternative. You are talking about a couple of different types of diagrams, Activity Diagrams and Sequence Diagrams. Also useful are Data Flow Diagrams. Given a correct set of these documents, getting a new developer up to speed can be much easier. Of course, from time to time you will have to get them up to speed on UML first (although reading UML is much easier than writing proper UML).
From their page (emphasis added) ...
就我个人而言，我使用 Enterprise Architect 进行此类建模。 它可以通过分析静态源代码信息和运行时行为来自动构建某些关系。 但是，我个人不会那样使用它......我首先对系统进行建模，然后基于该模型构建系统（通常会从模型生成大量代码）。
Personally I use Enterprise Architect for this type of modeling. It can automatically build certain relationships by analyzing both your static source code information as well as runtime behavior. However, I personally don't use it that way... I model the system first, then build the system based on that model (often with a good deal of code generation from the model.