MKS 完整性要求
我注意到这里关于 MKS Integrity 与其他源代码控制相比的帖子。有人使用 MKS Integrity 来管理需求吗？最近好吗？如果您有任何见解，我将不胜感激：
- 您安装它并使用它，
- 评估它，但决定使用其他东西
我注意到它宣传它可以做很多其他事情，并且可能与其他系统结合使用（JIRA，测试链接） ？）协调流程（错误跟踪、测试和覆盖）——集成的复杂程度如何？有人试图报告所有这些集成系统吗？
很多问题可能有很大的答案...我知道...但是对任何一点的任何评论都将受到堆栈溢出宇宙的赞赏:)
I noticed posts on here about MKS Integrity as compared to other source code control. Has anyone been using MKS Integrity to manage requirements? How is it going? I'd appreciate any insights about it if:
- you install it and use it
- evaluated it but decided to go with something else
I noticed that it advertises that it can do lots of other things and possibly tie in with other systems (JIRA, Test Link?) to coordinate processes (bug tracking, testing and coverage) - how sophisticated is the integration? Anybody trying to report across all these integrated systems?
lots of questions with possibly big answers ... i know ... but any comment on any point would be appreciated from the stack overflow universe :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们在工作中使用 MKS 进行版本控制、问题跟踪和需求管理。
一切都非常糟糕。如果可能的话避免。 MKS 需求管理非常缓慢、过于复杂且繁琐。
在使用 DOORS 和 MKS RM 工作了 7 年之后，我不得不说需求管理总体上被高估了。
这只是戴领带的人们的一种时尚表达方式。
到目前为止，我从 RM 工具中看到，没有什么是一个像样的 Wiki 引擎做不到的。
想想 Redmine：它有 Wiki、问题跟踪和版本控制集成。
这个问题还有另一个方面，即专有工具的价格过高。
我们投入了大量工作来满足 DOORS 的要求，然后高层管理人员突然决定不再使用 DOORS
因为它太贵了。多年的努力或多或少都白费了。而且MKS比DOORS贵很多。
与主流观点相反，对开源工具的支持非常好，并且它们通常在导入/导出以及与其他工具配合使用方面要好得多。并且不存在因节省成本而关闭整个工具的危险。
We use MKS at work for version control, issue tracking and requirement management.
It's all very bad. Avoid if possible. MKS Requirement Management is very slow, overcomplicated and cumbersome.
After having worked for 7 years with DOORS and MKS RM, I've to say that requirement management in general is overrated.
It's just a fashionable expression among people wearing ties.
What I've seen from RM tools so far, there is nothing a decent Wiki engine could not do.
Just think about Redmine: it has Wikis, issue tracking and version control integration.
There is another aspect of this issue, namely the exorbitant prices of proprietary tools.
We've invested a lot of work to cover our requirements in DOORS, then suddenly upper management decided DOORS is out
because it's too expensive. Years' work more or less lost. And MKS is much more expensive than DOORS.
Contrary to mainstream opinions, support for open source tools is very good, and they are much better at import/export and working with other tools in general. And there is no danger that the whole tool will be shut down due to cost savings.
也许对你来说已经太晚了，但我对 MKS-RM 的体验也很糟糕：一个昂贵的垃圾，仍然让我们头疼。与其他工具的“集成”主要是使用 SCC 接口，特别是在 Windows 7 64 位中，您可能会遇到一些问题，因为到目前为止 MKS 没有 64 位版本。
与一个像样的关系数据库甚至 Excel 相比，我真的没有看到太多的收获！
Maybe it is too late for you, but my experience with MKS-RM is also terrible: an expensive piece of crap that still make us headaches. The "integrations" to other tools is mostly using SCC interface and specially in Windows 7 64-bit you might face some issues with this, as so far MKS has no 64-bit version.
I really don't see much gain comparing lets say to a decent relational database or even excel!