您使用哪些案例工具？
您使用哪些计算机辅助软件工程工具？为什么？ 它们以什么方式提高您的生产力或帮助您设计程序？ 或者，如果您不使用 CASE 工具，您这样做的原因是什么？
Which Computer-aided Software Engineering tools do you use and why? In what ways do they increase your productivity or help you design your programs? Or, in case you do not use CASE tools, what are your reasons for this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我必须使用的最好的 CASE 工具是 Enterprise Architect Sparx。
与 Rose 相比，它很轻（更容易购买，也更便宜），但功能非常强大。 您可以以良好且有组织的方式制作出色的 UML 图或数据库模型或任何您想要的东西。
它对细化过程的初始阶段有很大帮助，因为您可以创建域模型，执行一些初步用例，将它们映射到需求并以良好的方式向客户呈现所有内容。 它帮助我思考，并用它重构我的设计，直到我足够满意，可以开始正确的文档记录。
它对于数据库模型也非常有用，因为它可以非常巧妙地对大多数数据库进行逆向工程。
在我看来，它唯一的（但相当严重的）缺点是它的文档生成器，温和地说，是垃圾。 从中获得合适的文档几乎是不可能的，除非您在模板上投入了大量的工作，然后就可以了。
The best CASE tool I had to work with is the Enterprise Architect from Sparx.
It's lightweight comparing to Rose (easier to buy and cheaper too) but extremely powerful. You could do great UML diagrams or database model or anything else you want but in a nice and organised way.
It greatly helps on the initial stages of the elaboration process as you could create domain model, do some preliminary use cases, map them to the requirements and present all of it in a nice way to the customer. It helps me thinking and I re-factor my design with it until I am satisfied enough to start proper documentation.
It is also very good for database models as it could reverse-engineer most databases very neatly.
The only (but quite serious) drawback it has in my eyes is that its documentation generator is, to put it mildly, crap. Getting a proper document from it is almost impossible unless you invest a significant amount of work in the templates and then it would be only OK.
我过去使用过 Rational Rose 和其他一些类似的软件包。 大多数情况下，我将它们用于 UML 图元素，并且没有深入讨论更详细的功能，例如代码生成等。
我主要使用它们来帮助设计过程并阐明我自己的想法。 我经常发现，在尝试设计一个组件时，我最终需要写下/画出我想要发生的事情，这样我就可以在脑海中清楚地了解需要发生什么以及为什么发生。 我发现在很多情况下，我最终尝试绘制的内容本质上与 UML 中预定义类型的图相同，例如用例图等，然后采用该样式，就变得更容易获得我的想法写在纸上，因为我有一些可以在其中工作的框架。
因此，我主要将 CASE 工具用于较高的半抽象级别的 UML/设计工具。
I have used Rational Rose and a few other similar packages in the past. Mostly I have used them for the UML diagram elements and have not gone into the more detailed functionality such as code generation etc.
I mostly use them for aiding the design process and clarifying my own ideas. Often I find that, in trying to come up with a design for a componant, I end up needing to write down / draw what I want to happen so I can get a clear overview in my mind of what needs to happen and why. I have found that in a lot of cases, what I end up trying to draw is essentially the same as a predefined kind of diagram in UML, such as a Use Case Diagram etc. and by then adopting that style, it becomes easier to get my ideas on paper as I have some framework to work within.
So, I use CASE tools principally for thier UML / designing tools at a highish, semi-abstract level.
甲骨文设计师
Oracle Designer
没有使用任何。 没有钱给他们。
Not using any. No money for them.