支持 CMMI 目标的需求开发工具的建议
我们目前正在改进我们的开发流程，以努力达到 CMMI 合规性（我们将从 2 级开始，然后从该级别升级）。 我们正在尝试找到一种廉价（或免费）的工具，使我们能够本着 CMMI 的精神开发需求。 换句话说，我们需要能够输入需求、跟踪需求变更、在需求变更时向个人提供警报、执行可追溯性等。我们的项目通常很小（通常有 3 - 7 名开发人员和一两名测试人员）。
我们已经研究了许多商业工具，但它们的成本超出了我们的承受能力。 我们在 SourceForge（OSRM 和其他）上查看了一些，但找不到任何足够成熟且具有我们需要的功能的东西。
我们正在寻找满足上述要求的工具的建议。
We are currently evolving our development processes in an effort to become CMMI compliant (we will start with level 2, and move up from there). We are trying to locate a tool that is inexpensive (or free) that will allow us to develop requirements in the spirit of CMMI. In other words, we need to be able to enter our requirements, track changes to them, provide alerts to individuals when requirements change, perform traceability, etc. Our projects are typically small (typically 3 - 7 developers and a tester or two).
We have looked at many of the commercial tools, but they cost more than we are able to afford. We looked at a few on SourceForge (OSRM and others) but could not find anything that was sufficiently mature that also had the features that we needed.
We are looking for suggestions for a tool that meets the above requirements.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
INCOSE 是解答此类问题的绝佳资源。 他们维护一个工具数据库，对 COTS 和 GOTS 系统工程工具进行索引。 一些执行需求管理的工具还具有高级系统工程功能（例如 CORE），而其他工具的关注范围更窄（即 RequistePro）。
这些工具中的大多数都需要花钱，但可能提供一些有限的免费功能。 例如，Workspace.com 提供了一些免费功能。 我建议不要推出自己的解决方案，或采用并非专门用于需求管理的工具，因为实现它的隐性成本以及预期任务的低效率可能会变得繁重。
如果您绝对无力在需求工具上花任何钱，那么最好使用商业工具的免费功能。 但不要这样做...花点钱购买 RequisitePro，知道您正在获得适合工作的正确工具，您就可以睡得更好了。
INCOSE is an excellent resource for this sort of question. They maintain a Tools Database that indexes COTS and GOTS System Engineering tools. Some of the tools that perform requirements management also have high-level System Eng functionality (CORE, for example) whereas others are more narrowly-focused (i.e. RequistePro).
Most of these tools will cost money, but may provide some limited free functionality. Workspace.com, for example, provides some free functionality. I would recommend against rolling your own solution, or adapting a tool that is not specifically intended for requirements management, because the hidden cost of getting it going, as well as inefficiency at the intended task could become burdensome.
If you absolutely can't afford to spend any money on a requirements tool, it would be better to use the free functionality from a commercial tool. But don't do that... pony up the cash for RequisitePro and sleep better knowing that you're getting the right tool for the job.
从 Wiki 开始怎么样？ 我们使用 TWiki，但还有许多其他可用的。 当任何页面更改时，我们使用的 wiki
您可以创建需求层次结构这似乎涵盖了您的大部分项目。 像 TWiki 这样的 Wiki 有插件也可能对您有帮助。
如果您的项目只有 3-7 名开发人员，那么使用其中一种大型商业工具可能会过于复杂，无法满足您的需求。
How about starting of with a Wiki? We use TWiki but there are many others available. The wiki we uses
This seems to cover most of your items. Wikis like TWiki have plugins which may also help you.
If you only have 3-7 developers on a project using one of the big commercial tools may be far too complex for what you need.
我们公司非常重视 CMMI，但我们所有的工具都是内部开发的。
我所能建议的就是开发您自己的工具。 您至少将拥有一个优势，即它将反映您的业务流程。
一般来说，对于新工具，我们首先从在项目上开发的工具开始，如果成功的话，然后与公司的其他部门共享。 不要害怕使用 Excel 来跟踪您的需求以及统计数据，它与良好的变更控制系统（例如 subversion）一起为您提供了很多可跟踪性。
We're heavily into CMMI at our company, but all of our tools are developed in-house.
All I can recommend is to develop your own tools. You will at least have the advantage that it will reflect your business process.
In general, for a new tool, we start off with a tool developed on a project, which is then shared with the rest of the company, if it has been successful. Don't be afraid to use Excel to trace your requirements along with a statuts, which along with a good change control system, such as subversion, gives you a lot of traceability.
我曾经工作过的公司的一个团队正在致力于自定义 Visual Studio Team System 工作项模板来处理需求跟踪。 您也应该考虑的一个目标是实现从需求到开发人员工作项再到缺陷的可追溯性。 这使得能够对哪些需求与最多的缺陷相关进行一些强有力的分析。
A team in the company I used to work for was working on customizing Visual Studio Team System work item templates to handle requirements tracking. One goal, which you should consider as well, was to enable traceability from requirements through to developer work items and then defects. This enables some powerful analysis of which requirements are tied to the most defects.