IBM Rational DOORS - 我应该自己部署它，还是有更合适的东西？
我正在继承一个项目，到目前为止，该项目的所有工件都保存在 CVS 和 FogBugz 中。有大量 MS Office 格式的新旧文档需要协调。
我看过一些有关 IBM Rational DOORS 的演示，并认为它将解决所有这些不同文档和系统之间缺乏可追溯性的问题。我（可能不正确）的理解是，例如，我可以突出显示 Word 文档中的一个短语并将其标记为要求，然后在该短语和其他工件（例如错误跟踪系统中的任务）之间创建双向链接或更改日志和用户指南中的条目，以表明要求已得到满足。
不幸的是，如果我想使用 DOORS，我可能必须自己安装和维护它。我发现了一个名为 rmtoo 的需求管理开源产品，但看起来它需要我重写所有内容将文档记录成一堆特殊格式的文本文件——对我来说，这违背了整个目的。如果 DOOR 过于杀伤力，是否有任何低开销的 DOORS 替代方案？
I'm inheriting a project that has, until now, had all its artifacts maintained in CVS and FogBugz. There's a ton of old and new documentation in MS Office format that needs to be reconciled.
I've seen some presentations on IBM Rational DOORS and think it would solve the lack of traceability across all these different documents and systems. My (possibly incorrect) understanding is that I could, for example, highlight a phrase in a Word document and mark that as a requirement, then create bi-directional links between that phrase and other artifacts, such as tasks in a bug-tracking system or entries in the changelog and user guide, to show that the requirement has been satisfied.
Unfortunately, if I want to use DOORS, I would probably have to install and maintain it myself. I found an open-source product for requirements management called rmtoo, but it looks like it would require me to rewrite all the documents document into a bunch of specially-formatted text files--which, for me, defeats the whole purpose. If DOORs is overkill, are there any low-overhead alternatives to DOORS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
DOORS 具有双向链接，但它们仅是从“DOORS 模块”中的“DOORS 对象”到同一或另一个“DOORS 模块”中的另一个“DOORS 对象”。
DOORS 对象有点像电子表格文件中的一行，DOORS 模块有点像电子表格文件。
您必须将所有材料导入 DOORS 才能使用它 - DOORS 无法处理文档或通常无法与外界很好地沟通。将 Word 文档导入和导出到 DOORS 非常困难。
DOORS 确实过时且有限。
DOORS has bidirectional links, but they are only from "DOORS objects" in a "DOORS module" to another "DOORS object" in the same or another "DOORS module".
A DOORS object is a little like a row in a spreadsheet file, and a DOORS module is a little like a spreadsheet file.
You have to import all of your material into DOORS to work with it -- DOORS can't work with documents or generally communicate with the outside world very well. Importing and exporting Word documents into DOORS is incredibly breaky.
DOORS is really dated and limited.
2022 年更新：正如评论者正确指出的那样，由于工具生态系统的变化，答案已经过时了。
让我感到沮丧的事情之一是有许多昂贵的工具（主要的工具是 DOORS Next、Jama Connect、Codebeamer 和 Polarion）。
对于预算较低的开发人员，我经常推荐 R4J，这是一个 Jira 插件。我觉得安装和配置过程有点麻烦，但除此之外，它提供了基本的功能，尤其是可追溯性。截至撰写本文时，最多 10 人的费用为 100 美元/年。
原始答案
我是否正确理解您正在尝试跟踪 DOORS、Word、Tracker-entry 等中的元素？我认为您所看到的情况在开箱即用的 DOORS 中是不可能实现的。我认为您需要像 agosense 这样的工具，以及针对您所需工具的适配器的大量定制。如果您确实想知道，我会与 IBM 销售代表交谈。但是基于 DOORS 的解决方案将非常昂贵。
从您的描述中不清楚您对工具链有多少控制权。如果您拥有完全控制权并且正在寻找廉价的解决方案，您可能需要查看 Trac 之类的东西。它是免费的，并集成了错误跟踪和 Wiki（所以本质上，要实现此功能，您必须将文档从 Office 迁移到 Wiki，并将错误从 FogBugz 迁移到 Trac - 不确定您的用户是否会接受这一点，并且它会创建与 rmtoo 遇到的问题相同）。
最后，您可以考虑 Requisite Pro，这是一款更便宜的 IBM 产品比门。它的优点是您的需求可以直接在 Word 中管理。
希望这有帮助！
Update 2022: As a commenter rightly pointed out, the answer is dated due to changes in the tool ecosystem.
One of my frustrations is that there are many expensive tools (the main players are DOORS Next, Jama Connect, Codebeamer and Polarion).
For developers with a low budget, I often recommend R4J, which is a Jira Plugin. I find the installation and configuration process a little cumbersome, but other than that, it provides basic functions, especially traceability. As of this writing, it was $100/year for up to 10 people.
Original Answer
Do I understand correctly that you're trying to trace elements in DOORS, Word, Tracker-entry, etc.? I don't think what you saw is possible with DOORS out of the box. I think you need a tool like agosense for that, and tons of customization for adapters to the tools you need. If you really want to know, I'd talk to an IBM Sales Rep. But a DOORS-based solution will be really expensive.
It's unclear from your description how much control you have over the tool chain. If you have full control and are looking for a cheap solution, you may want to check out something like Trac. It's free and integrates bug tracking and Wiki (so essentially, for this to work you'd have to migrate your documentation from Office to the Wiki, and bugs from FogBugz to Trac - not sure whether your users will accept this, and it creates the same problem that rmtoo does).
Last, you could look into Requisite Pro, an IBM product that is cheaper than DOORS. It has the advantage that your requirements are managed directly in Word.
Hope this helps!
根据经验，有超过 20 个软件工具（通常是 ALM）支持“需求工程”的方法。
以下是一个简短的列表：
...以及 IBM DOORS NG“下一代”、SAP、MKS/PTC Integrity with RE Addon 等。
至于架构，我推荐 EA，狂想曲、NoMagic、视觉范式。
我们还有使用 Confluence 管理需求的项目。显然 Gitlab 正在计划 RE 功能。
DOORS 仍在积极使用，具体取决于您所在的行业。这是有充分理由的。
From experience, there are easily over 20 software tools (often ALM) that support the means of 'Requirements Engineering'.
Here is a short list:
...and further IBM DOORS NG "Next Gen", SAP, MKS/PTC Integrity with RE Addon, etc.
As for architecture, I'd recommend EA, Rhapsody, NoMagic, Visual Paradigm.
We have also projects that manage requirements with Confluence. Apparently Gitlab is planning a RE feature.
DOORS is still in actively in use depending on your industry. And there is good reason why.