您认为 CASE Tools 中的哪些功能最有用？
大家好， 这实际上并不是一个与编程相关的问题，但绝对与程序员相关。 如果正在开发新的案例工具。您希望在其中看到哪些功能来描述从规范到设计的系统行为。
HI All,
It is not really a programming related question but definitely programmers'related.
If a new Case tool was being developed. What features would you like to see in it which describe behaviour of system in from specification to design.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
CASE 的基本问题是，当您进行分析/设计/编码/部署（或您选择的任何步骤）的迭代时，需要处理的细节和映射呈指数级增长。
软件系统的各种视图之间的维护和合理化。就是这个爆炸
这击败了我遇到过的所有 Case 工具。他们似乎都进展顺利
但是当面临返工一些中级工件时，变化的影响是非常大的
很难在不破坏其他东西的情况下传播，这反过来会破坏其他东西，最终
导致级联变得难以管理。级联影响只是爆炸的逻辑结果
当一个人从较高的抽象层次转移到较低的细节层次时，就会产生一种关系。
最终，在案例工具中管理变更控制/影响所花费的时间/资源超出了其收益
我们都会回到简单的非案例图表/书写工具。
所以我的建议是忘记尝试构建一个紧密集成的 CASE 系统。提供基本的图表和
对 UML 的符号支持。除此之外，还提供宏功能，以便用户可以自定义行为和
与用于管理软件开发的其他工具集成。
最后，将 Case 工具管理的所有“工件”保留在 XML 中，这确实为用户添加添加内容打开了大门
他们自己的定制处理器和 xsl 到产品。
最终真正的价值可能不是你的CASE工具实际做了多少，而是你提供的框架
供用户构建自己的解决方案。
The basic problem with CASE is that as you proceed through iterations of analysis/design/coding/deployment (or whatever steps you choose) there is an exponential explosion of detail and mapping that needs to be
maintained and rationalized among various views of the software system. It is this explosion
that defeats every Case tool I have ever come across. They all seem to work well enough moving forward
but when faced with reworking some middle level artifact the impacts of the change are very
difficult to propagate without breaking something else, which in turn breaks something else and eventually
leads to a cascade that becomes unmanageable. The impact cascade is just a logical consequence of exploding
relationships as one moves from higher levels of abstraction to lower levels of detail.
Eventually the time/resources spent managing change control/impact within the Case tool exceeds its benefit
and we all go back to simple non-Case diagramming/writing tools.
So my advice is to forget trying to build a tightly integrated CASE system. Provide basic diagramming and
notational support for UML. Beyond that provide macro capabilities so users can customize behaviour and
integrate with other tools used to manage software development.
Finally, keep all the "artifacts" managed by the Case tool in XML, this really opens the door for users to add
their own custom processors and xsl to the product.
In the end the true value may not be how much your CASE tool actually does, but the framework that you provide
for users to build their own solution.