UML时间可视化
我相信你们中的许多人都使用过或至少听说过 Gource 和 Code Swarm。它们是非常好的工具，可以可视化项目发展过程中的提交历史记录。
我感兴趣的是 UML 形式的代码本身随着时间的推移而演变的类似 repo 驱动的动画。
在过去的三年里，我投入了大量的工作来重构和清理项目的代码库，如果能够以有形的形式向管理层演示这一点，那就太好了。当然，“之前”和“之后”的图表也可以，但是这有什么乐趣呢？ :P
有这样的工具吗？具体来说，我正在寻找 ObjC++，但对任何语言中可用的任何内容都感兴趣。
大声说出任何其他可以制作很酷的演示的工具。如果没有任何东西可以展示，重构有时很难推销！
I'm sure many of you have used or at least heard of Gource and Code Swarm. They are very nice tools for visualising the commit history of a project as it evolves.
What I am interested in is an similarly repo-driven animation of the code itself in UML form as it evolves over time.
I have put a great deal of work into refactoring and cleaning up the codebase of a project over the last 3 years and it would be really neat to be able to demo this in tangible form to management. Of course 'before' and 'after' diagrams would work, but where's the fun in that? :P
Does any such tool exist? Specifically I am looking for ObjC++ but am interested in anything available in any language.
Shout out any other tools that could make for a cool demo. Refactoring is sometimes hard to sell without having anything to show!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
让你的首席执行官相信这类技术的重要性总是非常棘手的。如果您能够展示 UML 历史动画，我认为任何非工程师都不会欣赏它。
我的方法是“展示结果”。如果您有错误/更改跟踪工具并且正在以正确的方式进行重构，那么花在错误或更改上的时间应该会以某种方式减少。
制作一些电子表格，绘制一些图表并将其全部放入演示文稿中。不幸的是，CEO 脑子里传达的正是这样的信息。
就像 Martin Folwer 在他的书中所说的 重构，有时更好在得到结果之前不要告诉。那么结果就是你应该展示的！ （请参阅“我该告诉我的经理什么？”一章）
Convincing your CEO about the importance of that kind of tech stuff it's always very tricky. In case you are able to show a UML history animation, I don't think it will be appreciated by any non-engineer person.
My approach is "show results". If you have a bug/changes tracking tool and you are doing refactor in a correct way, time spent on bugs or changes should drop in some way.
Do some spreadsheets, paint some charts and put it all in a presentation. Unfortunatelly, that's the kind of message that reaches CEO's minds.
Like Martin Folwer says in his book Refactoring, sometimes is better to don't tell until you have results. Then results is what you should show! (see "What Do I Tell My Manager?" chapter)
我怀疑你能找到的最好的方法是在大学开发一个研究原型。我正在考虑类似 REFVIS 的东西。即使如此，要使其与您的代码兼容仍需要做大量工作。除此之外，自动提取的 UML 图往往会包含太多供人类使用的细节，因此减少这些细节以使其对管理层具有可呈现性和信息性将是一个难题。我认为您提出了一项有趣的研究挑战，但您无法找到现成的解决方案！
I suspect the best you would find to do this is a research prototype developed in a university. I'm thinking of something like REFVIS. Even then it would be a lot of work to make it work with your code. That aside, automatically extracted UML diagrams tend to carry way too much detail for human consumption, so reducing this to make it presentable and informative to management would be a hard problem. I think you're posing an interesting research challenge, but not one to which you'll find a ready solution!