使用 CASE 工具进行开发可提高生产力
我在我正在开发的系统中使用了一个名为 MAGIC 的 CASE，我从未使用过这种类型我一开始就喜欢这个工具，一个月后我生成了很多应用程序，我感觉非常高效并且......我会说......满意。
在某种程度上，我感到不舒服，因为没有代码和我习惯的一切，但另一方面我可以加快我的开发速度。 事实是，最终我又重新使用 C#，因为我发现它开发起来更灵活，我可以进行单元测试，使用 CVS，我可以访问更多资源，基本上我拥有“所有控制权”。 我觉得这个工具没有给我信心，我认为在项目后期我无法管理它，因为它强制建立了开发规则。 而且很多事情，比如发送电子邮件，使用我自己的控件，以及其他事情都有其复杂性，似乎在某些时候它不会像我最初想象的和产品最初声称的那么容易。 这让我想起了一篇非常好的文章，名为“No Silver Bullet”。
这个CASE有它的优点，但另一方面它没有可以参考的资源，而且实际上许可证和认证非常昂贵。 对我来说，另一件令人失望的事情是，由于其过于简单的开发方法，我感到害怕，第一原因是我对此类工具缺乏经验，第二原因是我认为如果我继续使用它，它可能会变成一个复杂的怪物我在项目后期无法管理。
我认为使用这些解决方案来加快速度是件好事，但我想知道，如果这些程序声称比我所使用的工具更能提高生产力，为什么它们不像 VS.Net、J2EE、Ruby、Python 等那样流行呢？有指出吗？
I was using a CASE called MAGIC for a system I'm developing, I've never used this kind of tool before and at first sight I liked, a month later I had a lot of the application generated, I felt very productive and ... I would say ... satisfied.
In some way a felt uncomfortable, cause, there is no code and everything I was used to, but in the other hand I could speed up my developing. The fact is that eventually I returned to use C# because I find it more flexible to develop, I can make unit testing, use CVS, I have access to more resources and basically I had "all the control". I felt that this tool didn't give me confidence and I thought that later in the project I could not manage it due to its forced established rules of development. And also a lot of things like sending emails, using my own controls, and other things had their complication, it seemed that at some point it was not going to be as easy as initially I thought and as initially the product claims. This reminds me a very nice article called "No Silver Bullet".
This CASE had its advantages but on the other hand it doesn't have resources you can consult and actually the license and certification are very expensive. For me another dissapointing thing is that because of its simplistic approach for development I felt scared on first hand cause of my unexperience on these kind of tools and second cause I thought that if I continued using it maybe it would have turned to be a complex monster that I could not manage later in the project.
I think it's good to use these kind of solutions to speed up things but I wonder, why aren't these programs as popular as VS.Net, J2EE, Ruby, Python, etc. if they claim to enhance productivity better than the tools I've pointed?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我们在当前的公司使用 CASE 工具来生成代码，并且我们正在尝试摆脱它。
在我看来，它带来的好处——代码的图形表示使新开发人员“更容易”掌握组件——被它的缺点所抵消。
这些主要缺点是：
我们无法进行自动合并，这使得在一个组件上并行开发几乎不可能。
开发人员依赖该工具并“忘记”如何手动编码。
We use a CASE tool at my current company for code generation and we are trying to move away from it.
The benefits that it brings - a graphical representation of the code making components 'easier' to pick up for new developers - are outweighed by the disadvantges in my opinion.
Those main disadvantages are:
We cannot do automatic merges, making it close to impossible for parallel development on one component.
Developers get dependant on the tool and 'forget' how to handcode.
只是有几个问题要问您：
与您使用的控件相比，您获得了多少生产力？
您创建的代码的可测试性和可靠性如何？
您能将新模式应用到您的设计中吗？
我无法想象有一个案例可以让我先编写一个测试，然后使用一个案例来生成我需要的代码。 我宁愿坚持使用 resharper，它可以轻松完成我的日常任务并保留对我的代码的完全控制。
Just a couple questions for you:
How much productivity do you gain compared to the control that you use?
How testable and reliant is the code you create?
How well can you implement a new pattern into your design?
I can't imagine that there is a CASE out there that I could write a test first and then use a CASE to generate the code I need. I'd rather stick to resharper which can easily do my mundane tasks and retain full control of my code.
我参与的项目最初使用 Oracle 开发套件来构建一个 Web 应用程序。
随着时间的推移（5 年以上），客户的要求变得比最初预期的更加复杂，而且屏幕也不容易维护。 因此，团队非正式地决定开始在 Web PL/SQL 中进行自定义（手动编码）屏幕，而不是使用 Oracle 开发套件 CASE 工具 (Oracle Designer) 生成它们。
该团队仍在使用开发套件的 Oracle Report Builder 组件，因为它似乎及时“完成了工作”。 一般来说，使用报表生成器工具的开发人员不太擅长编码。
在这种情况下，此类 CASE 工具的生产力方面似乎在很大程度上取决于客户需求和开发人员技能集/培训/背景。
The project I'm on originally went w/ the Oracle Development Suite to put together a web application.
Over time (5+ years), customer requirements became more complex than originally anticipated, and the screens were not easily maintainable. So, the team informally decided to start doing custom (hand coded) screens in web PL/SQL, instead of generating them using the Oracle Development Suite CASE tools (Oracle Designer).
The Oracle Report Builder component of the Development Suite is still being used by the team, as it seems to "get the job done" in a timely fashion. In general, the developers using the Report Builder tool are not very comfortable coding.
In this case, it seems that the productivity aspect of such CASE tools is heavily dependent on customer requirements and developer skill sets/training/background.
不幸的是，Magic 工具不会生成代码，也无法实现设计模式。 我无法控制代码，因为正如我之前所说，它没有要修改的代码。 最重要的是，它可以以某种方式提高生产力，但它无法使用 CVS、模式，而且我无法控制所有细节。
我同意加里的说法，“似乎此类 CASE 工具的生产力方面在很大程度上取决于客户需求和开发人员技能集/培训/背景”，但我也非常同意 Klelky 的观点；
这些主要缺点是：
1.我们无法进行自动合并，这使得在一个组件上并行开发几乎不可能。
2.开发人员依赖该工具并“忘记”如何手动编码。
谢谢
Unfortunaly the Magic tool doesn't generates code and also it can't implement a design pattern. I don't have control over the code cause as i stated before it doesn't have code to modify. Te bottom line is that it can speed up productivity in some way but it has the impossibility to user CVS, patterns also and I can't control all the details.
I agree with gary when he says "it seems that the productivity aspect of such CASE tools is heavily dependent on customer requirements and developer skill sets/training/background" but also I can't agree more with Klelky;
Those main disadvantages are:
1. We cannot do automatic merges, making it close to impossible for parallel development on one component.
2.Developers get dependant on the tool and 'forget' how to handcode.
Thanks