The other day, I discovered a tool from the University of Victoria called Diver: Dynamic Interactive Views For Reverse Engineering. You can either find a method and create a static sequence diagram starting with that method or you can run an application in a trace mode to capture the sequence diagram for a particular execution of an application.
I'm the initiator of the ModelGoon project, and I'm currently working on building sequence diagrams from a method. And I plan a release in few weeks. Therefore, I don't really know what are the features expected by users. I mean it is possible to build a very detailed sequence diagram from a method body, but is it really useful? I usually use sequence diagrams "to think something through, either to verify the logic in a use case or to design a method or service" as advised in Agile Modeling.
Can you tell me more about your use of the generated sequence diagram? as you said it would be better if it is modifiable, what kind of modifications do you expect, and what about code synchronization? What is the level of detail you're expecting from it?
TPTP seems to be the only real option so far. That crystallized over the last few days after trying a number of different solutions. After installing TPTP from the regular Eclipse update site, follow these steps :
select Profile As from the context menu of a runnable element (eg. a method, a test, a testcase..)
select Profile Configurations
select the Profile Setting tab
select Exection Time Analysis as the data collector
in the Profiling and Logging view, select Open with from the context menu of the profiling data (the clock with glasses) and pick UML2 Class Interactions
After that you will have to hide many many lifelines per right-click to make the diagram remotely readable while getting annoyed by TPTPs choice of color (light blue on white - also very unreadable).
You can then print the diagram, effectively exporting it to pdf, tiff, eps and other formats via your favorite file printer.
There is one big bitter pill to swallow though : what you get is an execution trace in disguise of a sequence diagram. This means - no loops, no conditions, no notes and such. Even the diagram title sucks, being a cryptic 50-odd character monstrosity you cant change.
On the other hand, TPTP offers you much more that a sequence diagram. For example, you get a color-coded execution hot spot analysis on the side of the diagram as a bonus.
But it seems that even the expensive tools boasting round-trip code engineering like Enterprise Architect offer nothing more than tracing (and admittedly much nicer graphics). Reverse engineering a real sequence diagram seems to be quite non-trivial.
ObjectAid has a sequence diagram now. It's not free, but not expensive either. It does reverse engineering from source code, stack traces and call stacks in the debugger.
发布评论
评论（4）
有一天，我发现了维多利亚大学的一个工具，名为Diver：逆向工程的动态交互视图。您可以找到一个方法并从该方法开始创建静态序列图，也可以在跟踪模式下运行应用程序以捕获应用程序特定执行的序列图。
The other day, I discovered a tool from the University of Victoria called Diver: Dynamic Interactive Views For Reverse Engineering. You can either find a method and create a static sequence diagram starting with that method or you can run an application in a trace mode to capture the sequence diagram for a particular execution of an application.
我是 ModelGoon 项目的发起人，目前正在致力于通过方法构建序列图。我计划在几周内发布。因此，我真的不知道用户期望的功能是什么。我的意思是可以从方法体构建非常详细的序列图，但它真的有用吗？我通常使用序列图“来思考一些事情，要么验证用例中的逻辑，要么设计方法或服务”，如 敏捷建模。
您能告诉我更多关于您对生成的序列图的使用吗？正如你所说，如果是可修改的就更好了，你期望什么样的修改，代码同步呢？您期望它的详细程度如何？
您是否尝试过 Netbeans UML 建模模块？
欢迎通过我的网站与我联系。
I'm the initiator of the ModelGoon project, and I'm currently working on building sequence diagrams from a method. And I plan a release in few weeks. Therefore, I don't really know what are the features expected by users. I mean it is possible to build a very detailed sequence diagram from a method body, but is it really useful? I usually use sequence diagrams "to think something through, either to verify the logic in a use case or to design a method or service" as advised in Agile Modeling.
Can you tell me more about your use of the generated sequence diagram? as you said it would be better if it is modifiable, what kind of modifications do you expect, and what about code synchronization? What is the level of detail you're expecting from it?
Have you tried the Netbeans UML Modeling module?
Fell free to contact me from my website.
TPTP 似乎是迄今为止唯一真正的选择。在尝试了多种不同的解决方案后，在过去的几天里，这一点变得更加明确。从常规 Eclipse 更新站点安装 TPTP 后，请执行以下步骤：
此后，您将不得不在每次右键单击时隐藏许多生命线，以使图表远程可读，同时对 TPTP 的颜色选择感到恼火（白色上的浅蓝色 - 也非常难以阅读）。
然后您可以打印图表，通过您最喜欢的文件打印机将其有效导出为 pdf、tiff、eps 和其他格式。
不过，有一个很大的苦药丸需要吞下：您得到的是伪装成序列图的执行跟踪。这意味着——没有循环、没有条件、没有注释等等。就连图表标题也很糟糕，是一个你无法改变的 50 多个字符的神秘怪物。
另一方面，TPTP 为您提供的不仅仅是序列图。例如，作为奖励，您可以在图表一侧获得颜色编码的执行热点分析。
但似乎即使是像 Enterprise Architect 这样拥有往返代码工程的昂贵工具也只能提供跟踪（并且不可否认的是更好的图形）。对真实序列图进行逆向工程似乎非常重要。
TPTP seems to be the only real option so far. That crystallized over the last few days after trying a number of different solutions. After installing TPTP from the regular Eclipse update site, follow these steps :
After that you will have to hide many many lifelines per right-click to make the diagram remotely readable while getting annoyed by TPTPs choice of color (light blue on white - also very unreadable).
You can then print the diagram, effectively exporting it to pdf, tiff, eps and other formats via your favorite file printer.
There is one big bitter pill to swallow though : what you get is an execution trace in disguise of a sequence diagram. This means - no loops, no conditions, no notes and such. Even the diagram title sucks, being a cryptic 50-odd character monstrosity you cant change.
On the other hand, TPTP offers you much more that a sequence diagram. For example, you get a color-coded execution hot spot analysis on the side of the diagram as a bonus.
But it seems that even the expensive tools boasting round-trip code engineering like Enterprise Architect offer nothing more than tracing (and admittedly much nicer graphics). Reverse engineering a real sequence diagram seems to be quite non-trivial.
ObjectAid 现在有一个序列图。它不是免费的，但也不贵。它在调试器中从源代码、堆栈跟踪和调用堆栈进行逆向工程。
ObjectAid has a sequence diagram now. It's not free, but not expensive either. It does reverse engineering from source code, stack traces and call stacks in the debugger.